Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
I have the same strange behavior on Ubuntu 13.04 (64-bit) Server. I installed my system using VMWare, but I don't think it makes a difference.
isc-dhcp-4.2.4 is what came with my distro. I also tested the latest version (isc-dhclient-4.2.5-P1) with the same result.
What is odd is that even though I specify the -4 option to ensure I'm enfocing IPv4 it is listening on random ports for both IPv4 and IPv6.
I read through the dhclient.c source code, but I couldn't see an obvious socket and bind. I thought perhaps it was related to omapi so I added "omapi port 9999" to my /etc/dhcp/dhclient.conf which did add a forth port that was being listened on so that doesn't seem the reason.
From the source code I suspect these random ports may be coming from interface discovery which creates some sockets (although it didn't seem like they performed binds) to probe various interfaces.
I'd like to know what these ports are for as well so I can be sure they don't cause a security issue. I sent a bug report to dhcp-bugs @@ isc.org asking about this behavior.
I think they're used for dynamic DNS. I don't need that functionality, but it cannot be disabled with any config-file options, so have to recompile the package:
You were correct! Making those three modifications removed the extra listening ports! I'll update my bug report to isc so they can fix their documentation and ideally add a configuration option to disable that behavior.
Wow. Four years later and still dhclient is exhibiting the same idiotic, unconfigurable behaviour. I think it's ridiculous and burdensome to recompile something like dhclient. What the hell is ISC thinking???!?