[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Can ifstetd sense carp interfaces status?
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: Can ifstetd sense carp interfaces status?
- From: stan <stanb_(_at_)_panix_(_dot_)_com>
- Date: Thu, 27 May 2004 09:50:32 -0400
- Mail-followup-to: misc_(_at_)_openbsd_(_dot_)_org
On Thu, May 27, 2004 at 02:09:42PM +0200, Henning Brauer wrote:
> * stan <stanb_(_at_)_panix_(_dot_)_com> [2004-05-27 13:32]:
> > On Wed, May 26, 2004 at 06:48:08PM +0200, Henning Brauer wrote:
> > > * Ryan McBride <mcbride_(_at_)_openbsd_(_dot_)_org> [2004-05-26 17:26]:
> > > > On Wed, May 26, 2004 at 10:58:42AM -0400, stan wrote:
> > > > i.e. 'if (carp0 link up)' checks whether carp0 is master.
> > > > > And on a related note, given a 10 or 100baseT fxp card, why does the
> > > > > interface sattus stay in UP, when the cable is unpluged? Is there another
> > > > > (ifstated sensable) flag that would tell me the cable is unpluged?
> > > > This may be a software bug, but is more likely related to the
> > > > functionality of the media independant interface (phy) on that card.
> > > > I'll look into the specific case of the inphy on the fxp, but don't hold
> > > > your breath. Some phy's take quite some time to recognise that the link
> > > > is down; the nsphyter found in Soekris net4x0x boxes takes 5 seconds or
> > > > so do detect that the link is down. How long are you waiting?
> > >
> > > I think he refers to the interface flag "UP", which is in no way
> > > related to the link state.
> > > ifconfig tells the link state in the "status" line, the UP in flags has
> > > nothing to do with link state.
> > Yes, I was talking about the flahs line, so which one of these is the status line?
> > fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> > address: 00:d0:b7:9e:02:28
> > media: Ethernet manual (none)
> > inet 192.168.254.253 netmask 0xffffff00 broadcast 192.168.254.255
> > inet6 fe80::2d0:b7ff:fe9e:228%fxp0 prefixlen 64 scopeid 0x1
> hmm, interestingly enough there is no in your output, meaning that we
> can't get link status from the hardware - never seen this with fxp
> actually. but then, the media line clearly shows us you do not have a
> <brahe_(_at_)_skywalker> pfctl $ ifconfig fxp0
> fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> address: 00:e0:00:3f:2b:f1
> media: Ethernet autoselect (100baseTX full-duplex)
> status: active
> inet6 fe80::2e0:ff:fe3f:2bf1%fxp0 prefixlen 64 scopeid 0x1
> inet 126.96.36.199 netmask 0xffffffe0 broadcast 188.8.131.52
> there is the status line.
Thanks, that may well explain the dificulties I'm having with ifstated.
These are older fxp cards. I must have seen 8 or so differeing hardware
models of these things. We have stndardized on them, and have, quite
literally, undreds of them. And if course, what I get for my projects tend
to be old recycled units.
I doubt if I can find 6 "modern" ones.
Dies it make sense that this could be part of my problem with ifstated?
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin