NIC on Bridge gets IP but no access
-
I'm trying to bridge multiple NICs together. The WAN and LAN initial setup ports work perfectly - computers attached to the LAN connect to the DHCP server and are able to connect to the internet. I've gone ahead and created a bridge across a 3rd ethernet port and the LAN interface. I've created firewall rules allowing for traffic on both the 3rd ethernet port and the LAN port. As a test, I've created a static IP for the device I'm connecting to the 3rd ethernet port. The device is able to get the IP address... but is unable to communicate to either the WAN or LAN. pfSense is also unable to ping the device.
Does anyone have any ideas what the issue might be? This is my second rodeo with pfSense, so it is certainly possible that I'm doing something wrong. I should add that I know the NIC card works because I did a test deployment with it on a physical machine before virtualizing it in VirtualBox.
Here's the "Wifi" (LAN) port that's working - it has the DHCP server attached to it
Here's the firewall rule for one of the ports I'm trying to bridge (all of the ports have the same rule)
Here's the Firewall rule for the bridge - it seems to be getting no traffic?
Bridge setup is here
Bridge interface
Bridge definition
Interfaces
I should mention that I've tried running the interface with as "Static IPv4" with a DHCP server on a separate range... but the device on the bridged port still pulls it's IP address from the Wifi interface DHCP server.
-
What are you actually connecting to the port?
You say it does pull an IP address from the pfSense, can you see that is Status > DHCP leases?
Steve
-
@stephenw10 Here's the DHCP lease:
Pinging the device from another machine:
Pinging it from pfSense:
-
What IP are you pinging from there? How is it connected?
What is 192.168.1.7?
What is your WIFI subnet set to?
-
@stephenw10 192.168.1.7 is the machine I'm pinging from. Wifi subnet (if I understand the question correctly) is set to 192.168.1.1 / 24
-
Ok, so the client itself is replying that .3 is unreachable which means it isn't responding to ARP.
Do you see anything blocked in the firewall logs in pfSense?
-
@stephenw10 I don't see anything in the Firewall logs around that device.
I did notice one peculiar thing - the Windows based machine hosting the VirtualBox instance with pfSense can fully communicate to the device (192.168.1.3). I'm not sure what to make of the whole thing.
-
How is the host itself attached? Is it possible there's a loop created?
Otherwise this seems like a VBox firewall problem... or maybe something on the host itself?
