Hi!
What is the current status of BGP MD5 support for STABLE branch?
I know that STABLE has TCP_SIGNATURE kernel option for basic compatibility
with Cisco BGP neighbors but wonder if zebra/quagga/something have
RFC 2385 support for FreeBSD?
Are there corresponding patches for routing daemons ava
Bruce Evans wrote:
On Sun, 25 Apr 2004, David Burns wrote:
Mike Silbersack wrote:
On Sat, 24 Apr 2004, David Burns wrote:
NB this assumes that a DELAY(1) is really a delay of 1?s! Which I don't
think it is ... :-(
Correct, DELAY takes far longer than it should.
Actually, it takes at least as lo
On Sun, 25 Apr 2004, David Burns wrote:
> Mike Silbersack wrote:
> >
> > On Sat, 24 Apr 2004, David Burns wrote:
> >>NB this assumes that a DELAY(1) is really a delay of 1?s! Which I don't
> >>think it is ... :-(
> >
> > Correct, DELAY takes far longer than it should.
Actually, it takes at least
Here is a snapshot of the new arp code that i have been working on
lately, based a on Andre's ideas. (I say 'ARP' for brevity, what i
mean is the layer3-to-layer2 address translation code -- arp, aarp, nd6
all fit in the category).
The basic idea is to have per-ifp, per-af tables linked to the
ifn
Mike Silbersack wrote:
On Sat, 24 Apr 2004, David Burns wrote:
Hello all,
It appears that quite a few of the "el cheapo" hardware Fast Ethernet
drivers (at least rl, sis, ste, vr, wb - these are just the ones I found
in /usr/src/sys/pci) have added DELAY(1) statements around MII serial
clock op
Andre Oppermann wrote:
This is a very interesting observation. I've just worked my way through
the MII code to add link state notification to the routing socket and had
to remove a couple of return(0) when the link is up to break so the later
status function can read the MII and announce the state
