DHCP options, iptables?
Hi, as I wait for my Blue to arrive, I’ve a few questions about DHCP mode:
1.) Assuming router @ 10.0.0.1, wireless AP @ 10.0.0.2, and all other devices @ 10.0.0.x, etc., when DHCP mode is enabled with secondary 192.168.218.x network, which devices should move over?
I assume only the router stays in the original network and all other devices move to the overlay network so that they can be monitored, right? Any exceptions to this?
2.) How will Firewalla work with Pi-hole in DHCP mode? I assume the Pi should also move to the new secondary network?
3.) Since DHCP is turned off at router side, would Firewalla in DHCP mode allow user to set custom DNS, DHCP reservations, DHCP options, and iptable rules?
I understand editing DNS and setting static IP address are now in beta, what about DHCP options and iptables editing? This is more for advertising DNS through DHCP and routing hardcoded DNS in certain devices. I assume Firewalla runs Dnsmasq, no?
Thanks!
-
1. When DHCP mode is enabled, your assumption is correct.
2. PiHole devices should have a static IP ... the reason is, you really depend on this service, and if IP changes, you will be losing functionality. So you can manually move it's IP or have it stay the same place, doesn't matter. Make sure in simple mode, never monitor pihole.
3. This is in alpha now, as the time of this message. https://help.firewalla.com/hc/en-us/community/posts/360029230894-April-6-2019-Firewalla-Red-Blue-Alpha-Release-1-963-iOS-1-30-Android-2-41-
DHCP option: we do not expose it now ... but it is all possible to add that, and you need to let us know the use case.
iptable: it is already in rules. unlike, we will expose iptables directly.
For managing DHS/DHCP: we can do as well, need more use case.
Yes, we use a form of DNSMASQ.
Please sign in to leave a comment.
Comments
3 comments