[Bug 923387] New: Wireless doesn't stay connected in hotels
http://bugzilla.opensuse.org/show_bug.cgi?id=923387 Bug ID: 923387 Summary: Wireless doesn't stay connected in hotels Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: munguanaweza@netzero.net QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0 Build Identifier: The wireless system doesn't stay connected in various hotels around the world. In some hotels, there is no problem and the wireless will stay connected. In most hotels, the opensuse wireless will be cut off from the hotel wireless network withing about 10 minutes. The only way to get it to reconnect is to restart the operating system for about another 10 minutes of connection. While the opensuse wireless is connected, the wireless transfer rate of bytes/sec gets slower and slower. To contrast this with windows, it will remain connected without problem indefinitely. Windows also will not slow down its bytes/sec transfer rate over time, and the general transfer rate is higher in windows than in opensuse. I have had this issue on two different laptops, using opensuse 12.1 through 13.2. I compare these opensuse versions to both windows 7 and 8 on these two laptops. I am writing this from the hotel Pullman Bercy in Paris, France, where I am having this issue. But please don't think that this is just an isolated incident, I have this issue in hotels all over the world. I travel for a living and find this problem in hotels all over the world for several years running. I have tried to resolve this various times on the opensuse mailing list, and also have tried to work with various hotel tech support services to find a clue to resolve this, without success. Many of the hotels that I stay in while travelling used to have wired connections and I was able to bypass the wireless problem, but they have been gradually eliminated in favor of wireless systems and this problem has become a major issue and a great annoyance. I would very much appreciate if you could fix this problem! Reproducible: Always Steps to Reproduce: 1.Start up the computer 2.Connect to the hotel network 3. Soon the wireless connection will reduce to no transfer of data. Actual Results: I couldn't continue using opensuse to connect to the internet, and I have to switch to windows. Expected Results: I should have been able to stay connected to the internet via opensuse wifi without issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=923387 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann@suse.com, | |dleuenberger@novell.com, | |wicked-maintainers@suse.de --- Comment #1 from Bernhard Wiedemann <bwiedemann@suse.com> --- is this with NetworkManager or wicked? could be related to bug 923225 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=923387 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Network |Kernel -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=923387 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Larry.Finger@lwfinger.net -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=923387 --- Comment #7 from Larry Finger <Larry.Finger@lwfinger.net> --- As this happens with both Realtek and Intel devices, it is some problem with the common networking components, not with the wireless drivers. Without more detailed info regarding which AP is being used in the hotel, and their level of firmware, there is little that can be done. Unfortunately, you cannot determine that level of information from the connection. You would need to get that from the hotel's IT personnel, and the level of expertise to get that info may not be on site. The standard kernel in 13.2 is 3.16, which is more than 4 versions old. I would try a 4.0.0 kernel from http://download.opensuse.org/repositories/Kernel:/HEAD/standard/. Choose the architecture (32- or 64-bit) and get the "desktop" flavor. BTW, a lot of European sites use FritzBox access points. They are notorious for not adhering to the 802.11 protocols. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=923387 --- Comment #8 from Mark Misulich <munguanaweza@embarqmail.com> --- I would like to get this networking problem resolved, as it is a great annoyance for me and a detriment for the utility of this distribution. I already have the contact info for the head of IT for one hotel chain that I frequent, and can obtain information that you require from him. From other hotels, I can get it with some persistence. Maybe not today or tomorrow, but with some time as I work through their bureaucracy. Please be succinct and tell me specifically what you need. Mark -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=923387 --- Comment #9 from Larry Finger <Larry.Finger@lwfinger.net> --- I doubt that this is only an openSUSE problem. The distro-specific code is important in making the connection; however, maintaining the connection is the kernel's responsibility. NM, wicked, and other such code is out of the loop at that point. The specific information needed is the make and model of the AP, and the firmware version being run. It would also be useful to know if the networks at the problem hotels are busier than the ones that work. That would likely be difficult for you to determine. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com