Forums

Resolved
0 votes
Possible bug? More people having this issue?

Fresh install of ClearOS 7.5.0. The issue I have is that the nameservers of my ISP are not picked up. I have to manual add a DNS server.
Sunday, January 27 2019, 05:25 PM
Share this post:
Responses (24)
  • Accepted Answer

    Saturday, February 02 2019, 07:58 PM - #Permalink
    Resolved
    0 votes
    Hi Tony,

    How are you?

    Tony Ellis wrote:

    Marcel - There are three classes of Intel Network NICs devices using the same igb driver.
    82575/6, 82580
    I350
    I210 and I211
    Have a dual port 82575EB based NIC in one of my firewalls using the ClearOS 7.x supplied igb driver - never been a problem.


    Good information. Thank you!



    Changed subnets!

    Is this just a statement you changed them manually - or they changed on you during the reset unexpectedly?


    Sorry, Tony that was a reaction to Nick. He advised me to change my subnet to something else as 192.168.0.x or 192.168.1.x because that is often used for VPN.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 02 2019, 01:55 PM - #Permalink
    Resolved
    0 votes
    Marcel - There are three classes of Intel Network NICs devices using the same igb driver.
    82575/6, 82580
    I350
    I210 and I211
    Have a dual port 82575EB based NIC in one of my firewalls using the ClearOS 7.x supplied igb driver - never been a problem.

    Changed subnets!

    Is this just a statement you changed them manually - or they changed on you during the reset unexpectedly?
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 02 2019, 10:48 AM - #Permalink
    Resolved
    0 votes
    This is the chassis.

    https://cdn.shopify.com/s/files/1/1058/4910/products/1-14101Q31410B3_078c5a9f-d1e6-4f3b-9492-6e8b4c5b5f7b_2048x.jpg?v=1527194393

    I bought it from X-case located in the UK. It has very nice chassis and the people are friendly. Now with the Brexit buy chassis from this webshop becomes more expensive. :(

    This is the board I want to use.

    https://www.supermicro.com/CDS_Image/uploads/imagecache/600px_wide/intel_motherboard_active/n13it4hx.png

    Supermicro website

    It uses "Dual LAN with Intel® Ethernet Controller I210-AT". Is that the same as my old ClearOS server????!!!! <lol>
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 02 2019, 10:43 AM - #Permalink
    Resolved
    0 votes
    Before searching for a solution I'm thinking of building a ClearOS server with my 24 bays chassis. I want to move my hardware of my dedicated Plex server to this chassis, and use the hardware were ClearOS now is running on for my dedicated Plex server. This hardware is the oldest hardware, and I want to replace it in the near future. So the hardware for the 24 bays chassis consist of a Supermicro board with a Xeon E3-1270v5. I think this is very nice hardware for ClearOS build not the newest but powerful (very) enough!
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 02 2019, 08:43 AM - #Permalink
    Resolved
    0 votes
    I don't know of any fixes for the igb driver. ElRepo don't publish drivers for it. I use it on my LAN with no noticeable problems.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, February 02 2019, 07:16 AM - #Permalink
    Resolved
    0 votes
    Changed subnets!

    Marcel van van Leeuwen wrote:

    No the infamous:

    [root@voyager ~]# lspci -k | grep Eth -A 3
    03:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
    Subsystem: Intel Corporation Device 35b4
    Kernel driver in use: igb
    Kernel modules: igb
    04:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
    Subsystem: Intel Corporation Device 35b4
    Kernel driver in use: igb
    Kernel modules: igb


    If I remember correctly there was also something with the drivers some version ago of ClearOS....


    And indeed the server did a reset yesterday. If I remember correctly the issue is as I said because of the NIC.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, January 29 2019, 07:59 PM - #Permalink
    Resolved
    0 votes
    Yeah, it was not my intention to change anything I understood why you asked for the output.

    I think it would be nice to hide unused interface a bit more in the DHCP server app, but it's minor thing..

    That is what I thought. I'm going to change that this weekend. Good information!
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, January 29 2019, 03:49 PM - #Permalink
    Resolved
    0 votes
    Don't change anything there. All those settings belong to your LAN interface. In the DHCP server screen, eno1 is not configured waiting for you to configure if necessary (which it is not). Really I would argue the option should net even be there for an external WAN interface. The problem then is that in standalone mode, you still use a WAN interface and it is valid if you want to configure ClearOS as the DHCP server on its WAN interface (your LAN).

    192.168.0.0/24 and 192.168.1.0/24 are not good for roadwarrior VPN's as too many locations use them. Also if you ever connect a router as a WAP to your LAN they often come configured in one of those two subnets (often with a .1 or .254 IP address) and you can accidentally end up with two devices on the same IP address which is a problem and very hard to diagnose.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, January 29 2019, 03:04 PM - #Permalink
    Resolved
    0 votes
    It's a bit strange that you can't remove eno1 from the list in my opinion. Just completely remove and that one enox is visible active with the DHCP server.

    [root@voyager ~]# 
    cat /etc/dnsmasq.d/dhcp.conf
    # This file is managed by the API. Please add custom options in dnsmasq.conf.
    dhcp-option=eno2,1,255.255.255.0
    dhcp-option=eno2,28,192.168.1.255
    dhcp-option=eno2,3,192.168.1.1
    dhcp-option=eno2,6,192.168.1.1
    dhcp-range=eno2,192.168.1.100,192.168.1.254,12h


    It looks okay. I can set the lease time to unlimited I guess...

    Avoid subnets 192.168.0.0/24 and 192.168.1.0/24 because of vpn? 192.168.1.0/24 that is what I use because of my Ubiquiti Unifi gear and is by default on that range. I will change it!
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, January 29 2019, 02:14 PM - #Permalink
    Resolved
    0 votes
    Disabled is fine. It should then have no references in /etc/dnsmasq.d/dhcp.conf.

    BTW the LAN subnets 192.168.0.0/24 and 192.168.1.0/24 (as in your screenshot) are best avoided.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, January 29 2019, 01:07 PM - #Permalink
    Resolved
    0 votes
    Checked.

    [root@voyager ~]# 
    cat /etc/resolv.conf
    # Please do not edit this file.
    # See http://www.clearcenter.com/support/documentation/clearos_guides/dns_and_resolver
    domain lionux.nl
    nameserver 127.0.0.1



    [root@voyager ~]# cat /etc/resolv-peerdns.conf
    ; generated by /usr/sbin/dhclient-script
    search arnhem.chello.nl lionux.lan
    nameserver 62.179.104.196
    nameserver 213.46.228.196


    Nothing strange looks okay to me.

    I now understand what you mean with the DHCP server part. I did not configure that.., ClearOS did. I tried to delete the IP range start and end but ClearOS does not accept a blank field. Strange! How is yours configured? See screenshot mine eno1 gets every time disabled.., or is that okay when it's disabled? So it's not controlled by the DHCP server?
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, January 29 2019, 12:39 PM - #Permalink
    Resolved
    0 votes
    Sure you can do a temporary override in IP settings, but a WAN interface should never be configured as a DHCP server and client at the same time and it is very unlikely you will ever want it as a DHCP server. You configure it as a DHCP client in the IP settings screen just by saying the interface type is DHCP. The only webconfig option you get is to override the DNS settings you get by DHCP. Please delete the DHCP server configuration you have attached to you WAN.

    At a guess you got that by checking a box Enable DHCP Server when you first configured the interface.

    It may also be worth checking your /etc/resolv.conf and /etc/resolv-peerdns.conf. Mine are:
    [root@server ~]# cat /etc/resolv.conf
    # Please do not edit this file.
    # See http://www.clearcenter.com/support/documentation/clearos_guides/dns_and_resolver
    domain howitts.co.uk
    nameserver 127.0.0.1
    and
    [root@server ~]# cat /etc/resolv-peerdns.conf
    ; generated by /usr/sbin/dhclient-script
    search cable.virginmedia.net
    nameserver 208.67.222.222
    nameserver 208.67.220.220
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, January 29 2019, 11:55 AM - #Permalink
    Resolved
    0 votes
    I'm not sure if I follow you.. but indeed the WAN site is acting as a DHCP client because the DHCP server of my ISP is handing out the IP address and DNS servers. You can temporary override the DNS server so it's not using the DNS servers of your ISP.

    I un-ticked "Automatic DNS Servers" Network Interfaces --> Interface --> Settings, and after that I reactivated it again and now it use the DNS servers of my ISP. See screenshot.
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, January 29 2019, 10:29 AM - #Permalink
    Resolved
    0 votes
    The WAN should not have the DHCP server configured. It is acting as a DHCP client and not a server.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, January 29 2019, 10:10 AM - #Permalink
    Resolved
    0 votes
    Checked the DHCP settings of the NIC on the WAN site and it receives the address of the nameserver. See my screenshot. If I remove the temporary nameserver I have no nameserver... It seems that the nameserver is not pass through?

    Update: hmmm, the nameserver has the same ip address as the gateway that is not good..
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 28 2019, 09:22 PM - #Permalink
    Resolved
    0 votes
    No the infamous:

    [root@voyager ~]# lspci -k | grep Eth -A 3
    03:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
    Subsystem: Intel Corporation Device 35b4
    Kernel driver in use: igb
    Kernel modules: igb
    04:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
    Subsystem: Intel Corporation Device 35b4
    Kernel driver in use: igb
    Kernel modules: igb


    If I remember correctly there was also something with the drivers some version ago of ClearOS....
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 28 2019, 08:43 PM - #Permalink
    Resolved
    0 votes
    Is it our infamous r8169 driver on an RTL8111/8168/8411 NIC?
    lspci -k | grep Eth -A 3
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 28 2019, 08:36 PM - #Permalink
    Resolved
    0 votes
    The server is set as gateway and connects to my ISP. The connection is set to external and has DHCP enabled. I have no static ip address.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 28 2019, 08:25 PM - #Permalink
    Resolved
    0 votes
    Could your DHCP server be misconfigured at all? The one which ClearOS is trying to get the DNS servers from?
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 28 2019, 04:46 PM - #Permalink
    Resolved
    0 votes
    For some reason I can't add a attachment to a post that I edit. So new post! See picture below.
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 28 2019, 04:43 PM - #Permalink
    Resolved
    0 votes
    Yes, that is true!

    I did a re-install today, and the result are the same. No name server before registering the system during registering I have to manually add a temporary name server then the installation wizard completes without issues. If I don't add a name server manually I can't complete the installation wizard.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, January 27 2019, 06:46 PM - #Permalink
    Resolved
    0 votes
    That is weird. I think the installer does a DNS test during installation. The first run wizard also does.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, January 27 2019, 06:04 PM - #Permalink
    Resolved
    0 votes
    I did a reboot and now the issue is resolved.

    Not sure but it seems during installation it is not pick up or refreshes the DNS server, but after reboot everything is fine.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, January 27 2019, 05:41 PM - #Permalink
    Resolved
    0 votes
    I did a fresh installation a couple of weeks ago as a VM without that issue. I started in Standalone mode then switched to gateway once I worked out how to add another NIC in libvirt.
    The reply is currently minimized Show
Your Reply