<div dir="ltr"><img width="0" height="0" class="mailtrack-img" src="https://mailtrack.io/trace/mail/fc78c41641aa11dfa2b9bc68777def0166752733.png?u=847429">Hi,<div><br></div><div>Thanks. Actually solved it this morning after piecing together help from a few people. Option 82 googling makes it FAR scarier than it needs to be. I also then started debugging source to figure out the problem with the "unknown network segment" to find out it was my misreading the correct subnet 205 times. </div><div><br></div><div>Yes, it was actually as easy as adding a shared-network and putting the correct subnet. I didn't need to mess with agent.link-selection or anything!</div><div><br></div><div>Thanks, Tuc<br><br><br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 24, 2017 at 9:41 PM, Patrick Trapp <span dir="ltr"><<a href="mailto:ptrapp@nex-tech.com" target="_blank">ptrapp@nex-tech.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">When I see those in my logs, it is because the request is coming from a network the DHCP server is not addressing and it does not know what pool to associate the request with. I create a shared-network statement including the intended pool and the mystery network. Since I'm not providing an address for the mystery network, the network statement (where i would normally define the network) is a pair of empty braces.<br>
<br>
I hope that makes sense - I can provide example configs later, but not at the moment. Hope it helps.<br>
<br>
Patrick<br>
<br>
> On Mar 24, 2017, at 7:51 PM, Tuc at Beach House <<a href="mailto:tuctboh@gmail.com">tuctboh@gmail.com</a>> wrote:<br>
><br>
> Hi,<br>
><br>
><br>
> I'm trying to figure out how to do relayed subnets within a datacenter<br>
> owners environment and our (sorry, old) 4.1.1-38.P1 ISC DHCP server.<br>
> Normally we allocated an interface to our machine for every subnet<br>
> that its on, but this new network is "remote" and they won't stretch<br>
> L2 to us.<br>
><br>
> So the normal config isn't what I'm used to, but works :<br>
><br>
> subnet 10.14.14.0 netmask 255.255.255.0 {<br>
><br>
> interface eth0;<br>
> authoritative;<br>
> allow booting;<br>
> option routers 10.14.14.1;<br>
> option subnet-mask 255.255.255.0;<br>
> option domain-name "<a href="http://cust19782.dc.example.com" rel="noreferrer" target="_blank">cust19782.dc.example.com</a>";<br>
> option domain-name-servers 10.14.2.1;<br>
> option ntp-servers 10.14.2.1;<br>
> next-server 10.14.14.11<br>
> filename "pxelinux.0";<br>
> pool {<br>
> option routers 10.14.14.1;<br>
> option domain-name-servers 10.14.2.1;<br>
> max-lease-time 600;<br>
> range 10.14.14.200 10.14.14.254;<br>
> allow unknown-clients;<br>
> }<br>
> }<br>
><br>
><br>
> And the others all are the same, but with different "interface"<br>
> statements. It is not wrapped in any sort of "shared-network"<br>
> statement.<br>
><br>
> I'm getting valid Option 82 information, so I did :<br>
><br>
> class "EXTDHCP" {<br>
> match if option agent.link-selection = "10.14.18.0";<br>
> }<br>
><br>
> And then pretty much the same except removed the "interface"<br>
> statement, and added "allow members of "EXTDHCP";" into the pool<br>
> statement.<br>
><br>
> However, all I keep seeing in my logs is :<br>
><br>
> dhcpd: DHCPDISCOVER from 81:9c:de:3b:61:02 via <a href="http://10.14.17.2" rel="noreferrer" target="_blank">10.14.17.2</a>: unknown<br>
> network segment<br>
><br>
> 10.14.17.2 is the TOR switch IP thats handling the relay. I can't seem<br>
> to find any more in depth debug. Pointers to where I went wrong? (And<br>
> "Using DHCPD 4.1.1" if it can't do it is acceptable)<br>
><br>
><br>
> Thanks, Tuc<br>
> ______________________________<wbr>_________________<br>
> dhcp-users mailing list<br>
> <a href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br>
> <a href="https://lists.isc.org/mailman/listinfo/dhcp-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/<wbr>listinfo/dhcp-users</a><br>
______________________________<wbr>_________________<br>
dhcp-users mailing list<br>
<a href="mailto:dhcp-users@lists.isc.org">dhcp-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/dhcp-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/<wbr>listinfo/dhcp-users</a><br>
</blockquote></div><br></div>