summaryrefslogtreecommitdiff
path: root/usr.bin
diff options
context:
space:
mode:
authorChristopher Pascoe <pascoe@cvs.openbsd.org>2005-06-19 18:17:03 +0000
committerChristopher Pascoe <pascoe@cvs.openbsd.org>2005-06-19 18:17:03 +0000
commit9dfb608c70ddcf83e073ac8297b39055ab310446 (patch)
treeaeabd2d263cfc724daeab572e18b82448bfb521f /usr.bin
parent5ac07b6fb920184f3abbc389aa8d92b1036fd2df (diff)
Don't reflect CARP's internal state via IFF_UP (which a user can modify), use
IFF_RUNNING instead. Also, do not blindly restore flags onto an interface when returning to the running state. This eliminates the possibility that the kernel will bring the interface back up after a link state change on the physical interface, even though the user may have done an "ifconfig carpN down" in the meantime. Similarly two link state down events on the physical interface in succession could result in us never coming out of the INIT state. The master/backup state is still reported via link state information, so bgpd/ospfd, etc, should function as before. This also addresses PR4238. ok mpf@, ok with the idea etc henning@
Diffstat (limited to 'usr.bin')
0 files changed, 0 insertions, 0 deletions