PacketFence - BTS - PacketFence
View Issue Details
0001188PacketFenceupstreampublic2011-02-21 13:582011-03-03 15:25
obilodeau 
obilodeau 
normalmajorrandom
closedfixed 
 
2.1.0 
48e606bbc24225f730070db71166690c0c3b558f
0001188: Ubuntu / NetworkManager / Linux kernel doesn't do DHCP after a 2 second link down
We got report of this on the mailing list and we independently experienced it in our lab.

A 2 sec down / up is not long enough for Ubuntu to detect a link change and perform DHCP again.

I'm not sure why we haven't heard about this sooner.. Did it used to work? Is it a regression or not? If so, what in component?

I would think that it is in NetworkManager but it could be the kernel that is taking it's time to pass the information to userland.

The problem with raising the delay from 2 to 6 (for ex.) is that we affect all operating systems, even those who could be bounced quicker.
No tags attached.
Issue History
2011-02-21 13:58obilodeauNew Issue
2011-02-21 13:58obilodeauStatusnew => assigned
2011-02-21 13:58obilodeauAssigned To => obilodeau
2011-02-21 14:00obilodeauNote Added: 0001873
2011-03-01 17:42obilodeaumtn revision => 48e606bbc24225f730070db71166690c0c3b558f
2011-03-01 17:42obilodeauNote Added: 0001890
2011-03-01 17:42obilodeauStatusassigned => resolved
2011-03-01 17:42obilodeauFixed in Version => 2.0.2
2011-03-01 17:42obilodeauResolutionopen => fixed
2011-03-03 15:20obilodeauFixed in Version2.0.2 => 2.1.0
2011-03-03 15:25obilodeauStatusresolved => closed

Notes
(0001873)
obilodeau   
2011-02-21 14:00   
work around for now: edit sbin/pfsetvlan on line 1625 (as of 2.0.1) and change sleep(2); with sleep(6);

things should work afterwards
(0001890)
obilodeau   
2011-03-01 17:42   
Default bounce duration is now 4 seconds long which is enough for Ubuntu to see the linkdown. Also the value is configurable with bounce_duration under [vlan] in conf/pf.conf. Default value in conf/pf.conf.defaults.