PacketFence - BTS - PacketFence
View Issue Details
0001013PacketFenceconfigurationpublic2010-06-09 03:592011-05-04 11:51
obilodeau 
obilodeau 
normalminorhave not tried
closedno change required 
 
 
0001013: pfdhcplistener not listening on routed interfaces by default
Routed isolation and registration networks were not being DHCP sniffed. I had to add an explicit type=dhcplistener entry. IIRC this is done automatically on spanned networks.

Wasn't intuitive to me. I configured PacketFence to run a DHCP server on these interfaces, of course it should run a dhcplistener!? no?
No tags attached.
Issue History
2010-06-09 03:59obilodeauNew Issue
2010-06-09 03:59obilodeauStatusnew => assigned
2010-06-09 03:59obilodeauAssigned To => obilodeau
2010-06-09 03:59obilodeauSummarypfdhcplistener not listening on routed interfaces => pfdhcplistener not listening on routed interfaces by default
2010-09-15 11:39obilodeauTarget Version1.9.1 => 1.9.2
2010-09-22 16:02obilodeauTarget Version1.9.2 => 1.9.3
2010-10-07 14:58obilodeauNote Added: 0001720
2010-10-07 14:58obilodeauStatusassigned => resolved
2010-10-07 14:58obilodeauResolutionopen => no change required
2011-05-04 11:51obilodeauStatusresolved => closed

Notes
(0001720)
obilodeau   
2010-10-07 14:58   
Tried to reproduce in lab on trunk/ (revno 5eb6a643a63d20379b95368b6f3b03fdc1007b29) using networks.conf (routed) mechanism.

I was not able to reproduce. pfdhcplisteners went up and worked fine for all interfaces without a specific statement in pf.conf.

I'm guessing some other change since the bug was reported fixed the behavior. Feel free to re-open with instructions to reproduce.