G'day Larry. thanks for your imput here,
---------------------------------------- > Date: Fri, 21 Mar 2008 08:10:16 -0700 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > CC: [email protected] > Subject: Re: More on ASUS WL-138G V2 > > kala mazoo wrote: >> Well, things have moved along a bit here -- nothing >> works, but it all looks like it wants to... >> >> Upgraded to 2.6.24, now using b43 driver + debug on >> >> Perhaps I'm doing something wrong....anyhow, the background realm consists >> of my son's XP box, >> running one of the same cards with the asus proprietary drivers + config >> frontend, and is setup >> in so called 'softAP' mode instead of 'station' mode, I'm telling it channel >> 1...and no >> additional encryption (which I hope infers WEP only encryption), it's >> network IP is set on >> 192.168.1.0/24 space, and as far as the blowz' box is concerned, everything >> it's end is >> hunky-dory. Except it can't seemingly see this machine at all... >> >> ....on this linux end (and being all new to this), I'm not sure if what I'm >> seeing is actually >> correct. For instance ; >> >> [EMAIL PROTECTED]:# iwconfig wlan0 >> wlan0 IEEE 802.11g ESSID:"dfg" >> Mode:Managed Frequency:2.412 GHz Access Point: 00:1B:FC:61:19:58 >> Tx-Power=27 dBm >> Retry min limit:7 RTS thr:off Fragment thr=2346 B >> Encryption key:1122-3344-55 >> Link Quality:0 Signal level:0 Noise level:0 >> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >> >> ...the AP Mac is that of the XP box -- I didn't expect to see 'Link >> Quality:0 Signal level:0 Noise level:0'... > > The zeros in the signal level is a minor problem that is not severe enough > for anyone to spend time > fixing. Please ignore it for now. The fact that you see the AP's MAC address > implies association, > and the presence of the encryption key means that it has authenticated. > Everything looks normal. > Okay...ignoring the reporting error forthwith....... >> Looking at the same situation from another point of view....; >> >> [EMAIL PROTECTED]:# iwlist wlan0 scanning >> wlan0 Scan completed : >> Cell 01 - Address: 00:1B:FC:61:19:58 >> ESSID:"dfg" >> Mode:Master >> Channel:1 >> Frequency:2.412 GHz (Channel 1) >> Quality=73/100 Signal level=-15 dBm Noise level=-52 dBm >> Encryption key:on >> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s >> 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s >> 12 Mb/s; 48 Mb/s >> Extra:tsf=00000004c4c6c18b >> >> ....and I'll convince myself that sortta looks correct...but shouldn't the >> link/signal/noise stats have appeared in the output of iwconfig? Why are >> they not? > > What is "sortta"? This is _exactly_ what you should see. > The word 'sortta' is an Australian colloquialism which implies the paraphrase 'sort of'....which means something looks right even if one is not 100% sure that it's all actually correct. Without knowing the word's meaning, you've answered it correctly!! Well done.... >> What is the purpose of the wmaster0 interface, and when does it get used? >> Issuing 'ifconfig' returns ; > > With mac80211, multiple interfaces of multiple types are supported. The > master controller for all of > these is 'wmaster0'. It is always there, but you can ignore it. > >> wlan0 Link encap:Ethernet HWaddr 00:1B:FC:61:15:E1 >> inet addr:192.168.1.123 Bcast:192.168.1.255 Mask:255.255.255.0 >> UP BROADCAST MULTICAST MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Okay, I understand now.... > > Was this IP address obtained by DHCP or did you manually assign it? If the > former, then all is > working in the Linux box. It was actually the latter - I manually assigned that IP_addr to wlan0..... > In either case, I would look to problems with the Windoze setup. Their > wizards make everything look deceptively simple, but often it doesn't work. > In addition, make sure > that all firewalls are off until you get it working. Then turn them back on > separately on both ends > and fix any problems that turn up. Yeah, I was loath to do what I did for exactly these reasons - one can never be sure if 'blowz is doing the right thing. I did remember to drop all firewalls (both ends), but such made no difference....I'll go out and buy a wireless router/AP today and remove this conjecture altogether.... > > What does a 'route' command show on the Linux box? Can the Linux box ping > localhost? If the answer > is yes, what does 'ping 192.168.1.123' show? Finally ping the default gateway > shown in the route > command output. If that works, your Linux box is doing exactly what it should. Well, considered the WIRED interface is still active, the routing table looks like ; Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0 172.16.1.0 * 255.255.255.0 U 0 0 0 eth0 default desmo.thehut.ne 0.0.0.0 UG 0 0 0 eth0 ..the 'blowz box is at 192.168.1.1 ....I cannot ping it, and it cannot ping me. I can rehash this to ; Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0 172.16.1.0 * 255.255.255.0 U 0 0 0 eth0 default 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0 but this changes nothing ; PING 192.168.1.1 (192.168.1.1): 48 data bytes 60 bytes from 192.168.1.123: Destination Host Unreachable Vr HL TOS Len ID Flg off TTL Pro cks Src Dst Data 4 5 c0 6800 366f 0 0000 40 01 5886 192.168.1.123 192.168.1.123 --- 192.168.1.1 ping statistics --- 1 packets transmitted, 0 packets received, 100% packet loss and even if I add a host route..so it looks like this; Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.1 * 255.255.255.255 UH 0 0 0 wlan0 192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0 172.16.1.0 * 255.255.255.0 U 0 0 0 eth0 default desmo.thehut.ne 0.0.0.0 UG 0 0 0 eth0 ..but again, this changes nothing. To answer the other questions... PING localhost (127.0.0.1): 48 data bytes 56 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.109 ms 56 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.082 ms 56 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.074 ms --- localhost ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.074/0.088/0.109/0.015 ms PING 192.168.1.123 (192.168.1.123): 48 data bytes 56 bytes from 192.168.1.123: icmp_seq=0 ttl=64 time=0.103 ms 56 bytes from 192.168.1.123: icmp_seq=1 ttl=64 time=0.704 ms 56 bytes from 192.168.1.123: icmp_seq=2 ttl=64 time=0.452 ms --- 192.168.1.123 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.103/0.420/0.704/0.246 ms So go figure. I did all this hours ago, and it was about then I decided it was XP's fault ... Unless of course if the other posting is right, and I actually need hostapd to use the card in managed/ad-hoc modes....in which case all of this is myfault instead... Thanks for everyone's help here, I'll be back, Donald > > Larry > > _________________________________________________________________ Are you paid what you're worth? Find out: SEEK Salary Centre http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2Fcareer%2Dresources%2Fsalary%2Dcentre%2F%3Ftracking%3Dsk%3Ahet%3Asc%3Anine%3A0%3Ahot%3Atext&_t=764565661&_r=OCT07_endtext_salary&_m=EXT _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
