Skip to content

Conversation

Harvie
Copy link

@Harvie Harvie commented Feb 16, 2013

Copypaste from mail:
Hi!
Manpage of dhcrelay says:
"The client supports inclusion of a Remote ID suboption as well, but this is not used by default."

But there's no support of setting Remote ID in Option 82 at dhcrelay. I think this would be really usefull. I need central DHCP server with relays in my company. We use manageable switches with Option 82 support, these are OK (they're including RemoteID of switch and CircuitID of port to DHCP requests). But in some places without these switches we need to use Linux with dhcrelay instead (CircuitID identifies interface as needed, but we also need to set RemoteID as we have multiple relays in our network, which means shitloads of conflicting eth0s and eth1s)

So i really need to append different RemoteIDs set by commandline argument on each relay...

Right now i am going to make some ugly dirty adhoc patch to dhcrelay, but i guess you can do it much better... Do you think it's possible to get this improvement in official release?

Copypaste from mail:
Hi!
Manpage of dhcrelay says:
"The client supports inclusion of a Remote ID  suboption as well, but this is not used by default."

But there's no support of setting Remote ID in Option 82 at dhcrelay. I think this would be really usefull. I need central DHCP server with relays in my company. We use manageable switches with Option 82 support, these are OK (they're including RemoteID of switch and CircuitID of port to DHCP requests). But in some places without these switches we need to use Linux with dhcrelay instead (CircuitID identifies interface as needed, but we also need to set RemoteID as we have multiple relays in our network, which means shitloads of conflicting eth0s and eth1s)

So i really need to append different RemoteIDs set by commandline argument on each relay...

Right now i am going to make some ugly dirty adhoc patch to dhcrelay, but i guess you can do it much better... Do you think it's possible to get this improvement in official release?
@marschap
Copy link
Owner

Hi,

I am sorry, but I guess I will not be able to help you much:
I am neither a developer of ISC DHCP upstream nor a Debian Developer.

I guess the bvest way to get your issue solved is if you post it to the
upstream ISC DHCP mailing list [email protected]

Best
Peter

On Saturday, 16. February 2013, Tomas Mudrunka wrote:

Copypaste from mail:
Hi!
Manpage of dhcrelay says:
"The client supports inclusion of a Remote ID suboption as well, but
this is not used by default."

But there's no support of setting Remote ID in Option 82 at dhcrelay. I
think this would be really usefull. I need central DHCP server with relays
in my company. We use manageable switches with Option 82 support, these
are OK (they're including RemoteID of switch and CircuitID of port to DHCP
requests). But in some places without these switches we need to use Linux
with dhcrelay instead (CircuitID identifies interface as needed, but we
also need to set RemoteID as we have multiple relays in our network, which
means shitloads of conflicting eth0s and eth1s)

So i really need to append different RemoteIDs set by commandline argument
on each relay...

Right now i am going to make some ugly dirty adhoc patch to dhcrelay, but i
guess you can do it much better... Do you think it's possible to get this
improvement in official release? You can merge this Pull Request by
running:

git pull https://github.com/Harvie/debian-isc-dhcp upstream

Or you can view, comment on it, or merge it online at:

#1

-- Commit Summary --

  • Added support for passing custom Remote ID in Option 82

-- File Changes --

M relay/dhcrelay.8 (11)
M relay/dhcrelay.c (25)

-- Patch Links --

https://github.com/marschap/debian-isc-dhcp/pull/1.patch
https://github.com/marschap/debian-isc-dhcp/pull/1.diff

Peter Marschall
[email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants