PacketFence - BTS - PacketFence | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001557 | PacketFence | dhcp | public | 2012-09-28 13:54 | 2012-10-19 11:10 |
| Reporter | candlerb | ||||
| Assigned To | |||||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | open | ||
| Platform | OS | OS Version | |||
| Product Version | 3.5.1 | ||||
| Target Version | 3.6.0 | Fixed in Version | devel | ||
| fixed in git revision | |||||
| fixed in mtn revision | |||||
| Summary | 0001557: Two instances of pfdhcplistener started | ||||
| Description | [root@pf pf]# ps auxwww | grep pfdhcp root 12180 0.0 0.8 238956 33896 ? Ss Sep27 0:08 pfdhcplistener: listening on eth0 root 12198 0.0 0.8 238956 33896 ? Ss Sep27 0:08 pfdhcplistener: listening on eth0 root 17280 0.0 0.0 103244 836 pts/0 S+ 17:22 0:00 grep pfdhcp # grep "pfdhcp.*Start" logs/packetfence.log|tail Sep 27 07:24:47 pfcmd(12114) INFO: Starting pfdhcplistener with '/usr/local/pf/sbin/pfdhcplistener -i eth0 -d &' (pf::services::service_ctl) Sep 27 07:24:47 pfcmd(12114) INFO: Starting pfdhcplistener with '/usr/local/pf/sbin/pfdhcplistener -i eth0 -d &' (pf::services::service_ctl) However the web GUI shows only one process: pfdhcplistener Running Running (pid: 12180) Configuration: ---- 8< ---- [interface eth0] ip=192.0.2.14 type=internal,management mask=255.255.255.224 enforcement=vlan [database] pass=XXXXXX [general] dhcpservers=10.1.7.10,192.0.2.14,192.0.2.15 domain=example.com hostname=pf dnsservers=192.0.2.10,192.0.2.24,192.0.2.80 timezone=Africa/Accra [alerting] emailaddr=postmaster@example.com [interface eth1] ip=0.0.0.0 mask=255.255.255.255 type=monitor enforcement= [guests_self_registration] modes=sponsor [registration] auth=radius guests_self_registration=disabled [trapping] range=192.0.0.0/16,10.0.0.0/8 registration=enabled detection=enabled ------------ (IPs sanitised to 192.0.2, domain sanitised to example.com) Note: you can see eth0 has 'internal,management'. If I change this to 'management' only, then on attempting to start the daemons I get: Checking configuration sanity... FATAL - internal network(s) not defined! | ||||
| Steps To Reproduce | |||||
| Additional Information | It appears that: @listen_ints gets interfaces with type=internal @dhcplistener_ints gets interfaces with type=management and these are combined: my @devices = @listen_ints; push @devices, @dhcplistener_ints; Hence two instances of the daemon are started, because the same interface is marked as both internal and management | ||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2012-09-28 13:54 | candlerb | New Issue | |||
| 2012-09-28 14:02 | obilodeau | Note Added: 0003109 | |||
| 2012-09-29 15:42 | candlerb | Note Added: 0003110 | |||
| 2012-10-19 11:10 | fgaudreault | Status | new => resolved | ||
| 2012-10-19 11:10 | fgaudreault | Fixed in Version | => devel | ||
| 2012-10-19 11:10 | fgaudreault | Target Version | => 3.6.0 | ||
| Notes | |||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||