2 proxmox servers, no internet access on the second one

R

rfdarter

New Member
Dec 2, 2024
6
0
1
Hi,
I added a second proxmox server to my setup and created a cluster.
I made sure that i ran `apt update && apt ugrade` on both before doing that.

I seems to work fine, my Vm`s have access to the LAN and Internet without a problem, but the host does not.

Comparing the settings of the two proxmox servers I cant seem to find a difference

`/etc/network/interfaces` on the server that has internet access:

Code: 
auto lo
iface lo inet loopback

iface enp1s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.179.1/16
        gateway 192.168.178.1
        bridge-ports enp1s0
        bridge-stp off

`ip route`
Code: 
default via 192.168.178.1 dev vmbr0 proto kernel onlink 
192.168.0.0/16 dev vmbr0 proto kernel scope link src 192.168.179.1

`/etc/resolv.conf`
Code: 
search pi.hole
nameserver 192.168.179.2
nameserver 192.167.178.1

`/etc/hosts`
Code: 
127.0.0.1 localhost.localdomain localhost
192.168.179.1 pve.fritz.box pve

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts


and on the machine that does not have internet access:

Code: 
auto lo
iface lo inet loopback

iface enp0s31f6 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.180.1/16
        gateway 192.168.178.1
        bridge-ports enp0s31f6
        bridge-stp off

`ip route`
Code: 
default via 192.168.178.1 dev vmbr0 proto kernel onlink 
192.168.0.0/16 dev vmbr0 proto kernel scope link src 192.168.180.1

`/etc/resolv.conf`
Code: 
search pi.hole
nameserver 192.168.179.2
nameserver 192.168.178.1

`/etc/hosts`
Code: 
127.0.0.1 localhost.localdomain localhost
192.168.180.1 pve2.fritz.box pve2

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

My router recognizes the seconds server fine and displays the right ip address.
`nslookup` works alsow fine and i get an ip from pihole but a ping fails

Code: 
root@pve2:~# nslookup google.com
Server:         192.168.179.2
Address:        192.168.179.2#53

Non-authoritative answer:
Name:   google.com
Address: 142.251.36.174
Name:   google.com
Address: 2a00:1450:4016:808::200e

root@pve2:~# ping google.com
PING google.com (142.251.36.174) 56(84) bytes of data.
From pve2.fritz.box (192.168.180.1) icmp_seq=1 Destination Host Unreachable

I hope someone can help me.
 
Thanks, I followed a yt video which stated you should make sure they are both on the same software version, so in my mind i never even thought about somthing else than `apt update && apt upgrade` o_O

But since i never ran "full-upgrade" or "dist-upgrade" on any of the machines and I installed both form the same ISO i think it should be fine?

I looked at the posted tutorial link, but the wiring should be fine since the VM`s can access the internet.
The configurations looks also good or do you see a mistake I made?
 
rfdarter said:
But since i never ran "full-upgrade" or "dist-upgrade" on any of the machines and I installed both form the same ISO i think it should be fine?
Click to expand...
Yes, I think it is fine. Just run "apt full-upgrade" now and in future.

rfdarter said:
I looked at the posted tutorial link, but the wiring should be fine since the VM`s can access the internet.
Click to expand...
Okay, that article was not meant to fit exactly to your situation but is more general.

rfdarter said:
The configurations looks also good or do you see a mistake I made?
Click to expand...
No, everything I see looks fine. But it lacks a simple ip addr show...

And... a "/16" for 192.168 is really unusual - while technically ok. Are you sure the router does accept that? For example an "AVM Fritz!Box" uses 192.168.178.0/24 by default (as far as I remember)... and your "192.168.180.1" would not be inside that network...
 
UdoB said:
ip addr show
Click to expand...
Code: 
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: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 90:1b:0e:da:0c:17 brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 90:1b:0e:da:0c:17 brd ff:ff:ff:ff:ff:ff
    inet 192.168.180.1/16 scope global vmbr0
       valid_lft forever preferred_lft forever
4: veth108i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr108i0 state UP group default qlen 1000
    link/ether fe:3b:f8:ad:2a:ca brd ff:ff:ff:ff:ff:ff link-netnsid 0
5: fwbr108i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 1e:49:e8:92:b0:0e brd ff:ff:ff:ff:ff:ff
6: fwpr108p0@fwln108i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 3a:e4:42:89:46:ea brd ff:ff:ff:ff:ff:ff
7: fwln108i0@fwpr108p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr108i0 state UP group default qlen 1000
    link/ether 1e:49:e8:92:b0:0e brd ff:ff:ff:ff:ff:ff
8: veth200i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fe:e7:ac:a7:5d:71 brd ff:ff:ff:ff:ff:ff link-netnsid 1
13: veth210i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr210i0 state UP group default qlen 1000
    link/ether fe:3b:e2:74:4c:06 brd ff:ff:ff:ff:ff:ff link-netnsid 2
14: fwbr210i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 26:79:2b:d9:a7:1c brd ff:ff:ff:ff:ff:ff
15: fwpr210p0@fwln210i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 82:a3:ab:0a:78:77 brd ff:ff:ff:ff:ff:ff
16: fwln210i0@fwpr210p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr210i0 state UP group default qlen 1000
    link/ether 26:79:2b:d9:a7:1c brd ff:ff:ff:ff:ff:ff

I used '/16' on purpose to give each proxmox server a base ip adress of `192.168.179.1` and `192.168.180.1` and the VM`s `192.168.179.2` to `192.168.179.254` and `192.168.180.2` to `192.168.180.254`
So i could easily tell by the ip on which proxmox server the Vm is running.
Not a good idea? Is a `/16` in general not a good idea or just using `192.168`?

Yes on a FrizBox the default is 192.168.178.0/24 but i have set it to 192.168.0.0/16
My Proxmox server using the ip `192.168.179.1` works fine, and can access the internet, just the on using `192.168.180.1` can not
 
I just noticed something.
From the proxmox server that can not connect to the internet i can ping everything in the LAN except the gateway(192.168.178.1)
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom