-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stuart Henderson wrote:
On 2009-03-18, sonjaya sonj...@gmail.com wrote:
ps: i'm so sory to ask this because Efficiency and reduce IT
cost .
how does one increase efficiency and reduce IT costs by making
things more complicated
Let me put it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am experiencing the same thing on 4.3 with a very similar setup. I
can add that the downtime doesn't have to be very long for the OpenBSD
to get stuck. I also get messages like this:
Mar 13 02:36:34 akita dhclient[25444]: send_packet: No route to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Laurie wrote:
Hello,
I'm trying to use tcpdump to capture a range of ports and can't get
it to work. I've read the man page, searched the Internet and
experimented with many combinations like 10:120 10-120 { 10 120 }
etc. and nothing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
And I managed to grab the bgpctl data with a slightly different
version of the bgpd config:
The line
network 192.168.0.0/16
was commented out when I grabbed the data, but it doesn't seem to
change the behaviour.
/Pehr Svderman
Comment: Using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello!
I hope this is the right forum to discuss OpenBGP on OpenBSD.
I am setting up a lab network using a combination of OpenBSD 4.4
(About as standard install as they get) and Junier routers and have
run into an interesting problem with OpenBGP.
5 matches
Mail list logo