Changed up my network equipment, now i'm unable to access the PVE Web GUI.

R

Roguestratus

Member
Nov 24, 2022
11
1
8
This was my old network setup: Internet -> Uverse BGW210 ->Archer A7 -> Optiplex 5060 with Proxmox install and all subsequent vms, gaming pcs, work laptop, wireless devices, etc.

I removed the Archer A7 so that I can make way to virtualize OPNSense and install my TL-SG2008P, and then EAP225 and all other devices.

I'm no networking expert, but i'm familiar with certain terminology like private IPs and whatnot. I figured since moving around networks, I would come across this issue of my Proxmox not being recognized, and right I was. I can't access the GUI.

Proxmox wasn't even showing up in my BGW210 router at all. So here's what I did:

After checking the BGW210, it shows that it had a range of 192.168.1.64-253. Proxmox was sitting at 192.168.0.216:8006. By going into the shell and changing it to 192.168.1.216, Proxmox finally showed up on the BGW210 router. But still cannot connect. So I changed Proxmoxs IP back to its original (192.168.0.216:8006) and basically readjusted the private IP ranges inside my router:

Device IPv4 Address Old: 192.168.1.254
Device IPv4 Address New: 192.168.0.254
Subnet Mask: 255.255.255.0

DHCPv4 Start Address Old: 192.168.1.64
DHCPv4 Start Address New: 192.168.0.2

DHCPv4 End Address Old: 192.168.1.253
DHCPv4 End Address New: 192.168.0.253

Restarted both the BGW210 and baremetal, and still nothing. On my BGW210, it clearly shows the baremetal and even says "Status: On". So i'm not sure what gives at this point. I also tried all variations: https, https, with and without the 8006, and just the IP by itself. Is it because its expecting a certain network port that it was previously used to? That's the only thing I can think of, but again i'm lost at this point.
 
bbgeek17 said:
What is your workstation IP address? (ipconfig /all ; ip a)
What is the full output from Proxmox:
ip a
ip route

Can you ping PVE IP from your workstation? Can you ping the router from both workstation and PVE?

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
If by workstation, youre talking about my main PC I use everyday? If so, it only shows my public IP. Its hardwired too.

ip a:
Code: 
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65535 qdisc noqueue state UNKNOWN group default qlen 100
    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: enp3s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 90:e2:ba:0d:c4:5a brd ff:ff:ff:ff:ff:ff
3: enp3s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 90:e2:ba:0d:c4:5b brd ff:ff:ff:ff:ff:ff
4: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 6c:2b:59:fb:6c:87 brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 6c:2b:59:fb:6c:87 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.216/24 scope global vmbr0
        valid_lft forever preferred_lft forever
    inet6 fo80::6e2b:59ff:fefb:6c87/64 scope link
        valid_lft forever preferred_lft forever

ip route:
Code: 
default via 192.168.0.1 dev vmbr0 proto kernel onlink
192.168.0.0/24 dev vmbr0 proto kernel scope link src 192.168.0.216

Can I ping PVE IP from my workstation?
Code: 
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.216:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Can I ping the router from both workstation and PVE?
Workstation:
Code: 
Reply from 192.168.0.254: bytes=32 time<1ms TTL=64
Reply from 192.168.0.254: bytes=32 time<1ms TTL=64
Reply from 192.168.0.254: bytes=32 time<1ms TTL=64
Reply from 192.168.0.254: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.0.254:
    Packets: Sent = 4, received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

PVE:
Code: 
PING 192.168.0.254 (192.168.0.254) 56(84)
64 bytes from 192.168.0.254: icmp_seq1-100 ttl=64 time=0.90ms - 1.20ms
 
Roguestratus said:
If by workstation, youre talking about my main PC I use everyday? If so, it only shows my public IP. Its hardwired too.
Click to expand...
your workstation has a public IP? Sounds unusual. Assuming thats a correct statement - how does your workstation know how to get to private IP of a router? What is the routing table on your workstation?

It seems that your networking is more complicated than you initially indicated. Start from basics - put any workstation on the same subnet as PVE and test access. Use a direct cable if you have to. I have suspicion that it will work.
Keep peeling off or adding layers until you find the culprit. If the above ^^ experiment works, then its clearly not a PVE issue. There are thousands of network troubleshooting guides online you can refer to.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
bbgeek17 said:
your workstation has a public IP? Sounds unusual. Assuming thats a correct statement - how does your workstation know how to get to private IP of a router? What is the routing table on your workstation?

It seems that your networking is more complicated than you initially indicated. Start from basics - put any workstation on the same subnet as PVE and test access. Use a direct cable if you have to. I have suspicion that it will work.
Keep peeling off or adding layers until you find the culprit. If the above ^^ experiment works, then its clearly not a PVE issue. There are thousands of network troubleshooting guides online you can refer to.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
You know what? That IS weird now that I think about it. Because I just tried to access it another way and I am actually able to access Proxmox Web GUI from my smartphone connecting to the BGW210 and even another computer with a private IP.

The culprit is my pc trying to access the WebGUI using a public IP, or at the very least in my BGW210 router GUI it shows my main PC being the only one with a public IP while every other device connected having a private. Not sure why my PC shows the public in the router GUI. At least its a start.
 
bbgeek17 said:
your workstation has a public IP? Sounds unusual. Assuming thats a correct statement - how does your workstation know how to get to private IP of a router? What is the routing table on your workstation?

It seems that your networking is more complicated than you initially indicated. Start from basics - put any workstation on the same subnet as PVE and test access. Use a direct cable if you have to. I have suspicion that it will work.
Keep peeling off or adding layers until you find the culprit. If the above ^^ experiment works, then its clearly not a PVE issue. There are thousands of network troubleshooting guides online you can refer to.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
Figured it out: my BGW210 was still in IP Passthrough mode, which I needed it on to pass the public IP to my Archer A7. Since the Archer A7 was decommissioned but I never turned off IP Passthrough in my BGW210, it ended up passing it to my pc which made it unable to communicate with the private network.
 
You must log in or register to reply here.
Top Bottom