On 2008-10-26T22:41:44, Andrew Beekhof [EMAIL PROTECTED] wrote:
ping the dhcp server?
ping google.com?
or even more likely, the name server(s)
there is no way those aren't statically assigned.
ping is not a good indication whether the link is up, at least not in
all scenarios.
I'd
On Sun, Oct 26, 2008 at 19:37, tje [EMAIL PROTECTED] wrote:
Through an interface that *must* be up (or we should fail over), there is no
address that can be the subject of a ping. Everything is dynamically
assigned via DHCP, all L2 switching on that side is incapable of having even
a loopback
I am also the DHCP sever, and access to everything north also flows thru me.
On 10/26/08 1:40 PM, Andrew Beekhof [EMAIL PROTECTED] wrote:
On Sun, Oct 26, 2008 at 19:37, tje [EMAIL PROTECTED] wrote:
Through an interface that *must* be up (or we should fail over), there is no
address that can
On Fri, Oct 24, 2008 at 12:25:32PM -0700, tje wrote:
I'm in a situation where I don't have an address that can work as a ping
address (don't ask). In this case I really just want to detect if the
freakin ethernet link is gone. I've looked at how ipfail works inside, and
I've looked at the
ethtool is a way to detect link state from the command line, but if the
right NIC goes down, I need to give up HB_ALL_RESOURCES, so I don't see a
way to do this w/out writing code. Please let me know if I am missing a
clue.
Is this easy with v2, hard w/v1?
On 10/24/08 1:55 PM, Brian Reichert
