November 2020 - Bird-users

Tests fail on s390x
by Mark Stopka 16 Nov '20

16 Nov '20

Hi, I am packaging bird 2.0.7 for openSUSE s390x, and the tests are failing with the following: [ 48s] LD -Wl,-z,relro -pie -pthread -o obj/nest/a-path_test obj/nest/a-path_test.o ... [ 48s] obj/filter/tree_test 0.115749752s [ OK ] [ 49s] obj/filter/filter_test 0.700194688s [ OK ] [ 49s] obj/filter/trie_test 0.157692001s [ OK ] [ 49s] obj/lib/heap_test 0.011880888s [ OK ] [ 49s] obj/lib/buffer_test 0.002189509s [ OK ] [ 49s] obj/lib/event_test 0.000482824s [ OK ] [ 49s] obj/lib/flowspec_test 0.001865918s [ OK ] [ 49s] obj/lib/bitops_test 0.001912407s [ OK ] [ 49s] obj/lib/patmatch_test 0.000268604s [ OK ] [ 49s] obj/lib/fletcher16_test: t_fletcher16_compute 0.000228385s [FAIL] [ 49s] obj/lib/fletcher16_test: t_fletcher16_checksum 0.000196775s [FAIL] [ 49s] obj/lib/fletcher16_test 0.000489688s [FAIL] [ 49s] make: *** [Makefile:180: obj/lib/fletcher16_test.ok] Error 1 [ 49s] error: Bad exit status from /var/tmp/rpm-tmp.Y1ueWS (%check) [ 49s] Has anybody looked into that? Fedora "solved it" by simply disabling tests for s390x architecture, Debian and Ubuntu don't build Bird for s390x... -- Best regards / S pozdravem, BSc. Mark Stopka, BBA Managing Partner (at) PERLUR Group mobile: +420 704 373 561 website: www.perlur.cloud

3 5

Typo in doc/bird.conf.example2: MB-BGP -> MP-BGP
by Hexhu 15 Nov '20

15 Nov '20

Hi, In https://gitlab.nic.cz/labs/bird/-/blob/master/doc/bird.conf.example2, the comment says "This is an example configuration file for MB-BGP setting". Shouldn't it be MP-BGP setting? From git blame at https://gitlab.nic.cz/labs/bird/-/blame/master/doc/bird.conf.example2, the commit message says "Doc: Add MP-BGP example config file". It's quite trivial though 😂. Best regards, Hexhu

2 1

Filter route attribute "from"
by Alex Rydzewski 15 Nov '20

15 Nov '20

Good times, bird community! I'm have trouble with filter routes by "from" attribute. Routes in Bird route table have data about router which the route has originated from: 80.239.201.11/32 via 193.124.176.1 on eth1 [kernel1 2020-08-11] * (10) 10.0.0.0/30 via 10.0.0.18 on bond0 [MyOSPF 2020-11-09] * I (150/20) [172.21.1.1] 154.47.36.2/32 via 193.124.176.1 on eth1 [kernel1 2020-08-13] * (10) but if i try get that routes: show route where from = 172.21.1.1 I get empty respond without any errors. When I was add print statement to config for check which "from" attribute supplied to filter: export filter { print "route: ", net, ", ", from, ", ", proto,; accept; }; I was saw that from is 0.0.0.0: ... bird: route: 172.21.24.0/23, 0.0.0.0, MyOSPF The issue is observed with 1.4 and 1.6 bird versions. Explain me please, what i understand wrong about that?

2 1

Match Neighbor on Export Filter
by Marcelo Balbinot 10 Nov '20

10 Nov '20

Hello, I have a filter used in export by several protocols, I would like to apply MED to exported routes only for a specific protocol that uses this filter. I understand that one of the options would be to make another filter for this specific protocol, but will there be any way to execute an IF? Any idea? -- Marcelo Balbinot AS53062 +55 49 99923 9347 INOC 53062*100

4 3

redistributing static routes into OSPF, need to change next-hop
by Eugene M. Zheganin 07 Nov '20

07 Nov '20

Hello, How do I redistribute static routes into OSPF ? Suppose I have this: protocol static { route 10.101.6.61/32 via 172.16.0.70; } If the export filter will allow this route into OSPF, the neighbor will receive it with this very next-hop, and in the absense of direct connectivity to 172.16.0.70 (which is the case) it will complain "Received route 10.101.6.61/32 with strange next-hop 172.16.0.70" and refuse to install it into FIB. How do I change next-hop to the address of the originating router ? The BGP proto has the option "next hop self", which OSPF does not. Thanks. Eugene.

1 0

Limitations of BGP AS confederations?
by Erik Zscheile (Software Development) 07 Nov '20

07 Nov '20

Hello, in an article [1] (which was one of very few articles which I found about BIRD + BGP AS confederations) it is stated that currently, BGP AS confederations have the following limitation: > Bird won't consider the confederation part while calculating distance, which leads to weird routing results. > Bird neither provides a variable for the filter to calculate confederation length and make manual adjustments. > * bgp_path.len in Bird doesn't contain the length of Confederation, as stated above; (citation from section below "But there is some problem when using Confederation in Bird") The article seems to be tested against BIRD version 2.0.7. I'm not sure if that information is really correct, as I wasn't able to find any other source which stated that, but on the other hand, I also found no other source which explains BIRD + BGP AS confederation equally (or at least) that detailed. I (as of now) wasn't able to test it, but maybe I do that soon. (but I have no lab env running here, and didn't want to disrupt my currently working BGP setup, althrough it is not 'extremely' important if it is interrupted for a short amount of time...) ## If this is still an issue in the master branch: I think it would be a good idea to add an config option to conditionally enable "count confederation AS's in bgp_path.len / distance calculations" (or add another "method" on bgp_path and an option to switch the default AS-path-length calculation to that). * The statements above and the documentation combined sound like the confederation AS's are kept inside an aggregated, (unordered?) AS-set inside of bgp_path. Is that true? (I wasn't able to find any concrete documentation about this, and previously just thought that confederation AS's were kept as an sequence.) In BGP protocol terms [2], this would imply that either: * BIRD only uses AS_CONFED_SET's for the "confederation part" (under the assumption that these are treated like AS_SET), or * BIRD uses AS_CONFED_SEQUENCE as expected, but treats AS_SET, AS_CONFED_SET and AS_CONFED_SEQUENCE equally, even though that doesn't seem like a universally practicable choice. * Is there some easier way to fix this (either via configuration which I just missed or via patching of code)? * If not, is it possible to implement a more complex fix for this in a reasonable timeframe (e.g. not an excessive amount of work for a rather niche feature)? * If it is possible, where should I start implementing it (e.g. which parts of the BGP code are probably related to this, as I don't want to read all the BGP code multiple times just to find those places)? Regards, Erik Zscheile [1]: https://lantian.pub/en/article/modify-website/bird-confederation.lantian/ [2]: RFC 5065, page 5; https://www.rfc-editor.org/rfc/rfc5065.txt

2 3

BGP peer not established
by Truth Seeker 06 Nov '20

06 Nov '20

I am running bird 1.6.6. As shown in the following log messages, I have 2 BGP neighbors configured, but the sessions are not up. I keep getting those connection rejected messages. Anyone knows what’s the cause of it and how to fix it? Thanks in advance, Wei ============================================================================= 2020-10-29 17:58:27 <RMT> bgp1_rdomain_0: Error: Hold timer expired 2020-10-29 17:58:28 <WARN> bgp found listen socket for p:bgp1_rdomain_0 s_node:0000000000693770 s:0000000000693640 2020-10-29 17:58:48 <INFO> bgp1_rdomain_0: Incoming connection sk:0000000000693a30 from 10.0.143.81 (port 37163) rejected 2020-10-29 17:59:01 <INFO> bgp1_rdomain_0: Incoming connection sk:00000000007e6e80 from 10.0.143.81 (port 11955) rejected 2020-10-29 17:59:14 <INFO> bgp1_rdomain_0: Incoming connection sk:0000000000698de0 from 10.0.143.81 (port 43375) rejected 2020-10-29 18:56:28 <RMT> bgp2_rdomain_0: Error: Hold timer expired 2020-10-29 18:56:29 <WARN> bgp found listen socket for p:bgp2_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 18:56:59 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000006d39a0 from 10.0.142.81 (port 45446) rejected 2020-10-29 18:57:11 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000007f3de0 from 10.0.142.81 (port 36129) rejected 2020-10-29 18:57:16 <INFO> Processed 2 routes for message of size 40 2020-10-29 18:57:22 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000007f4140 from 10.0.142.81 (port 30384) rejected 2020-10-29 18:57:30 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9d50 from 10.0.142.81 (port 39059) accepted 2020-10-29 18:58:30 <INFO> Processed 2 routes for message of size 40 2020-10-29 19:25:16 <RMT> bgp2_rdomain_0: Error: Hold timer expired 2020-10-29 19:25:17 <WARN> bgp found listen socket for p:bgp2_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 19:25:48 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9d50 from 10.0.142.81 (port 32690) rejected 2020-10-29 19:26:02 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9d50 from 10.0.142.81 (port 52332) rejected 2020-10-29 19:55:43 <RMT> bgp2_rdomain_0: Error: Hold timer expired 2020-10-29 19:55:43 <WARN> bgp found listen socket for p:bgp2_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 19:55:53 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9d50 from 10.0.142.81 (port 49693) rejected 2020-10-29 19:56:07 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9d50 from 10.0.142.81 (port 34617) rejected 2020-10-29 19:56:21 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9d50 from 10.0.142.81 (port 16554) rejected 2020-10-29 19:56:30 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9d50 from 10.0.142.81 (port 40954) rejected 2020-10-29 19:59:26 <RMT> bgp2_rdomain_0: Error: Hold timer expired 2020-10-29 19:59:26 <WARN> bgp found listen socket for p:bgp3_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 19:59:26 <WARN> bgp found listen socket for p:bgp2_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 19:59:40 <INFO> bgp2_rdomain_0: Incoming connection sk:0000000000693b40 from 10.0.142.81 (port 48975) rejected 2020-10-29 19:59:50 <RMT> bgp1_rdomain_0: Error: Hold timer expired 2020-10-29 19:59:51 <WARN> bgp found listen socket for p:bgp1_rdomain_0 s_node:0000000000693770 s:0000000000693640 2020-10-29 19:59:52 <INFO> bgp2_rdomain_0: Incoming connection sk:0000000000693b40 from 10.0.142.81 (port 11000) rejected 2020-10-29 19:59:52 <INFO> bgp1_rdomain_0: Incoming connection sk:00000000006a3590 from 10.0.143.81 (port 19880) rejected 2020-10-29 20:00:00 <INFO> bgp1_rdomain_0: Incoming connection sk:00000000006a3590 from 10.0.143.81 (port 25771) rejected 2020-10-29 20:00:01 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000006a3590 from 10.0.142.81 (port 30442) rejected 2020-10-29 20:00:10 <INFO> bgp1_rdomain_0: Incoming connection sk:00000000006a3590 from 10.0.143.81 (port 44408) rejected 2020-10-29 20:00:10 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000006a3590 from 10.0.142.81 (port 47468) rejected 2020-10-29 20:00:18 <INFO> bgp1_rdomain_0: Incoming connection sk:00000000006a3590 from 10.0.143.81 (port 23674) rejected 2020-10-29 20:00:19 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000006a3590 from 10.0.142.81 (port 21274) rejected 2020-10-29 20:00:25 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000006d3b30 from 10.0.142.81 (port 14859) rejected 2020-10-29 20:00:28 <INFO> bgp1_rdomain_0: Incoming connection sk:00000000006d3b30 from 10.0.143.81 (port 43656) rejected 2020-10-29 20:00:33 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000006d3b30 from 10.0.142.81 (port 44701) rejected 2020-10-29 20:00:39 <INFO> bgp1_rdomain_0: Incoming connection sk:00000000006d3b30 from 10.0.143.81 (port 34627) rejected 2020-10-29 20:00:43 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000006d3bc0 from 10.0.142.81 (port 43653) rejected 2020-10-29 20:00:55 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000007f34f0 from 10.0.142.81 (port 53653) rejected 2020-10-29 20:01:07 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9200 from 10.0.142.81 (port 32885) accepted 2020-10-29 20:08:15 <RMT> bgp2_rdomain_0: Error: Hold timer expired 2020-10-29 20:08:16 <WARN> bgp found listen socket for p:bgp2_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 20:08:16 <RMT> bgp4_rdomain_0: Received: Hold timer expired 2020-10-29 20:08:16 <WARN> bgp found listen socket for p:bgp4_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 20:08:35 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9200 from 10.0.142.81 (port 39637) rejected 2020-10-29 20:08:45 <INFO> bgp2_rdomain_0: Incoming connection sk:000000000089f870 from 10.0.142.81 (port 25534) rejected 2020-10-29 20:08:58 <INFO> bgp2_rdomain_0: Incoming connection sk:000000000089f870 from 10.0.142.81 (port 34717) rejected 2020-10-29 20:09:06 <INFO> bgp4_rdomain_0: Incoming connection sk:000000000089f870 from 10.0.142.50 (port 57037) rejected 2020-10-29 20:09:09 <INFO> bgp2_rdomain_0: Incoming connection sk:000000000089f870 from 10.0.142.81 (port 43132) rejected 2020-10-29 20:09:10 <INFO> bgp4_rdomain_0: Incoming connection sk:000000000089f870 from 10.0.142.50 (port 52005) accepted 2020-10-29 20:12:39 <RMT> bgp3_rdomain_0: Error: Hold timer expired 2020-10-29 20:12:40 <WARN> bgp found listen socket for p:bgp3_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 20:13:27 <RMT> bgp4_rdomain_0: Error: Hold timer expired 2020-10-29 20:13:28 <WARN> bgp found listen socket for p:bgp4_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 20:14:24 <INFO> bgp4_rdomain_0: Incoming connection sk:00000000007e0710 from 10.0.142.50 (port 43162) accepted 2020-10-29 20:16:40 <RMT> bgp4_rdomain_0: Error: Hold timer expired 2020-10-29 20:16:41 <WARN> bgp found listen socket for p:bgp4_rdomain_0 s_node:0000000000693110 s:0000000000693140

1 0

BIRD2 BFD only listen on IPv6 or IPv4
by Stefan Plug 06 Nov '20

06 Nov '20

Hey guys, BIRD2 2.0.7 I want to run 2 BIRD2 Daemons, one with ipv4 config and one with ipv6 config, just like as with BIRD1 this works fine for BGP. However, I have noticed that it doesn’t seem possible (?) to point BFD within a daemon to only listen to ipv4 or ipv6 which will make both daemons listen to both protocols regardless of if they even have any ipv4 or ipv6 configuration. This means that if daemon1 was first then all BFD packets will got to daemon1 and not to daemon2, so no BFD will come up in daemon2. Is there a way to tell BIRD2 to only listen to ipv4 or ipv6 with BFD? Kind regards, Stefan -- Stefan Plug Network Engineer (EU) Phone: +49 160 2504854 ECIX, a Megaport company PEERING GmbH Tauentzienstraße 11 10789 Berlin Germany Office: +49 30 233 24 16-0 Web: www.ecix.net Sitz der Gesellschaft: Berlin, Germany. Registergericht: Amtsgericht Charlottenburg, HRB 97752B Vertretungsberechtigte Geschäftsführung: Vincent English, Bevan Slattery, Prokuristen: Stefan Wahl This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient please delete it and notify the sender.

3 4

How to change route gw on export to BGP neighbor?
by ico 04 Nov '20

04 Nov '20

Hello, I'm trying to to export some routes from our internal OSPF to BGP , both running in the same bird instance. I am able to filter those routes via BGP just fine (some tables connected via pipe). The problem is that all exported routes have private gw addresses (10.x.x.x). I am unable to configure bird to change gw of routes before then get sent to neighbors. Neighbors see original gateways from 10.0.0.0/8 range which is invalid/unreachable from outside of course. Here is also some simplyfied example, not showing OSPF setup etc. In this example I also don't show the pipes between tables. All of those doesn't seem to be important in this case. ######## router id 1.1.1.2; protocol kernel krnl4 { ipv4 { export all; import all; # route 2.2.2.0/24 gets into bird here }; learn; } protocol device { } protocol bgp { local 1.1.1.2 as 65000; neighbor 1.1.1.1 as 65000; strict bind; ipv4 { import none; export filter { # here I want to export routes with changed gateways bgp_next_hop = 1.1.1.5; # sets next hop but not gw gw = 1.1.1.5; # <ERR> filters, line XY: Invalid gw address print "export bgp ", net, " gw ", gw, " bnh ", bgp_next_hop; # <INFO> export bgp 2.2.2.0/24 gw 1.1.1.5 bnh 1.1.1.5 accept; }; }; } ######## With similar setup in a lab I was able to change those gw attributes on RECEIVING side in import filter to any arbitrary value I wanted. In real life I don't manage those BGP routers so I need to make sure to send correct routes. The example config prints changed gw but BGP peer sees the original gw. In some tests I got error "Invalid gw address" but now I don't have that config. Here it just ignores changed gw. Is there a configuration to achieve this? Thanks ico

2 3

BGP session not established correctly
by Truth Seeker 03 Nov '20

03 Nov '20

I am running bird 1.6.6. As shown in the following log messages, I have 2 BGP neighbors configured, but the sessions are not up. I keep getting those connection rejected messages. Anyone knows what’s the cause of it and how to fix it? Thanks in advance, Wei ============================================================================= 2020-10-29 17:58:27 <RMT> bgp1_rdomain_0: Error: Hold timer expired 2020-10-29 17:58:28 <WARN> bgp found listen socket for p:bgp1_rdomain_0 s_node:0000000000693770 s:0000000000693640 2020-10-29 17:58:48 <INFO> bgp1_rdomain_0: Incoming connection sk:0000000000693a30 from 10.0.143.81 (port 37163) rejected 2020-10-29 17:59:01 <INFO> bgp1_rdomain_0: Incoming connection sk:00000000007e6e80 from 10.0.143.81 (port 11955) rejected 2020-10-29 17:59:14 <INFO> bgp1_rdomain_0: Incoming connection sk:0000000000698de0 from 10.0.143.81 (port 43375) rejected 2020-10-29 18:56:28 <RMT> bgp2_rdomain_0: Error: Hold timer expired 2020-10-29 18:56:29 <WARN> bgp found listen socket for p:bgp2_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 18:56:59 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000006d39a0 from 10.0.142.81 (port 45446) rejected 2020-10-29 18:57:11 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000007f3de0 from 10.0.142.81 (port 36129) rejected 2020-10-29 18:57:16 <INFO> Processed 2 routes for message of size 40 2020-10-29 18:57:22 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000007f4140 from 10.0.142.81 (port 30384) rejected 2020-10-29 18:57:30 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9d50 from 10.0.142.81 (port 39059) accepted 2020-10-29 18:58:30 <INFO> Processed 2 routes for message of size 40 2020-10-29 19:25:16 <RMT> bgp2_rdomain_0: Error: Hold timer expired 2020-10-29 19:25:17 <WARN> bgp found listen socket for p:bgp2_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 19:25:48 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9d50 from 10.0.142.81 (port 32690) rejected 2020-10-29 19:26:02 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9d50 from 10.0.142.81 (port 52332) rejected 2020-10-29 19:55:43 <RMT> bgp2_rdomain_0: Error: Hold timer expired 2020-10-29 19:55:43 <WARN> bgp found listen socket for p:bgp2_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 19:55:53 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9d50 from 10.0.142.81 (port 49693) rejected 2020-10-29 19:56:07 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9d50 from 10.0.142.81 (port 34617) rejected 2020-10-29 19:56:21 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9d50 from 10.0.142.81 (port 16554) rejected 2020-10-29 19:56:30 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9d50 from 10.0.142.81 (port 40954) rejected 2020-10-29 19:59:26 <RMT> bgp2_rdomain_0: Error: Hold timer expired 2020-10-29 19:59:26 <WARN> bgp found listen socket for p:bgp3_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 19:59:26 <WARN> bgp found listen socket for p:bgp2_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 19:59:40 <INFO> bgp2_rdomain_0: Incoming connection sk:0000000000693b40 from 10.0.142.81 (port 48975) rejected 2020-10-29 19:59:50 <RMT> bgp1_rdomain_0: Error: Hold timer expired 2020-10-29 19:59:51 <WARN> bgp found listen socket for p:bgp1_rdomain_0 s_node:0000000000693770 s:0000000000693640 2020-10-29 19:59:52 <INFO> bgp2_rdomain_0: Incoming connection sk:0000000000693b40 from 10.0.142.81 (port 11000) rejected 2020-10-29 19:59:52 <INFO> bgp1_rdomain_0: Incoming connection sk:00000000006a3590 from 10.0.143.81 (port 19880) rejected 2020-10-29 20:00:00 <INFO> bgp1_rdomain_0: Incoming connection sk:00000000006a3590 from 10.0.143.81 (port 25771) rejected 2020-10-29 20:00:01 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000006a3590 from 10.0.142.81 (port 30442) rejected 2020-10-29 20:00:10 <INFO> bgp1_rdomain_0: Incoming connection sk:00000000006a3590 from 10.0.143.81 (port 44408) rejected 2020-10-29 20:00:10 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000006a3590 from 10.0.142.81 (port 47468) rejected 2020-10-29 20:00:18 <INFO> bgp1_rdomain_0: Incoming connection sk:00000000006a3590 from 10.0.143.81 (port 23674) rejected 2020-10-29 20:00:19 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000006a3590 from 10.0.142.81 (port 21274) rejected 2020-10-29 20:00:25 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000006d3b30 from 10.0.142.81 (port 14859) rejected 2020-10-29 20:00:28 <INFO> bgp1_rdomain_0: Incoming connection sk:00000000006d3b30 from 10.0.143.81 (port 43656) rejected 2020-10-29 20:00:33 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000006d3b30 from 10.0.142.81 (port 44701) rejected 2020-10-29 20:00:39 <INFO> bgp1_rdomain_0: Incoming connection sk:00000000006d3b30 from 10.0.143.81 (port 34627) rejected 2020-10-29 20:00:43 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000006d3bc0 from 10.0.142.81 (port 43653) rejected 2020-10-29 20:00:55 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000007f34f0 from 10.0.142.81 (port 53653) rejected 2020-10-29 20:01:07 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9200 from 10.0.142.81 (port 32885) accepted 2020-10-29 20:08:15 <RMT> bgp2_rdomain_0: Error: Hold timer expired 2020-10-29 20:08:16 <WARN> bgp found listen socket for p:bgp2_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 20:08:16 <RMT> bgp4_rdomain_0: Received: Hold timer expired 2020-10-29 20:08:16 <WARN> bgp found listen socket for p:bgp4_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 20:08:35 <INFO> bgp2_rdomain_0: Incoming connection sk:00000000008a9200 from 10.0.142.81 (port 39637) rejected 2020-10-29 20:08:45 <INFO> bgp2_rdomain_0: Incoming connection sk:000000000089f870 from 10.0.142.81 (port 25534) rejected 2020-10-29 20:08:58 <INFO> bgp2_rdomain_0: Incoming connection sk:000000000089f870 from 10.0.142.81 (port 34717) rejected 2020-10-29 20:09:06 <INFO> bgp4_rdomain_0: Incoming connection sk:000000000089f870 from 10.0.142.50 (port 57037) rejected 2020-10-29 20:09:09 <INFO> bgp2_rdomain_0: Incoming connection sk:000000000089f870 from 10.0.142.81 (port 43132) rejected 2020-10-29 20:09:10 <INFO> bgp4_rdomain_0: Incoming connection sk:000000000089f870 from 10.0.142.50 (port 52005) accepted 2020-10-29 20:12:39 <RMT> bgp3_rdomain_0: Error: Hold timer expired 2020-10-29 20:12:40 <WARN> bgp found listen socket for p:bgp3_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 20:13:27 <RMT> bgp4_rdomain_0: Error: Hold timer expired 2020-10-29 20:13:28 <WARN> bgp found listen socket for p:bgp4_rdomain_0 s_node:0000000000693110 s:0000000000693140 2020-10-29 20:14:24 <INFO> bgp4_rdomain_0: Incoming connection sk:00000000007e0710 from 10.0.142.50 (port 43162) accepted 2020-10-29 20:16:40 <RMT> bgp4_rdomain_0: Error: Hold timer expired 2020-10-29 20:16:41 <WARN> bgp found listen socket for p:bgp4_rdomain_0 s_node:0000000000693110 s:0000000000693140

1 0