No subnet declaration; Can't open /var/lib/dhcp/dhcpd.leases for append
bill at c3po.polymerindustries.biz
Sat Jan 27 21:44:59 UTC 2018
True. Another way is to forget about using wlp2s0, buy and inexpensive router,
turn OFF the router's DHCP server, and plug the LAN side of the router into the
same switch as enp4s5. Nothing is plugged into the WAN side of the router.
The router will pass everything, including DHCP traffic, through to the enp4s5
interface and all internal devices will be on one subnet. This works well.
On 1/27/2018 4:38 PM, Simon Hobson wrote:
> Bill Shirley <bill at c3po.polymerindustries.biz> wrote:
>> I would suggest setting wlp2s0 as a different subnet, say 10.1.2.1/24
>> and create an additional subnet declaration in DHCP with option routers
>> 10.1.2.1. 'yellow' should route between 10.1.1.0/24 and 10.1.2.0/24
>> for your internal devices.
> That's another way of doing it, but it precludes most autodicovery protocols working between wired and wireless devices. Eg you wireless device won't be able to discover a wired printer through mDNS (aka Zeroconf).
> That's a significant problem where people want to segregate devices (eg put IoTat one it's own network so it can't blab about other stuff you have) because so much of it is written on the assumption that (eg) your smartphone is on the same network as the device.
> dhcp-users mailing list
> dhcp-users at lists.isc.org
More information about the dhcp-users