Re: [solved - I hope] Re: if_bwn woes
On Fri, Oct 8, 2010 at 12:15 PM, Paul B Mahol wrote: > On 10/8/10, Eitan Adler wrote: >> Finally, thank to Freenode's ##freebsd I tried wpa_supplicant which worked. >> I can now connect to the internet. >> >> I'd still like to know why I must use the program and I can't use the >> raw commands though. > > So OPEN authmode is broken somehow? Send a problem report if really is. > I used key_mgmt=NONE in wpa_supplicant.conf so I think it is still using OPEN. I'm not really sure what the difference is. -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [solved - I hope] Re: if_bwn woes
On 10/8/10, Eitan Adler wrote: > Finally, thank to Freenode's ##freebsd I tried wpa_supplicant which worked. > I can now connect to the internet. > > I'd still like to know why I must use the program and I can't use the > raw commands though. So OPEN authmode is broken somehow? Send a problem report if really is. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
[solved - I hope] Re: if_bwn woes
Finally, thank to Freenode's ##freebsd I tried wpa_supplicant which worked. I can now connect to the internet. I'd still like to know why I must use the program and I can't use the raw commands though. On Thu, Oct 7, 2010 at 9:18 PM, Eitan Adler wrote: > On Thu, Oct 7, 2010 at 9:14 PM, Paul B Mahol wrote: >> On 10/7/10, Eitan Adler wrote: >>> On Thu, Oct 7, 2010 at 5:22 PM, Paul B Mahol wrote: On 10/7/10, Eitan Adler wrote: >> Looks like you cant associate at all. >> Also signal power is too low. >> >> Why is INT (beacon interval of AP) 102 ? > > These are the defaults - I have no idea what these numbers mean. What > should/could I be changing? I doubt that AP have capatibility to change that. Anyway maybe you could associate if your txpower is big enough... >>> >>> Sorry - I realized a brief portion of out conversation was done off-list. >>> >>> I just noticed that when I put in the ssid ifconfig seems to be >>> cycling among multiple channels (1,5, 11,12,13 ,14 and maybe others). >> >> Well, force it to stay on channel 1 all the time. >> > I destroyed and recreated wlan0 with the channel 1 > Now it stopped cycling but bwn0 now says "no carrier" as well. > > > -- > Eitan Adler > -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: if_bwn woes
On Thu, Oct 7, 2010 at 9:14 PM, Paul B Mahol wrote: > On 10/7/10, Eitan Adler wrote: >> On Thu, Oct 7, 2010 at 5:22 PM, Paul B Mahol wrote: >>> On 10/7/10, Eitan Adler wrote: > Looks like you cant associate at all. > Also signal power is too low. > > Why is INT (beacon interval of AP) 102 ? These are the defaults - I have no idea what these numbers mean. What should/could I be changing? >>> >>> I doubt that AP have capatibility to change that. >>> Anyway maybe you could associate if your txpower is big enough... >>> >> >> Sorry - I realized a brief portion of out conversation was done off-list. >> >> I just noticed that when I put in the ssid ifconfig seems to be >> cycling among multiple channels (1,5, 11,12,13 ,14 and maybe others). > > Well, force it to stay on channel 1 all the time. > I destroyed and recreated wlan0 with the channel 1 Now it stopped cycling but bwn0 now says "no carrier" as well. -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: if_bwn woes
On 10/7/10, Eitan Adler wrote: > On Thu, Oct 7, 2010 at 5:22 PM, Paul B Mahol wrote: >> On 10/7/10, Eitan Adler wrote: Looks like you cant associate at all. Also signal power is too low. Why is INT (beacon interval of AP) 102 ? >>> >>> These are the defaults - I have no idea what these numbers mean. What >>> should/could I be changing? >> >> I doubt that AP have capatibility to change that. >> Anyway maybe you could associate if your txpower is big enough... >> > > Sorry - I realized a brief portion of out conversation was done off-list. > > I just noticed that when I put in the ssid ifconfig seems to be > cycling among multiple channels (1,5, 11,12,13 ,14 and maybe others). Well, force it to stay on channel 1 all the time. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: if_bwn woes
Sorry for the reply-to-self On Thu, Oct 7, 2010 at 9:11 PM, Eitan Adler wrote: > On Thu, Oct 7, 2010 at 5:22 PM, Paul B Mahol wrote: >> On 10/7/10, Eitan Adler wrote: Looks like you cant associate at all. Also signal power is too low. Why is INT (beacon interval of AP) 102 ? >>> >>> These are the defaults - I have no idea what these numbers mean. What >>> should/could I be changing? >> >> I doubt that AP have capatibility to change that. >> Anyway maybe you could associate if your txpower is big enough... >> > > Sorry - I realized a brief portion of out conversation was done off-list. > > I just noticed that when I put in the ssid ifconfig seems to be > cycling among multiple channels (1,5, 11,12,13 ,14 and maybe others). > > I'm not sure what this behavior means. > > What would the best way see why I can't connect be? > > I tried > $ifconfig wlan0 txpower 50 > but txpower stays at 30. > > Is this for sure a signal strength problem? it worked when I used ndis > from the same location. > ... I also noticed that bwn0 says status: associated while wlan0 says status: no carrier -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: if_bwn woes
On Thu, Oct 7, 2010 at 5:22 PM, Paul B Mahol wrote: > On 10/7/10, Eitan Adler wrote: >>> Looks like you cant associate at all. >>> Also signal power is too low. >>> >>> Why is INT (beacon interval of AP) 102 ? >> >> These are the defaults - I have no idea what these numbers mean. What >> should/could I be changing? > > I doubt that AP have capatibility to change that. > Anyway maybe you could associate if your txpower is big enough... > Sorry - I realized a brief portion of out conversation was done off-list. I just noticed that when I put in the ssid ifconfig seems to be cycling among multiple channels (1,5, 11,12,13 ,14 and maybe others). I'm not sure what this behavior means. What would the best way see why I can't connect be? I tried $ifconfig wlan0 txpower 50 but txpower stays at 30. Is this for sure a signal strength problem? it worked when I used ndis from the same location. -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: if_bwn woes
On 10/7/10, Eitan Adler wrote: >> Looks like you cant associate at all. >> Also signal power is too low. >> >> Why is INT (beacon interval of AP) 102 ? > > These are the defaults - I have no idea what these numbers mean. What > should/could I be changing? I doubt that AP have capatibility to change that. Anyway maybe you could associate if your txpower is big enough... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: if_bwn woes
> Looks like you cant associate at all. > Also signal power is too low. > > Why is INT (beacon interval of AP) 102 ? These are the defaults - I have no idea what these numbers mean. What should/could I be changing? -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: if_bwn woes
On 10/7/10, Eitan Adler wrote: > On Thu, Oct 7, 2010 at 2:31 PM, Paul B Mahol wrote: >> On 10/7/10, Eitan Adler wrote: > > ifconfig wlan0 scan results in no output and takes forever (ie - it > hangs) If you set wlan0 for manual roaming it will not hang. Use 'ifconfig wlan0 list scan' instead. >>> That worked, thanks. >>> >>> dhclient still results in no link being found. >> >> Are you sure that you setup is correct? >> For example you can not connect to AP which require RSN authmode >> if you configure wlan0 for OPEN authmode, you also may not >> connect to AP if you are far away, because you are able >> to receive and send doesn't mean AP can see your packets >> >> Try changing ucastrate to lower values. >> > > I'm not really sure what ucastrate does - but here it goes: > > $ifconfig wlan0 list scan|head -1 > xyz 00:23:xx:yy:zz:aa:bb 1 54M -125:-95 102 E HTCAP WME > $ifconfig wlan0 ssid xyz > $dhclient wlan0 > ... no link ... > $ifconfig wlan0 ucastrate 9 > $dhclient wlan0 > ... no link ... > $ifconfig wlan0 ucastrate 1 > $dhclient wlan0 > ... no link ... > > I'm fairly sure that I'm in an area where the signal reaches because > when I was using the ndis driver (on an old install) it worked. > This is a fresh install now. Looks like you cant associate at all. Also signal power is too low. Why is INT (beacon interval of AP) 102 ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: if_bwn woes
On Thu, Oct 7, 2010 at 2:31 PM, Paul B Mahol wrote: > On 10/7/10, Eitan Adler wrote: ifconfig wlan0 scan results in no output and takes forever (ie - it hangs) >>> If you set wlan0 for manual roaming it will not hang. >>> >>> Use 'ifconfig wlan0 list scan' instead. >> That worked, thanks. >> >> dhclient still results in no link being found. > > Are you sure that you setup is correct? > For example you can not connect to AP which require RSN authmode > if you configure wlan0 for OPEN authmode, you also may not > connect to AP if you are far away, because you are able > to receive and send doesn't mean AP can see your packets > > Try changing ucastrate to lower values. > I'm not really sure what ucastrate does - but here it goes: $ifconfig wlan0 list scan|head -1 xyz 00:23:xx:yy:zz:aa:bb 1 54M -125:-95 102 E HTCAP WME $ifconfig wlan0 ssid xyz $dhclient wlan0 ... no link ... $ifconfig wlan0 ucastrate 9 $dhclient wlan0 ... no link ... $ifconfig wlan0 ucastrate 1 $dhclient wlan0 ... no link ... I'm fairly sure that I'm in an area where the signal reaches because when I was using the ndis driver (on an old install) it worked. This is a fresh install now. -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: if_bwn woes
On 10/7/10, Eitan Adler wrote: >>> >>> ifconfig wlan0 scan results in no output and takes forever (ie - it >>> hangs) >> If you set wlan0 for manual roaming it will not hang. >> >> Use 'ifconfig wlan0 list scan' instead. > That worked, thanks. > > dhclient still results in no link being found. Are you sure that you setup is correct? For example you can not connect to AP which require RSN authmode if you configure wlan0 for OPEN authmode, you also may not connect to AP if you are far away, because you are able to receive and send doesn't mean AP can see your packets Try changing ucastrate to lower values. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: if_bwn woes
>> >> ifconfig wlan0 scan results in no output and takes forever (ie - it hangs) > If you set wlan0 for manual roaming it will not hang. > > Use 'ifconfig wlan0 list scan' instead. That worked, thanks. dhclient still results in no link being found. > >> ifconfig wlan0 ssid my_ssid >> dhclient wlan0 >> results in no link being discovered >> >> Here is some relevant system config and such to help diagnose the problem: >> >> #ifconfig wlan0 create wlandev bwn0 >> >> #ifconfig bwn0 >> bwn0: flags=8843 metric 0 mtu 2290 >> ether xx:yy:zz:xx:yy:zz >> media: IEEE 8.2.11 Wireless Ethernet autoselect mode 11g >> status: associated >> >> # cat /boot/loader.conf |head -2 >> bwn_b4_lp_ucode_load="YES" >> if_bwn_load="YES" >> >> #kldstat |grep bwn >> 2 1 0xc0fb6000 37248 if_bwn.ko >> 3 2 0xc0fee000 a26c siba_bwn.ko >> 7 1 0xc1078000 2cbd8 bwn_v4_lp_ucode >> >> #pciconf -lv | grep -A3 bwn >> siba_b...@pci0:4:0:0: class=0x028000 card=0x04b514e4 chip=0x431514e4 >> rev=0x01 hdr=0x00 >> vender = 'Broadcom Corporation' >> device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' >> class = network >> >> #uname -rms >> FreeBSD 8.1-RELEASE i386 >> >> On a Lenovo G530 >> >> -- >> Eitan Adler >> ___ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" >> > -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: if_bwn woes
On 10/7/10, Eitan Adler wrote: > On a fresh 8.1-RELEASE install > > ifconfig wlan0 scan results in no output and takes forever (ie - it hangs) If you set wlan0 for manual roaming it will not hang. Use 'ifconfig wlan0 list scan' instead. > ifconfig wlan0 ssid my_ssid > dhclient wlan0 > results in no link being discovered > > Here is some relevant system config and such to help diagnose the problem: > > #ifconfig wlan0 create wlandev bwn0 > > #ifconfig bwn0 > bwn0: flags=8843 metric 0 mtu 2290 >ether xx:yy:zz:xx:yy:zz >media: IEEE 8.2.11 Wireless Ethernet autoselect mode 11g >status: associated > > # cat /boot/loader.conf |head -2 > bwn_b4_lp_ucode_load="YES" > if_bwn_load="YES" > > #kldstat |grep bwn > 2 1 0xc0fb6000 37248 if_bwn.ko > 3 2 0xc0fee000 a26c siba_bwn.ko > 7 1 0xc1078000 2cbd8 bwn_v4_lp_ucode > > #pciconf -lv | grep -A3 bwn > siba_b...@pci0:4:0:0: class=0x028000 card=0x04b514e4 chip=0x431514e4 > rev=0x01 hdr=0x00 > vender = 'Broadcom Corporation' > device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' > class= network > > #uname -rms > FreeBSD 8.1-RELEASE i386 > > On a Lenovo G530 > > -- > Eitan Adler > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
if_bwn woes
On a fresh 8.1-RELEASE install ifconfig wlan0 scan results in no output and takes forever (ie - it hangs) ifconfig wlan0 ssid my_ssid dhclient wlan0 results in no link being discovered Here is some relevant system config and such to help diagnose the problem: #ifconfig wlan0 create wlandev bwn0 #ifconfig bwn0 bwn0: flags=8843 metric 0 mtu 2290 ether xx:yy:zz:xx:yy:zz media: IEEE 8.2.11 Wireless Ethernet autoselect mode 11g status: associated # cat /boot/loader.conf |head -2 bwn_b4_lp_ucode_load="YES" if_bwn_load="YES" #kldstat |grep bwn 2 1 0xc0fb6000 37248 if_bwn.ko 3 2 0xc0fee000 a26c siba_bwn.ko 7 1 0xc1078000 2cbd8 bwn_v4_lp_ucode #pciconf -lv | grep -A3 bwn siba_b...@pci0:4:0:0: class=0x028000 card=0x04b514e4 chip=0x431514e4 rev=0x01 hdr=0x00 vender = 'Broadcom Corporation' device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' class= network #uname -rms FreeBSD 8.1-RELEASE i386 On a Lenovo G530 -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
