Date: Sat, 5 Jul 2003 19:51:30 +0200 (CEST) From: Lukas Ertl <l.ertl@univie.ac.at> To: Robert Watson <rwatson@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: Experiences with ath(4) Message-ID: <20030705195029.C3328@korben.in.tern> In-Reply-To: <Pine.NEB.3.96L.1030705134145.43745D-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1030705134145.43745D-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 5 Jul 2003, Robert Watson wrote: > On Sat, 5 Jul 2003, Lukas Ertl wrote: > > > 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? No, the access point has no NAT functionality. regards, le -- Lukas Ertl eMail: l.ertl@univie.ac.at UNIX-Systemadministrator Tel.: (+43 1) 4277-14073 Zentraler Informatikdienst (ZID) Fax.: (+43 1) 4277-9140 der Universität Wien http://mailbox.univie.ac.at/~le/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030705195029.C3328>