0 votes
So, I have a pretty decent setup with a custom system for a home office/home

I have ran Ethernet through the walls of my mum's house fishing the lines up using fishtape and set up a system in her basement by the Coaxial in and the Modem replacing the wall jack with a 6 slot jack to add the additional lines while keeping the Coaxial jack in the same plate....
the system itself is an older AM2 Athlon x64 X2 2.6Ghz w/ 8GB DDR2

I am currently running it with, Onboard Gbe, 2 PCI-E Gbe server cards, a PCI Gbe Intel server card and a PCI WiFi N card,

Piror to installing the Intel NIC everything was nice and dandy I had 3 different subnets to segregate the Office, Home network and the Guest WiFi and Personal Wifi from each networks.

after adding the additional NIC to segregate the Office from the Home network is where things went funky

Original Layout

WAN (Marvel PCI-e) > ClearOS
LAN1 (Marvel PCI-e) > Home+Office Subnet
LAN2 (Marvel On-Board) > Guest WiFi Subnet ran to a bridged WiFi AC router
WLAN (PCI WiFi) > Personal WiFi Subnet

Everything worked perfect

New Layout

WAN (Marvel PCI-e) > ClearOS
LAN1 (Marvel PCI-e) > Home Subnet
LAN2 (Intel (Realtek) PCI) > Office Subnet
LAN3 (Marvel On-Board) > Guest WiFi Subnet ran to a bridged WiFi AC router
WLAN (PCI WiFi) > Personal WiFi Subnet

So what is happening is upon adding the Intel NIC and assigning it a subnet to work with the Marvel (Home) stopped receiving WAN traffic and the DHCP server has become shoddy at best for assigning IP's

I have no idea what caused this from what I can tell all the settings are correct when I shell in using SSH or even with peripherals hooked up to the hardware to check.

maybe it's something stupid easy and I'm just missing it but LAN1's only change was the removal of the Office connections then applying a new IP subnet and DHCP

from the looks everything's perfect




Do not know what the issue was but I deleted all the IP and DHCP settings turned off Authoritative mode for DHCP switched all the Zones to different NIC's reassigned IP Addresses and re-setup DHCP and it's working now.

Would be nice to know what caused it but I might never find out but just glad to have my networks back up and online ready for workloads.
Wednesday, May 30 2018, 02:56 PM
Share this post:
Responses (1)
  • Accepted Answer

    Wednesday, May 30 2018, 04:28 PM - #Permalink
    0 votes
    It may be because the IP Settings and DHCP settings are not linked so if you change the NIC subnet in IP Settings, the DHCP server does not follow the changes and you end up with the interface on one IP and the DHCP server on a different subnet.. If you look at the DHCP server at that point it will say your settings are invalid on that interface.

    An alternative explanation could be that you ended up with two interfaces on the same subnet (or one subnet was within the other). If you have two interfaces on the same subnet, ClearOS does not know which interface to send any packets to, so outbound traffic will start but may not return. For interfaces to share the same subnet, you have to configure them in Bridge Mode. This is a manual configuration and there is a HowTo which covers it.

    Can I ask a quick question about the Realtek? Do you know if it is an RTL8111/8068/8411 or RTL8169 card or something different? If it is the foemer (generally PCIe) it could do with a driver which is different to default. "lspci -knn | grep Eth -A 3" will identify the cards and their drivers.
    The reply is currently minimized Show
Your Reply