Please can you remove the DHCP Server configuration for enp0s25 (webconfig > network > infrastructure > DHCP server). That is for when ClearOS is acting as a DHCP server, so handing out IP addresses, rather than as a DHCP client where it is trying to obtain its IP address from another DHCP server.

To remove the firewall in standalone mode, use the "Standalone - No Firewall" mode rather than "Standalone". It leaves a bit of the firewall in place but it is totally open. It would also be a good idea to set up your "Domain and Internet Hostname". I thought this was part of the first-run wizard so I am not sure how you don't have it set.

As of yesterday, USB NICs are removed and deleted, only the onboard Ethernet adapter is connected. Wifi is disabled in BIOS. It does work fine without any configuration with other Linux distros.

Switching to Standalone produces the same results. I have not found a way to enable/disable the firewall through a shell.

Pardon minor typos, can't copy and paste between computers.

ifconfig shows a standard loopback, and an enp0s25 interface:

flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::221:86ff:fea3:3826
no IPv4. IPV6 may be enabled, but I don't use it.

It's been running for 2 days now and has some RX and TX packets, but no errors, drops, overruns, frames, collisions, or carriers.

cat network.conf shows:

MODE="gateway"
EXTIF=enp0s25
LANIF=
DMZIF=
HOTIF=

DEFAULT_DOMAIN=
INTERNET_HOSTNAME=

EXTRALANS=

ENP0S25_MAX_DOWNSTREAM=0
ENP0S25_MAX_UPSTREAM=0
ENP0S29F7U1C2_MAX_DOWNSTREAM=0
ENP0S29F7U1C2_MAX_UPSTREAM=0

---

cat dhcp.conf:

dhcp-option=enp0s25,1,255.255.255.0
dhcp-option=enp0s25,1,255.255.255.0
dhcp-option=enp0s25,25,28,192.168.1.255
dhcp-option=enp0s25,25,28,192.168.1.255
dhcp-option=enp0s25,3,192.168.1.100
dhcp-option=enp0s25,3,192.168.1.100
dhcp-option=enp0s25,6,192.168.1.100
dhcp-option=enp0s25,6,192.168.1.100
dhcp-range=enp0s25,192.168.1.100,192.168.1.254,12h
dhcp-range=enp0s25,192.168.1.100,192.168.1.254,12h
read-ethers

---

Other than for the loopback, one network script:

cat ifcfg-enp0s25

DEVICE=enp0s25
TYPE="Ethernet"
ONBOOT="yes"
USERCTL="no"
BOOTPROTO="dhcp"
PEERDNS="yes"

This is puzzling me. Can you give the output to:

ifconfig

and the contents of /etc/clearos/network.conf, /etc/dnsmasq.d/dhcp.conf and any /etc/sysconfig/network-scripts/ifcfg-* fiel except the ifcfg-lo file.

It may be easiest to try to get this working in Standalone mode with no firewall and without the USB NICs. They can be added later and the mode changed then.

Thank you for the reply Nick.

Network adapters do show up, and I am able to add or remove them. The onboard NIC is an Intel 82567LM Gigabit device, and the USB-Ethernet adapter is a Dell model FM76N / DBJBCBC064.
ClearOS sees the link up/down for the USB adapter, but is unable to determine the speed. ClearOS seems to properly recognize the vendor and device, and is able to determine that it is a 100 Mb/s link (router's max speed).

For the ClearOS LAN defaults, I would think I should be able to change the default LAN to 192.168.2.0/24, or remove the NIC completely to prevent it from interfering with the External setting. Either way, still can't communicate with anything on the external network.

Anyways, the internal NIC is set to Gateway Mode, using Google's (8.8.8.8) and my upstairs router's DNS (192.168.1.1), with a DHCP Connection type. When pulling up a shell no IPv4 address is given.

I'll implement a different IP scheme later once everything is working.

Do all your NIC's show in the IP Settings screen? I hope so or we'll have to hunt down the drivers.

By default, the first ClearOS LAN is on the 192.168.1.0/24 subnet which is going to be bad news as that is your existing LAN subnet and you'll end up with the WAN and LAN on the same subnet which will not work. The easiest thing to do is change the ClearOS LAN subnet.

In gateway mode, the ClearOS WAN should then be set to External/DHCP and the LANs to LAN/Static with DHCP enabled.

In standalone mode you only use the External/DHCP settings. The other NIC's, even if configured as LAN will not route.

Longer term the 192.168.0.0/24 and 192.168.1.0/24 subnets are not good ones to use as they are too popular and can really mess up VPN's. They can also have hard-to-diagnose issues when adding new kit to the network.