Hi I finally got my bpg annonce working, bird do works i have 2 interface on the machine,
as stated here: 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 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 56:00:02:fc:bd:ba brd ff:ff:ff:ff:ff:ff inet 207.246.122.57/23 brd 207.246.123.255 scope global dynamic ens3 valid_lft 72787sec preferred_lft 72787sec 3: dummy1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 9e:fe:80:f5:a5:e2 brd ff:ff:ff:ff:ff:ff inet 44.135.59.0/24 brd 44.135.59.255 scope global dummy1 valid_lft forever preferred_lft forever
when I list my route I have this:
route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 207.246.122.1 0.0.0.0 UG 0 0 0 ens3 44.135.59.0 0.0.0.0 255.255.255.0 U 0 0 0 dummy1 169.254.169.254 207.246.122.1 255.255.255.255 UGH 0 0 0 ens3 207.246.122.0 0.0.0.0 255.255.254.0 U 0 0 0 ens3
Now my next thing is to have an openvpn server so that the client can use address from the /24 as there ip adress to the world. (openvpn is a vpn solution, but if you have other/better solution I am open).
one little other thing. will the connection by the vpn be limited to one ip address by tunel or can I specify the number of address available by client configuration?
one other thing, is there a dashboard to control/monitor by a web interface a server like openvpn?
thanks
Pierre VE2PF
Pierre,
Does your current configuration work? If you used the vultr BGP guide then you are announcing your /24 route statically. You needn't assign your network address to dummy1. You only need 44.135.59.1/32 there. Once you set up your vpn interfaces you may wind up with more IPs for your router and the dummy will be redundant although many like having the .1 there as well.
There are many guides to openvpn setup. I personally have used it with private IPs in peer-to-peer. This saves you from wasting more space in your /24 for peering. Once your p2p connection is made (for instance with your VPS as 172.16.44.1/30 and another end at 172.16.44.2/30) you can set a static route to send 44.135.59.128/25 to 172.16.44.2.
The way I did this in OpenVPN was using minimal configuration and pre-shared keys as described here: https://dn42.eu/howto/openvpn. I did not use ifconfig in my configuration though, I had it set in /etc/network/interfaces.d which I have lost. This way I could use a pre-up to launch openvpn, and a post-up command to add the static route (ie: post-up ip route add 44.x.x.x/25 via 172.16.44.2).
I hope this helps get you started.
Regards, Scott.
On Sun, Nov 22, 2020 at 8:57 PM pete M via 44Net 44net@mailman.ampr.org wrote:
Hi I finally got my bpg annonce working, bird do works i have 2 interface on the machine,
as stated here: 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 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 56:00:02:fc:bd:ba brd ff:ff:ff:ff:ff:ff inet 207.246.122.57/23 brd 207.246.123.255 scope global dynamic ens3 valid_lft 72787sec preferred_lft 72787sec 3: dummy1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 9e:fe:80:f5:a5:e2 brd ff:ff:ff:ff:ff:ff inet 44.135.59.0/24 brd 44.135.59.255 scope global dummy1 valid_lft forever preferred_lft forever
when I list my route I have this:
route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 207.246.122.1 0.0.0.0 UG 0 0 0 ens3 44.135.59.0 0.0.0.0 255.255.255.0 U 0 0 0 dummy1 169.254.169.254 207.246.122.1 255.255.255.255 UGH 0 0 0 ens3 207.246.122.0 0.0.0.0 255.255.254.0 U 0 0 0 ens3
Now my next thing is to have an openvpn server so that the client can use address from the /24 as there ip adress to the world. (openvpn is a vpn solution, but if you have other/better solution I am open).
one little other thing. will the connection by the vpn be limited to one ip address by tunel or can I specify the number of address available by client configuration?
one other thing, is there a dashboard to control/monitor by a web interface a server like openvpn?
thanks
Pierre VE2PF
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Hi Scott,
I am no networking Guru and this whole project is for helping me learn a bit more. I followed the How to from Vultr to the letter. beside having to modify /etc/network/interface file so that the dummy interface get up and down as needed
Here is a copy
----------------------------------- auto lo iface lo inet loopback
auto ens3 allow-hotplug ens3 iface ens3 inet dhcp iface ens3 inet6 auto
auto dummy1 iface dummy1 inet static address 44.135.59.0/24 pre-up ip link add dummy1 type dummy post-down ip link del dummy1 ------------------------------------------
Are you saying that I should have my dummy1 interface to only have 44.135.59.1/32 assigned?
On the openvpn side I will take a look.
I am not sure I understand the last part about "/etc/network/interfaces.d which I have lost"
Thanks for the information I will go and read a bit more.
Pierre VE2PF
________________________________________ De : Scott Nicholas scott.nicholas@scottn.us Envoyé : 23 novembre 2020 00:45 À : AMPRNet working group Cc : pete M Objet : Re: [44net] now what is he next step
Pierre,
Does your current configuration work? If you used the vultr BGP guide then you are announcing your /24 route statically. You needn't assign your network address to dummy1. You only need 44.135.59.1/32 there. Once you set up your vpn interfaces you may wind up with more IPs for your router and the dummy will be redundant although many like having the .1 there as well.
There are many guides to openvpn setup. I personally have used it with private IPs in peer-to-peer. This saves you from wasting more space in your /24 for peering. Once your p2p connection is made (for instance with your VPS as 172.16.44.1/30 and another end at 172.16.44.2/30) you can set a static route to send 44.135.59.128/25 to 172.16.44.2.
The way I did this in OpenVPN was using minimal configuration and pre-shared keys as described here: https://dn42.eu/howto/openvpn. I did not use ifconfig in my configuration though, I had it set in /etc/network/interfaces.d which I have lost. This way I could use a pre-up to launch openvpn, and a post-up command to add the static route (ie: post-up ip route add 44.x.x.x/25 via 172.16.44.2).
I hope this helps get you started.
Regards, Scott.
On Sun, Nov 22, 2020 at 8:57 PM pete M via 44Net 44net@mailman.ampr.org wrote:
Hi I finally got my bpg annonce working, bird do works i have 2 interface on the machine,
as stated here: 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 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 56:00:02:fc:bd:ba brd ff:ff:ff:ff:ff:ff inet 207.246.122.57/23 brd 207.246.123.255 scope global dynamic ens3 valid_lft 72787sec preferred_lft 72787sec 3: dummy1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 9e:fe:80:f5:a5:e2 brd ff:ff:ff:ff:ff:ff inet 44.135.59.0/24 brd 44.135.59.255 scope global dummy1 valid_lft forever preferred_lft forever
when I list my route I have this:
route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 207.246.122.1 0.0.0.0 UG 0 0 0 ens3 44.135.59.0 0.0.0.0 255.255.255.0 U 0 0 0 dummy1 169.254.169.254 207.246.122.1 255.255.255.255 UGH 0 0 0 ens3 207.246.122.0 0.0.0.0 255.255.254.0 U 0 0 0 ens3
Now my next thing is to have an openvpn server so that the client can use address from the /24 as there ip adress to the world. (openvpn is a vpn solution, but if you have other/better solution I am open).
one little other thing. will the connection by the vpn be limited to one ip address by tunel or can I specify the number of address available by client configuration?
one other thing, is there a dashboard to control/monitor by a web interface a server like openvpn?
thanks
Pierre VE2PF
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Well I am not sure my bgp is working.
Here is the log of bird. I got since I fixed the file ownership problem 2020-11-22 19:56:45 <INFO> Started 2020-11-22 21:57:48 <INFO> Shutting down 2020-11-22 21:57:48 <FATAL> Shutdown completed 2020-11-22 21:58:07 <INFO> Started 2020-11-23 13:30:53 <INFO> Shutting down 2020-11-23 13:30:53 <FATAL> Shutdown completed 2020-11-23 13:31:09 <INFO> Started
------------------------------------------
when I try to do a traceroute from my home network the pasket still go toward ucsd.
------------------------------------------ 6 20 ms 20 ms 16 ms be3259.ccr31.yyz02.atlas.cogentco.com [154.54.41.205] 7 20 ms 18 ms 20 ms ae-4.bar4.Toronto1.Level3.net [4.68.38.245] 8 * * * Délai d’attente de la demande dépassé. 9 75 ms 78 ms 78 ms CENIC.ear1.SanJose1.Level3.net [4.15.122.46] 10 77 ms 77 ms 79 ms dc-svl-agg8--svl-agg10-300g.cenic.net [137.164.11.81] 11 81 ms 81 ms 85 ms dc-lax-agg8--svl-agg8-100ge-1.cenic.net [137.164.11.0] 12 83 ms 82 ms 81 ms dc-tus-agg8--lax-agg8-300g.cenic.net [137.164.11.83] 13 83 ms 80 ms 83 ms dc-sdg-agg4--tus-agg8-300g.cenic.net [137.164.11.85] 14 83 ms 81 ms 82 ms dc-ucsd-100ge--sdg-agg4.cenic.net [137.164.23.177] 15 82 ms 90 ms 81 ms mcore-flow-bypass-mx0-p2p.ucsd.edu [132.239.254.61] 16 86 ms 82 ms 83 ms sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu [132.239.255.50]
-------------------------------------------
I was doing a traceroute to 44.135.59.1 As I have set my dummy1 interface to that address.
On the local machine I can ping and traceroute that ip as it should.
------------------------------------------- root@hamrad:~# traceroute 44 traceroute to 44 (0.0.0.44), 30 hops max, 60 byte packets connect: Invalid argument root@hamrad:~# traceroute 44.135.59.1 traceroute to 44.135.59.1 (44.135.59.1), 30 hops max, 60 byte packets 1 44.135.59.1 (44.135.59.1) 0.142 ms 0.026 ms 0.013 ms root@hamrad:~# ping 44.135.59.1 PING 44.135.59.1 (44.135.59.1) 56(84) bytes of data. 64 bytes from 44.135.59.1: icmp_seq=1 ttl=64 time=0.052 ms 64 bytes from 44.135.59.1: icmp_seq=2 ttl=64 time=0.068 ms 64 bytes from 44.135.59.1: icmp_seq=3 ttl=64 time=0.076 ms ^C --- 44.135.59.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 39ms rtt min/avg/max/mdev = 0.052/0.065/0.076/0.012 ms
------------------------------------------
Now I am really lost.
________________________________________ De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de pete M via 44Net 44net@mailman.ampr.org Envoyé : 23 novembre 2020 08:20 À : AMPRNet working group Cc : pete M Objet : Re: [44net] now what is he next step
Hi Scott,
I am no networking Guru and this whole project is for helping me learn a bit more. I followed the How to from Vultr to the letter. beside having to modify /etc/network/interface file so that the dummy interface get up and down as needed
Here is a copy
----------------------------------- auto lo iface lo inet loopback
auto ens3 allow-hotplug ens3 iface ens3 inet dhcp iface ens3 inet6 auto
auto dummy1 iface dummy1 inet static address 44.135.59.0/24 pre-up ip link add dummy1 type dummy post-down ip link del dummy1 ------------------------------------------
Are you saying that I should have my dummy1 interface to only have 44.135.59.1/32 assigned?
On the openvpn side I will take a look.
I am not sure I understand the last part about "/etc/network/interfaces.d which I have lost"
Thanks for the information I will go and read a bit more.
Pierre VE2PF
________________________________________ De : Scott Nicholas scott.nicholas@scottn.us Envoyé : 23 novembre 2020 00:45 À : AMPRNet working group Cc : pete M Objet : Re: [44net] now what is he next step
Pierre,
Does your current configuration work? If you used the vultr BGP guide then you are announcing your /24 route statically. You needn't assign your network address to dummy1. You only need 44.135.59.1/32 there. Once you set up your vpn interfaces you may wind up with more IPs for your router and the dummy will be redundant although many like having the .1 there as well.
There are many guides to openvpn setup. I personally have used it with private IPs in peer-to-peer. This saves you from wasting more space in your /24 for peering. Once your p2p connection is made (for instance with your VPS as 172.16.44.1/30 and another end at 172.16.44.2/30) you can set a static route to send 44.135.59.128/25 to 172.16.44.2.
The way I did this in OpenVPN was using minimal configuration and pre-shared keys as described here: https://dn42.eu/howto/openvpn. I did not use ifconfig in my configuration though, I had it set in /etc/network/interfaces.d which I have lost. This way I could use a pre-up to launch openvpn, and a post-up command to add the static route (ie: post-up ip route add 44.x.x.x/25 via 172.16.44.2).
I hope this helps get you started.
Regards, Scott.
On Sun, Nov 22, 2020 at 8:57 PM pete M via 44Net 44net@mailman.ampr.org wrote:
Hi I finally got my bpg annonce working, bird do works i have 2 interface on the machine,
as stated here: 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 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 56:00:02:fc:bd:ba brd ff:ff:ff:ff:ff:ff inet 207.246.122.57/23 brd 207.246.123.255 scope global dynamic ens3 valid_lft 72787sec preferred_lft 72787sec 3: dummy1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 9e:fe:80:f5:a5:e2 brd ff:ff:ff:ff:ff:ff inet 44.135.59.0/24 brd 44.135.59.255 scope global dummy1 valid_lft forever preferred_lft forever
when I list my route I have this:
route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 207.246.122.1 0.0.0.0 UG 0 0 0 ens3 44.135.59.0 0.0.0.0 255.255.255.0 U 0 0 0 dummy1 169.254.169.254 207.246.122.1 255.255.255.255 UGH 0 0 0 ens3 207.246.122.0 0.0.0.0 255.255.254.0 U 0 0 0 ens3
Now my next thing is to have an openvpn server so that the client can use address from the /24 as there ip adress to the world. (openvpn is a vpn solution, but if you have other/better solution I am open).
one little other thing. will the connection by the vpn be limited to one ip address by tunel or can I specify the number of address available by client configuration?
one other thing, is there a dashboard to control/monitor by a web interface a server like openvpn?
thanks
Pierre VE2PF
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
On 2020-11-23 13:43, pete M via 44Net wrote:
Well I am not sure my bgp is working.
Here is the log of bird. I got since I fixed the file ownership problem 2020-11-22 19:56:45 <INFO> Started 2020-11-22 21:57:48 <INFO> Shutting down 2020-11-22 21:57:48 <FATAL> Shutdown completed 2020-11-22 21:58:07 <INFO> Started 2020-11-23 13:30:53 <INFO> Shutting down 2020-11-23 13:30:53 <FATAL> Shutdown completed 2020-11-23 13:31:09 <INFO> Started
when I try to do a traceroute from my home network the pasket still go toward ucsd.
6 20 ms 20 ms 16 ms be3259.ccr31.yyz02.atlas.cogentco.com [154.54.41.205] 7 20 ms 18 ms 20 ms ae-4.bar4.Toronto1.Level3.net [4.68.38.245] 8 * * * Délai d’attente de la demande dépassé. 9 75 ms 78 ms 78 ms CENIC.ear1.SanJose1.Level3.net [4.15.122.46] 10 77 ms 77 ms 79 ms dc-svl-agg8--svl-agg10-300g.cenic.net [137.164.11.81] 11 81 ms 81 ms 85 ms dc-lax-agg8--svl-agg8-100ge-1.cenic.net [137.164.11.0] 12 83 ms 82 ms 81 ms dc-tus-agg8--lax-agg8-300g.cenic.net [137.164.11.83] 13 83 ms 80 ms 83 ms dc-sdg-agg4--tus-agg8-300g.cenic.net [137.164.11.85] 14 83 ms 81 ms 82 ms dc-ucsd-100ge--sdg-agg4.cenic.net [137.164.23.177] 15 82 ms 90 ms 81 ms mcore-flow-bypass-mx0-p2p.ucsd.edu [132.239.254.61] 16 86 ms 82 ms 83 ms sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu [132.239.255.50]
I was doing a traceroute to 44.135.59.1 As I have set my dummy1 interface to that address.
On the local machine I can ping and traceroute that ip as it should.
root@hamrad:~# traceroute 44 traceroute to 44 (0.0.0.44), 30 hops max, 60 byte packets connect: Invalid argument root@hamrad:~# traceroute 44.135.59.1 traceroute to 44.135.59.1 (44.135.59.1), 30 hops max, 60 byte packets 1 44.135.59.1 (44.135.59.1) 0.142 ms 0.026 ms 0.013 ms root@hamrad:~# ping 44.135.59.1 PING 44.135.59.1 (44.135.59.1) 56(84) bytes of data. 64 bytes from 44.135.59.1: icmp_seq=1 ttl=64 time=0.052 ms 64 bytes from 44.135.59.1: icmp_seq=2 ttl=64 time=0.068 ms 64 bytes from 44.135.59.1: icmp_seq=3 ttl=64 time=0.076 ms ^C --- 44.135.59.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 39ms rtt min/avg/max/mdev = 0.052/0.065/0.076/0.012 ms
Now I am really lost.
De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de pete M via 44Net 44net@mailman.ampr.org Envoyé : 23 novembre 2020 08:20 À : AMPRNet working group Cc : pete M Objet : Re: [44net] now what is he next step
Hi Scott,
I am no networking Guru and this whole project is for helping me learn a bit more. I followed the How to from Vultr to the letter. beside having to modify /etc/network/interface file so that the dummy interface get up and down as needed
Here is a copy
auto lo iface lo inet loopback
auto ens3 allow-hotplug ens3 iface ens3 inet dhcp iface ens3 inet6 auto
auto dummy1 iface dummy1 inet static address 44.135.59.0/24 pre-up ip link add dummy1 type dummy post-down ip link del dummy1
Are you saying that I should have my dummy1 interface to only have 44.135.59.1/32 assigned?
On the openvpn side I will take a look.
I am not sure I understand the last part about "/etc/network/interfaces.d which I have lost"
Thanks for the information I will go and read a bit more.
Pierre VE2PF
De : Scott Nicholas scott.nicholas@scottn.us Envoyé : 23 novembre 2020 00:45 À : AMPRNet working group Cc : pete M Objet : Re: [44net] now what is he next step
Pierre,
Does your current configuration work? If you used the vultr BGP guide then you are announcing your /24 route statically. You needn't assign your network address to dummy1. You only need 44.135.59.1/32 there. Once you set up your vpn interfaces you may wind up with more IPs for your router and the dummy will be redundant although many like having the .1 there as well.
There are many guides to openvpn setup. I personally have used it with private IPs in peer-to-peer. This saves you from wasting more space in your /24 for peering. Once your p2p connection is made (for instance with your VPS as 172.16.44.1/30 and another end at 172.16.44.2/30) you can set a static route to send 44.135.59.128/25 to 172.16.44.2.
The way I did this in OpenVPN was using minimal configuration and pre-shared keys as described here: https://dn42.eu/howto/openvpn. I did not use ifconfig in my configuration though, I had it set in /etc/network/interfaces.d which I have lost. This way I could use a pre-up to launch openvpn, and a post-up command to add the static route (ie: post-up ip route add 44.x.x.x/25 via 172.16.44.2).
I hope this helps get you started.
Regards, Scott.
On Sun, Nov 22, 2020 at 8:57 PM pete M via 44Net 44net@mailman.ampr.org wrote:
Hi I finally got my bpg annonce working, bird do works i have 2 interface on the machine,
as stated here: 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 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 56:00:02:fc:bd:ba brd ff:ff:ff:ff:ff:ff inet 207.246.122.57/23 brd 207.246.123.255 scope global dynamic ens3 valid_lft 72787sec preferred_lft 72787sec 3: dummy1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 9e:fe:80:f5:a5:e2 brd ff:ff:ff:ff:ff:ff inet 44.135.59.0/24 brd 44.135.59.255 scope global dummy1 valid_lft forever preferred_lft forever
when I list my route I have this:
route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 207.246.122.1 0.0.0.0 UG 0 0 0 ens3 44.135.59.0 0.0.0.0 255.255.255.0 U 0 0 0 dummy1 169.254.169.254 207.246.122.1 255.255.255.255 UGH 0 0 0 ens3 207.246.122.0 0.0.0.0 255.255.254.0 U 0 0 0 ens3
Now my next thing is to have an openvpn server so that the client can use address from the /24 as there ip adress to the world. (openvpn is a vpn solution, but if you have other/better solution I am open).
one little other thing. will the connection by the vpn be limited to one ip address by tunel or can I specify the number of address available by client configuration?
one other thing, is there a dashboard to control/monitor by a web interface a server like openvpn?
thanks
Pierre VE2PF
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
FWIW I can't see your announcements in my BGP table.
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@mailman.ampr.org de la part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
I'm mobile at the moment but last night I did ping the .0 successfully with low latency to east coast so I assume it was ok and in bgp then. Did you make any changes to bird since?
This gives overview of status: birdc show proto
can see more by putting the name at the end: birdc show proto vultr
In regards to previous question yes I believe just the .1/32 on dummy1 is best.
Regards, Scott
On Mon, Nov 23, 2020, 8:57 AM pete M via 44Net 44net@mailman.ampr.org wrote:
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@mailman.ampr.org de la part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
There seem to be a connection from vultr to my machine for BGP tcp 0 0 207.246.122.57.vu:42087 169.254.169.254:bgp ESTABLISHED the only thing I changed was on the dummy1 ip address to .1/32
here the result of birdc show proto BIRD 1.6.6 ready. name proto table state since info device1 Device master up 13:31:08 direct1 Direct master up 13:31:08 vultr BGP master up 13:31:12 Established
and birdc show proto vultr BIRD 1.6.6 ready. name proto table state since info vultr BGP master up 13:31:11 Established
________________________________________ De : Scott Nicholas scott.nicholas@scottn.us Envoyé : 23 novembre 2020 09:04 À : AMPRNet working group Cc : pete M Objet : Re: [44net] now what is he next step
I'm mobile at the moment but last night I did ping the .0 successfully with low latency to east coast so I assume it was ok and in bgp then. Did you make any changes to bird since?
This gives overview of status: birdc show proto
can see more by putting the name at the end: birdc show proto vultr
In regards to previous question yes I believe just the .1/32 on dummy1 is best.
Regards, Scott
On Mon, Nov 23, 2020, 8:57 AM pete M via 44Net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org> wrote: 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@mailman.ampr.orgmailto:hotmail.com@mailman.ampr.org> de la part de James Colderwood via 44Net <44net@mailman.ampr.orgmailto:44net@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@mailman.ampr.orgmailto:44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.orgmailto:44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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@mailman.ampr.org On Behalf Of pete M via 44Net Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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@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@mailman.ampr.org On Behalf Of pete M via 44Net Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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@hotmail.com Sent: Monday, November 23, 2020 15:22 To: Ruben ON3RVH on3rvh@on3rvh.be; AMPRNet working group 44net@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@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@mailman.ampr.org On Behalf Of pete M via 44Net Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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@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@hotmail.com Sent: Monday, November 23, 2020 15:22 To: Ruben ON3RVH on3rvh@on3rvh.be; AMPRNet working group 44net@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@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@mailman.ampr.org On Behalf Of pete M via 44Net Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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@mailman.ampr.org de la part de pete M via 44Net 44net@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@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@hotmail.com Sent: Monday, November 23, 2020 15:22 To: Ruben ON3RVH on3rvh@on3rvh.be; AMPRNet working group 44net@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@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@mailman.ampr.org On Behalf Of pete M via 44Net Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
And the route is now working. and tested positively. OUF! thanks guys.!
________________________________________ De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de pete M via 44Net 44net@mailman.ampr.org Envoyé : 23 novembre 2020 09:31 À : AMPRNet working group Cc : pete M Objet : 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@mailman.ampr.org de la part de pete M via 44Net 44net@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@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@hotmail.com Sent: Monday, November 23, 2020 15:22 To: Ruben ON3RVH on3rvh@on3rvh.be; AMPRNet working group 44net@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@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@mailman.ampr.org On Behalf Of pete M via 44Net Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Perhaps someone could do a write up for the Wiki?
Thanks, Chris
On 23 Nov 2020, at 14:35, pete M via 44Net 44net@mailman.ampr.org wrote:
And the route is now working. and tested positively. OUF! thanks guys.!
De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de pete M via 44Net 44net@mailman.ampr.org Envoyé : 23 novembre 2020 09:31 À : AMPRNet working group Cc : pete M Objet : 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@mailman.ampr.org de la part de pete M via 44Net 44net@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@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@hotmail.com Sent: Monday, November 23, 2020 15:22 To: Ruben ON3RVH on3rvh@on3rvh.be; AMPRNet working group 44net@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@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@mailman.ampr.org On Behalf Of pete M via 44Net Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
That is a good idea. And I would love to do it. But As you can see in my last few messages. I know just enough to break things, and my usage of the Shakespeare language is not that great..
________________________________________ De : G1FEF chris@g1fef.co.uk Envoyé : 23 novembre 2020 09:37 À : AMPRNet working group Cc : pete M Objet : Re: [44net] now what is he next step
Perhaps someone could do a write up for the Wiki?
Thanks, Chris
On 23 Nov 2020, at 14:35, pete M via 44Net 44net@mailman.ampr.org wrote:
And the route is now working. and tested positively. OUF! thanks guys.!
De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de pete M via 44Net 44net@mailman.ampr.org Envoyé : 23 novembre 2020 09:31 À : AMPRNet working group Cc : pete M Objet : 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@mailman.ampr.org de la part de pete M via 44Net 44net@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@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@hotmail.com Sent: Monday, November 23, 2020 15:22 To: Ruben ON3RVH on3rvh@on3rvh.be; AMPRNet working group 44net@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@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@mailman.ampr.org On Behalf Of pete M via 44Net Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Actually, the bird configuration is specific to Vultr.com. They have their process well documented on their site. It really is very clever and completely automated. I have another block through a local SP. It took them about three weeks to negotiate with all of their upstreams, At Vultr.com, within a few hours, it just worked. Less time if you already have a private ASN form them.
-Dave K9DC Indianapolis
On Nov 23, 2020, at 09:37, G1FEF via 44Net 44net@mailman.ampr.org wrote:
Perhaps someone could do a write up for the Wiki?
Thanks, Chris
I can have a look at starting a wiki section on bird.
There are so many ways but vultr is very popular. They sometimes have $2.50/m (without ipv4) which you can then announce ipv4 from.
I should have asked to see config, I assumed a static was set from guide. Sorry about that. Glad to hear it worked out.
-Scott
On Mon, Nov 23, 2020, 9:41 AM G1FEF via 44Net 44net@mailman.ampr.org wrote:
Perhaps someone could do a write up for the Wiki?
Thanks, Chris
On 23 Nov 2020, at 14:35, pete M via 44Net 44net@mailman.ampr.org
wrote:
And the route is now working. and tested positively. OUF! thanks guys.!
De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la
part de pete M via 44Net 44net@mailman.ampr.org
Envoyé : 23 novembre 2020 09:31 À : AMPRNet working group Cc : pete M Objet : 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@mailman.ampr.org de la
part de pete M via 44Net 44net@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@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@hotmail.com Sent: Monday, November 23, 2020 15:22 To: Ruben ON3RVH on3rvh@on3rvh.be; AMPRNet working group <
44net@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@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@mailman.ampr.org On Behalf
Of pete M via 44Net
Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la
part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Scott,
The complete config would be: —
log "/var/log/bird.log" all;
router id 207.246.122.57;
protocol device { scan time 60; }
protocol bgp vultr { local as 4288000072tel: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" ; }
protocol static { route 44.135.59.0/24 via 207.246.122.57; }
— Ruben - ON3RVH
On 23 Nov 2020, at 16:36, Scott Nicholas via 44Net 44net@mailman.ampr.org wrote:
I can have a look at starting a wiki section on bird.
There are so many ways but vultr is very popular. They sometimes have $2.50/m (without ipv4) which you can then announce ipv4 from.
I should have asked to see config, I assumed a static was set from guide. Sorry about that. Glad to hear it worked out.
-Scott
On Mon, Nov 23, 2020, 9:41 AM G1FEF via 44Net 44net@mailman.ampr.org wrote:
Perhaps someone could do a write up for the Wiki?
Thanks, Chris
On 23 Nov 2020, at 14:35, pete M via 44Net 44net@mailman.ampr.org wrote:
And the route is now working. and tested positively. OUF! thanks guys.!
________________________________________ De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de pete M via 44Net 44net@mailman.ampr.org Envoyé : 23 novembre 2020 09:31 À : AMPRNet working group Cc : pete M Objet : 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@mailman.ampr.org de la part de pete M via 44Net 44net@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@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@hotmail.com Sent: Monday, November 23, 2020 15:22 To: Ruben ON3RVH on3rvh@on3rvh.be; AMPRNet working group < 44net@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@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@mailman.ampr.org On Behalf Of pete M via 44Net Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
I can make a writeup on the wiki if you like and maybe also add a config for a mikrotik chr on vultr?
Ruben - ON3RVH
On 23 Nov 2020, at 16:36, Scott Nicholas via 44Net 44net@mailman.ampr.org wrote:
I can have a look at starting a wiki section on bird.
There are so many ways but vultr is very popular. They sometimes have $2.50/m (without ipv4) which you can then announce ipv4 from.
I should have asked to see config, I assumed a static was set from guide. Sorry about that. Glad to hear it worked out.
-Scott
On Mon, Nov 23, 2020, 9:41 AM G1FEF via 44Net 44net@mailman.ampr.org wrote:
Perhaps someone could do a write up for the Wiki?
Thanks, Chris
On 23 Nov 2020, at 14:35, pete M via 44Net 44net@mailman.ampr.org
wrote:
And the route is now working. and tested positively. OUF! thanks guys.!
De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la
part de pete M via 44Net 44net@mailman.ampr.org
Envoyé : 23 novembre 2020 09:31 À : AMPRNet working group Cc : pete M Objet : 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@mailman.ampr.org de la
part de pete M via 44Net 44net@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@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@hotmail.com Sent: Monday, November 23, 2020 15:22 To: Ruben ON3RVH on3rvh@on3rvh.be; AMPRNet working group <
44net@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@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@mailman.ampr.org On Behalf
Of pete M via 44Net
Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la
part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
If you start it before me I'll put my notes in yours.
I have some extras that cover changing preferred outgoing source ip, function to ignore own prefix coming back in (unlikely with a /24).
For what it's worth the static entry doesn't matter for this simple static announcement. I used the following without worrying my gateway ip:
protocol static me { route 44.38.10.0/24 unreachable; }
If you are getting default route by bgp instead of dhcp this sets preferred source ip
protocol kernel { scan time 20; import none; export filter { if source = RTS_STATIC then reject; if ifname = "wg_rtr" then krt_prefsrc = 192.168.255.249; else krt_prefsrc = 44.38.10.1; accept; }; }
There is also lots of policy routing fun that can be documented for the far end of tunnels to select path by source ip that should all go together.
Regards, Scott.
On Mon, Nov 23, 2020, 10:55 AM Ruben ON3RVH on3rvh@on3rvh.be wrote:
I can make a writeup on the wiki if you like and maybe also add a config for a mikrotik chr on vultr?
Ruben - ON3RVH
On 23 Nov 2020, at 16:36, Scott Nicholas via 44Net <
44net@mailman.ampr.org> wrote:
I can have a look at starting a wiki section on bird.
There are so many ways but vultr is very popular. They sometimes have $2.50/m (without ipv4) which you can then announce ipv4 from.
I should have asked to see config, I assumed a static was set from guide. Sorry about that. Glad to hear it worked out.
-Scott
On Mon, Nov 23, 2020, 9:41 AM G1FEF via 44Net 44net@mailman.ampr.org wrote:
Perhaps someone could do a write up for the Wiki?
Thanks, Chris
On 23 Nov 2020, at 14:35, pete M via 44Net 44net@mailman.ampr.org
wrote:
And the route is now working. and tested positively. OUF! thanks guys.!
De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la
part de pete M via 44Net 44net@mailman.ampr.org
Envoyé : 23 novembre 2020 09:31 À : AMPRNet working group Cc : pete M Objet : 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@mailman.ampr.org de la
part de pete M via 44Net 44net@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@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@hotmail.com Sent: Monday, November 23, 2020 15:22 To: Ruben ON3RVH on3rvh@on3rvh.be; AMPRNet working group <
44net@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@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@mailman.ampr.org On
Behalf
Of pete M via 44Net
Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la
part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Scott I don't know what is the guide you are talking about. But on the vultr website they don't talk about static section..
Take a look!
https://www.vultr.com/docs/high-availability-on-vultr-with-floating-ip-and-b...
So you were not wrong, I only did use a bad howto. which I do find strange that vultr promote the service with bogus instruction.
________________________________________ De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de Scott Nicholas via 44Net 44net@mailman.ampr.org Envoyé : 23 novembre 2020 10:35 À : AMPRNet working group Cc : Scott Nicholas Objet : Re: [44net] now what is he next step
I can have a look at starting a wiki section on bird.
There are so many ways but vultr is very popular. They sometimes have $2.50/m (without ipv4) which you can then announce ipv4 from.
I should have asked to see config, I assumed a static was set from guide. Sorry about that. Glad to hear it worked out.
-Scott
On Mon, Nov 23, 2020, 9:41 AM G1FEF via 44Net 44net@mailman.ampr.org wrote:
Perhaps someone could do a write up for the Wiki?
Thanks, Chris
On 23 Nov 2020, at 14:35, pete M via 44Net 44net@mailman.ampr.org
wrote:
And the route is now working. and tested positively. OUF! thanks guys.!
De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la
part de pete M via 44Net 44net@mailman.ampr.org
Envoyé : 23 novembre 2020 09:31 À : AMPRNet working group Cc : pete M Objet : 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@mailman.ampr.org de la
part de pete M via 44Net 44net@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@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@hotmail.com Sent: Monday, November 23, 2020 15:22 To: Ruben ON3RVH on3rvh@on3rvh.be; AMPRNet working group <
44net@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@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@mailman.ampr.org On Behalf
Of pete M via 44Net
Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la
part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Hey Pete,
I had another guide.
https://www.vultr.com/docs/configuring-bgp-on-vultr
I just did a google for the doc and came to that one :)
Ruben - ON3RVH
On 23 Nov 2020, at 17:21, pete M via 44Net 44net@mailman.ampr.org wrote:
Scott I don't know what is the guide you are talking about. But on the vultr website they don't talk about static section..
Take a look!
https://www.vultr.com/docs/high-availability-on-vultr-with-floating-ip-and-b...
So you were not wrong, I only did use a bad howto. which I do find strange that vultr promote the service with bogus instruction.
________________________________________ De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de Scott Nicholas via 44Net 44net@mailman.ampr.org Envoyé : 23 novembre 2020 10:35 À : AMPRNet working group Cc : Scott Nicholas Objet : Re: [44net] now what is he next step
I can have a look at starting a wiki section on bird.
There are so many ways but vultr is very popular. They sometimes have $2.50/m (without ipv4) which you can then announce ipv4 from.
I should have asked to see config, I assumed a static was set from guide. Sorry about that. Glad to hear it worked out.
-Scott
On Mon, Nov 23, 2020, 9:41 AM G1FEF via 44Net 44net@mailman.ampr.org wrote:
Perhaps someone could do a write up for the Wiki?
Thanks, Chris
On 23 Nov 2020, at 14:35, pete M via 44Net 44net@mailman.ampr.org wrote:
And the route is now working. and tested positively. OUF! thanks guys.!
________________________________________ De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de pete M via 44Net 44net@mailman.ampr.org Envoyé : 23 novembre 2020 09:31 À : AMPRNet working group Cc : pete M Objet : 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@mailman.ampr.org de la part de pete M via 44Net 44net@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@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@hotmail.com Sent: Monday, November 23, 2020 15:22 To: Ruben ON3RVH on3rvh@on3rvh.be; AMPRNet working group < 44net@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@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@mailman.ampr.org On Behalf Of pete M via 44Net Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
I can see that both of those guide have been edited the same day.
My search on google gave me the other guide. pretty odd.
This just prove that we are not ready yet to have bots helping us with every technical question we have!
Thanks again to everyone that helped..
Pierre (the only one with a large smile in line at the coffee shop this morning, even the mask don't hide it!) VE2PF
________________________________________ De : Ruben ON3RVH on3rvh@on3rvh.be Envoyé : 23 novembre 2020 11:25 À : AMPRNet working group Cc : pete M Objet : Re: [44net] now what is he next step
Hey Pete,
I had another guide.
https://www.vultr.com/docs/configuring-bgp-on-vultr
I just did a google for the doc and came to that one :)
Ruben - ON3RVH
On 23 Nov 2020, at 17:21, pete M via 44Net 44net@mailman.ampr.org wrote:
Scott I don't know what is the guide you are talking about. But on the vultr website they don't talk about static section..
Take a look!
https://www.vultr.com/docs/high-availability-on-vultr-with-floating-ip-and-b...
So you were not wrong, I only did use a bad howto. which I do find strange that vultr promote the service with bogus instruction.
________________________________________ De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de Scott Nicholas via 44Net 44net@mailman.ampr.org Envoyé : 23 novembre 2020 10:35 À : AMPRNet working group Cc : Scott Nicholas Objet : Re: [44net] now what is he next step
I can have a look at starting a wiki section on bird.
There are so many ways but vultr is very popular. They sometimes have $2.50/m (without ipv4) which you can then announce ipv4 from.
I should have asked to see config, I assumed a static was set from guide. Sorry about that. Glad to hear it worked out.
-Scott
On Mon, Nov 23, 2020, 9:41 AM G1FEF via 44Net 44net@mailman.ampr.org wrote:
Perhaps someone could do a write up for the Wiki?
Thanks, Chris
On 23 Nov 2020, at 14:35, pete M via 44Net 44net@mailman.ampr.org wrote:
And the route is now working. and tested positively. OUF! thanks guys.!
________________________________________ De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de pete M via 44Net 44net@mailman.ampr.org Envoyé : 23 novembre 2020 09:31 À : AMPRNet working group Cc : pete M Objet : 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@mailman.ampr.org de la part de pete M via 44Net 44net@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@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@hotmail.com Sent: Monday, November 23, 2020 15:22 To: Ruben ON3RVH on3rvh@on3rvh.be; AMPRNet working group < 44net@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@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@mailman.ampr.org On Behalf Of pete M via 44Net Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
https://www.vultr.com/docs/configuring-bgp-on-vultr
-k9dc
On Nov 23, 2020, at 11:35, pete M via 44Net 44net@mailman.ampr.org wrote:
I can see that both of those guide have been edited the same day.
My search on google gave me the other guide. pretty odd.
This just prove that we are not ready yet to have bots helping us with every technical question we have!
Thanks again to everyone that helped..
Pierre (the only one with a large smile in line at the coffee shop this morning, even the mask don't hide it!) VE2PF
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@mailman.ampr.org On Behalf Of pete M via 44Net Sent: Monday, November 23, 2020 15:32 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la part de pete M via 44Net 44net@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@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@hotmail.com Sent: Monday, November 23, 2020 15:22 To: Ruben ON3RVH on3rvh@on3rvh.be; AMPRNet working group 44net@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@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@mailman.ampr.org On Behalf Of pete M via 44Net Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
GREAT news!
I was starting to wonder if I had broke too much stuff in there..
I never went much further then doing some nat and building small routers from a dual nic computer. That and DNS zone. So all this is very new to me.. At least I understand some of the operation on the OS.
________________________________________ De : Ruben ON3RVH on3rvh@on3rvh.be Envoyé : 23 novembre 2020 09:36 À : AMPRNet working group Cc : pete M Objet : RE: [44net] now what is he next step
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@mailman.ampr.org On Behalf Of pete M via 44Net Sent: Monday, November 23, 2020 15:32 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la part de pete M via 44Net 44net@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@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@hotmail.com Sent: Monday, November 23, 2020 15:22 To: Ruben ON3RVH on3rvh@on3rvh.be; AMPRNet working group 44net@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@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@mailman.ampr.org On Behalf Of pete M via 44Net Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
On 2020-11-23 14:31, pete M via 44Net wrote:
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@mailman.ampr.org de la part de pete M via 44Net 44net@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@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@hotmail.com Sent: Monday, November 23, 2020 15:22 To: Ruben ON3RVH on3rvh@on3rvh.be; AMPRNet working group 44net@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@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@mailman.ampr.org On Behalf Of pete M via 44Net Sent: Monday, November 23, 2020 14:56 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@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@mailman.ampr.org de la part de James Colderwood via 44Net 44net@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@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Can confirm I can now see your announcement :-) core2# bgpctl show rib | grep "44.135.59" *> N 44.135.59.0/24 169.254.169.254 100 0 64515 65534 20473 2914 20473 i
Yeah thanks.. Been on this for like 10 days every nights from time to time.
The learning curve is harder than anticipated. I must be getting old.
But for a grandpa of 6 that do computer stuff only for fun I am proud of my little achievement. ;-)
------------------------------------
Can confirm I can now see your announcement :-) core2# bgpctl show rib | grep "44.135.59" *> N 44.135.59.0/24 169.254.169.254 100 0 64515 65534 20473 2914 20473 i
-- Kind Regards James B Colderwood M0ZAH _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
It depends.
You might want to try checking your outgoing IP with a tool like 'telnet telnetmyip.com’ and see if your outgoing address is what you want it to be.
We have a bunch of other IRLP services running on the same machine in my example, that must remain accessible with or without a tunnel. You can change outgoing source by using 44.135.59.1 as the gateway in the route table. From ifconfig...
ens3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 149.28.163.64 netmask 255.255.254.0 broadcast 149.28.163.255
tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 44.136.33.1 netmask 255.255.255.255 destination 44.136.33.2
I can use either of those addresses as the outgoing source.
root@server4:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 128.0.0.0 44.136.33.1 128.0.0.0 UG 0 0 0 ens3 0.0.0.0 44.136.33.1 128.0.0.0 UG 0 0 0 ens3 0.0.0.0 149.28.162.1 0.0.0.0 UG 0 0 0 ens3
As long as OpenVPN (server side) is running, outgoing traffic will use 44.136.33.1 as its source. If you stop OpenVPN, traffic will originate from the 149-network address.
-Dave K9DC Indianapolis
On Nov 23, 2020, at 10:19, James Colderwood via 44Net 44net@mailman.ampr.org wrote:
On 2020-11-23 14:31, pete M via 44Net wrote:
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
Here is what is working great for me at vultr, for IRLP repeaters. I am doing this twice, using OpenVPN. Once in Chicago for North America, and a second instance in Sydney (North America and Australia have the bulk of the IRLP network).
My Sydney interfaces file and routing table below.
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5).
#source /etc/network/interfaces.d/*
auto lo iface lo inet loopback
allow-hotplug ens3 iface ens3 inet dhcp #iface ens3 inet6 auto up /sbin/ip addr add 44.136.33.1/24 dev ens3 up /sbin/ip route add 0.0.0.0/1 via 44.136.33.1 dev ens3 up /sbin/ip route add 128.0.0.0/1 via 44.136.33.1 dev ens3
iface ens3:1 inet static iface ens3:2 inet static up /sbin/ip addr add 192.168.168.1/32 dev ens3:1 up /sbin/ip addr add 172.23.168.1/32 dev ens3:2
root@server4:~# ifconfig ens3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 149.28.163.64 netmask 255.255.254.0 broadcast 149.28.163.255 inet6 fe80::5400:2ff:fe4e:dcb1 prefixlen 64 scopeid 0x20<link> ether 56:00:02:4e:dc:b1 txqueuelen 1000 (Ethernet) RX packets 613089025 bytes 92170994578 (85.8 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 392296914 bytes 89720106151 (83.5 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ens3:0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.168.1 netmask 255.255.255.255 broadcast 192.168.168.255 ether 56:00:02:4e:dc:b1 txqueuelen 1000 (Ethernet)
ens3:1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.23.168.1 netmask 255.255.255.255 broadcast 172.23.255.255 ether 56:00:02:4e:dc:b1 txqueuelen 1000 (Ethernet)
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1 (Local Loopback) RX packets 74751 bytes 4597613 (4.3 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 74751 bytes 4597613 (4.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 44.136.33.1 netmask 255.255.255.255 destination 44.136.33.2 inet6 fe80::e299:1a4f:9831:8248 prefixlen 64 scopeid 0x20<link> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC) RX packets 103033849 bytes 17211100391 (16.0 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 347861887 bytes 46690629693 (43.4 GiB) TX errors 0 dropped 39777 overruns 0 carrier 0 collisions 0
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface44.136.33.0 149.28.162.0 0.0.0.0 255.255.254.0 U 0 0 0 ens3 44.136.33.2 0.0.0.0 255.255.255.0 UG 0 0 0 tun0 44.136.33.0 0.0.0.0 255.255.255.0 U 0 0 0 ens3 44.136.33.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun0 0.0.0.0 44.136.33.1 128.0.0.0 UG 0 0 0 ens3 128.0.0.0 44.136.33.1 128.0.0.0 UG 0 0 0 ens3 0.0.0.0 149.28.162.1 0.0.0.0 UG 0 0 0 ens3 169.254.169.254 149.28.162.1 255.255.255.255 UGH 0 0 0 ens3
(I edited the order of the routes above, for easier read)
The two private addresses (192.168.168.1 and 172.23.168.1) were added so our users could configure a test to determine if their tunnel was still up. All the public addresses are accessible with or without the tunnel operating. The only way you can get to either one of private addresses though, is over a working tunnel.
Regarding OpenVPN, take a look at https://pivpn.io. PiVPN was designed to run on a Raspberry Pi, but it works fine on any Debian 9. It makes managing key assignments a real snap.
We have roughly 250 repeaters around the world using this solution to keep their repeaters in the network, most often using cellular for Internet access.
-Dave K9DC Indianapolis
On Nov 22, 2020, at 20:55, pete M via 44Net 44net@mailman.ampr.org wrote:
Hi I finally got my bpg annonce working, bird do works i have 2 interface on the machine,
when I list my route I have this:
route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 207.246.122.1 0.0.0.0 UG 0 0 0 ens3 44.135.59.0 0.0.0.0 255.255.255.0 U 0 0 0 dummy1 169.254.169.254 207.246.122.1 255.255.255.255 UGH 0 0 0 ens3 207.246.122.0 0.0.0.0 255.255.254.0 U 0 0 0 ens3
Now my next thing is to have an openvpn server so that the client can use address from the /24 as there ip adress to the world. (openvpn is a vpn solution, but if you have other/better solution I am open).
one little other thing. will the connection by the vpn be limited to one ip address by tunel or can I specify the number of address available by client configuration?
one other thing, is there a dashboard to control/monitor by a web interface a server like openvpn?
thanks
Pierre VE2PF
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
One other thing I meant to include, is the two /1 routes (mask 128.0.0.0) forces the machine to speak using the 44-net address (44.136.33.1) as a source, rather than the public IP assigned by Vultr (149.28.162.1). The two /1 routes override the default route, because the mask is longer. Without those two /1 routes, the default route will use 149.28.162.1 as its source. All the clients use the vultr assigned address (149.28.162.1) as the destination for their tunnel.
-Dave K9DC Indianapolis
On Nov 23, 2020, at 09:37, Dave Gingrich via 44Net 44net@mailman.ampr.org wrote:
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface44.136.33.0 149.28.162.0 0.0.0.0 255.255.254.0 U 0 0 0 ens3 44.136.33.2 0.0.0.0 255.255.255.0 UG 0 0 0 tun0 44.136.33.0 0.0.0.0 255.255.255.0 U 0 0 0 ens3 44.136.33.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun0 0.0.0.0 44.136.33.1 128.0.0.0 UG 0 0 0 ens3 128.0.0.0 44.136.33.1 128.0.0.0 UG 0 0 0 ens3 0.0.0.0 149.28.162.1 0.0.0.0 UG 0 0 0 ens3 169.254.169.254 149.28.162.1 255.255.255.255 UGH 0 0 0 ens3
-
Dave Gingrich -
G1FEF -
James Colderwood -
pete M -
Ruben ON3RVH -
Scott Nicholas