Issues connecting to host

[ATQ]

I've just made new install of Proxmox (through Debian). I messed around a bit too much with old install so making a backup of the VM's and reinstalling seemed like the best approach. The new install is giving me a headache though...

So, I have two NIC's in my server. One is connected to the internet and the other to my desktop. Try as I might though, I can't connect to the server through LAN. If I set the NIC to static IP and assign an address to it, the network is unreachable (ping requests return "unreachable", not timed out). However, if I connect through a router it works (I have an old and slow router that I don't actually want to use).

Routing through Pfsense VM also works, except in that case the server has no WAN. This is with the same settings I used on the old install of Proxmox.

auto lo
iface lo inet loopback

auto enp4s0
iface enp4s0 inet manual

auto enp6s0
iface enp6s0 inet manual

auto vmbr0
iface vmbr0 inet static
               address 192.168.1.106/24
               gateway 192.168.1.1
               bridge-ports enp4s0
               bridge stp off
               bridge-fd 0
               
auto vmbr1
iface vmbr1 inet manual
               bridge-ports enp6s0
               bridge stp off
               bridge-fd 0

Any ideas of what is the matter here?

 

[aaron]

vmbr0 is the internal NIC connected to your desktop and vmbr1 connected to the modem?

 

[ATQ]

vmbr0 is the internal NIC connected to your desktop and vmbr1 connected to the modem?

That's right, except I have fibre directly from the wall - no modem needed.

 

[aaron]

That's right, except I have fibre directly from the wall - no modem needed.

You can be sure of my envy

So, I have two NIC's in my server. One is connected to the internet and the other to my desktop. Try as I might though, I can't connect to the server through LAN. If I set the NIC to static IP and assign an address to it, the network is unreachable (ping requests return "unreachable", not timed out). However, if I connect through a router it works (I have an old and slow router that I don't actually want to use).

So to better grasp the situation, if you connect directly from your desktop to the port that vmbr0 is using, you cannot ping the PVE node but can access the internet via the virtual PFsense that is using the same vmbr0 for the LAN network?

If you put an old router in between (probably just the internal ports of it to use it as a switch?) it works as in, you can access the PVE node and internet via the virtual PFSense works too?

If I got the situation correctly I must say, that it is weird .

Just as a guess, but what does ip a and ip r on the PVE server show?

 

[ATQ]

Sorry, I missed your reply and then went away for a few days. I'm back at trying to fix this issue, but honestly... I can't make any sense of it. Direct connection to the server through LAN just refuses to work. I can only get it to work if I connect through my old router. Otherwise the network is unreachable.

Tried a fresh install of Proxmox (through Debian since the Proxmox installer doesn't like my hardware). Because, well... why not? Anyhow, figured I'd focus on this one issue first - get the LAN connection to work.

So, here's the /etc/network/interfaces

# 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/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug enp6s0
iface enp6s0 inet dhcp

allow-hotplug enp4s0
iface enp4s0 inet static
        address 192.168.1.106
        netmask 255.255.255.0

Here's 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
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp6s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 20:cf:30:04:90:54 brd ff:ff:ff:ff:ff:ff
    inet 176.10.255.237/22 brd 176.10.255.255 scope global dynamic enp6s0
       valid_lft 12827sec preferred_lft 12827sec
    inet6 fe80::22cf:30ff:fe04:9054/64 scope link 
       valid_lft forever preferred_lft forever
3: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 50:3e:aa:1f:6a:67 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.106/24 brd 192.168.1.255 scope global enp4s0
       valid_lft forever preferred_lft forever
    inet6 fe80::523e:aaff:fe1f:6a67/64 scope link 
       valid_lft forever preferred_lft forever
4: wlp5s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 60:e3:27:7e:66:54 brd ff:ff:ff:ff:ff:ff

And finally, ip r

default via 176.10.252.1 dev enp6s0 
176.10.252.0/22 dev enp6s0 proto kernel scope link src 176.10.255.237
192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.106

So, just for clarification:

enp6s0 is connected to WAN
enp4s0 is the LAN connection between server and desktop

That way the LAN is unreachable.

If I connect the old router to WAN and connect my desktop and server through enp4s0, it works. As of writing this, that's how I'm connected and I can reach the server through LAN.

I have also tried switching the interfaces around, just to make sure it's not a problem with the individual interface, but it's the same result.

I'm at my wits end here, so would really appreciate any help.