PacketFence - BTS - PacketFence | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001565 | PacketFence | dhcp | public | 2012-09-29 16:59 | 2012-10-19 11:03 |
| 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 | 0001565: dhcpd does not start if all isolation/registration networks are remote | ||||
| Description | Suppose you have a registration interface configured: [interface eth1.255] enforcement=vlan ip=192.168.255.1 type=internal mask=255.255.255.0 Similarly, isolation interface eth1.254, 192.168.254.1 However the actual networks you want to enforce are remote. So in conf/networks.conf do you not have any entries [192.168.255.0] or [192.168.254.0]. Instead you have, say, [192.168.2.0] dns=192.168.2.1 dhcp_start=192.168.2.10 gateway=192.168.2.1 named=enabled dhcp_max_lease_time=30 dhcpd=enabled type=vlan-registration netmask=255.255.255.0 dhcp_end=192.168.2.246 dhcp_default_lease_time=30 domain-name=vlan-registration.localdomain ... similar for remote isolation VLAN. Under this circumstance, dhcpd does not start. You get the following error: ---- No subnet declaration for eth1.255 (192.168.255.1). ** Ignoring requests on eth1.255. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth1.255 is attached. ** No subnet declaration for eth1.254 (192.168.254.1). ** Ignoring requests on eth1.254. If this is not what you want, please write a subnet declaration in your dhcpd.conf file for the network segment to which interface eth1.254 is attached. ** Not configured to listen on any interfaces! ---- The problem is simple to fix. You need to add empty subnet declarations for the connected interfaces where you wish to listen for remote DHCP requests, but not actually serve DHCP for the local network. It would be good if PF did this automatically in the generated %%networks%% | ||||
| Steps To Reproduce | |||||
| Additional Information | WORKAROUND: manually add the empty interface subnets into conf/dhcpd.conf # dhcpd configuration # This file is manipulated on PacketFence's startup before being given to dhcpd authoritative; ddns-update-style none; ignore client-updates; ### ENABLE DHCP ON INTERFACES ### subnet 192.168.255.0 netmask 255.255.255.0 { } subnet 192.168.254.0 netmask 255.255.255.0 { } ### END ### %%networks%% | ||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2012-09-29 16:59 | candlerb | New Issue | |||
| 2012-09-30 04:37 | candlerb | Note Added: 0003112 | |||
| 2012-10-19 11:03 | fgaudreault | Status | new => resolved | ||
| 2012-10-19 11:03 | fgaudreault | Fixed in Version | => devel | ||
| 2012-10-19 11:03 | fgaudreault | Target Version | => 3.6.0 | ||
| Notes | |||||
|
|
|||||
|
|
||||