- Bird-users - Mailing Lists

Intermittent no listening socket error - IPv6 BGP
by Jimmy Halim 05 Feb '13

05 Feb '13

Hi guys, I have intermittent "No listening socket error" on IPv6 BGP when setting my server's IPv6 address on different interface from my IPv4. Everything is ok if I put my IPv6 address in the same interface as my IPv4 address. I am using my IPv6 address as BGP listening address under bird6.conf. It this common? By the way, the setting of my IPv6 interface is: DEVICE=p1p2 NM_CONTROLLED=no ONBOOT=yes TYPE=Ethernet UUID="65dbd13f-10fc-4f9d-b8aa-7642fc527f34" DEFROUTE=no IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=no IPV6_DEFROUTE=no IPV6_FAILURE_FATAL=yes NAME="System p1p2" USERCTL=no HWADDR=00:1B:21:A9:C8:C5 IPV6_DEFAULTGW=:: IPV6ADDR=2001:de8:5::2:4115:99/64 Thanks, Jimmy

1 0

filter in filter
by Tapio Haapala 04 Feb '13

04 Feb '13

Yaw dawg, Can I put filter in filter? I mean that if I have: filter own_net { if net ~ [1.2.3.0/24] then accept; reject; } Can I somehow include that to: filter bgp_net { if source = RTS_BGP then accept; #some kind reference to own_net filter here. reject; } I try find right syntax from documentation but I did not find it. -- F-Solutions Oy Tapio Haapala PL7, 90571 Oulu GSM 0400 998371 Skype burner- IRC Burner@ircnet

2 1

Sstatic protocol routes not loaded until extra reload is done on unchanged config.
by Hans van Kranenburg 04 Feb '13

04 Feb '13

Hi all, Loosely based on https://redmine.labs.nic.cz/projects/bird/wiki/Route_server_with_community_… I set up a bird test configuration for an eBGP router which is located in AS64515 and talks to another router in AS65517, using an extra routing table, T65517 and pipe protocol to get fine-grained, and easily debuggable control about which routes I want to announce to the peer, and which received routes I want to import into the local AS: (AS64515) Tmaster - P65517 - T65517 <-> eBGP peer AS65517

2 3

BGPSEC implementation
by Michael Baer 30 Jan '13

30 Jan '13

Hi, I sent mail awhile ago mentioning work being done to implement BGPSEC within the BIRD code and I wanted to give an update. The current code supports the newest version of BGPSEC protocol document as far as capability negotiation and update messages. This includes the cryptographic signing/checking using the openssl libraries. We are continuing to work on it. There are a couple things missing from the update processing (e.g. proper confed handling) and one of the major next steps would be to integrate RPKI data, hopefully using the BIRD ROA tables and pulling from a cache. I can make a patch available of the current code base, if anyone is interested in playing with it (GPL licensed to match the BIRD). Feedback on bugs and improvements would be welcome. I noticed that Ondrej Filip is giving a BIRD presentation at NANOG 57. Several people associated with our project, including Sam cc'd above, will be at that meeting if you want to talk to one of us about it. Let me or Sam know, and one of us can send other contact info privately. Thanks, Mike -- Michael Baer baerm(a)tislabs.com

2 1

Fwd: cloning direct routes into another routing table
by Gustav Koller 29 Jan '13

29 Jan '13

Hello, I'm trying to clone some routes bird leaned via the direct protocol into another kernel routing table. A simple example: log syslog all; debug protocols all; table t_test; protocol device {} # export t_test table to kernel table 100 protocol kernel k_test { table t_test; kernel table 100; export all; } # static route - shows up in table 100 protocol static static_test { table t_test; route 10.1.1.1/32 drop; } # direct routes # doesn't show up in table 100 protocol direct d_test { table t_test; } bird learns the routes perfectly fine but doesn't export them to the kernel table again: # birdc show route table t_test BIRD 1.3.9 ready. 10.1.1.1/32 blackhole [static_test 19:40] * (200) 192.168.0.0/24 dev eth0 [d_test 19:40] * (240) # ip route show table 100 blackhole 10.1.1.1 proto bird This log extract shows the reason for this: k_test: Connected to table t_test k_test < added 10.1.1.1/32 blackhole k_test < rejected by protocol 192.168.0.0/24 dev eth0 I suspect that this is intentional behavior (kernel protocol rejecting routes from direct protocol) as it doesn't make much sense adding direct routes to the kernel in scenarios with a single default/main routing table. But in my case that's what I need. Is there a workaround to make this work? Best regards, Gustav

2 1

Problem with bird 1.3.9 on mips/linux
by Robert Hass 26 Jan '13

26 Jan '13

Hi I compiled bird 1.3.9 on Linux/MIPS (Debian 6.0.6) and I have problem that my bird is not listening on port TCP/179 ? Any comments or recommendations ? Rob # ps auxw | grep bird root 16334 0.0 0.2 2612 1056 pts/0 S 23:46 0:00 ./bird # netstat -a -l | grep bird unix 2 [ ACC ] STREAM LISTENING 84588 bird.ctl # birdc BIRD 1.3.9 ready. bird> show protocols all name proto table state since info device1 Device master up 23:46 Preference: 240 Input filter: ACCEPT Output filter: REJECT Routes: 0 imported, 0 exported, 0 preferred Route change stats: received rejected filtered ignored accepted Import updates: 0 0 0 0 0 Import withdraws: 0 0 --- 0 0 Export updates: 0 0 0 --- 0 Export withdraws: 0 --- --- --- 0 OLIVE4 BGP master start 23:46 Idle Description: JunOS Preference: 100 Input filter: bgp_olive4_in Output filter: bgp_olive4_out Routes: 0 imported, 0 exported, 0 preferred Route change stats: received rejected filtered ignored accepted Import updates: 0 0 0 0 0 Import withdraws: 0 0 --- 0 0 Export updates: 0 0 0 --- 0 Export withdraws: 0 --- --- --- 0 BGP state: Idle Neighbor address: 10.17.0.139 Neighbor AS: 60000 My bird.conf configuration file: log syslog { debug, trace, info, remote, warning, error, auth, fatal, bug }; router id 10.17.0.254; listen bgp address 10.17.0.254 port 179; protocol device { scan time 60; } filter bgp_olive4_in { bgp_local_pref=100; accept; } filter bgp_olive4_out { reject; } protocol bgp OLIVE4 { description "JunOS"; local as 60000; source address 10.17.0.254; neighbor 10.17.0.139 as 60000; import filter bgp_olive4_in; export filter bgp_olive4_out; }

4 10

rs client and bgp soft reload out
by Jimmy Halim 25 Jan '13

25 Jan '13

Hi guys, I have 2 BGP related questions that would like to confirm with you guys: 1. Can we run the route server without setting "rs client" BGP configuration in each client? I can bring up the eBGP as well without that setting in place. 2. Birdc reload out "protocol_name" command will do soft reload on the exported routes to that particular neighbour. However this will reset the uptime. Any idea whether we can keep the uptime? It is very worrying while doing the troubleshooting if the uptime is not reflecting the correct uptime. Thanks, Jimmy

2 2

Re: BUG: /lib/lists.c.. Don`t use -O2 . Use -O1
by Uwe Kleine-König 22 Jan '13

22 Jan '13

On Tue, Jan 22, 2013 at 04:20:06PM +0400, Maksim Tamarsky wrote: > I don`t exprt in ARM-ASM but my colleague say and i se this, that some > ASM code from rem_node and add_head was interlaced and will now be run > in parallel mode and this can lead to error. It's normal that the compiler does reorder the machine instructions for two consecutive inline functions. The overall result still is the same, at least if you stick to defined C constructs and your compiler doesn't have a bug. I don't understand what you mean saying "parallel mode", AFAIK bird is single-threaded so there is nothing running in parallel. If your colleague still thinks there is a bug please ask him to describe it here on the mailing list. Best regards Uwe

1 0

BUG: /lib/lists.c
by Тамарский Максим 21 Jan '13

21 Jan '13

LIST_INLINE void rem_node(node *n) { node *z = n->prev; node *x = n->next; z->next = x; x->prev = z; } Using of this function may broke list.tail and list.head. Later call to function like add_head or add_tail may couse problem. -- Тамарский Максим Александрович Инженер-программист ООО Эн-Эс-Джи г.Москва, Кирпичная 39/41 оф.1302 Почтовый адрес: 105187 Россия, Москва ул.Вольная, д.35, оф.NSG Тел./факс: +7 495 727-19-59 Web-сайт: http://www.nsg.ru

6 6

Seems I can't get bird to open a bgp listen socket
by Hans van Kranenburg 21 Jan '13

21 Jan '13

Hi Bird users, I'm setting up a bird test router, using bird 1.3.9 on debian squeeze (backport of the packages in unstable). It seems I cannot get bird to listen on tcp port 179. tcpdump shows outgoing traffic from 10.140.59.20 to 10.140.59.16, but there's just nothing listening on port 179 when I start bird. $ netstat -an | grep 179 $ This really feels like I'm missing something small, something stupid. Here's my test config: router id 10.140.59.20; debug protocols all; protocol kernel { persist; scan time 60; import none; # filter!!1~1 export all; } protocol device { scan time 60; } protocol static { import all; route 10.0.0.0/8 blackhole; route 172.16.0.0/12 blackhole; route 192.168.0.0/16 blackhole; debug all; } protocol ospf ospf1918 { area 0.0.0.0 { interface "eth2" { authentication cryptographic; password "xxxx" { id 25; }; }; interface "eth1" { stub; }; interface "lo" { stub; }; }; } protocol bgp bgp1918_knud { import all; local as 64521; source address 10.140.59.20; keepalive time 20; hold time 60; neighbor 10.140.59.16 as 64521; } protocol bgp bgp1918_oele { import all; local as 64521; source address 10.140.59.20; keepalive time 20; hold time 60; neighbor 10.140.59.18 as 64521; } I tried to explicitely add "listen bgp address 0.0.0.0 port 179;" to the config, but still no listening 179. Logs do not show any errors or warnings why the listening socket is not opened... Jan 20 14:29:12 cabbage bird: bgp1918_knud: Initializing Jan 20 14:29:12 cabbage bird: bgp1918_oele: Initializing Jan 20 14:29:12 cabbage bird: bgp1918_knud: Starting Jan 20 14:29:12 cabbage bird: bgp1918_oele: Starting Jan 20 14:29:12 cabbage bird: bgp1918_oele: Waiting for 10.140.59.18 to become my neighbor Jan 20 14:29:12 cabbage bird: bgp1918_knud: Waiting for 10.140.59.16 to become my neighbor Here's some output of show protocols. bird> show protocols all bgp1918_oele name proto table state since info bgp1918_oele BGP master start 14:19 Idle Preference: 100 Input filter: ACCEPT Output filter: REJECT Routes: 0 imported, 0 exported, 0 preferred Route change stats: received rejected filtered ignored accepted Import updates: 0 0 0 0 0 Import withdraws: 0 0 --- 0 0 Export updates: 0 0 0 --- 0 Export withdraws: 0 --- --- --- 0 BGP state: Idle Neighbor address: 10.140.59.18 Neighbor AS: 64521 -- Hans van Kranenburg - System / Network Engineer T +31 (0)10 2760434 | hans.van.kranenburg(a)mendix.com | www.mendix.com

2 4