Hi I've run across an situation which I wanted to dig a bit more to find out if I'm encountering a known/expected behaviour or not.
In this case a carp interface is configured to have a VLAN interface as carpdev. On the VLAN interface a couple of static routes are defined. (see at the end of the message) * On a 6.1 router I modified the description of hostname.carp5 * ifconfig carp5 destroy * sh /etc/netstart carp5 Result: Traffic stalled on carp5 to the static routes What brought it back up was destroying the underlying VLAN interface first, bring it back up with netstart - and then only netstart was able to bring the CARP interface backup up to a state where it transfered packages properly. I was by surprise by that, but wanted to ask whether or not this was an expected behaviour. The primary router is currently being upgraded from an old release as such carp is not yet doing its full job. I see that /etc/netstart brings up CARP interfaces after bringing up physical or VLAN interfaces so that works at regular boot. -- Mathieu Attached is a somewhat cleansed config of the VLAN and the carp interface in question: /etc/hostname.vlan120 inet 192.168.11.3 255.255.255.0 192.168.11.255 vlan 120 vlandev trunk0 !/sbin/route add -net 10.10.1.0/24 192.168.11.4 # removed1 !/sbin/route add -net 10.10.2.0/24 192.168.11.4 # removed2 descr "AnyDescription" /etc/hostname.carp5 inet 192.168.11.1 255.255.255.0 192.168.11.255 vhid 29 carpdev vlan120 pass FFFFFFFFFFFFFF advskew 100 inet6 2001:111:1:111::1/64 descr "CarpDescription"