Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Improve handling of hosts coming back online #32
This was something I talked about with @kleinig on IRC, but it should really be a formal feature request.
The issue is that when a device comes back online, internet connectivity isn't immediate.
There are certain operating systems where this doesn't work, because they have a broken DHCP behaviour -- they will immediately try to use an old address on the network without renewing their lease, or will try to use an old address on the network that they have ended the lease and returned to the DHCP server. This tends to effect operating systems that have "instant" network access after resuming from sleep:
Princeton University's Office of IT have quite detailed information about this misbehaviour:
I suspect that Windows 8 will introduce similar broken functionality.
Anyway, the basic implementation of this feature will be to have a script that ISC's DHCPd and dnsmasq can call to notify tollgate there is a new lease on the network. This will help speed up reconnection.
Likewise, the DHCP servers could also notify tollgate about DHCP lease expiries or releases by a similar mechanism.
This would probably be a management command in frontend.
dnsmasq supports calling a script whenever a host is added or removed from the DHCP lease table. This is done with the
It also supplies a number of environment variables with extra information about the dnsmasq instance. Because this only supports calling a script, a wrapper will be needed to transfer this information to a management command, eg:
ISC dhcpd has "on commit" events which allow similar programs to be executed, however does not define a strict format.
This page describes how to run a script whenever there is a new lease: http://jpmens.net/2011/07/06/execute-a-script-when-isc-dhcp-hands-out-a-new-lease/
(Note, those commands aren't actually implemented yet, they're just plans.)
Though given the concerns above I'm worried that triggering on expiry will break some devices.
But I'm of the opinion that it's a bug on their end, not mine. But that won't stop us copping the blame for it either.
perhaps a quick fix would be, instead of "online computers and devices" it should be "all devices listed"
On the my devices and quota page
Switch on internet connectivity. If you have quota available, internet access will be granted to all of your online computers and devices.
No, this is something different.
Basically at the moment in order for a host to come back online, it needs to either go through one of the following two conditions:
At the moment number 2 isn't happening often enough.
But the better way to handle this is to have the DHCP server notify when it's lease table has changed. This way it isn't run an excessive amount of times.