Forums

Resolved
0 votes
Years ago I set up ClearOS 5.2 as my home gateway. Recently the PC it was running on died, so I replaced it and installed the latest ClearOS 7.

I also have a FreeNAS box inside the network, which uses FreeBSD "jails" in which to run its Plugin services such as Plex, Transmission, etc. (I know ClearOS has these services as well, but it makes more sense to me to run them on the same box that the files associated with them are stored.) For the uninitiated, a jail is a kind of faux-VM inside the operating system, with its own IP address and filesystem. Nothing has changed on the FreeNAS box.

In my network, I have the following:
<ul>
ClearOS gateway - 192.168.1.1
FreeNAS - 192.168.1.10
Plex jail (within FreeNAS) - 192.168.1.11
Transmission jail (within FreeNAS) - 192.168.1.12
DHCP range - 192.168.1.100-254
</ul>

With the new ClearOS gateway, most everything works, except one aspect of networking that was not an issue before. I cannot establish communication between the gateway and any of the jails, or vice versa. I can PING the jails from any PC on my network (static or DHCP), and the jails can PING them back: but the ClearOS gateway is unreachable. The host FreeNAS box (192.168.1.10) has no issues, only the jails. This obviously means that I can no longer use Transmission, since it cannot route traffic to and from the internet without the ability to communicate with the gateway.

Any ideas as to what might be different between 5.2 and 7 in this respect? Thanks.
Saturday, May 19 2018, 01:27 AM
Share this post:
Responses (5)
  • Accepted Answer

    Sunday, May 20 2018, 05:40 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    How do you mean invisible to the gateway. Are you saying you cannot ping them from the gateway?

    Can I have some basic configs please:

    cat /etc/clearos/network.conf
    cat /etc/dnsmasq.d/dhcp.conf
    ifconfig | egrep "^(e|w|t)" -A 2
    traceroute 192.168.1.12


    Also the result from:
    arping -I your_ClearOS_LAN_interface 192.168.1.1
    The result should be no response. Clt+c to stop it.

    Please put the results between code tags (the piece of paper icon with a <> on it).


    Yes, that was what I explained before when I said "invisible". The jails cannot be pinged from the gateway, and vice versa. I could port forward all I wanted, and nothing would be getting through. Meanwhile other devices were able to ping the jails without issue.

    Unfortunately I got tired of this and I installed pfsense on the box this morning. I don't like the admin interface and I haven't figured it all out yet, but I can confirm that this issue doesn't exist. The jails and pfsense can see each other just fine, and Transmission on the FreeNAS box is running happily now, just as it was with 5.2. The issue obviously was with ClearOS 7, or at least it was with the way it got configured by default on my install.

    I'll come back to this thread if I decide to give ClearOS another shot.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, May 20 2018, 04:13 PM - #Permalink
    Resolved
    0 votes
    How do you mean invisible to the gateway. Are you saying you cannot ping them from the gateway?

    Can I have some basic configs please:

    cat /etc/clearos/network.conf
    cat /etc/dnsmasq.d/dhcp.conf
    ifconfig | egrep "^(e|w|t)" -A 2
    traceroute 192.168.1.12


    Also the result from:
    arping -I your_ClearOS_LAN_interface 192.168.1.1
    The result should be no response. Clt+c to stop it.

    Please put the results between code tags (the piece of paper icon with a <> on it).
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, May 19 2018, 08:26 AM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    At a guess you mounted some FreeNAS drives in ClearOS manually in /etc/fstab. Do you by any chance have a configuration backup from 5.2? You should be able to see the contents of your old /etc/fstab. I don't imagine it is something native to ClearOS which has changed because, most likely you needed usernames and passwords to access there jails.

    BTW, for Transmission you may need to set up a port forward or use the MiniUPnP app from the marketplace


    I don't have a config backup from my old 5.2 machine. But I don't recall making any manual changes to anything.

    (And also I don't think your hypothesis about access is correct. As I mentioned, other computers on the network have no issue with this. My Linux Mint PC wth a static address and my Windows laptop on DHCP are both able to receive responses to pings sent to the jails, and vice versa. Yet the jails are invisible to the gateway.)

    I have already configured port forwarding for Transmission to the jail's IP address 192.168.1.12, as I had before with 5.2. Naturally, until ClearOS can be made to see this address, it is not functioning.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, May 19 2018, 08:23 AM - #Permalink
    Resolved
    0 votes
    (sorry, duplicate reply)
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, May 19 2018, 07:18 AM - #Permalink
    Resolved
    0 votes
    At a guess you mounted some FreeNAS drives in ClearOS manually in /etc/fstab. Do you by any chance have a configuration backup from 5.2? You should be able to see the contents of your old /etc/fstab. I don't imagine it is something native to ClearOS which has changed because, most likely you needed usernames and passwords to access there jails.

    BTW, for Transmission you may need to set up a port forward or use the MiniUPnP app from the marketplace
    The reply is currently minimized Show
Your Reply