23 Nov
2020
23 Nov
'20
8:36 a.m.
Yep, I see your /24 as announced now on a customer's router:
--
$ show ip bgp 44.135.59.0
BGP routing table entry for 44.135.59.0/24
Paths: (2 available, best #2, table Default-IP-Routing-Table)
Advertised to non peer-group peers:
193.30.110.29
39923 2914 20473
193.30.110.29 (metric 1) from 193.30.110.29 (193.30.110.29)
Origin IGP, metric 0, localpref 100, valid, internal
Community: 2914:410 2914:1009 2914:2000 2914:3000 20473:11 20473:4000 39641:1003
39923:2914
Last update: Mon Nov 23 15:30:49 2020
39923 2914 20473
109.68.160.108 from 109.68.160.108 (109.68.160.2)
Origin IGP, metric 0, localpref 100, valid, external, best
Community: 39641:1003
Last update: Mon Nov 23 15:30:49 2020
--
And your .1 is also reachable from Europe:
--
17. 44.135.59.1
0.0% 2 108.6 107.9 107.3 108.6 0.9
--
73
Ruben ON3RVH
-----Original Message-----
From: 44Net <44net-bounces+on3rvh=on3rvh.be(a)mailman.ampr.org> On Behalf Of pete M
via 44Net
Sent: Monday, November 23, 2020 15:32
To: AMPRNet working group <44net(a)mailman.ampr.org>
Cc: pete M <petem001(a)hotmail.com>
Subject: Re: [44net] now what is he next step
After changing the conf file I have now
birdc show route
BIRD 1.6.6 ready.
44.135.59.0/24 via 207.246.122.57 on ens3 [static1 14:30:41] * (200)
sounds better
________________________________________
De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la part de pete
M via 44Net <44net(a)mailman.ampr.org> Envoyé : 23 novembre 2020 09:29 À : Ruben
ON3RVH; AMPRNet working group Cc : pete M Objet : Re: [44net] now what is he next step
birdc show route
BIRD 1.6.6 ready.
44.135.59.1/32 dev dummy1 [direct1 13:31:07] * (240)
I will change the bird conf file to
protocol static
{
route 44.135.59.0/24 via 207.246.122.57; }
I hope this will "fix" something on the BGP side
________________________________________
De : Ruben ON3RVH <on3rvh(a)on3rvh.be>
Envoyé : 23 novembre 2020 09:26
À : pete M; AMPRNet working group
Objet : RE: [44net] now what is he next step
Hey Pete,
From what I am reading and comparing the Vultr docs,
you either need
--
protocol static
{
route 44.135.59.0/24 via 207.246.122.57; }
protocol device
{
scan time 5;
}
--
Or
--
protocol direct
{
interface "dummy1";
import all; <---- this part
}
--
I would recommend the first, being the static protocol. That way your more specifics over
the vpn will work too.
What does "birdc show route" tell you?
73
Ruben ON3RVH
-----Original Message-----
From: pete M <petem001(a)hotmail.com>
Sent: Monday, November 23, 2020 15:22
To: Ruben ON3RVH <on3rvh(a)on3rvh.be>be>; AMPRNet working group
<44net(a)mailman.ampr.org>
Subject: Re: [44net] now what is he next step
thanks for jumping in Ruben
here is a copy and paste of my bird.conf I of course changed some secret information.
log "/var/log/bird.log" all;
router id 207.246.122.57;
protocol device
{
scan time 60;
}
protocol direct
{
interface "dummy1";
}
protocol bgp vultr
{
local as 4288000072;
source address 207.246.122.57;
import none;
export all;
graceful restart on;
next hop self;
multihop 2;
neighbor 169.254.169.254 as 64515;
password "Secret" ;
}
________________________________________
De : Ruben ON3RVH <on3rvh(a)on3rvh.be>
Envoyé : 23 novembre 2020 09:13
À : AMPRNet working group
Cc : pete M
Objet : RE: [44net] now what is he next step
Pete,
Can you share your bird config please?
The dummy interface is indeed not needed, but I would recommend a nullroute for your /24.
In case your vpn clients faisl, the source will not get stuck in an routing loop.
But let's have a look at your bird config first please.
Either Bird is not running, or it is not announcing your subnet to Vultr.
73
Ruben ON3RVH
-----Original Message-----
From: 44Net <44net-bounces+on3rvh=on3rvh.be(a)mailman.ampr.org> On Behalf Of pete M
via 44Net
Sent: Monday, November 23, 2020 14:56
To: AMPRNet working group <44net(a)mailman.ampr.org>
Cc: pete M <petem001(a)hotmail.com>
Subject: Re: [44net] now what is he next step
Thanks James.
That is what I was thinking.
Anyone can give me some pointer on how to debug bird?
the logs are not doing much to help.
________________________________________
De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la part de James
Colderwood via 44Net <44net(a)mailman.ampr.org> Envoyé : 23 novembre 2020 08:48 À :
AMPRNet working group Cc : James Colderwood Objet : Re: [44net] now what is he next step
FWIW I can't see your announcements in my BGP table.
--
Kind Regards
James B Colderwood
M0ZAH
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net