Date: Sat, 5 Jul 2003 13:43:39 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: Lukas Ertl <l.ertl@univie.ac.at> Cc: freebsd-current@freebsd.org Subject: Re: Experiences with ath(4) Message-ID: <Pine.NEB.3.96L.1030705134145.43745D-100000@fledge.watson.org> In-Reply-To: <20030705192426.U3328@korben.in.tern>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 5 Jul 2003, Lukas Ertl wrote: > > The ADSL router (a Speedtouch 510) does NAT. Everything seems to work > > fine, but after some time, all connections from the WLAN client to the > > outside world have died. I can connect to the other hosts in the LAN just > > fine, though, and there are no further messages in the log files. > > The quickest way to make it work again, is pulling the card out and plug > > it back it. Any ideas? > > Ok, I've investigated this further. The strange thing is: whenever the > connections to the outside drop, I can ping and connect to any host in > my LAN (10.0.0.0/24), but I _cannot_ ping 10.0.0.138 from the WLAN > client, which is the inside interface of the ADSL router and thus the > default route. I can't explain why. "ifconfig ath0 down && ifconfig ath0 > up" solves this lock-up. Could this be a driver bug? Just to check: you're not using multiple NATs in this configuration, right? I've noticed terrible TCP and general networking interactions when I layer a Linksys wireless router NAT behind a SpeedStream DSL modem that was also doing NAT -- TCP connections frequently stall, disconnect, etc. Using the Linksys router to bridge the wired and wireless networks, and avoiding network address translation, really made a difference. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1030705134145.43745D-100000>