Date: Thu, 18 Oct 2012 21:24:36 -0700 From: "Ronald F. Guilmette" <rfg@tristatelogic.com> To: Kevin Oberman <kob6558@gmail.com> Cc: freebsd-net@freebsd.org, Adrian Chadd <adrian@freebsd.org> Subject: Re: Wireless Networking Bug(s) in 9.1-RC2 (?) Message-ID: <2529.1350620676@tristatelogic.com> In-Reply-To: <CAN6yY1u2cnXZnPuCOwigDRGD9FayDucf78Gw9BX3FMYoSGBZfQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <CAN6yY1u2cnXZnPuCOwigDRGD9FayDucf78Gw9BX3FMYoSGBZfQ@mail.gmail.com>
, Kevin Oberman <kob6558@gmail.com> wrote:
>To use WPA and a static address, you need something like:
>ifconfig_wlan0 ="WPA inet 192.168.1.21/24"
>so that was OK.
Yea, actually I did already have the static+WPA working.
>Now, you seem to have both interfaces on the same /24 with a /24
>netmask. This is probably going to result in some poorly defined
>behavior.
:-)
I think that's the polite way of putting it.
>I'm not sure just what you are trying to do...
That's OK. Tha makes two of us.
(1/2 :-)
>but I suspect that it is not what you are doing.
Actually, I wasn't trying to achieve much of anything, specifically,
when I had _two_ ifconfig_XXX= lines in rc.conf for _both_ my wired and
wirless interfaces. I was just being lazy, not taking the ifconfig
for the wired out when I started using the wirless. And then I
looked at it and realized pretty much what you said, which is basically:
Who the hell knows where the packets will go if there are multiple
routes from one machine to someplace else, and if none of them is
more specific than the other.
It's definitely an enigma. Does this produce Heisenbergian packet flow?
(I was rather hoping that you FreeBSD networking gurus would enlighten
me on this somewhat interesting, even if obscure point.)
>This said, I am not sure how this might cause the interface to fail to
>associate.
I am with you. I don't think it would or should.
>I'm guessing that you are simply not associating and the
>scan is falling back to 'B' after failing to find an AP in faster
>modes. The question is "why?".
Yea, it seems kind of odd.
>What is the output of "ifconfig wlan0 list aps"?
Umm... well... I've rebooted since I mailed/posted earlier, and now things
are looking rather different. In particular, it appears that I have `G'
notw on the wirless link _and_ from elsewher on my network I can successfully
ping _both_ 192.168.1.23 (the wired connection) _and_ also 192.168.1.21
(the wireless connection). And traceroute says that those are both one
hop away from my other server which is at 192.168.1.2.
==============================================================================
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
ether 00:24:21:65:ad:a0
inet 192.168.1.23 netmask 0xffffff00 broadcast 192.168.1.255
inet6 fe80::224:21ff:fe65:ada0%re0 prefixlen 64 scopeid 0x4
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
iwn0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 2290
ether 00:22:fb:76:6d:18
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng
status: associated
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0xa
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:22:fb:76:6d:18
inet 192.168.1.21 netmask 0xffffff00 broadcast 192.168.1.255
inet6 fe80::222:fbff:fe76:6d18%wlan0 prefixlen 64 scopeid 0xb
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: IEEE 802.11 Wireless Ethernet OFDM/36Mbps mode 11ng
status: associated
ssid ronair2-1 channel 11 (2462 MHz 11g ht/40-) bssid c0:c1:c0:8b:4b:f3
country US authmode WPA2/802.11i privacy ON deftxkey UNDEF
AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 15 bmiss 10 scanvalid 450
bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 64
protmode CTS ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi
wme roaming MANUAL
==============================================================================
Here's the stuff that you specifically asked for, although I don't know if
it is even relevant anymore:
==============================================================================
% ifconfig wlan0 list aps
SSID/MESH ID BSSID CHAN RATE S:N INT CAPS
Cisco 58:6d:8f:7e:6c:5d 11 54M -74:-95 100 EP RSN HTCAP WPS WPA WME
ronair2-1 c0:c1:c0:8b:4b:f3 11 54M -65:-95 100 EP RSN HTCAP WPS WME
belkin.194 08:86:3b:6f:91:94 11 54M -81:-95 100 EP HTCAP WPA RSN WME WPS
Cisco 58:6d:8f:7e:6c:5e 36 54M -86:-95 100 EP RSN HTCAP WPS WPA WME
Fluff c0:3f:0e:78:3e:f5 2 54M -82:-95 100 EPS RSN WPA WME HTCAP ATH WPS
linksysLA 00:18:f8:e6:4b:58 5 54M -90:-95 100 EP RSN HTCAP WPA WME
belkin.194.... 08:86:3b:6f:91:96 149 54M -90:-95 100 EP WPS HTCAP WPA RSN WME
erikadoming... a0:21:b7:9d:0f:98 5 54M -83:-95 100 EPS RSN WPA WME HTCAP ATH WPS
dcz_26 00:1b:2f:02:40:de 11 54M -91:-95 100 EPS WPA
==============================================================================
(My AP is "ronair2-1". As you can see, I live is a busy neighborhood.)
>One thing I see is:
>country US authmode WPA1+WPA2/802.11i privacy OFF
Huh?? Where are you seeing THAT?
Oh! I see. I guess it must have been in the ifconfig -a ioutput that I sent
earlier.
Well, as you can see above, that appears to have changed now too.
>For home users I would normally expect WPA-PSK to be used.
Indeed. And as far as I know, that _is_ what I _am_ using.
>What key_mgmt are you specifying?
Sorry. I don't understand the question.
Anyway, the bottom line here is that it appears that I no longer have any
bug report to file. Whatever was causing me to get `B' (or was it `A'?
I forget now) before seems to have sorted itself out on its own.
As I was telling my neighbor just the other day, it never ceases to amaze
me what vast numers of problems are so often cured by a simple hard reset
(i.e. power cycle).
Anyway, if I ever see the problme arise again, I'll let somebody know.
Regards,
rfg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2529.1350620676>