EF> If I unplug a cable on a bge, ifwatchd doesn't trigger the scripts ...
EF> ... until you run ifconfig bge0.
EF> 
EF> According to documentation, ifwatchd uses messages on the routing
EF> socket and I admit not knowing too much about the routing socket.
EF> 
EF> Is this a bug in bge(4)?

SB> I see the same problem with bge on brief tests, on -current.

Hm, anyone round here able to tell whether this is a bug in bge?