Can't ping devices from vmbr1

M

mountaindrewtech

New Member
Aug 17, 2022
4
1
3
Hello,

I took some time to try to resolve this myself, but like many, I'm new to this and wanted to reach out for some help.

I'm trying to mount NFS storage to Proxmox from TrueNAS, which is one of my VM's of course!, and I have TrueNAS on my vmbr1 interface, however, I can't get connectivity between the two. Proxmox itself doesn't seem to want to ping the two networks it has bridges for, and I'm not sure how to fix that yet.

My Proxmox server is on vmbr0 on the 192.168.100.0/24 network and is assigned 192.168.100.5
TrueNAS is hosted on vmbr1 on the 192.168.200.0/24 network and is assigned 192.168.200.3

I've confirmed that TrueNAS is able to ping every device on the .100 network BESIDES Proxmox, and Proxmox is able to ping everything, but the 192.168.200.0 network and 10.10.250.0 network. I do typically have a Firewall to only allow ping from vmbr0, but I've disabled it on the datacenter and node and no cigar.

Any help would be gladly appreciated, I'll probably end up moving Proxmox over to .200 as well if I can't get this working, but I'd like to keep Proxmox off of my VM/CT's subnet, and I want to learn! ^_^

Screenshot 2022-08-17 163917.pngScreenshot 2022-08-17 164251.pngScreenshot 2022-08-17 164351.pngScreenshot 2022-08-17 164546.pngScreenshot 2022-08-17 164605.png
 
Last edited:
shrdlicka said:
Hi,
I would stay away from giving the the ".0" in 192.168.200.0/24 to a host. Try giving PVE any IP in that range except 0. And then see if ping works.
Click to expand...
yes

For Subnet = 192.168.200.0/24 &10.10.250/24
192.168.200.0 is the network address and should not be used.
10.10.250.0 is the network address and should not be used.

usable IP Hosts* = 192.168.1.1 - 192.168.1.254 & 10.10.250.1 - 10.10.250.254

Easy calculator to see the usable IP's for different subnets.
https://www.dan.me.uk/ipsubnets?csrfmiddlewaretoken=MTY2MDgzMzg1MA==&ip=192.168.1.0
 
Last edited:
  • Like
Reactions: mountaindrewtech
shrdlicka said:
Hi,
I would stay away from giving the the ".0" in 192.168.200.0/24 to a host. Try giving PVE any IP in that range except 0. And then see if ping works.
Click to expand...
That makes perfect sense... wow, thank you. I thought I was assigning the interface to the network, but yeah that makes 10000% sense thank you again lol.
 
  • Like
Reactions: shrdlicka
Alright, so I am still having issues :) Might be missing something simple, but I set the two interfaces to end with .2 now, but I still can't seem to ping the vmbr1 or vmbr2 interface from any device.
 
The PVE firewall is still disabled? What is the output of ip a on the server?
 
shrdlicka said:
The PVE firewall is still disabled? What is the output of ip a on the server?
Click to expand...

Yes it is : P

root@proxmox:~# 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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
link/ether bc:30:5b:f5:52:e4 brd ff:ff:ff:ff:ff:ff
altname enp1s0f0
3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP group default qlen 1000
link/ether bc:30:5b:f5:52:e5 brd ff:ff:ff:ff:ff:ff
altname enp1s0f1
4: eno3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr2 state UP group default qlen 1000
link/ether bc:30:5b:f5:52:e6 brd ff:ff:ff:ff:ff:ff
altname enp1s0f2
5: eno4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether bc:30:5b:f5:52:e7 brd ff:ff:ff:ff:ff:ff
altname enp1s0f3
6: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether bc:30:5b:f5:52:e4 brd ff:ff:ff:ff:ff:ff
inet 192.168.100.5/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::be30:5bff:fef5:52e4/64 scope link
valid_lft forever preferred_lft forever
7: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether bc:30:5b:f5:52:e5 brd ff:ff:ff:ff:ff:ff
inet 192.168.200.2/24 scope global vmbr1
valid_lft forever preferred_lft forever
inet6 fe80::be30:5bff:fef5:52e5/64 scope link
valid_lft forever preferred_lft forever
8: vmbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether bc:30:5b:f5:52:e6 brd ff:ff:ff:ff:ff:ff
inet 10.10.250.2/24 scope global vmbr2
valid_lft forever preferred_lft forever
inet6 fe80::be30:5bff:fef5:52e6/64 scope link
valid_lft forever preferred_lft forever
9: tap201i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr201i0 state UNKNOWN group default qlen 1000
link/ether b2:13:40:06:76:a6 brd ff:ff:ff:ff:ff:ff
10: fwbr201i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether c6:bf:e6:e1:2b:eb brd ff:ff:ff:ff:ff:ff
11: fwpr201p0@fwln201i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1 state UP group default qlen 1000
link/ether 6e:dc:36:15:98:8b brd ff:ff:ff:ff:ff:ff
12: fwln201i0@fwpr201p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr201i0 state UP group default qlen 1000
link/ether 72:66:98:f1:a5:10 brd ff:ff:ff:ff:ff:ff
13: veth202i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr202i0 state UP group default qlen 1000
link/ether fe:b2:5a:df:df:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0
14: fwbr202i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 66:38:d2:48:82:8c brd ff:ff:ff:ff:ff:ff
15: fwpr202p0@fwln202i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1 state UP group default qlen 1000
link/ether 2a:91:af:bd:52:4e brd ff:ff:ff:ff:ff:ff
16: fwln202i0@fwpr202p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr202i0 state UP group default qlen 1000
link/ether 4e:c4:76:3b:99:f6 brd ff:ff:ff:ff:ff:ff
17: veth250i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr250i0 state UP group default qlen 1000
link/ether fe:ba:fa:9a:d1:03 brd ff:ff:ff:ff:ff:ff link-netnsid 1
18: fwbr250i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether f2:c8:ff:f0:15:74 brd ff:ff:ff:ff:ff:ff
19: fwpr250p0@fwln250i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr2 state UP group default qlen 1000
link/ether 66:f2:ec:69:45:b5 brd ff:ff:ff:ff:ff:ff
20: fwln250i0@fwpr250p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr250i0 state UP group default qlen 1000
link/ether ca:b6:8f:fa:93:2f brd ff:ff:ff:ff:ff:ff
39: veth100i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
link/ether fe:fa:41:da:d6:a1 brd ff:ff:ff:ff:ff:ff link-netnsid 2
40: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 9a:94:eb:9e:00:36 brd ff:ff:ff:ff:ff:ff
41: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1 state UP group default qlen 1000
link/ether ee:42:ed:66:0e:60 brd ff:ff:ff:ff:ff:ff
42: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
link/ether 0e:41:5b:b6:86:36 brd ff:ff:ff:ff:ff:ff

root@jellyfin-debian11-ct:~# 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: eth0@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 5a:91:94:e7:7e:4f brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 192.168.200.5/24 brd 192.168.200.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::5891:94ff:fee7:7e4f/64 scope link
valid_lft forever preferred_lft forever

Can't seem to run ip a on truenas lemme see what i can find..
 
Last edited:
Can the router reach the Proxmox server? When reading it again, it sounds a bit like a routing issue.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back