PacketFence - BTS - PacketFence
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000928PacketFenceweb adminpublic2010-03-04 14:152011-01-26 15:43
Reporterobilodeau 
Assigned Torbalzard 
PrioritynormalSeverityminorReproducibilityrandom
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
fixed in git revision
fixed in mtn revision
Summary0000928: Networks sub-menu not visible under Configuration
DescriptionRouted VLANs are not configurable from the web admin.

Roughly, the test to show the networks sub-menu is
- if in vlan mode
- if conf/networks.conf exists
- if conf/networks.conf is not empty

By default, we provide an empty networks.conf so we never display it.

The next statement at line 1603 of bin/pfcmd is the reason why the tab is not visible.
Steps To Reproduce
Additional Information
Tagsusability
Relationships
related to 0000904closed rbalzard Editting Networks and Switches not possible in Web gui, 1.8.7. ZEN 
related to 0001112closed rbalzard configurator.pl and conf/networks.conf 
child of 0000929closed obilodeau Proper routed VLAN support 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-03-04 14:15obilodeauNew Issue
2010-03-04 14:15obilodeauStatusnew => assigned
2010-03-04 14:15obilodeauAssigned To => rbalzard
2010-03-04 14:15obilodeauRelationship addedrelated to 0000904
2010-03-04 14:20obilodeauRelationship addedchild of 0000929
2010-04-29 13:39obilodeauTarget Version1.8.8 => 1.9.0
2010-05-04 17:51obilodeauNote Added: 0001537
2010-05-04 17:51obilodeauTarget Version1.9.0 => 1.9.1
2010-09-15 13:23obilodeauTarget Version1.9.1 => 1.9.2
2010-09-15 13:24obilodeauTag Attached: usability
2010-09-22 16:02obilodeauTarget Version1.9.2 => 1.9.3
2010-11-10 09:53rbalzardNote Added: 0001758
2010-11-10 09:53rbalzardStatusassigned => resolved
2010-11-10 09:53rbalzardResolutionopen => fixed
2010-11-10 10:05obilodeauNote Added: 0001760
2010-11-10 10:05obilodeauStatusresolved => assigned
2010-11-10 10:05obilodeauResolutionfixed => reopened
2010-11-10 11:17rbalzardNote Added: 0001761
2010-11-10 11:18rbalzardStatusassigned => resolved
2010-11-10 11:18rbalzardResolutionreopened => fixed
2010-11-10 11:22obilodeauNote Added: 0001762
2010-11-10 11:23obilodeauRelationship addedrelated to 0001112
2011-01-26 15:43obilodeauStatusresolved => closed

Notes
(0001537)
obilodeau   
2010-05-04 17:51   
since admin guide is clear that we have to start manually then it'll show up on the web, its ok for 1.9.0 and we'll look at it later
(0001758)
rbalzard   
2010-11-10 09:53   
Since PF now generates DHCP and DNS servers configuration files using networks.conf, it is now recommanded to use this feature to manage DHCP and DNS in registration and isolation vlans.

So I put a default/example configuration in networks.conf in the distribution.

The networks sub-menu under Configuration will always be available whether PF generates or not the DHCP and DNS.
I added some documentation in the Admin Guide.
(0001760)
obilodeau   
2010-11-10 10:05   
- I don't think it should be populated with default values except in PF ZEN (we never done that anywhere). Configurator.pl would be the place to do that.
- I think Networks menu should still appear even if the file is empty. so this specific bug is not fixed.
(0001761)
rbalzard   
2010-11-10 11:17   
I changed pfcmd so now we show the networks sub-menu when:
- in vlan mode
- conf/networks.conf exists

Since networks.conf is included in the distribution, the second test will always be true.
(0001762)
obilodeau   
2010-11-10 11:22   
filed an issue for configurator.pl integration 0001112