PacketFence - BTS - PacketFence
View Issue Details
0000929PacketFencecorepublic2010-03-04 14:202012-05-08 10:30
obilodeau 
obilodeau 
highminorN/A
closedfixed 
 
3.0.03.0.0 
0000929: Proper routed VLAN support
Routed VLAN support needs love.

Issues out of my head:
- no documentation
- no example config (networks.conf format not even documented)
- no documentation.conf entries
- confusion over wether vlan.dhcpd and vlan.named need to be enabled or not
- under what conditions should the Networks tab be visible?

The fix will need review as we think we can achieve massive simplification if we do it right.
usability
parent of 0000928closed rbalzard Networks sub-menu not visible under Configuration 
parent of 0000957closed obilodeau snort should have a flag in networks.conf 
parent of 0001031closed obilodeau better validation for networks.conf file 
parent of 0001112closed rbalzard configurator.pl and conf/networks.conf 
parent of 0001113closed rbalzard Re-validate install guide / admin guide with new dhcpd and bind handled by default 
related to 0000934closed obilodeau PacketFence should always manage dhcpd and named 
related to 0000956closed fgaudreault confusion between trapping.range, pf.conf's interfaces and networks.conf 
Issue History
2010-03-04 14:20obilodeauNew Issue
2010-03-04 14:20obilodeauStatusnew => assigned
2010-03-04 14:20obilodeauAssigned To => rbalzard
2010-03-04 14:20obilodeauRelationship addedparent of 0000928
2010-03-17 14:03obilodeauRelationship addedrelated to 0000934
2010-04-14 09:42obilodeauRelationship addedrelated to 0000956
2010-04-14 09:58obilodeauRelationship addedparent of 0000957
2010-04-29 13:39obilodeauTarget Version1.8.8 => 1.9.0
2010-05-04 16:23obilodeauTarget Version1.9.0 => 1.9.1
2010-07-13 15:02obilodeauRelationship addedparent of 0001031
2010-09-10 10:43obilodeauNote Added: 0001650
2010-09-10 10:43obilodeauTag Attached: usability
2010-09-10 10:50obilodeauNote Edited: 0001650
2010-09-15 11:20obilodeauNote Added: 0001663
2010-09-15 11:20obilodeauTarget Version1.9.1 => 1.9.2
2010-09-22 16:02obilodeauTarget Version1.9.2 => 1.9.3
2010-11-10 10:02rbalzardNote Added: 0001759
2010-11-10 11:22obilodeauRelationship addedparent of 0001112
2010-11-10 11:47obilodeauRelationship addedparent of 0001113
2011-09-07 17:24obilodeauRelationship addedrelated to 0001043
2011-09-07 17:27obilodeauAssigned Torbalzard =>
2011-09-07 17:27obilodeauTarget Version1.9.3 => +1
2011-10-14 10:19fgaudreaultNote Added: 0002356
2011-10-14 16:30obilodeauRelationship deletedrelated to 0001043
2012-02-29 10:58obilodeauCategoryfuture => core
2012-05-08 10:30obilodeauNote Added: 0002706
2012-05-08 10:30obilodeauStatusassigned => resolved
2012-05-08 10:30obilodeauFixed in Version => 3.0.0
2012-05-08 10:30obilodeauResolutionopen => fixed
2012-05-08 10:30obilodeauAssigned To => obilodeau
2012-05-08 10:30obilodeauStatusresolved => closed
2012-05-08 10:30obilodeauTarget Version+1 => 3.0.0

Notes
(0001650)
obilodeau   
2010-09-10 10:43   
(edited on: 2010-09-10 10:50)
Add to this list:

- clarify in the documentation the difference between gateway and pf_gateway

someone on the list mentionned the fact that it is unclear and he is right about that!

my explanation at the time: Gateway is the official gateway of the network you added (sent to clients in dhcp reply). pf_gateway is the IP that PF must use to reach that subnet (add in it's own routing table as a hop to reach said subnet).

(0001663)
obilodeau   
2010-09-15 11:20   
It's a bit sad but it looks like it won't make 1.9.1 cycle.
(0001759)
rbalzard   
2010-11-10 10:02   
I added some documentation in the Admin Guide about networks.conf so that every setting is now well detailed and there wont be any confusion anymore between gateway and pf_gateway
(0002356)
fgaudreault   
2011-10-14 10:19   
Should we close this one? I think everything is there and explained for routed installs.
(0002706)
obilodeau   
2012-05-08 10:30   
Agreed. This one is 'done' since the 3.0 release at the very least.