In a previous mail re this problem, Adrian Chadd had asked:
What's the routing table and ifconfig output look like? It sounds like
you're creating the interface and moving things over without:
* deleting the route/IP table entry;
* create the lagg;
* adding the interfaces to the lagg, including the one you booted off of;
* assigning the correct IP and readding the default route.
In answer, info for the DC is below. This is the situation with the
rc.d/lagg script disabled and below line in jail/etc/rc.conf commented
out. Anything I do with lagg after this point freezes the system
ifconfig_lagg0="up laggproto failover laggport re1 laggport re0
192.168.2.2 netmask 255.255.255.0"
ROUTE TABLE:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.2.1 UG 0 0 re0
127.0.0.1 link#3 UH 0 0 lo0
192.168.2.0/24 link#1 U 2 7653 re0
192.168.2.2 link#1 UHS 0 0 lo0
IFCONFIG
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=82008<VLAN_MTU,WOL_MAGIC,LINKSTATE>
ether 00:30:67:91:6c:c2
inet 192.168.2.2 netmask 0xffffff00 broadcast 192.168.2.255
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
re1: 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:30:67:91:6c:c2
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=3<RXCSUM,TXCSUM>
inet 127.0.0.1 netmask 0xff000000
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:30:67:91:6c:c2
media: Ethernet autoselect
status: no carrier
laggproto failover
_______________________________________________
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"
