Direct connection says host is down
-
@williamsilverstein said in Direct connection says host is down:
10.1.X.X for a local network.
That's /16.
I agree seeing /8 like that is a massive red flag for me. It would be very easy to get a subnet conflict with such a huge subnet on one interface. It's also almost always the result of an initial setup by someone who didn't really understand the available private subnets at the time.
But, yes, how are the VMs configured inside PVE?
-
@stephenw10 The /8 was only connected to the other port. I put a switch in, but no difference.
This is the original:
I inserted a router, just in case I was wrong. No difference.
-
So you are not using 10.x.x.x. on any other interfaces there?
How are those ports configured in PVE? Are you passing them through to the pfSense VM(s)?
-
@stephenw10 There ports are not configured in the proxmox or the VM. The network device is passed through to the VM
-
Ok, well those subnets are killing me! But they should work.
So are you sure the ports you have linked are actually the ports you have passed through?
Do you see it lose link when you unplug it?
-
@stephenw10 Yes. I checked it before, and I just checked it again.
-
Ok so how are you testing the connectivity?
'Host is down' implies it's ARPing for the target device and not seeing any replies. Can we assume neither host appears in the ARP table of the other?
-
@stephenw10 You are correct. I plugged a windows laptop into the same switch and set an IP address of 10.1.2.50 (netmask 255.0.0.0) and it would not see either 10.1.1.50 or 10.1.0.50..
The other network does not show up in the arp list.
-
Hmm. How are you actually testing? Just trying to ping the other IPs?
Try running a packet capture on that interface and see is anything is arriving at all. One both VMs.
It looks like it's not passing the NIC through correctly IMO. Some hardware off loading perhaps.
Are you connecting to the VMs using the LAN? The vtnet interface?
Can the VMs connect out using the other passed through NIC on the WAN?
-
The 2nd ports on each machine did not.
I changed the PCI passthrough to allow only one passthrough on each machine with all functions checked, which now provides two Ethernet devices in PfSense. Now, one works, not the other. One machine works (10.1.0.50), the other shows that the 2nd port (on 10.1.1.50) is down on the interface status screen.
