Re: quick advice on wireless routers

From: JM (no_at_spam.com)
Date: 07/13/03


Date: Sun, 13 Jul 2003 02:50:35 GMT

trey wrote:

> Hello good people of alt.os.linux.suse...so I moved to a new place, got a
> cable modem and went out and bought a wireless router. I got the LinkSys
> BEFW11S4 802.11b.

I have this router and it works great. But I didn't change my firmware. I
am using version 1.39.2, Oct 09 2001. As I understand it AT&T had a chat
with linksys about their routers doing NAT and consealing users having more
then one computer. This might be true or not but the newer routers say AT&T
approved,or at lest they did the last time I looked. The difference is in
the firmware. Why don't you try changing the firmware to 1.39.2 and see if
your problem goes away.

JM



Relevant Pages

  • RE: Serious flaw in Linksys wireless AP password security
    ... encryption was enabled on my router, but not on my nic, there was no ... Serious flaw in Linksys wireless AP password security ... > It appears that firmware version 4.50.6 for the Linksys WRT54GS ...
    (Bugtraq)
  • Re: Networking adding of DI-524
    ... I am writing this letter to ALL Wireless Router manufacturers. ... screen shots from Linksys' own self help technical support site. ... and that is where my Network must be at Fault. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Linksys WRT54G and 54GS versions 5 and versions 6
    ... He's using old firmware. ... linksys switched to a different operating system -- VxWorks. ... The V5 and V6 router are also somewhat different hardware. ... my neighbor is running a WRT54G v5 using the Linksys ...
    (alt.internet.wireless)
  • Re: wireless router choice
    ... I have a Linksys Wireless Router Model:BEFW11S4. ... What has happend to "The Customer Is ...
    (microsoft.public.windowsxp.hardware)
  • Re: Networking adding of DI-524
    ... wireless on Internet was to put one Computer through Wireless Router WAN. ... >> used as a switch in that I did not plug my connection from the Linksys to the ... >> but in a port. ...
    (microsoft.public.windowsxp.network_web)