ifwatchd(8) problems on bge(4)

[Edgar Fuß]

I'm using ifwatchd(8) to switch machines to use interfaces on a backup
switch should the main switch fail.

If I unplug cables on an fxp, everything works as expected.

If I unplug a cable on a bge, ifwatchd doesn't trigger the scripts ...
... until you run ifconfig bge0.

According to documentation, ifwatchd uses messages on the routing socket
and I admit not knowing too much about the routing socket.

Is this a bug in bge(4)?


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Steven M. Bellovin]

On Wed, 11 Apr 2007 16:48:49 +0200

Post by Edgar Fuß
I'm using ifwatchd(8) to switch machines to use interfaces on a backup
switch should the main switch fail.
If I unplug cables on an fxp, everything works as expected.
If I unplug a cable on a bge, ifwatchd doesn't trigger the scripts ...
... until you run ifconfig bge0.
According to documentation, ifwatchd uses messages on the routing
socket and I admit not knowing too much about the routing socket.
Is this a bug in bge(4)?

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


--Steve Bellovin, http://www.cs.columbia.edu/~smb

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Edgar Fuß]

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?

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Michael van Elst]

Post by Edgar Fuß
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?

I see the same problem. The bug is probably in the phy code,
brgphy in my case, and not in the bge driver itself.

When the interface is down, then ifwatchd sees neither carrier
nor nocarrier events until you run 'ifconfig bge0' and poll
the status.
When the interface is up, then ifwatchd sees carrier events,
and nocarrier events need to be "polled".