I’m attempting to solve an issue that seems to be a Opensuse 12.1 issue but have difficulty trouble shooting it; my wireless router (Thompson TG585 v8) reboots about a min after the wireless connection is established with my Opensuse 12.1 KDE laptop x64. The router doesn’t have difficulty working with other wireless devices like MS Windows, Android and other wireless bits. This router worked fine with previous Opensuse releases. Laptop hadware is an HP DV7-1020ea with intel PRO/Wireless 5100 AGN. Repositories used are OSS, NonOSS, Update and Packman.
On 02/25/2012 03:36 PM, allianux wrote:
>
> I’m attempting to solve an issue that seems to be a Opensuse 12.1 issue
> but have difficulty trouble shooting it; my wireless router (Thompson
> TG585 v8) reboots about a min after the wireless connection is
> established with my Opensuse 12.1 KDE laptop x64. The router doesn’t
> have difficulty working with other wireless devices like MS Windows,
> Android and other wireless bits. This router worked fine with previous
> Opensuse releases. Laptop hadware is an HP DV7-1020ea with intel
> PRO/Wireless 5100 AGN. Repositories used are OSS, NonOSS, Update and
> Packman.
This is most certainly not an openSUSE problem. It might be a kernel problem,
but if the router crashes from some string of input data, then the bug is in the
router firmware. As the kernel is constantly being updated to conform to the
latest standards, I would guess that kernel 3.1 implements some function
differently that does 2.6.37 as found in openSUSE 11.4. In any case, if a bad
packet is transmitted, the router should reject it, and not crash.
Do you have the latest version of the router firmware?
The only way to debug this will be to use wireshark to capture the transmitted
data that crashes the router. You can then supply that data to either Thompson
or Intel.
On 2012-02-26 00:45, Larry Finger wrote:
> In any case, if a bad packet is transmitted, the router should reject it,
> and not crash.
There is not only transmitted packages that pass through, but also there is
a negotiation to establish and maintain the connection. A crash should not
happen, but during dialogs between software programs one of the two can
create a situation that the other does not expect, error, and perhaps
crash. It happens all the time on lots of software.
It is unfortunate that one of the pieces is in a hardware that seldom get
updates, like a router.
Yes, tracking the connection with wireshark might help to locate the
problem. Perhaps.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Just to close out this thread:
The problem is with the Thompson router; a know bug that is not going to be fixed. The solution is to disable to N and only use A/G. Not such a loss as its N is only 65MB/s as opposed to 150MB/s and better of a typical N wireless router.
If your ISP offers you this router; ask for another model.