management gui has disappeared

[pattonb]

I had a working proxmox setup in my lab, and then I moved it to be in production. This is the intended setup.

proxmox pve ( I call host) just manages the vm's. I have 2 vm's. vm1 will be a debian gw and firewall, and also run samba for the internal lan.
I am not sure what I have "pooched", however, I am able to access the pve and vm1 via ssh , ( as I have another gw device on the network)
the pve network/interfaces show me this.

[CODE]root@cvh:~# ip a[/INDENT] [INDENT]1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000[/INDENT] [INDENT] link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00[/INDENT] [INDENT] inet 127.0.0.1/8 scope host lo[/INDENT] [INDENT] valid_lft forever preferred_lft forever[/INDENT] [INDENT]2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000[/INDENT] [INDENT] link/ether 84:2b:2b:42:ed:68 brd ff:ff:ff:ff:ff:ff[/INDENT] [INDENT]3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP group default qlen 1000[/INDENT] [INDENT] link/ether 84:2b:2b:42:ed:69 brd ff:ff:ff:ff:ff:ff[/INDENT] [INDENT]4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000[/INDENT] [INDENT] link/ether 84:2b:2b:42:ed:68 brd ff:ff:ff:ff:ff:ff[/INDENT] [INDENT] inet 192.168.1.12/24 brd 192.168.1.255 scope global vmbr0[/INDENT] [INDENT] valid_lft forever preferred_lft forever[/INDENT] [INDENT]5: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000[/INDENT] [INDENT] link/ether 84:2b:2b:42:ed:69 brd ff:ff:ff:ff:ff:ff[/INDENT] [INDENT] inet 192.168.1.10/24 brd 192.168.1.255 scope global vmbr1[/INDENT] [INDENT] valid_lft forever preferred_lft forever[/INDENT] [INDENT]6: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr100i0 state UNKNOWN group default qlen 1000[/INDENT] [INDENT] link/ether 0a:b8:73:5b:69:54 brd ff:ff:ff:ff:ff:ff[/INDENT] [INDENT]7: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000[/INDENT] [INDENT] link/ether ae:e8:3e:70:7f:a4 brd ff:ff:ff:ff:ff:ff[/INDENT] [INDENT]8: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000[/INDENT] [INDENT] link/ether 6a:4d:78:45:dc:7c brd ff:ff:ff:ff:ff:ff[/INDENT] [INDENT]9: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000[/INDENT] [INDENT] link/ether ae:e8:3e:70:7f:a4 brd ff:ff:ff:ff:ff:ff[/INDENT] [INDENT]10: tap100i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr100i1 state UNKNOWN group default qlen 1000[/INDENT] [INDENT] link/ether 7a:0a:df:2e:0b:24 brd ff:ff:ff:ff:ff:ff[/INDENT] [INDENT]11: fwbr100i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000[/INDENT] [INDENT] link/ether ce:82:53:1b:3b:8a brd ff:ff:ff:ff:ff:ff​

12: fwpr100p1@fwln100i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1 state UP group default qlen 1000​

link/ether 46:84:5c:6b:fa:b2 brd ff:ff:ff:ff:ff:ff​

13: fwln100i1@fwpr100p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i1 state UP group default qlen 1000​

link/ether ce:82:53:1b:3b:8a brd ff:ff:ff:ff:ff:ff​

14: tap101i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr101i0 state UNKNOWN group default qlen 1000​

link/ether 46:7d:eb:a7:a4:c4 brd ff:ff:ff:ff:ff:ff​

15: fwbr101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000​

link/ether ee:b6:05:90:1b:bb brd ff:ff:ff:ff:ff:ff​

16: fwpr101p0@fwln101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000​

link/ether 2e:fa:79:7d:f4:61 brd ff:ff:ff:ff:ff:ff​

17: fwln101i0@fwpr101p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr101i0 state UP group default qlen 1000​

link/ether ee:b6:05:90:1b:bb brd ff:ff:ff:ff:ff:ff[/CODE]​

​

so basically 2 bridges, one bridge to eno1 and the other bridge to eno2

if I run "nmap -p 8006 vmbr0 or vmbr1" they both show the same that the web gui is running.

root@cvh:~# nmap -p 8006 192.168.1.10​

Starting Nmap 7.70 ( https://nmap.org ) at 2021-06-03 01:40 MDT​

Nmap scan report for 192.168.1.10​

Host is up (0.000067s latency).​

​

PORT STATE SERVICE​

8006/tcp open wpl-analytics​

​

Nmap done: 1 IP address (1 host up) scanned in 13.35 seconds​

root@cvh:~#​

root@cvh:~# nmap -p 8006 192.168.1.12​

Starting Nmap 7.70 ( https://nmap.org ) at 2021-06-03 01:41 MDT​

Nmap scan report for cvh.network1.ca (192.168.1.12)​

Host is up (0.000055s latency).​

​

PORT STATE SERVICE​

8006/tcp open wpl-analytics​

if run nmap from outside the host ( on the internal lan) on either of the ip's, ( 192.168.1.10 or 192.168.1.12) I get the following, and am not able to connect to the management gui.

root@cranstonvh:/etc/iptables# nmap -p 8006 192.168.1.10​

Starting Nmap 7.70 ( https://nmap.org ) at 2021-06-03 01:43 MDT​

Nmap scan report for 192.168.1.10​

Host is up (0.00029s latency).​

​

PORT STATE SERVICE​

8006/tcp filtered wpl-analytics​

MAC Address: 84:2B:2B:42:ED:69 (Dell)​

​

Nmap done: 1 IP address (1 host up) scanned in 0.58 seconds​

​

root@cranstonvh:/etc/iptables# nmap -p 8006 192.168.1.12​

Starting Nmap 7.70 ( https://nmap.org ) at 2021-06-03 01:43 MDT​

Nmap scan report for 192.168.1.12​

Host is up (0.00026s latency).​

​

PORT STATE SERVICE​

8006/tcp filtered wpl-analytics​

MAC Address: 84:2B:2B:42:ED:69 (Dell)​

on the host eno1 is connected to the ISP gw ( wan) and eno2 is connected to the lan switch.

any ideas, I think I have over thought this and am just confused.

thank you

​

 

[ph0x]

So you have two NICs in the same subnet? There's probably already your problem. Just don't.

 

[pattonb]

So you have two NICs in the same subnet? There's probably already your problem. Just don't.

actually no, one nic is connected to the ISP/internet/wan and the other is connected to the internal lan

 

[ph0x]

192.168.1.10/24 and 192.168.1.12/24 are on the same subnet, regardless what you connect them to.

 

[pattonb]

sigh, humbled again. as I look closer at this, my ignorance is displayed. thank you for your time.