Re: [44net] now what is he next step

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 &lt;44net-bounces+petem001=hotmail.com(a)mailman.ampr.org&gt; de la part de pete M via 44Net &lt;44net(a)mailman.ampr.org&gt; 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 &lt;scott.nicholas(a)scottn.us&gt; 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 &lt;44net(a)mailman.ampr.org&gt; wrote: _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net