How to make DHCP pool IPs access static assigned IPs outside the pool?

[tavi]

Hi,

I have a very simple setup. On LAN, DHCP service giving IPs within 192.168.100.101 - 192.168.100.254 range.

Outside, I have static assigned IPs for a lot of MACs. The range for these static IPs is between 192.168.0.1 to 192.168.11.254.

LAN0 IP 192.168.0.1

I cannot from DHCP pool to outside and vice versa.

Is there a solution to this problem, other than extending the pool?

[Patrick M. Hausen]

What is the netmask set of this LAN IP of 192.168.0.1?

[tavi]

Hi,

192.168.0.1/16

[tavi]

[meyergru]

Is the netmask and gateway that the DHCP service hands out correct? Or is it /24?

[tavi]

Inside the pool:

Code Select Expand

IPv4 Address. . . . . . . . . . . : 192.168.100.104(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1


[pfry]

How is that Killer wireless connected? Guessing an AP, which I'd expect to be a bridge; does it have any firewall rules?

Also, specifics of connectivity: on the same subnet, you should see ARP for everything. "arp -a" on Windows and FreeBSD shell; "Interfaces: Diagnostics: ARP Table" in OPNsense GUI.

[tavi]

Thanks for the tips. Once I get back to the PCs I will try your suggestions.

But, I did some tests. So, if I switch, ETH mac in the pool, and Wi-Fi static assigned, like 192.168.0.20 then things get switched.

No access to anything outside the pool for the ETH interface.

[tavi]

Well, this little bugger was checked:



Unchecked and all seems normal so far.

But I swear I'm not sure how this got activated. I'm not really tinkering too much on the firewall.

First time I noticed there were issues, was when I was plying around with netboot.xyz and some machines could not download the environment.