Interface name handling

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Interface name handling

Shawn Routhier
It appears that a new(er) feature in some OSes
is creating interface names of a length that causes
problems for ISC DHCP programs (server, relay and client).

We have created a patch for this and it will ship in
the next releases of the code (4.3.5 and 4.1-ESV-R14).
However as this issue seems to be causing problems
for a number of people I’ve concluded that sending out the
patch to the users list is reasonable.

If you have a problem with your program crashing
or interface recognition errors and your interface name
is 15 bytes long please try applying this patch before
submitting a bug report.

regards,
Shawn


_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

rt42226.diff (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Interface name handling

yrw22
Resolving interface recognition errors in ISC DHCP requires technical precision, but your digital documentation doesn’t have to look purely clinical. Integrating Name decoration into your internal server logs or project folders can help differentiate between various patched versions of the code. By using unique symbols or bold dividers, you can highlight the 4.3.5 and 4.1-ESV-R14 releases, making your troubleshooting guides easier to navigate visit here. This creative touch ensures that critical technical updates stand out clearly during high-pressure network maintenance.