Date: Fri, 20 Mar 2009 06:10:13 -0400 From: Boris Kochergin <spawk@acm.poly.edu> To: Matthias Apitz <guru@unixarea.de> Cc: freebsd-net@freebsd.org Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Message-ID: <49C36B85.2050202@acm.poly.edu> In-Reply-To: <20090320095603.GA5239@rebelion.Sisis.de> References: <20090317103650.GA6156@rebelion.Sisis.de> <49BF7DE4.4010804@incunabulum.net> <20090317104548.GB6182@rebelion.Sisis.de> <alpine.BSF.2.00.0903171148250.51892@thor.farley.org> <49BFF258.4020207@freebsd.org> <20090319144251.GA13320@rebelion.Sisis.de> <49C2685D.6040801@freebsd.org> <20090320095603.GA5239@rebelion.Sisis.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthias Apitz wrote: > El día Thursday, March 19, 2009 a las 08:44:29AM -0700, Sam Leffler escribió: > > >> Matthias Apitz wrote: >> >>> I will try to collect a better tcpdump of the dhclient packets on the >>> weekend and as well figure out what kind of model the AP is; >>> >>> would it be helpful to connect with a Windows XP laptop (which seems to >>> work) to gather some information of the Wifi and other network >>> parameters? how this could be seen in Windows? maybe there is some >>> special compression of the payload of the packages in place? >>> >>> >> Having a packet trace of a working connection to compare would be very >> helpful. >> > > What would be the best tool in WinXP to log Wifi traffic, like tcpdump > does? I see some 'Tcpdump for Windows' as > http://microolap.com/products/network/tcpdump/ > but it seems that it does not work for wireless adapters; > any hints? > > matthias > http://www.wireshark.org/download.html -Boris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49C36B85.2050202>