Send dhcp-users mailing list submissions to

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to

You can reach the person managing the list at

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."

Today's Topics:

   1. Re: multiple relay destinations (


Message: 1
Date: Mon, 24 Jul 2023 00:09:46 +1000
To: Users of ISC DHCP <>
Subject: Re: multiple relay destinations
Message-ID: <>
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.



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).
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: blocked.gif
Type: image/gif
Size: 118 bytes
Desc: not available


Subject: Digest Footer

ISC funds the development of this software with paid support subscriptions. 
Contact us at for more information.

dhcp-users mailing list


End of dhcp-users Digest, Vol 176, Issue 7

Reply via email to