DHCP on non-standard additional interfaces

General questions.
Post Reply
dsm5
Posts: 1
Joined: February 10th, 2019, 10:39 am

DHCP on non-standard additional interfaces

Post by dsm5 » February 10th, 2019, 11:59 am

I have an IPFire installation running on a box with 4 Ethernet ports. Because my Blue interface is on the WiFi adaptor I had a spare Ethernet port. I have manually configured this port as an additional interface for a low-trust domain for IoT devices that I call "PINK". My subnets therefore look like this:

Code: Select all

GREEN  192.168.0.0/25
PINK   192.168.0.128/27
BLUE   192.168.0.160/27
ORANGE 192.168.0.192/27
RED    [dynamically allocated by ISP]
Mostly this works very well: devices on my "PINK" subnet appear on some of the IPFire configuration pages (such as WIO) as white "unknown", but I cannot get DHCP to work on the PINK interface.

I have created a /var/ipfire/dhcp/dhcpd.conf.local file for my PINK interface and allowed bootp on it. I watch the traffic with dhcpdump when I connect a device that expects to get an address via bootp. That device sends the broadcast requests correctly but IPFire does not reply. When I run udhcpd on another machine on that subnet it issues an address to that device correctly.

Is my dhcpd.conf.local file being ignored? It is listed correctly as an include at the bottom of my dhcpd.conf file.

Post Reply