Forums

Resolved
0 votes
Hi all,

We are currently using ClearOS 7.5 in our office as gateway and I having this error Connection Failure or DNS Lookup Failed. It's just working fine recently but I don't what really happened.
We are using my ISPs default gateway as DNS. Please see attached file
Attachments:
Monday, October 04 2021, 04:42 AM
Share this post:
Responses (8)
  • Accepted Answer

    Wednesday, October 06 2021, 01:45 PM - #Permalink
    Resolved
    0 votes
    Sorry for the late reply, Our setup is a modem is connected to a Mikrotik router>Ubiquiti Switch>Supermicro(I cant remember the model) where the ClearOS is installed. Which we are currently figuring out what to do.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, October 05 2021, 09:11 AM - #Permalink
    Resolved
    0 votes
    Is the router in bridge mode or something? Otherwise how are you getting public IP's on ClearOS? Is ClearOS in a DMZ? Generally, if ClearOS were directly connected to a modem, I'd expect it to have a public address of base address +2 with a gateway of base address +1 so your ClearOS address would be 122.54.247.34 with a gateway of .33, so I am not understanding your set up. Presumably your Router is handling the IP subnet part and forwarding specified IP's to the ClearOS port on the router?

    Have you had this set up working and if so, has something changed recently?

    Also do you have the lspci output I requested?
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, October 05 2021, 08:52 AM - #Permalink
    Resolved
    0 votes
    You can install the System Reports from the Marketplace. You can get the same information from the file /etc/clearos-release.

    I can't access Marketplace, it said DNS Lookup failed and it's ClearOS release 7.9.1 (Final)

    Your report is showing you have connectivity issues and can't contact GoogleDNS or Cloudflare DNS. You need to fix that somehow. Has anything changed in your system recently? Is ClearOS your router or is it behind a router?

    my ClearOS is behind a router.

    Here's what I get:

    EXTIF="eno2"
    LANIF="enp1s0f1"
    DMZIF=""
    HOTIF=""
    [root@gateway ~]# ifconfig | grep '^\S' -A1
    eno2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 122.54.247.46 netmask 255.255.255.224 broadcast 122.54.247.63
    --
    eno2:200: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 122.54.247.58 netmask 255.255.255.255 broadcast 122.255.255.255
    --
    eno2:201: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 122.54.247.35 netmask 255.255.255.255 broadcast 122.255.255.255
    --
    eno2:202: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 122.54.247.60 netmask 255.255.255.255 broadcast 122.255.255.255
    --
    eno2:203: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 122.54.247.59 netmask 255.255.255.255 broadcast 122.255.255.255
    --
    enp1s0f1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.21.1 netmask 255.255.255.0 broadcast 192.168.21.255
    --
    lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
    inet 127.0.0.1 netmask 255.0.0.0
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, October 05 2021, 08:27 AM - #Permalink
    Resolved
    0 votes
    You can install the System Reports from the Marketplace. You can get the same information from the file /etc/clearos-release.

    Your report is showing you have connectivity issues and can't contact GoogleDNS or Cloudflare DNS. You need to fix that somehow. Has anything changed in your system recently? Is ClearOS your router or is it behind a router?

    What do you get from:
    grep IF /etc/clearos/network.conf
    ifconfig | grep '^\S' -A1
    lspci -k | grep Eth -A3
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, October 05 2021, 08:08 AM - #Permalink
    Resolved
    0 votes
    Have you checked for connectivity issues in /var/log/syswatch? Is it causing you any issues?


    Here's the log from/var/log/syswatch?:

    Tue Oct 5 15:59:12 2021 info: system - WAN network is not up
    Tue Oct 5 15:59:32 2021 info: eno2 - ping check on server #1 failed - 8.8.8.8 (ping size: 64)
    Tue Oct 5 15:59:45 2021 info: eno2 - ping check on server #2 failed - 1.1.1.1 (ping size: 64)
    Tue Oct 5 15:59:45 2021 warn: eno2 - connection is down
    Tue Oct 5 15:59:47 2021 info: eno2 - waiting for static IP reconnect
    Tue Oct 5 15:59:47 2021 info: system - WAN network is not up
    Tue Oct 5 16:00:07 2021 info: eno2 - ping check on server #1 failed - 8.8.8.8 (ping size: 64)
    Tue Oct 5 16:00:20 2021 info: eno2 - ping check on server #2 failed - 1.1.1.1 (ping size: 64)
    Tue Oct 5 16:00:20 2021 warn: eno2 - connection is down
    Tue Oct 5 16:00:22 2021 info: eno2 - waiting for static IP reconnect
    Tue Oct 5 16:00:22 2021 info: system - WAN network is not up
    Tue Oct 5 16:00:42 2021 info: eno2 - ping check on server #1 failed - 8.8.8.8 (ping size: 64)
    Tue Oct 5 16:00:55 2021 info: eno2 - ping check on server #2 failed - 1.1.1.1 (ping size: 64)
    Tue Oct 5 16:00:55 2021 warn: eno2 - connection is down
    Tue Oct 5 16:00:57 2021 info: eno2 - waiting for static IP reconnect
    Tue Oct 5 16:00:57 2021 info: system - WAN network is not up
    Tue Oct 5 16:01:17 2021 info: eno2 - ping check on server #1 failed - 8.8.8.8 (ping size: 64)
    Tue Oct 5 16:01:30 2021 info: eno2 - ping check on server #2 failed - 1.1.1.1 (ping size: 64)
    Tue Oct 5 16:01:30 2021 warn: eno2 - connection is down
    Tue Oct 5 16:01:32 2021 info: eno2 - waiting for static IP reconnect
    Tue Oct 5 16:01:32 2021 info: system - WAN network is not up
    Tue Oct 5 16:01:52 2021 info: eno2 - ping check on server #1 failed - 8.8.8.8 (ping size: 64)
    Tue Oct 5 16:02:05 2021 info: eno2 - ping check on server #2 failed - 1.1.1.1 (ping size: 64)
    Tue Oct 5 16:02:05 2021 warn: eno2 - connection is down
    Tue Oct 5 16:02:07 2021 info: eno2 - waiting for static IP reconnect
    Tue Oct 5 16:02:07 2021 info: system - WAN network is not up

    For the version, it is available from Reports > Performance and Resources > System Report.


    I dont have the System Report option.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, October 05 2021, 07:11 AM - #Permalink
    Resolved
    0 votes
    To see the logs you can either use the Log Viewer app from the Reports menu (install it if you don't have it) or you can use a tool like WinSCP and browse the file directly. I do the latter. For the version, it is available from Reports > Performance and Resources > System Report.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, October 05 2021, 01:16 AM - #Permalink
    Resolved
    0 votes
    Generally when you explicitly specify DNS servers you do it in pairs. Your ISP will generally have a Primary and Secondary DNS server so you would put those first and put GoogleDNS after that. If you can't enter more than 3 DNS servers in the webconfig, you can do it manually by editing /etc/resolv-peerdns.conf.


    I already brought back the 2 DNS server of our ISP and restarted but I still get Connection Failure.

    Have you checked for connectivity issues in /var/log/syswatch? Is it causing you any issues?


    Where can I access this?

    Also, are you really on ClearOS 7.5. If you have automatic updates enabled, you should be at 7.9.


    My mistake, the version I was telling is ClearOS Theme. Where can I check the software version without system report?
    The reply is currently minimized Show
  • Accepted Answer

    Monday, October 04 2021, 07:44 AM - #Permalink
    Resolved
    0 votes
    I am never sure where the Connection Failure message comes from. One of these days I will find out but I really need too wait for it appears to be able to hunt it down.

    Generally when you explicitly specify DNS servers you do it in pairs. Your ISP will generally have a Primary and Secondary DNS server so you would put those first and put GoogleDNS after that. If you can't enter more than 3 DNS servers in the webconfig, you can do it manually by editing /etc/resolv-peerdns.conf.

    Have you checked that your first DNS server is working with something like:
    dig @a.b.c.33 google.com
    There is an equivalent nslookup command.

    Have you checked for connectivity issues in /var/log/syswatch? Is it causing you any issues?

    Also, are you really on ClearOS 7.5. If you have automatic updates enabled, you should be at 7.9.
    The reply is currently minimized Show
Your Reply