wi0 doesn't like INET6 in 5.2.1-R?

I've got a stock 5.2.1 release, and am seeing weird symptoms related
to IPv6 in my kernel.

My laptop's on-board NIC works just fine, as does a PCMCIA-type
NIC, as does a USB-based NIC.

But my venerable Lucient wifi card doesn't seem to behave right.

I can associate to my WAP (with WEP enabled), and DHCP, et al. works
just fine, but when it comes time to actaully set an IPv4 address,
I get an error.

Some illustration:

After inserting card:

  chew% ifconfig wi0
  wi0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        ether 00:02:2d:22:4a:b3
        media: IEEE 802.11 Wireless Ethernet autoselect (none)
        ssid ""
        stationname "FreeBSD WaveLAN/IEEE node"
        channel -1 authmode OPEN powersavemode OFF powersavesleep 100
        wepmode OFF weptxkey 1

After ifconfig for WEP:

  chew% ifconfig wi0
  wi0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        ether 00:02:2d:22:4a:b3
        media: IEEE 802.11 Wireless Ethernet autoselect (none)
        ssid Numachi 1:Numachi
        stationname "FreeBSD WaveLAN/IEEE node"
        channel -1 authmode OPEN powersavemode OFF powersavesleep 100
        wepmode MIXED weptxkey 1
        wepkey 1:104-bit

Try to set an IPv4 address:

  chew% ifconfig wi0 inet 198.175.254.193 netmask 255.255.255.0
  ifconfig: ioctl (SIOCAIFADDR): File exists

  chew% ifconfig wi0
  wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::202:2dff:fe22:4ab3%wi0 prefixlen 64 scopeid 0x4 
        ether 00:02:2d:22:4a:b3
        media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps)
        status: associated
        ssid Numachi 1:Numachi
        stationname "FreeBSD WaveLAN/IEEE node"
        channel 11 authmode OPEN powersavemode OFF powersavesleep 100
        wepmode MIXED weptxkey 1
        wepkey 1:104-bit

Note: somehow, an IPv6 address got configured.  I have no connectivity.

When I rebuild my kernel, with INET6 commented out, this series of
commands works just fine.

I couldn't find anything in the archives associated with this issue,
but I may not have the right buzzwords...

Is this a recognized bug?  Should I open a PR?

-- 
Brian Reichert				<reichert_at_numachi.com>
37 Crystal Ave. #303			Daytime number: (603) 434-6842
Derry NH 03038-1713 USA			BSD admin/developer at large