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