Profile Details

Toggle Sidebar
Recent updates
  • We uninstalled it as it wasn't used.

    Is enp7s0 mentioned in /etc/clearos/multiwan.conf? If so, please remove it.

    It was - we removed all entries mentioning enp7s0.

    I don't like the message log either. Perhaps a full restart is in order.

    Full restarted helped - DHCP and internet are working on our new HotLAN :)

    We can ping 192.168.25.1 (HotLAN gatewa). We can also ping 192.168.2.1 (main LAN gateway) which is a bit strange. Our local domain is not visible from a client connected to HotLAN though.

  • Output of '/etc/dnsmasq.conf':



    In '/etc/dnsmasq.d' folder we have 2 files:
    - 'app-adamone.conf' which is empty
    - 'dhcp.conf' which contains:


    Output of 'tcpdump -nni enp7s0 portrange 67-68' when client PC unsuccessfully tried to obtain a lease from DHCP:
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on enp7s0, link-type EN10MB (Ethernet), capture size 262144 bytes
    16:22:51.588666 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
    16:22:55.124773 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
    16:23:00.136082 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
    16:23:08.883978 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
    16:23:25.839126 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
    16:23:58.210216 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
    16:24:03.047948 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
    16:24:10.554854 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
    16:24:26.462497 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:xx:xx:09:a1:9d, length 300
    ^C
    9 packets captured
    9 packets received by filter
    0 packets dropped by kernel

    'var/log/messages' filtered by 'enp7s0' contains plenty of:

  • Tomas
    Tomas unlocked the badge Bookworm
    Bookworm
    Loves reading the forums.
  • This is puzzling. On the PC, when IP Settings are by DHCP/automatic, is the PC getting any IP address (except one beginning 169.x.y.z)?


    It's getting '169. 254.27.239', subnet mask '255.255.0.0', no gateway, no DNS.


    no response when run on ClearOS.

    Output of:


    What is your HotLAN network set up while testing? Can you try with a PC directly connected to enp7s0?

    We eliminated all routers yesterday. Since yesterday all tests are made with one PC connected directly to 'enp7s0' via cat6 ethernet cable. We also tried different cables.

  • As it looks like there were some config files affected by the same NIC previously being set as 'external' we deleted it in 'IP Settings' and re-created the HotLAN with the same config.

    Still DHCP server is not working for HotLAN, can't ping 192.168.25.1 from the client with manual IP settings and internet is not working on the HotLAN client.

  • Please remove the line.


    Done.

    'ifcfg-enp7s0' is now:



    I have also amended '/etc/clearos/network.conf' and for enp7s0 put zeros. Then run: 'systemctl restart network.service'.

    Still no functional DHCP server for HotLAN and can't ping 192.168.25.1 from a client connected via ethernet to the enp7s0 NIC.

    Manual IP config of the Win 10 client used for testing:
    IP Address: 192.168.25.3
    Subnet mask: 255.255.255.0
    Gateway: 192.168.25.1
    DNS: 192.168.25.1

    Still can't ping 192.168.25.1 and no internet even if I use 8.8.8.8 as DNS.

  • Also, why does the ifcfg-enp7s0 file have GATEWAY line? That should not be there and only gets added for External interfaces.


    This NIC was previously used as 'External' interface so possible something that "remained" from that (bug in webconfig maybe)?

  • contents of '/etc/clearos/network.conf'




    contents of '/etc/dnsmasq.d/dhcp.conf'

  • Hi Nick,

    HotLAN does not have access to the server either which is why pings don't work.


    We have non-functional DHCP on our HotLAN and we can't ping the HotLAN gateway. Basically, HotLAN is not working at all.


    Output:



    'enp4s0' - external 1 (multi-WAN)
    'enp5s0' - external 2 (multi-WAN)
    'enp6s0' is our LAN.
    'enp7s0' is our HotLAN's NIC.

  • HotLAN and Firewall - no DHCP, no internet, can't ping gateway

    Hi

    Running 7.9.1 here with 4 NICS:

    enp4s0 - external 1 (multi-WAN)
    enp5s0 - external 2 (multi-WAN)
    enp6s0 - main LAN
    enp7s0 - NEW! -> HotLAN

    By definition in ClearOS docs HOT LAN is: "Interfaces designated as HotLAN have NAT applied to them but do not have access to LAN networks. Specify HotLAN for networks that are considered restricted but still need access to the Internet."

    'ifcfg-enp7s0':



    We also have DHCP enabled for our new HotLAN.

    The problem is nothing is working as it should - DHCP doesn't assign IP to HotLAN clients, if we enter IP settings manually on a client we can't ping gateway and obviously clients have no internet.

    The 'enp7s0' interface is up.

    Output of 'iptables -L -n -v':



    All IPtables rules for 'enp7s0' were added by ClearOS.