Profile Details

Toggle Sidebar
Recent updates
  • Hi Tony,
    I suspect the invalid condition can arise from configuring a NIC with a fixed IP, setting up the DHCP server on the NIC then changing the LAN IP/subnet. I'd need to test this scenario. iirc, on routers I've used, in this scenario they have automatically moved the DHCP settings to the IP/new subnet.

    Rob, do you know if these two errant NIC's, eth0 and eth1, had previously been configured to use the 192.168.130.0/24 subnet?

  • Nick Howitt wrote:

    Hi Tony,
    I suspect the invalid condition can arise from configuring a NIC with a fixed IP, setting up the DHCP server on the NIC then changing the LAN IP/subnet. I'd need to test this scenario. iirc, on routers I've used, in this scenario they have automatically moved the DHCP settings to the IP/new subnet.

    Rob, do you know if these two errant NIC's, eth0 and eth1, had previously been configured to use the 192.168.130.0/24 subnet?


    Now that I think about it, I installed ClearOS and it defaults to no VLANs to allow you to set it up and connect initially. Then I added the two VLAN subnets so yes, at one point eth0 was on the 130 subnet.

    I commented out the two DHCP lines for eth0 and eht1, deleted the eth1 interface from the ClearOS DHCP page. eth0 is also disabled now so it can't sneak in and mess stuff up.

    It seems to have worked, I just need to let the leases run out on the clients and we'll see what they get assigned.

    Thanks for your help Nick and Tony!

    Rob

  • You're right, it's even more confusing now.

    I only used the webconfig to set up the server but you're right, since both eth1 and eth0 aren't in use they're both listed as "Invalid" in the DHCP settings. I've never set up DHCP on them so I'm not sure where those entries came from.

    Can I safely delete the DHCP ranges/entries for eth1 and eth0 without messing up my nice vlans?

  • Here's the output:

    # ifconfig | grep ^e -A 1
    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.132.1 netmask 255.255.255.0 broadcast 192.168.132.255
    --
    eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet6 fe80::b8a7:cdff:feca:d118 prefixlen 64 scopeid 0x20<link>
    --
    eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet6 fe80::3893:47ff:fe06:a212 prefixlen 64 scopeid 0x20<link>
    --
    eth0.10: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.130.1 netmask 255.255.255.0 broadcast 192.168.130.255
    --
    eth0.20: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.131.1 netmask 255.255.255.0 broadcast 192.168.131.255
    # cat /etc/dnsmasq.d/dhcp.conf
    dhcp-option=eth0,1,255.255.255.0
    dhcp-option=eth0,28,192.168.130.255
    dhcp-option=eth0,3,192.168.130.1
    dhcp-option=eth0,6,192.168.130.1
    dhcp-option=eth0.10,1,255.255.255.0
    dhcp-option=eth0.10,28,192.168.130.255
    dhcp-option=eth0.10,3,192.168.130.1
    dhcp-option=eth0.10,6,192.168.130.3
    dhcp-option=eth0.20,1,255.255.255.0
    dhcp-option=eth0.20,28,192.168.131.255
    dhcp-option=eth0.20,3,192.168.131.1
    dhcp-option=eth0.20,6,192.168.131.1
    dhcp-option=eth1,1,255.255.255.0
    dhcp-option=eth1,28,192.168.130.255
    dhcp-option=eth1,3,192.168.130.1
    dhcp-option=eth1,6,192.168.130.1
    dhcp-range=eth0,192.168.130.100,192.168.130.254,12h
    dhcp-range=eth0.10,192.168.130.100,192.168.130.229,1h
    dhcp-range=eth0.20,192.168.131.100,192.168.131.229,1h
    dhcp-range=eth1,192.168.130.100,192.168.130.254,12h

  • The WAP is strictly an access point but the issue is occurring with some wired systems as well. This is a new issue in the last month but none of the hardware has changed in that time.

  • The WAP is strictly an access point but the issue is occurring with some wired systems as well. This is a new issue in the last month but none of the hardware has changed in that time.

  • The WAP is strictly an access point but the issue is occurring with some wired systems as well. This is a new issue in the last month but none of the hardware has changed in that time.

  • DHCP Assigning IPs Outside of Allowed Range

    I have a ClearOS server running V7 with latest updates. I have two VLANs that split an "open" (but still password protected) wireless network from the main wired and "secure" wireless network.

    The problem I'm having is that ClearOS seems to be ignoring my DHCP range for the secure network. I have it giving out IPs in the range 100-229 but I have several clients getting IPs in the 230+range. I've checked all of the configuration several times and nothing seems out of place. The clients are iPads, desktops, laptops, and android phones. Some are wired and some are wireless.

    This is a pretty big issue because I've given the 230+ range to another guy for testing networked equipment and he uses static IPs. It's only a matter of time until there's a conflict that shuts down his testing.

    This seems to be a recent thing within the last month.

    Any ideas what's going on?

    Thanks,

    Rob

  • Rob A
    Rob A unlocked the badge Newbie
    Newbie
    Congrats on registering on the site!