Server not visible from web, but desktop console appears to work

[zogkarndon]

I recently set up Proxmox VE on a Framework 13 motherboard (running standalone). I have ethernet attached via USB-C.

The initial installation worked fine, but now the machine isn't visible from the network, but if I connect a monitor & keyboard, a login prompt is displayed and I can type.

Also, the network link lights on the adapter are blinking, so the physical link seems to be working.

Two questions:
1) Is it possible to log in via the keyboard/monitor (instead of via the web)? I used the password I set up at installation, and it wasn't accepted.
2) Are there other ways to diagnose the network issues?

 

[Hannes Laimer]

Hey,

you can login directly on the console with root as user and the password you've setup. After doing so, could you post the output of ip a and cat /etc/network/interfaces? Can you ping your router?

 

[zogkarndon]

I was finally able to log in on the console (my guess is my crappy keyboard was duplicating keystrokes). The network *looks* like it's up on the device end, but pinging the router or gateway results in Destination Host Unreachable, so I suspect there's something funky on the switch.

/etc/network/interfaces:

auto lo
iface lo inet loopback
iface enx9cbf0d0012a7 inet manual
auto vmbr0
iface vmbr0 inet static
    address 192.168.3.51/22
    gateway 192.168.0.1
    bridge-ports enx9cbf0d0012a7
    bridge-stp off
    bridge-fd 0
    
source /etc/network/interfaces.d/*

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 noprefixroute
        valid_lft forever preferred_lft forever
3: vmbr0: <BROADCAST, MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 9c:bf:0d:00:12:a? brd ff:ff:ff:ff:ff:ff
    inet 192.168.3.51/22 scope global vmbr0
        valid_lft forever preferred_lft forever
    inet6 fe80::9ebf:dff:fe00:12a7/64 scope link
        valid_lft forever preferred_lft forever
4: veth100i0@ifz: <BROADCAST, MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether fe:11:04:b1:94:13 brd ff:ff:ff:ff:ff:ff link-netnsid 0
5: enx9cbf0d0012a7: <BROADCAST, MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 9c:bf:0d:00:12:a7 brd ff:ff:ff:ff:ff:ff

 

[sw-omit]

judging by your ip a, it looks like the physical device (enx9cbf0d0012a7) is down.
We could try to "force" it up with /sbin/ifup enx9cbf0d0012a7 (although unlikely to work, but worth the shot)
Or otherwise, what's the output of ethtool enx9cbf0d0012a7
I'm also noticing a "gap" in the numbering (going from 1: lo: to 3: vmbr0:), do you perhaps have any PCI(e)-Passthrough set up?

 

[zogkarndon]

After watching the status after rebooting, I noticed that the interfaces immediately after boot has enx9cbf0d0012a7 in "slot" 2, and the interface is UP.

After a few minutes, the interface enx9cbf0d0012a7 has moved to "slot" 5 and is DOWN.

The ethernet interface is actually connected via USB-C (it's a Framework 13); I suspect that the module is disconnecting and reconnecting, although I don't know for sure.

 

[gfngfn256]

address 192.168.3.51/22

gateway 192.168.0.1

That gateway should probably be 192.168.3.1

 

[sw-omit]

That gateway should probably be 192.168.3.1

Not necessarily, they are on a /22 after all, not a /24, and the 192.168.0.0/22 runs from 192.168.0.0 to 192.168.3.255

 

[zogkarndon]

After a bunch more searching, it turns out that the problem is with the wifi driver, and adding a quirks line to the grub command line has solved the problem.