Re: multiple relay destinations
[email protected] Mon, 24 Jul 2023 00:09:46 +1000
| Newsgroups | gmane.network.dhcp.isc.dhcp-client |
|---|---|
| Message-ID | <[email protected]> |
--===============8489178505250867134==
Content-Type: multipart/alternative;
boundary="=_b8f6e0399cb4efa9b2e830b1f5d6f5ee"
--=_b8f6e0399cb4efa9b2e830b1f5d6f5ee
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII;
format=flowed
I didn't see a reply to this, so here's a suggestion.
dhcrelay and dhcpd listen on the raw ethernet interface, that's why it
sees all the vlans as part of the same interface. So to get around this
you need a separate physical interface for directing the dhcp requests
to each dhcp server.
So if you could add another interface, say eth2, and configure eth2.900
then you could tell dhcrelay to route dhcp requests on eth1 to dhcp
server 1 and eth2 to dhcp server 2.
regards,
Glenn
On 2023-07-07 04:36, Gregory Malsack wrote:
> Hello All,
>
> I'm running isc-dhcrelay-4.4.3-P1 on an alpine linux router for a
> remote office to connect to our offices via a vpn. Currently we have
> eth0 on the internet, eth1 with no ip, then various vlans eth1.86
> eth1.87 eth1.900 and so on. From what I can tell, isc-dhcrelay only
> really listens on eth1, thus all of the vlan interface dhcp requests
> are sent upstream to the dhcrelay server listed in the config file.
>
> The problem I have is that eth1.86 and eth1.87 need to go to dhcp
> server 1 upstream and eth1.900 needs to go to dhcp server 2 upstream.
> If dhcrelay can do this great, but I don't know how to do this. I don't
> have eth1.900 listed in the iface directive, but that doesn't seem to
> matter because it's relaying dhcp requests on vlan anyway.
>
> Can someone help?
>
> Thanks!
> Greg
>
> Confidentiality Notice: Any materials and information enclosed on or
> with this electronic document are private and confidential and are the
> property of this sender. The email and the information it may contain
> is privileged and intended only for the use of the individual(s) or
> entity(ies) named above. All other use is strictly prohibited. If you
> are not the intended recipient, be advised that any unauthorized
> disclosure, copying, distribution or the taking of any action in
> reliance on the content is strictly prohibited. If you have received
> this email or document(s) in error, please notify us immediately to
> arrange for the return of the document(s).
--=_b8f6e0399cb4efa9b2e830b1f5d6f5ee
Content-Type: multipart/related;
boundary="=_63e9d3155247bf64e0c34e82c193cecc"
--=_63e9d3155247bf64e0c34e82c193cecc
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3DUTF-8" /></head><body style=3D'font-size: 10pt; font-family: Verdana,Gen=
eva,sans-serif'>
<p>I didn't see a reply to this, so here's a suggestion.</p>
<p>dhcrelay and dhcpd listen on the raw ethernet interface, that's why it s=
ees all the vlans as part of the same interface. So to get around this you =
need a separate physical interface for directing the dhcp requests to each =
dhcp server.</p>
<p>So if you could add another interface, say eth2, and configure eth2.900 =
then you could tell dhcrelay to route dhcp requests on eth1 to dhcp server =
1 and eth2 to dhcp server 2.</p>
<p>regards,</p>
<p>Glenn</p>
<p id=3D"reply-intro">On 2023-07-07 04:36, Gregory Malsack wrote:</p>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0">
<div id=3D"replybody1">
<style type=3D"text/css">#replybody1 P { margin-top: 0; margin-bottom: 0; }=
</style>
<div>
<div class=3D"v1elementToProof" style=3D"font-family: Calibri, Helvetica, s=
ans-serif; font-size: 11pt; color: #000000;">Hello All,</div>
<div class=3D"v1elementToProof" style=3D"font-family: Calibri, Helvetica, s=
ans-serif; font-size: 11pt; color: #000000;"> </div>
<div class=3D"v1elementToProof v1ContentPasted0" style=3D"font-family: Cali=
bri, Helvetica, sans-serif; font-size: 11pt; color: #000000;">I'm running&n=
bsp;isc-dhcrelay-4.4.3-P1 on an alpine linux router for a remote office to =
connect to our offices via a vpn. Currently we have eth0 on the internet, e=
th1 with no ip, then various vlans eth1.86 eth1.87 eth1.900 and so on. From=
what I can tell, isc-dhcrelay only really listens on eth1, thus all of the=
vlan interface dhcp requests are sent upstream to the dhcrelay server list=
ed in the config file.</div>
<div class=3D"v1elementToProof v1ContentPasted0" style=3D"font-family: Cali=
bri, Helvetica, sans-serif; font-size: 11pt; color: #000000;"> </div>
<div class=3D"v1elementToProof v1ContentPasted0" style=3D"font-family: Cali=
bri, Helvetica, sans-serif; font-size: 11pt; color: #000000;">The problem I=
have is that eth1.86 and eth1.87 need to go to dhcp server 1 upstream and =
eth1.900 needs to go to dhcp server 2 upstream. If dhcrelay can do this gre=
at, but I don't know how to do this. I don't have eth1.900 listed in the if=
ace directive, but that doesn't seem to matter because it's relaying dhcp r=
equests on vlan anyway.</div>
<div class=3D"v1elementToProof v1ContentPasted0" style=3D"font-family: Cali=
bri, Helvetica, sans-serif; font-size: 11pt; color: #000000;"> </div>
<div class=3D"v1elementToProof v1ContentPasted0" style=3D"font-family: Cali=
bri, Helvetica, sans-serif; font-size: 11pt; color: #000000;">Can someone h=
elp?</div>
<div class=3D"v1elementToProof v1ContentPasted0" style=3D"font-family: Cali=
bri, Helvetica, sans-serif; font-size: 11pt; color: #000000;"> </div>
<div class=3D"v1elementToProof v1ContentPasted0" style=3D"font-family: Cali=
bri, Helvetica, sans-serif; font-size: 11pt; color: #000000;">Thanks!</div>
<div class=3D"v1elementToProof v1ContentPasted0" style=3D"font-family: Cali=
bri, Helvetica, sans-serif; font-size: 11pt; color: #000000;">Greg</div>
<div class=3D"v1elementToProof">
<div id=3D"v1Signature">
<div> </div>
</div>
</div>
<img style=3D"width: 2px; max-height: 0; overflow: hidden;" src=3D"cid:1690=
[email protected]" width=3D"0" height=3D"0" /> Confi=
dentiality Notice: Any materials and information enclosed on or with this e=
lectronic document are private and confidential and are the property of thi=
s sender. The email and the information it may contain is privileged and in=
tended only for the use of the individual(s) or entity(ies) named above. Al=
l other use is strictly prohibited. If you are not the intended recipient, =
be advised that any unauthorized disclosure, copying, distribution or the t=
aking of any action in reliance on the content is strictly prohibited. If y=
ou have received this email or document(s) in error, please notify us immed=
iately to arrange for the return of the document(s).</div>
</div>
<br />
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">=
</div>
</blockquote>
<p><br /></p>
</body></html>
--=_63e9d3155247bf64e0c34e82c193cecc
Content-Transfer-Encoding: base64
Content-ID: <[email protected]>
Content-Type: image/gif;
name=blocked.gif
Content-Disposition: inline;
filename=blocked.gif;
size=118
R0lGODlhZAAyAIAAAPrOzgAAACH5BAAAAAAALAAAAABkADIAAAJNhI+py+0Po5y02ouz3rz7D4bi
SJbmiabqyrbuC8fyTNf2jef6zvf+DwwKh8Si8YhMKpfMpvMJjUqn1Kr1is1qt9yu9wsOi8fksvls
KwAAOw==
--=_63e9d3155247bf64e0c34e82c193cecc--
--=_b8f6e0399cb4efa9b2e830b1f5d6f5ee--
--===============8489178505250867134==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users
--===============8489178505250867134==--