, Arnoud Vermeer wrote:
I have a problem with filtering on the current route server
implementation. I currently have the following setup:
* 10.0.1.0/24 10.0.1.0/24
+---+ +---+
|AS1| |AS2|
| 10.0.0.50
' on
the roadmap?
Arnoud
On 3/18/09 11:32 AM, Claudio Jeker wrote:
On Wed, Mar 18, 2009 at 11:00:32AM +0100, Arnoud Vermeer wrote:
I have a problem with filtering on the current route server
implementation. I currently have the following setup:
* 10.0.1.0/24 10.0.1.0/24
to
implement this feature?
Arnoud Vermeer
Amsterdam Internet Exchange
ec ad 53 e5 05 42 31 ..US..B1
0040 1a e0 50 18 43 80 a9 dd 00 00 ff ff ff ff ff ff ..P.C...
0050 ff ff ff ff ff ff ff ff ff ff 00 26 02 00 00 00 ...
0060 0f 80 0f 0c 00 02 01 40 20 01 0d b8 00 97 00 00 ...@ ...
Thanks for the patch!
Arnoud Vermeer
Hi,
Elisa and I were looking at the production-pilot logs last night and
noticed the following:
Mar 10 04:41:45 radix-new bgpd[25100]: neighbor 2001:7f8:1::a501:6265:2
(LEASEWEB-v6-02) AS16265: withdraw 2001:1af8::/32
Mar 10 04:41:45 radix-new bgpd[12120]: neighbor 2001:7f8:1::a504:8345:1
I didn't modify the source code in any way. I'm running the latest
version from CVS on an amd64 machine and an i386 machine.
I have the following configuration:
AS 6777
router-id 195.69.145.245
fib-update no
log updates
listen on 195.69.145.245
listen on 2001:7F8:1::A500:6777:4
nexthop qualify
No, this is not the only session. Here is the full config, I hope it helps:
Things start going wrong when I add the following to a v6 session:
tcp md5sig password hondjes
--
AS 6777
router-id 195.69.145.245
fib-update no
log updates
listen on 195.69.145.245
listen on 2001:7F8:1::A500:6777:4
Ok, so this is what the RFC4724, section 2 states:
For the IPv4 unicast address family, the End-of-RIB
marker is an UPDATE message with the minimum length [BGP-4]. For any
other address family, it is an UPDATE message that contains only the
MP_UNREACH_NLRI attribute [BGP-MP] with no
Hi Claudio,
I've attached both the MRT session dumps and a tcpdump capture.
Kind regards,
Arnoud Vermeer
Claudio Jeker schreef:
On Mon, Feb 23, 2009 at 02:11:38PM +0100, Arnoud Vermeer wrote:
I found a different way to replicate the bug, this time it crashes ALL
the IPv6 sessions
regards,
Arnoud Vermeer
Henning Brauer schreef:
* Stuart Henderson s...@spacehopper.org [2009-01-30 17:59]:
On 2009-01-29, Arnoud Vermeer arnoud.verm...@ams-ix.net wrote:
While looking in to the problem, we found out that OpenBGPD sends a
empty UPDATE, on which quagga responds
-
Idle, reason: NOTIFICATION received
Jan 30 15:07:07 routeertnix bgpd[11747]: Connection attempt from
neighbor 2001:db8:1::a506:5502:1 (laborantix ipv6) while session is in
state Idle
I hope this abundunce of information helps.
Kind regards,
Arnoud
tico schreef:
Arnoud Vermeer wrote:
Hi,
I found
Field (10)
When the NOTIFICATION is received, the peer is set back to the state
Idle, where the process starts again. The only way to break the cicle is
to restart the entire OpenBGPD daemon.
Kind regards,
Arnoud Vermeer
12 matches
Mail list logo
