Weird DHCP server issue.

[turnkey]

Hello, this will be my first post here.

I'm a casual user of pfSense, I have basic networking understanding.

I'm experiencing some weird behaviour, maybe someone can help me out. Gonna start out in broad terms maybe you guys can help me hone in on the problem.

I have a Windows Desktop PC on it's own subnet, which is connected to a bridged interface (vSwitch2), which also services the DHCP for clients on that interface.

Please take note there is no LAN interface running DHCP.

But for some reason it's showing this when I look in DHCP Lease. Where does it get LAN interface from? I thought it should get an IP address from vSwitch2

Looking for some clues, I then tried to make a static mapping for the weird client in the dhcp lease to see which DHCP server it was using...

I'm presented with this LAN DHCP Server, which I've never created...

Going one step back to look at the DHCP server and I see a blank subnet, subnet mask 0.0.0.0, Available range 0.0.0.1 - 255.255.255.255

I tried replacing the Desktop with another PC and the same thing happens... help :)

[johnpoz]

@turnkey yeah that is never going to work.. What IP do you have set on that interface?

You mention "bridge" your not trying to do some bridge on pfsense are you? Can almost promise you did something wrong if that is the case.. Why would you think/want to bridge interfaces on some vm instance of pfsense?

[stephenw10]

Can I assume LAN_AP is a the renamed LAN interface?

[johnpoz]

@turnkey you got pfsense screaming at you about something being wrong

[turnkey]

@johnpoz Hi thank you for your reply.

LAN interface dosen't have an IP, it's part of vSwitch interface which has 192.168.1.1

What I mean with bridge is that I've grouped physical interfaces together like so, you can see bridge0 and bridge1 in the screenshot below are using vSwitch and vSwitch2 interfaces.

@stephenw10 Here are my interfaces, I haven't renamed my LAN interface:

Regarding Alerts here it is:

[johnpoz]

@turnkey said in Weird DHCP server issue.:

LAN interface dosen't have an IP, it's part of vSwitch interface which has 192.168.1.1

And why would you be doing that??

What is it your trying to accomplish in bridging these interfaces in pfsense?

[turnkey]

@johnpoz i want to group physical interfaces on the same subnet.

[johnpoz]

@turnkey said in Weird DHCP server issue.:

i want to group physical interfaces on the same subnet.

is this not a vm? Why would you call it a vswitch if was physical? vswitch is a Virtualization term.

If its actually physical interfaces on a pfsense box - what is plugged into these 2 interfaces?

Physical interfaces are not switch ports, bridging them does not make a switch - if you want switch ports get a switch.

There is rarely a reason to setup a bridge that makes any actual sense.. And you sure wouldn't run a dhcp server on an interface that doesn't have an IP. If your creating a bridge, then run the dhcp on the bridge interface you created.

[stephenw10]

Clear those alerts and reload the filter in Status > Filter Reload to make sure the current ruleset is loading.
Those pfBlocker errors are quite common at boot though and not usually a problem.

Steve