IPV6 connectivity issue

2025-01-06 Thread Julien Sansonnens via Bird-users
Dear all, I'm experincing a nasty problem with IPV6 for some time. I'm certainly missing something obvious, don't blame me, I'm still learning :) I'm using bird 2.0.12 under debian 12 as a router. This router (VPS) has a working IPV6 connectivity via the VPS provider. I own an ipv6 prefix in the

RPKI validation troubles

2020-11-27 Thread Julien Sansonnens
Hi everybody, I'm using bird 2.0.7 and experience some troubles with RPKI validation. here is my config (relevant parts only): roa6 table r6; protocol rpki validator { roa6 { table r6; }; remote "XX" port 8282; } protocol bgp { ipv6 { import keep filtered; import filter { if ( roa_check

Analyzing AS PATH in packets

2020-08-04 Thread Julien Sansonnens
Dear all, using bird 2.0.7 I'm a bit confused with the output of "show route export". I'm exporting a full table to a downstream. I'm expecting to see my own AS as the first AS in AS PATH but it will not show in "BGP.as_path" If I prepend it, then it appears on the output. I don't know if it's r

avoid transit because of default route

2020-07-27 Thread Julien Sansonnens
Dear list, I only export three prefixes I own to my peers and upstreams. In theory, nothing prevents one of my peers to choose my router as default route (without my consent), and to pass his packets through my network (only in output, therefore). How to prevent this abuse? It doesn't depend on

Re: cannot export routes (AS_PATH problem ?)

2019-01-05 Thread Julien Sansonnens
ntry in your routing table. > If you have multiple upstreams connected the routes are probably spread > over your upstreams because they all have different flavours of policy and > peering agreements. > > Kind regards > Kurt > > On Fri, Jan 4, 2019 at 8:46 AM Julien Sansonnens

cannot export routes (AS_PATH problem ?)

2019-01-03 Thread Julien Sansonnens
exported routes should have my AS on the left. Am I missing something? It's probably logical, but I do not understand what's going on here. In the same way, I can not export any route that comes from my peers (direct connection), since they have only their AS in the path. help would be highly appreciated. cheers, Julien Sansonnens

Re: Incoming connection rejected

2018-04-26 Thread Julien Sansonnens
Hi Max, There was indeed a problem with the netmask, so BIRD did not consider the peer as directly connected. thanks for your help. Julien 2018-04-25 23:33 GMT+02:00 Maximilian Wilhelm : > Anno domini 2018 Julien Sansonnens scripsit: > > Hi, > > > I'm having a hard time t

Incoming connection rejected

2018-04-25 Thread Julien Sansonnens
222, length 0 15:27:08.253429 IP6 fd00:::1.bgp > fd00:::2.42773: Flags [R.], seq 1, ack 48, win 222, length 0 I do not really see where the problem may come from, the same configuration works with all my other peers. Thank you for your help ! -- Julien Sansonnens

protocol kernel segfault

2016-09-29 Thread Julien Sansonnens
Hi list, I'm using bird 1.6.1 on debian Jessie. For some reason (COULD be related to updating to 1.6.1, but not sure), bird6 is not working anymore. It used to work some weeks ago. The problem is related to "protocol kernel". When I set it like this: protocol kernel { import none; export all; }