LAN Inaccessible from host

Pdawg

New Member
Mar 6, 2024
3
0
1
My Promox server (an old Dell Optiplex 960 with some upgrades) is unable to other devices on my LAN. The system uses an Intel 82567LM NIC.

My server is located at `192.168.50.77`, gateway at `192.168.50.1`, and the other device I'm pinging is at `192.168.50.71`. On my server, I can ping `google.com` just fine, I can ping the guest VMs, and I can ping my gateway; but I can't ping the other device. I have no clue why this is happening.

Also, I can ping the server and its guests from my other device just fine.
 
Last edited:
Output of cat /etc/network/interfaces might help us.
Did you check the config of your router? Maybe you plugged the Optiplex in a Port on your router that is for guest access, only allowing the connected device to access the internet but not any devices on your LAN? A "Fritxbox" for example is capable of doing this on Port 4.
 
Last edited:
Output of cat /etc/network/interfaces might help us.
Did you check the config of your router? Maybe you plugged the Optiplex in a Port on your router that is for guest access, only allowing the connected device to access the internet but not any devices on your LAN?
Hey! I ran the command:

Code:
root@pve:~# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface enp0s25 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.50.77/24
        gateway 192.168.50.1
        bridge-ports enp0s25
        bridge-stp off
        bridge-fd 0

source /etc/network/interfaces.d/*

This was its output. The port isn't on my main router, but instead on a mesh extender. That shouldn't be the issue though because other devices on that extender work just fine. Also, remember, I can ping the server just fine. It behaves like a one-way connection.