session established, no routes
Tiemen Ruiten
t.ruiten at tech-lab.io
Sun Nov 17 12:41:39 CET 2019
I compiled and installed Bird 1.6.8 from source and the following
configuration works:
log "/var/log/bird" all;
debug protocols all;
router id 95.179.136.70;
protocol device {
scan time 60;
}
protocol direct {
interface "dummy0";
}
protocol bgp vultr {
local as 64552;
source address 95.179.136.70;
neighbor 169.254.169.254 as 64515;
next hop self;
import none;
export all;
multihop 2;
password "XXXXXXXXXX";
}
[root at vultr-vm ~]# birdc show route
BIRD 1.6.8 ready.
209.250.247.219/32 dev dummy0 [direct1 11:25:34] * (240)
[root at vultr-vm ~]# birdc show proto all vultr
BIRD 1.6.8 ready.
name proto table state since info
vultr BGP master up 11:25:39 Established
Preference: 100
Input filter: REJECT
Output filter: ACCEPT
Routes: 0 imported, 1 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: 1 0 0 ---
1
Export withdraws: 0 --- --- ---
0
BGP state: Established
Neighbor address: 169.254.169.254
Neighbor AS: 64515
Neighbor ID: 45.76.40.53
Neighbor caps: refresh restart-aware AS4 add-path-rx
Session: external multihop AS4
Source address: 95.179.136.70
Hold timer: 140/180
Keepalive timer: 39/60
How do I adapt this config to working a 2.0 configuration?
On Sat, Nov 16, 2019 at 12:16 PM Tiemen Ruiten <t.ruiten at tech-lab.io> wrote:
> Apologies, forgot the subject line.
>
> On Sat, Nov 16, 2019 at 12:12 PM Tiemen Ruiten <t.ruiten at tech-lab.io>
> wrote:
>
>> Hello
>>
>> I'm a first time Bird user. I'm trying to route a Vultr floating IP to an
>> instance and the BGP session shows as established, but there are no routes:
>>
>> /etc/bird.conf:
>> log "/var/log/bird" all;
>>
>> debug protocols all;
>>
>> router id 95.179.136.70;
>>
>> protocol device {
>> scan time 60;
>> }
>>
>> protocol direct {
>> interface "dummy0";
>> }
>>
>> protocol bgp vultr {
>> local as 64552;
>> source address 95.179.136.70;
>> neighbor 169.254.169.254 as 64515;
>> ipv4 {
>> next hop self;
>> import none;
>> export all;
>> };
>> multihop 2;
>> password "XXXXXXXXXXXX";
>> }
>>
>> ip config:
>> [root at vultr-vm ~]# ip a
>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
>> default qlen 1000
>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> inet 127.0.0.1/8 scope host lo
>> valid_lft forever preferred_lft forever
>> inet6 ::1/128 scope host
>> valid_lft forever preferred_lft forever
>> 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
>> group default qlen 1000
>> link/ether 56:00:02:6a:51:a0 brd ff:ff:ff:ff:ff:ff
>> inet 95.179.136.70/23 brd 95.179.137.255 scope global dynamic
>> noprefixroute ens3
>> valid_lft 61854sec preferred_lft 61854sec
>> inet6 fe80::5400:2ff:fe6a:51a0/64 scope link noprefixroute
>> valid_lft forever preferred_lft forever
>> 3: ens7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc fq state UP
>> group default qlen 1000
>> link/ether 5a:00:02:6a:51:a0 brd ff:ff:ff:ff:ff:ff
>> inet 10.7.96.4/16 brd 10.7.255.255 scope global noprefixroute ens7
>> valid_lft forever preferred_lft forever
>> inet6 fe80::5800:2ff:fe6a:51a0/64 scope link
>> valid_lft forever preferred_lft forever
>> 4: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state
>> UNKNOWN group default qlen 1000
>> link/ether 8e:74:ee:f1:97:70 brd ff:ff:ff:ff:ff:ff
>> inet 209.250.247.219/32 scope global dummy0
>> valid_lft forever preferred_lft forever
>> inet6 fe80::8c74:eeff:fef1:9770/64 scope link
>> valid_lft forever preferred_lft forever
>> [root at vultr-vm ~]# ip r
>> default via 95.179.136.1 dev ens3 proto dhcp metric 100
>> 10.7.0.0/16 dev ens7 proto kernel scope link src 10.7.96.4 metric 101
>> 95.179.136.0/23 dev ens3 proto kernel scope link src 95.179.136.70
>> metric 100
>> 169.254.169.254 via 95.179.136.1 dev ens3 proto dhcp metric 100
>>
>> "birdc show route":
>> BIRD 2.0.7 ready.
>>
>> "birdc show proto all vultr"
>> BIRD 2.0.7 ready.
>> Name Proto Table State Since Info
>> vultr BGP --- up 18:52:49.401 Established
>> BGP state: Established
>> Neighbor address: 169.254.169.254
>> Neighbor AS: 64515
>> Local AS: 64552
>> Neighbor ID: 45.76.40.53
>> Local capabilities
>> Multiprotocol
>> AF announced: ipv4
>> Route refresh
>> Graceful restart
>> 4-octet AS numbers
>> Enhanced refresh
>> Long-lived graceful restart
>> Neighbor capabilities
>> Multiprotocol
>> AF announced: ipv4
>> Route refresh
>> Graceful restart
>> 4-octet AS numbers
>> ADD-PATH
>> RX: ipv4
>> TX:
>> Session: external multihop AS4
>> Source address: 95.179.136.70
>> Hold timer: 111.091/180
>> Keepalive timer: 12.978/60
>> Channel ipv4
>> State: UP
>> Table: master4
>> Preference: 100
>> Input filter: REJECT
>> Output filter: ACCEPT
>> 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 Next hop: 95.179.136.70
>> IGP IPv4 table: master4
>>
>> /var/log/bird:
>> 2019-11-16 11:05:28.055 <TRACE> device1: Initializing
>> 2019-11-16 11:05:28.055 <TRACE> direct1: Initializing
>> 2019-11-16 11:05:28.055 <TRACE> vultr: Channel ipv4 connected to table
>> master4
>> 2019-11-16 11:05:28.055 <TRACE> vultr: Initializing
>> 2019-11-16 11:05:28.055 <TRACE> device1: Starting
>> 2019-11-16 11:05:28.055 <TRACE> device1: Scanning interfaces
>> 2019-11-16 11:05:28.055 <TRACE> device1: State changed to up
>> 2019-11-16 11:05:28.055 <TRACE> direct1: Starting
>> 2019-11-16 11:05:28.055 <TRACE> direct1: State changed to up
>> 2019-11-16 11:05:28.055 <TRACE> vultr: Starting
>> 2019-11-16 11:05:28.055 <TRACE> vultr: State changed to start
>> 2019-11-16 11:05:28.055 <INFO> Started
>> 2019-11-16 11:05:28.065 <TRACE> direct1 < interface lo goes up
>> 2019-11-16 11:05:28.065 <TRACE> direct1 < address 127.0.0.0/8 on
>> interface lo added
>> 2019-11-16 11:05:28.065 <TRACE> direct1 < address ::1/128 on interface lo
>> added
>> 2019-11-16 11:05:28.065 <TRACE> direct1 < interface ens3 goes up
>> 2019-11-16 11:05:28.065 <TRACE> direct1 < address 95.179.136.0/23 on
>> interface ens3 added
>> 2019-11-16 11:05:28.065 <TRACE> direct1 < address fe80::/64 on interface
>> ens3 added
>> 2019-11-16 11:05:28.065 <TRACE> direct1 < interface ens7 goes up
>> 2019-11-16 11:05:28.065 <TRACE> direct1 < address 10.7.0.0/16 on
>> interface ens7 added
>> 2019-11-16 11:05:28.065 <TRACE> direct1 < address fe80::/64 on interface
>> ens7 added
>> 2019-11-16 11:05:28.065 <TRACE> direct1 < interface dummy0 goes up
>> 2019-11-16 11:05:28.065 <TRACE> direct1 < address 209.250.247.219/32 on
>> interface dummy0 added
>> 2019-11-16 11:05:28.065 <TRACE> direct1 < address fe80::/64 on interface
>> dummy0 added
>> 2019-11-16 11:05:28.065 <TRACE> vultr: Started
>> 2019-11-16 11:05:28.065 <TRACE> vultr: Connect delayed by 5 seconds
>> 2019-11-16 11:05:30.408 <TRACE> vultr: Incoming connection from
>> 169.254.169.254 (port 46411) accepted
>> 2019-11-16 11:05:30.408 <TRACE> vultr: Sending
>> OPEN(ver=4,as=64552,hold=240,id=5fb38846)
>> 2019-11-16 11:05:30.409 <TRACE> vultr: Got
>> OPEN(as=64515,hold=180,id=45.76.40.53)
>> 2019-11-16 11:05:30.409 <TRACE> vultr: Sending KEEPALIVE
>> 2019-11-16 11:05:30.409 <TRACE> vultr: Got KEEPALIVE
>> 2019-11-16 11:05:30.409 <TRACE> vultr: BGP session established
>> 2019-11-16 11:05:30.409 <TRACE> vultr: State changed to up
>> 2019-11-16 11:05:30.409 <TRACE> vultr: Sending END-OF-RIB
>> 2019-11-16 11:05:32.432 <TRACE> vultr: Got UPDATE
>> 2019-11-16 11:05:32.432 <TRACE> vultr: Got END-OF-RIB
>> 2019-11-16 11:06:28.057 <TRACE> device1: Scanning interfaces
>> 2019-11-16 11:06:30.025 <TRACE> vultr: Sending KEEPALIVE
>> 2019-11-16 11:06:30.410 <TRACE> vultr: Got KEEPALIVE
>>
>> What am I missing?
>>
>> --
>> Tiemen Ruiten
>> Infrastructure Engineer
>>
>
>
> --
> Tiemen Ruiten
> Infrastructure Engineer
>
--
Tiemen Ruiten
Infrastructure Engineer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20191117/e5fd07db/attachment.htm>
More information about the Bird-users
mailing list