Forums

×

Warning

JUser: :_load: Unable to load user with ID: 182061
Resolved
0 votes
This happened with two separate boxes at two separate locations that I manage.

as a result of a brief power flicker the gateway would shut down, upon power being restored the BIOS is set to restore last state thus turns the boxes back on.

once booted and the modems have finished their DOCSIS 3 boot (so slow) the gateway snags an IP address usually the one it had prior to power-loss as the Cable ISP here binds IP's to your MAC address for approx a week, the Modems are in Bridge mode so that the ClearOS Gateway has full external IP access. but the entire multi-lan network has lost internet connection.

the two boxes are of completely different AMD builds one being AM2 socket and the other being AM3 socket.

both however are running ClearOS 7.5, now prior to 7.5 I have not seen an issue like this ever arise from a small power outage. (yes I know a UPS would be ideal but they are not always affordable in a home office situation esp not for new people starting up.)

I'm not entirely sure why this is happening, I can still ssh in to the box and use the web interface, however unless I remove the custom DNS (IE: Cloudflare DNS) and revert back to the ISP's crappy DNS I can not ping from SSH as well the WebUI says no connection, yet it does have an IP address assigned from the ISP on the External Connection.

once I remove the Custom DNS (in IP Settings) and let the ISP manage DNS *shivers* than I can ping but still am not able to receive internet thru the lan(s)

I fixed it on one box by (thinking it was the hardware and upgrading the AM2 socket to an FM2 Socket and doing a reinstall)

P.S.
the AM2 box whenever I went to edit an interface, under the Edit>Settings > Interface it just showed ethernet and not the enp3s0 (etc) for all interfaces as well as showed and demanded a Wifi SSID and Passphrase when setting an external connection (makes no sense) they did have WiFi app installed and in use for their WiFi network but it was not set as external.
On the AM3 box this was not the issue, the interfaces showed up correctly.

Any fixes would be great, I do not want to reinstall at location 2, I have them on a bypass using the modem's builtin home-gateway but it's not feasible for extended periods.
as well this would be good info if said issue happens again at location 1.


Thanks!
Jayli
Wednesday, July 25 2018, 06:34 AM
Share this post:
Responses (3)
  • Accepted Answer

    Wednesday, July 25 2018, 07:43 AM - #Permalink
    Resolved
    0 votes
    Jayji - over the years with Clarkconnect/ClearOS have witness strange changes to the ifcfg-xxx files from being totally wiped out, changed to .bak files, interfaces swapped between internal/external on a reboot, valid options being deleted, wifi destroyed, a comment in a ifcfg file causing an Oops, webconfig not tolerating ifcfg-xxx backup files ending with "~" created by a decent editor. Webconfig clearly needs to be more robust and also recognise ALL valid options in these files - not just the tiny selection ClearOS allows. The Interface just showing up as ethernet was also reported recently (within the last 10 days?) on these forums. As a consequence of this - not a solution, but saves frustration - have been doing one or both of these things here for many years...
    1. Once setup and working, copy the ifcfg-xxx files elsewhere for safety and quick restore, if required...
    2. Using a sledge-hammer :) set the immutable bit on those files using chattr.

    Cannot help you with DNS. Ditched dnsmasq for bind and ISC dhcpd - this allow multiple DNS servers (master and any numbers of slaves) and dhcpd gives me two dhcp servers that synchronize with each other. Never see the DNS/dhcp problems that are reported on these forums...

    If it occurs again - check the logs - messages, syswatch, etc. Also try these in this order systemctl restart firewall.service, no go then syswatch.service, no go then try network.service (another sledge hammer

    One last thing - make sure you are using the latest kernel for 7.5 (currently kernel.x86_64 0:3.10.0-862.9.1.v7) - had multi-wan problems with the initial kernel installed by the 7.5 upgrade...

    Others with more conventional ClearOS systems may be able to provide better advice... mine are heavily modified...
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, July 25 2018, 05:36 PM - #Permalink
    Resolved
    1 votes
    P.S.
    the AM2 box whenever I went to edit an interface, under the Edit>Settings > Interface it just showed ethernet and not the enp3s0 (etc) for all interfaces as well as showed and demanded a Wifi SSID and Passphrase when setting an external connection (makes no sense) they did have WiFi app installed and in use for their WiFi network but it was not set as external.
    On the AM3 box this was not the issue, the interfaces showed up correctly.


    This is a temporary issue that came out after the latest updates, I don't think it is related to your other problem. Here you can find a temporary fix:

    https://www.clearos.com/clearfoundation/social/community/clearos-7-5-general-release-community,-home,-and-business#reply-226391
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, July 26 2018, 09:11 AM - #Permalink
    Resolved
    0 votes
    An app-network update was pushed through on Monday and I can't properly test as I have no spare slots, but adding a USB WiFi NIC worked fine today although it did insist on having WiFi parameters entered when they were already entered against another NIC.

    In a VM I created a new wired interface and this also worked correctly both as an internal interface and an external interface, creating the name correctly and not demanding WiFi parameters.

    It looks like the problem of the interface mis-labling may have been fixed as has the problem of demanding WiFi credentials with a non-wireless NIC. There are other problems, e.g. with two wireless NICs, but ClearOS has never been able to cope with that and Marc Laporte has WiFi enhancements on his list of projects for his interns.

    Can you post back if you still have DNS issues with a power glitch?

    Also can you check if you have any RTL8111/8168/8411 NIC's in your machines with:
    lspci -k | grep Eth -A 3
    If you do, can you update the drivers with a:
    yum install r816*
    then reboot? The kernel r8169 driver works a bit with these cards but not very well. The r8168 driver is way better.
    The reply is currently minimized Show
Your Reply