Hi Sir Nick,

I attached a diagram of the setup I'm trying to configure.

1. ClearOS Box
Gateway Mode
2 Interface = LAN & WAN
2. Modem / router
DHCP Enabled = 192.168.254.0/24

After successful installation
1. ClearOS Box
interface 1 get an ip from modem
interface 2 is down
2. Add static ip to interface 2 for LAN through console
3. ClearOS Box can ping google.com (internet is good)
4. ClearOS Box can't ping workstation = not permitted
5. Added the following command
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
Connection is successful and I can access webconfig from workstation but during initial config, iptables reject connection again.

For now I'll try installing the 7.5 and follow your suggestion.
Thanks for helping me out.

Regards,
Jess

I've had a look at the firewall when you get to your Network Console and it is pretty open (it is in the equivalent of Standalone - No Firewall mode) so should not be interfering. If you want, you can add the previously mentioned firewall line to /etc/clearos/firewall.d/local in the IPv4 section. You must use "$IPTABLES" or "iptables -w". If you get up an running, it would be a good idea to add the rule to the Custom firewall and then remove it from the "local" file (in that order as changing the local file restarts the firewall so you'd be left without any rule in place).

[edit]
Built-in editors are vi and nano.
[/edit]

Site can't be reached.
Also I can't even ping the server from the workstation and vice versa but both can ping the modem's ip

What happens when you try and connect? I won't be able to reply any more tonight as I'm just shutting down.

Hi Nick,
I did reinstall the OS again and follow your instructions. I connected one of the workstation to the modem to get same network of the clearos
ClearOS current IP = 192.168.254.107
Workstation = 192.168.254.109

I tried navigating to https://192.168.254.107:81 but I can't connect.

I have a feeling you may have too much knowledge! If you connect to the ClearOS LAN, the firewall should not get in the way, and there is no obvious way of disabling the firewall either (apart from Standalone Mode - No Firewall). ClearOS will do a lot to restore the firewall if it can. If you are connecting from the WAN then the webconfig is open by default and possibly (but perhaps not) SSH.

If you are connecting fro your WAN, for the moment just use the webconfig and complete the first-run wizard. You can then get to the firewall and open incoming ssh in the firewall, or, as I do when setting a box up on my LAN via its WAN, install the custom firewall and add a firewall rule:

$IPTABLES -I INPUT -s 192.168.254.0/24 -j ACCEPT

That will completely open the firewall to your WAN's subnet, and if you accidentally leave it in place when connecting directly to the internet, it is safe.

Just please make sure you set your LAN and WAN on different subnets.

Hi Nick,
I'm able to successfully add the static IP for Lan but now my issue is iptable rules is blocking access to the server so I can't access the webconfig from my workstation.
I did the following command
iptables -F
iptables -P INPUT ACCEPT
ptables -P OUTPUT ACCEPT
ptables -P FORWARD ACCEPT

after that I can successfully access the webconfig but after restarting the server, it iptables rule reverted to original. How can I save the changes permanently?

We are having a problem with the console for the moment and it is a tough one to find.

Can you plug your workstation (PC/laptop) into your modem/router at the same time then navigate to https://192.168.254.108:81 then complete the first run wizard from there. Note that you should give your LAN interface a static IP on a different subnet to your WAN (and enable the DHCP server) and it is best to avoid the 192.168.0.0/24 and 192.168.1.0/24 interfaces.

Once you have done that, you can plug your workstation into the ClearOS LAN and disable the Webconfig in the firewall - the incoming firewall only operates on the WAN, so you'll still have LAN access.

As an alternative, you can try plugging your workstation into your LAN NIC. Check its IP address. If it gets a proper one (so not 169.x.y.z) and is a windows device, do an "ipconfig" and note your Default Gateway. Then in a browser, navigate to https://default_gateway:81.

Note in both cases you will be using the non-standard port 81 with https and not http.

Also, until you have created your own certificate, you may have problems with the Firefox browser.