How to configure in interface under proxmox routed subnets?

General questions
, ,
1

Hello!

I have a Proxmox 5 isntalled on Bare Metall Server on Hetzner.de.
I want to use VyOS as router with slave in future, but in the beginning now I can’t understand how to configure IN ethernet…

For guest debian/ubuntu based VM I configure network interface like that:
iface ens18 inet static
address 195.201.xxx.xxx
netmask 255.255.255.255
pointopoint 195.201.yyy.yyy
gateway 195.201.yyy.yyy
dns-nameservers 213.133.98.98 8.8.8.8 8.8.4.4

But what option I must set for VyOS ? I don’t get any answer by Googling, so maybe some one can help me there? :frowning:

2

@dmbaturin do we support something like that ?

3

So I tried to do some changes:

vyos@vyos# set protocols static route 0.0.0.0/0 next-hop 195.201.yyy.yyy
vyos@vyos# show system gateway-address 
 gateway-address 195.201.yyy.yyy

vyos@vyos# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 94.130.xxx.xxx icmp_seq=1 Destination Host Unreachable
From 94.130.xxx.xxx icmp_seq=2 Destination Host Unreachable

[edit]
vyos@vyos# delete system gateway-address 195.201.yyy.yyy
[edit]
vyos@vyos# commi
commit          commit-confirm  
[edit]
vyos@vyos# commit
[edit]
vyos@vyos# save
Saving configuration to '/config/config.boot'...
Done
[edit]
vyos@vyos# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1000ms

[edit]
vyos@vyos# ping google.com
^C
[edit]
vyos@vyos# sudo ip ro
default dev eth0  proto zebra 
94.130.xxx.xxx dev eth0  proto kernel  scope link  src 94.130.xxx.xxx 
127.0.0.0/8 dev lo  proto kernel  scope link  src 127.0.0.1 
192.168.25.0/24 dev eth1  proto kernel  scope link  src 192.168.25.1 
195.201.yyy.yyy dev eth0  proto zebra  scope link 
[edit]
vyos@vyos# sudo ip ro del default
[edit]
vyos@vyos# sudo ip ro add 0.0.0.0/0 via 195.201.yyy.yyy
RTNETLINK answers: File exists
[edit]
vyos@vyos# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 94.130.xxx.xxx icmp_seq=1 Destination Host Unreachable
From 94.130.xxx.xxx icmp_seq=2 Destination Host Unreachable
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1999ms
pipe 2
[edit]
vyos@vyos# sudo ip ro
default dev eth0  proto zebra 
94.130.xxx.xxx dev eth0  proto kernel  scope link  src 94.130.xxx.xxx
127.0.0.0/8 dev lo  proto kernel  scope link  src 127.0.0.1 
192.168.25.0/24 dev eth1  proto kernel  scope link  src 192.168.25.1 
195.201.yyy.yyy dev eth0  proto zebra  scope link 
[edit]
4

I suppose it’s the same thing as in online.net et al. The solution is:
set interfaces ethernet eth0 address 192.0.2.100/32
sudo ip route add 192.0.2.1/32 dev eth0 # no gateway
sudo ip route add default via 192.0.2.1
You’ll need to add the ip route commands to /config/scripts/vyatta-postconfig-bootup.script to make them permanent.

Quagga doesn’t support this because, frankly, this is insanity and goes completely against the spirit of IP, even if not the letter of the RFCs. I’m afraid given how widespread it is, we’ll have to add a “fix” for it.

1 Like
5

Actually it’s supported on cli

set protocols static interface-route 195.201.yyy.1/32 next-hop-interface 'eth0'
set protocols static route 0.0.0.0/0 next-hop '195.201.yyy.1'

hope this helps

1 Like
6

Thanks, @dmbaturin in, it works for me on Hetzner. But @syncer cli commands doesn’t.