OPNsense Forum
Archive => 15.1 Legacy Series => Topic started by: mikeboss on February 19, 2015, 11:24:25 am
-
hello everybody. this is my first (actually 2nd) post here. I'm evaluating OPNsense because of m0n0wall being declared as EOL. so far I think that OPNsense looks great! I'm having a small issue with WiFi/DHCP. I did setup OPNsense on a PC Engines APU. to get the WiFi up and running, I bridged it to the LAN interface. I didn't get any IP addresses on the WiFi. ah, ok, there's a seprate config for DHCP on the WiFi interface. I then activated the DHCP service on the WiFi interface with its own range (same subnet though). now I'm getting IP addresses from the DHCP range of the WiFi on both interfaces (LAN and WiFi). I don't think that it should behave that way...?
-
Bridging literally means merging two interfaces on the link layer. DHCP is a one-per-link-layer service so what you are seeing is indeed expected behaviour.
You can create a separate subnet and run an exclusive DHCP on that one for WiFi alone. It has the added benefit of being able to route and secure your WiFi traffic according to different policies than the LAN.
Maybe there's trickery to make your setup work the way you want, but I wouldn't recommend it.
-
thank you for your reply, franco.
hm, but if it would work as expected I should get IP addresses from the DHCP service configured on the LAN in the first place, correct? and this didn't happen AFAIR...
regards,
michael