From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 10:43:47 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1CE037B401; Sat, 5 Jul 2003 10:43:46 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 192B644008; Sat, 5 Jul 2003 10:43:46 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h65HhdKJ044597; Sat, 5 Jul 2003 13:43:39 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h65HhdR7044594; Sat, 5 Jul 2003 13:43:39 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sat, 5 Jul 2003 13:43:39 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Lukas Ertl In-Reply-To: <20030705192426.U3328@korben.in.tern> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: sam@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Experiences with ath(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2003 17:43:47 -0000 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