On Tue, Oct 16, 2012 at 8:18 PM, Ronald F. Guilmette
<r...@tristatelogic.com> wrote:
>
>
> Greerings,
>
> I am currently running 9.1-RC2 on my laptop, and I'm wondering what the
> proper procedure is for reporting bugs in not-yet-released releases.
> Could somebody please tell me? Should I just file a regular PR? (I've
> never done this before for anything that's not an official -RELEASE,
> and I don't want to be busting anybody's chops over something that isn't
> considered ready-for-prine-time anyway.)
I think stable@ is probably the best choice. wireless@ would also be
an appropriate place.
> So anyway, I'll give the issue to you in a nutshell... This laptop has
> both wired ethernet and wireless (11{b,g,n}) capabilities. I have a
> Linksys E1000 which I had this thing successfully talking to/with
> (using 11n) under 9.0-RELEASE. (The Linksys is set to speak `N-Only'.)
>
> Now however, it does appear to me that in 9.1-RC2 there may perhaps be
> a problem which is causing the iwn0 interface to want to speak to the
> Linksys using 11b, of all things. (I would have though that if it was
> giving up on `N' it would have fallen back to `G' next.)
>
> I include below relevant portions of my /etc/rc.conf file and the output
> I am now getting from ifconfig -a.
>
> Guidance would be appreciated. Should I be filing a PR? Is my rc.conf
> goofed?
>
>
> Regards,
> rfg
>
>
> P.S. Actually, I've never tried running _both_ the wired & wireless stuff
> on this laptop in parallel before now. Is that part of the problem? And
> anyway, how exactly does the system establish a default route to 192.168.1.1
> when there are two (or more) ways to get there from here?
>
>
> rc.conf:
> =============================================================================
> hostname="slim.tristatelogic.com"
> ifconfig_re0="inet 192.168.1.23 netmask 255.255.255.0"
> defaultrouter="192.168.1.1"
> #
> wlans_iwn0="wlan0"
> ifconfig_wlan0="WPA inet 192.168.1.21 netmask 255.255.255.0 ssid ronair2-1"
> =============================================================================
>
> ifconfig -a:
> =============================================================================
> 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=8803<UP,BROADCAST,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 11b
> 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=8803<UP,BROADCAST,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 tentative scopeid
> 0xb
> nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
> status: no carrier
> ssid ronair2-1 channel 1 (2412 MHz 11b)
> country US authmode WPA1+WPA2/802.11i privacy OFF txpower 15 bmiss 10
> scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7
> roam:rate 1 wme roaming MANUAL bintval 0
> =============================================================================
I don't see any real issue with your configuration, but I do see
something odd and it may be tied to the problem you are seeing. FWIW,
I also have an agn iwn card, but I only have a G access point at this
time and it runs fine in G.
The oddity is that you specify your ssid in the rc.conf file while
using WPA. I've never seen that before. It's in my wpa_supplicant.conf
file. It seems more reasonable for a laptop that may need to associate
with a home and a work SSID as well as ones at conferences and, in my
case alternate work and home SSIDs. When it is in the rc.conf file, it
requires change with every relocation.
in any case, you might try moving the SID into the wpa_supplicant.conf
file, but my bet is it is N specific. Paging Adrian.
--
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
