route problems in 5.1-RELEASE

[Jesse Guardiani]

Howdy list,

I'm having major problems with the route command today.
My machine is an IBM Thinkpad A30p laptop, running FreeBSD
5.1-RELEASE.

I have two interfaces. wi0 and fxp0

Normally, if I want to swap from wi0 to fxp0, all I
have to do is:

killall dhclient
ifconfig wi0 down
ifconfig fxp0 up
dhclient fxp0

And I'm done. However, ocassionally this backfires,
like it did today:

My fxp0 interface is up:

fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::2d0:59ff:feaa:70ec%fxp0 prefixlen 64 scopeid 0x3
        inet 192.168.1.101 netmask 0xffffff00 broadcast 192.168.1.255
        ether 00:d0:59:aa:70:ec
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active

And my wi0 interface is down:

wi0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::220:e0ff:fe8a:9061%wi0 prefixlen 64 scopeid 0x2
        inet 192.168.1.47 netmask 0xffffff00 broadcast 192.168.1.255
        ether 00:20:e0:8a:90:61
        media: IEEE 802.11 Wireless Ethernet autoselect (none)
        ssid WingNET 1:WingNET
        stationname "FreeBSD WaveLAN/IEEE node"
        channel -1 authmode OPEN powersavemode OFF powersavesleep 100
        wepmode MIXED weptxkey 1
        wepkey 1:128-bit

But routes to the internet are still wanting to use the wi0
interface for some reason:

[16:06]jesse at trevarthan:[~]# route get 206.30.215.2
   route to: 206.30.215.2
destination: 206.30.215.2
    gateway: 192.168.1.1
  interface: wi0
      flags: <UP,GATEWAY,HOST,DONE,WASCLONED,PROTO3>
 recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu     expire
       0         0         0         0         0         0      1500      3584
[16:07]jesse at trevarthan:[~]#


I can change the interface on a per-route basis, but not globally:

[16:10]jesse at trevarthan:[~]# route change 206.30.215.2 -iface fxp0
change host 206.30.215.2: gateway fxp0
[16:11]jesse at trevarthan:[~]# route get 206.30.215.2
   route to: 206.30.215.2
destination: 206.30.215.2
    gateway: fxp0:0.d0.59.aa.70.ec
  interface: fxp0
      flags: <UP,GATEWAY,HOST,DONE,WASCLONED,PROTO3>
 recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu     expire
       0         0         0         0         0         0      1500      3582
[16:11]jesse at trevarthan:[~]# route get 206.30.215.4
   route to: 206.30.215.4
destination: default
       mask: default
    gateway: 192.168.1.1
  interface: wi0
      flags: <UP,GATEWAY,DONE,STATIC,PRCLONING>
 recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu     expire
       0         0         0         0         0         0      1500         0
[16:11]jesse at trevarthan:[~]#



Some funky combination of:

ifconfig wi0 -alias

And restarting dhclient fixed the problem, but it took forever.


1.) Is this a bug?
2.) If so, has it already been fixed in -CURRENT?

Thanks!

-- 
Jesse Guardiani, Systems Administrator
WingNET Internet Services,
P.O. Box 2605 // Cleveland, TN 37320-2605
423-559-LINK (v)  423-559-5145 (f)
http://www.wingnet.net