From owner-freebsd-current@FreeBSD.ORG Thu Jul 1 16:02:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 05FD916A4CF; Thu, 1 Jul 2004 16:02:23 +0000 (GMT) In-Reply-To: <40E40E16.9080109@portaone.com> from Maxim Sobolev at "Jul 1, 2004 04:13:58 pm" To: sobomax@portaone.com (Maxim Sobolev) Date: Thu, 1 Jul 2004 16:02:22 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20040701160223.05FD916A4CF@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) cc: freebsd-current@FreeBSD.ORG Subject: Re: Project Evil & ACX100-based cards (D-Link DWL-520+) 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: Thu, 01 Jul 2004 16:02:23 -0000 > Bill, > > Do you have any news on this? > > -Maxim I remember telling you there were a whole bunch of things you didn't tell me. There was a list. You didn't fill in all of the blanks, therefore you get no help. Go back and review the list and tell me everything that I asked for. (You told me the ssid is "portaone" and that you tried to connect to "that network" from WinXP, but you _STILL_ haven't told me anything about the other machine that hosts the ad-hoc cell. And you _STILL_ have not told me what happens when you do wicontrol -I bwe0 -l.) -Bill > Maxim Sobolev wrote: > > > OK, step by step: > > > > 1. cvsup ~1 hour ago > > 2. built/installed new kernel, rebooted > > 3. loaded ndis and if_ndis.ko modules: > > > > ndis0: port 0xa800-0xa81f > > mem 0xf2000000-0xf200ffff,0xf2011000-0xf2011fff irq 11 at device 6.0 on > > pci3 > > ndis0: [GIANT-LOCKED] > > ndis0: NDIS API version: 5.1 > > ndis0: Ethernet address: 00:0d:88:8b:7f:1c > > ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 11Mbps > > > > 4. Configured the interface: > > > > -bash-2.05b$ sudo ifconfig ndis0 mediaopt adhoc > > -bash-2.05b$ sudo ifconfig ndis0 ssid "portaone" > > -bash-2.05b$ sudo ifconfig ndis0 wepmode off > > -bash-2.05b$ sudo ifconfig ndis0 192.168.1.1 > > ndis0: link up > > -bash-2.05b$ ifconfig ndis0 > > ndis0: flags=8843 mtu 1500 > > inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 > > ether 00:0d:88:8b:7f:1c > > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect > > ) > > status: associated > > ssid "" > > channel -1 authmode OPEN powersavemode OFF powersavesleep 100 > > rtsthreshold 2312 protmode CTS > > wepmode OFF weptxkey 1 > > > > Then I'm trying to connect to that network from my WinXP laptop. I can > > see network portaone in wireless networks browser just fine. IP address > > on appropriate interface is configured statically in WinXP to be > > 192.168.1.2. I can connect to it also without any problems, but ping > > doen't work between those machines. Also, where I start tcpdump on the > > FreeBSD machine I don't see any traffic even ARPs. > > > > You can find tarball with my ndis_driver_data.h and files from > > /compat/ndis at http://www.portaone.com/~sobomax/dwl520.tar.bz2. Please > > let me know if any other information is necessary. > > > > Thank you very much! > > > > Regards, > > > > Maxim > > > > Bill Paul wrote: > > > >>> Hi Bill, > >>> > >>> I'm trying to make my D-Link DWL-520+ card working with if_ndis, but > >>> no luck yet. The card is correctly detected, driver attaches to it. > >>> If I configure it in the adhoc mode it is seen from the nearby > >>> machine and connected to, but traffic doesn't flow. :-( > >>> > >>> Any ideas? Please let me know if more information is necessary. > >>> > >>> Regards, > >>> > >>> Maxim > >> > >> > >> > >> Alright, I received a sample 520+ card and played with it a little. > >> I was able to get the card to talk to my RealTek 8180 NIC in my laptop > >> in ad-hoc mode with very little trouble. I am therefor forced to conclude > >> that you did not describe your problem with enough detail for me to > >> understand what's going on. Let's examine the things you did not do: > >> > >> - did not provide a transcript of commands/responses used to initialize > >> _both_ cards > >> - did not explain which NIC was initialized first (the first NIC is > >> always the master in an ad-hoc cell) > >> - did not explain exactly what steps were taken to reach the conclusion > >> that "traffic doesn't flow." (Ping? FTP? Slamming machines together > >> at high speed?) > >> - did not explain how it was determined that the card was "seen from > >> the nearby machine" > >> - did not provide _FULL_ dmesg output from both machines (no, it's not > >> enough to tell me "the card is correctly detected") > >> - did not tell me what make/model card was in the other machine and > >> what driver it uses > >> - did not tell me what version of FreeBSD is running on the "nearby > >> machine" - did not run wicontrol -i ndis0 -l on the first machine to > >> scan for > >> APs/ad-hoc nets > >> > >> I keep telling people to provide LOTS OF DETAILS when they report > >> problems, but nobody ever seems to listen. Don't wait for me to drag > >> information out of you: if you don't provide me with LOTS OF DETAILS > >> up front, I won't know what to ask you. > >> > >> -Bill > >> > >> -- > >> ============================================================================= > >> > >> -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu > >> wpaul@windriver.com | Wind River Systems > >> ============================================================================= > >> > >> you're just BEGGING to face the moose > >> ============================================================================= > >> > >> > >> > >> > > > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > > > > > >