I try to set up a trunk failover from my fxp0 to my ral0. After the
trunk is created, trunkport is added and address is assigned I have no
network connection any longer and I get some strange replies from ping:
$ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
ping: sendto: Device busy
ping: wrote 192.168.0.1 64 chars, ret=-1
I got the feeling that setting up a trunk-interface should be a piece of
cake so I'm probably doing something trivial mistake here. Hopefully
someone can point me to the right direction.
This is pre-trunk ifconfig:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33224
groups: lo
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:02:a5:b8:71:b5
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet6 fe80::202:a5ff:feb8:71b5%fxp0 prefixlen 64 scopeid 0x1
inet 192.168.0.32 netmask 0xffffff00 broadcast 192.168.0.255
pflog0: flags=0<> mtu 33224
pfsync0: flags=0<> mtu 1460
groups: carp
enc0: flags=0<> mtu 1536
ral0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:13:f7:1e:a7:86
groups: egress
media: IEEE802.11 OFDM54 mode 11g (DS1 mode 11g)
status: active
ieee80211: nwid himmet_wlan chan 11 bssid 00:13:f7:2a:f4:ab
118dB 100dBm inet6 fe80::213:f7ff:fe1e:a786%ral0 prefixlen 64
scopeid 0x6
inet 192.168.1.32 netmask 0xffffff00 broadcast 192.168.1.255
Then trunk is created with and assigned an ip at the same subnet as fxp0
# ifconfig trunk0 create
# ifconfig trunk0 trunkproto failover
# ifconfig trunk0 trunkport fxp0
# ifconfig trunk0 trunkport ral0
# ifconfig trunk0 192.168.0.35 255.255.255.0
And now the network is down. Only way I've found to bring it back again is:
# ifconfig trunk0 destroy
# ifconfig fxp0 up
# ifconfig ral0 up
This is the post-trunk ifconfig:
$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33224
groups: lo
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
fxp0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:02:a5:b8:71:b5
trunk: trunkdev trunk0
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet6 fe80::202:a5ff:feb8:71b5%fxp0 prefixlen 64 scopeid 0x1
inet 192.168.0.32 netmask 0xffffff00 broadcast 192.168.0.255
pflog0: flags=0<> mtu 33224
pfsync0: flags=0<> mtu 1460
groups: carp
enc0: flags=0<> mtu 1536
ral0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:02:a5:b8:71:b5
trunk: trunkdev trunk0
groups: egress
media: IEEE802.11 OFDM54 mode 11g (DS1 mode 11g)
status: active
ieee80211: nwid himmet_wlan chan 11 bssid 00:13:f7:2a:f4:ab
119dB 100dBm inet6 fe80::213:f7ff:fe1e:a786%ral0 prefixlen 64
scopeid 0x6
inet 192.168.1.32 netmask 0xffffff00 broadcast 192.168.1.255
trunk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:02:a5:b8:71:b5
trunk: trunkproto failover
trunkport ral0 active
trunkport fxp0 master,active
groups: trunk
media: Ethernet autoselect
status: active
inet 192.168.0.35 netmask 0xffffff00 broadcast 255.255.255.0
inet6 fe80::202:a5ff:feb8:71b5%trunk0 prefixlen 64 scopeid 0xa
Cheers,
Markus
