<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I would suggest setting wlp2s0 as a different subnet, say
10.1.2.1/24<br>
and create an additional subnet declaration in DHCP with option
routers<br>
10.1.2.1. 'yellow' should route between 10.1.1.0/24 and 10.1.2.0/24<br>
for your internal devices.<br>
<br>
Bill<br>
<br>
<div class="moz-cite-prefix">On 1/27/2018 4:10 PM, A wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4dcc8b0e-3a88-b94a-45d2-29e61d074c57@bak.rr.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 01/27/2018 11:57 AM, Simon Hobson
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:88B215D6-D788-4B5E-8908-90CCD185A8A7@thehobsons.co.uk">
<div>
<div>A <<a href="mailto:publicface@bak.rr.com"
moz-do-not-send="true">publicface@bak.rr.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div bgcolor="#FFFFFF">
<p># ip -4 -o addr</p>
1: lo inet 127.0.0.1/8 scope host lo\ valid_lft
forever preferred_lft forever<br>
2: enp4s5 inet 10.1.1.1/24 brd 10.1.1.255 scope global
enp4s5\ valid_lft forever preferred_lft forever<br>
3: enp6s0 inet [xx.xx.xx.xx/20 brd 255.255.255.255
scope global enp6s0\ valid_lft forever preferred_lft
forever<br>
4: wlp2s0 inet 10.1.1.10/24 brd 10.1.1.255 scope global
wlp2s0\ valid_lft forever preferred_lft forever<br>
...</div>
</blockquote>
<blockquote type="cite">
<div bgcolor="#FFFFFF">Jan 27 10:37:48 yellow sh[5804]: No
subnet declaration for enp4s5 (no IPv4 addresses).<br>
Jan 27 10:37:48 yellow sh[5804]: ** Ignoring requests on
enp4s5. If this is not what<br>
Jan 27 10:37:48 yellow sh[5804]: you want, please write
a subnet declaration<br>
Jan 27 10:37:48 yellow sh[5804]: in your dhcpd.conf
file for the network segment<br>
Jan 27 10:37:48 yellow sh[5804]: to which interface
enp4s5 is attached. **<br>
Jan 27 10:37:48 yellow dhcpd[5804]: No subnet declaration
for enp4s5 (no IPv4 addresses).<br>
Jan 27 10:37:48 yellow dhcpd[5804]: ** Ignoring requests
on enp4s5. If this is not what<br>
Jan 27 10:37:48 yellow dhcpd[5804]: you want, please
write a subnet declaration<br>
Jan 27 10:37:48 yellow dhcpd[5804]: in your dhcpd.conf
file for the network segment<br>
Jan 27 10:37:48 yellow dhcpd[5804]: to which interface
enp4s5 is attached. **<br>
Jan 27 10:37:48 yellow dhcpd[5804]: <br>
Jan 27 10:37:48 yellow dhcpd[5804]: Listening on
LPF/wlp2s0/f0:7d:68:c1:b4:13/10.1.1.0/24<br>
Jan 27 10:37:48 yellow dhcpd[5804]: Sending on
LPF/wlp2s0/f0:7d:68:c1:b4:13/10.1.1.0/24<br>
Jan 27 10:37:48 yellow sh[5804]: Listening on
LPF/wlp2s0/f0:7d:68:c1:b4:13/10.1.1.0/24<br>
Jan 27 10:37:48 yellow sh[5804]: Sending on
LPF/wlp2s0/f0:7d:68:c1:b4:13/10.1.1.0/24<br>
Jan 27 10:37:48 yellow sh[5804]: Sending on
Socket/fallback/fallback-net<br>
Jan 27 10:37:48 yellow dhcpd[5804]: Sending on
Socket/fallback/fallback-net<br>
Jan 27 10:37:48 yellow dhcpd[5804]: Server starting
service.<br>
</div>
</blockquote>
<div><br>
</div>
Hmm, I have an idea what the problem might be. You have two
interfaces in the same subnet and I don't think the dhcp
server can handle that. The OS can deal with it because it
keeps an ARP cache and so can figure out which interface to
use for outbound packets.</div>
<div>BUT, ISC DHCPD doesn't use the OS for routing a lot of it's
packets - it works at a lower level as it has to be able to
send packets which wouldn't ordinarily be routable (no
destination IP address) to clients.</div>
<div><br>
</div>
<div>So what I think might be happening is that it's connecting
the 10.1.1.0/24 subnet with the wlp2s0 interface, and then
when it tries to configure the enp4s5 interface, there is no
subnet available to connect with it<br>
<div><br>
</div>
</div>
</blockquote>
<br>
Sounds reasonable. And therefore if I was to force it to use
enp4s5 somehow, there'd be no subnet for wlp2s0; right?<br>
<br>
I did originally have two separate subnets with a /28 CIDR, but I
was unable to reach the Internet from blue and someone suggested I
have one subnet in order to act as a typical home router. So I
reconfigured everything and it's now borked worse than it was.
Said person disappeared shortly after of course.<br>
<br>
<blockquote type="cite"
cite="mid:88B215D6-D788-4B5E-8908-90CCD185A8A7@thehobsons.co.uk">
<div>I'm assuming this box is permanently connected to both
networks ? If not then it wouldn't be very useful as a DHCP
server.</div>
</blockquote>
<br>
Yellow - yes.<br>
<br>
<blockquote type="cite"
cite="mid:88B215D6-D788-4B5E-8908-90CCD185A8A7@thehobsons.co.uk">
<div>Is there another device bridging the ethernet and WiFi ? </div>
</blockquote>
<br>
Not anymore. There was a virtual bridge using bridge-utils at one
point as mentioned above. Wouldn't be impossible to put it back.<br>
<br>
<blockquote type="cite"
cite="mid:88B215D6-D788-4B5E-8908-90CCD185A8A7@thehobsons.co.uk">
<div>I assume there's an AP</div>
</blockquote>
<br>
I'm using hostapd as I'm unaware of any other option for AP
software at this time.<br>
<br>
<blockquote type="cite"
cite="mid:88B215D6-D788-4B5E-8908-90CCD185A8A7@thehobsons.co.uk">
<div>, or it's built into the router - and in that case, you do
not need (for DHCP anyway) to listen on the WiFi interface
since packets will get bridges to the ethernet interface by
the AP.</div>
</blockquote>
<br>
There is no commercial router. Yellow is the router, gateway,
access point, dhcp server, dns server, firewall (iptables) and
more.<br>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
dhcp-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/dhcp-users">https://lists.isc.org/mailman/listinfo/dhcp-users</a></pre>
</blockquote>
<br>
</body>
</html>