DHCP won't start with Virtual IP Alias on interface



  • I have a bridged interface with a bunch of VLAN interfaces on it.

    The IP address on bridge0 is 10.0.0.1/8

    DHCP is serving leases on bridge0 from 10.0.1.2 - 10.0.2.254. This is working fine.

    However, if I add a virtual IP alias to the bridge0 interface, 172.16.0.1/16 DHCP fails to start.

    DHCP error log gives me the following:

    Jan  9 19:03:00 t31 dhcpd: bad range, address 10.0.0.2 not in subnet 172.16.0.0 netmask 255.255.0.0
    

    For some reason, DHCPD is trying to bind on my virtual IP alias, not the real bridge0 IP.

    I don't need DHCP to serve on the 172.16.0.0/16 subnet, as they're all just access points with static IPs. I need to add this VIP to manage those APs from WAN.

    Is this a bug, or an intended function?


Log in to reply