ClearOS
if you want to enable shell logins for users you need to
in the /etc/system/webconfig add the following line
allow_shell = 1
to replace the logo, change logo2.png file at:
/var/webconfig/htdocs/templates/standard-5.1/images
to disable the GUI console, remove --autologin=clearconsole from the first line in/etc/inittab
system will start with console on tty1. If you now want to launch console try tconsole
ClearOS
ClearOS multiwan provides simple GUI based method to add source based rules (if you want a LAN IP to always access through a particular WAN) but there is no facility to do a destination based rule (a particular site/IP to be always accessed via a particular WAB). This can be accomplished with editing related files via command line
following post in Clear Foundations Forums
example uses routing yahoo and google traffic via a specific WAN
1. first get the yahoo/google domains address (something like 209.191.64.0 – 209.191.127.255 for yahoo)
2. add to rc.local (etc/rc.d/rc.local ot rc.local.firewall) two line (one per rule):
route add -net 209.191.65.0 gw ip-wan1 netmask 255.255.128.0
route add -net 98.136.0.0 gw ip-wan2 netmask 255.255.0.0
3. reboot/ run rc singulair over the counter.local
ClearOS
versions 5.x can have an issue with time zones singulair for allergies. Your Webconfig might be showing correct time as you set it but mrtg graphs will be showing something else, usually 12 hrs late. You have to set the time zone manually on the command line to get this sorted.
the command is:
cd /etc
ln -sf /usr/share/zoneinfo/Europe/London localtime
choose the set region and city in the above command to suit your location.
ClearOS
if the firewall fail to start in ClearOS 5.x it is possibly due to the Bandwidth / QoS.
simpley change
BANDWIDTH_QOS=”on”
to
BANDWIDTH_QOS=”off”
and restart.
This is a bug and should be fixed in new releases of ClearOS
ClearOS
tips by Adam from http://www.ifrit-fire.com/articles/9-tutor/148-clearos-51-patch-1-how-to
if you want to start the iptraf simply type ‘iptraf’ (without quotes) on command line.
General Unix
edited the text from ClearOS documentation
Static routes on a ClearOS system are associated with a particular network interface. The route is then enabled/disabled when the particular network interface is enabled/disabled. Here is a simple scenario:
*
A ClearOS LAN interface – eth1 – is configured with a 192.168.1.x network.
*
192.168.1.x is actually in a large VLAN environment with its gateway set to 192.168.1.1
In order for the ClearOS gateway to be aware of other VLANs e.g. 192.168.2.x, a static route must be configured. In this example, /etc/sysconfig/network-scripts/route-ethx is created with the following, where x is the eth number of your NIC.
192.168.2.0/24 via 192.168.1.1
After adding this static route, the route can be activated by re-enabling the ClearOS LAN interface:
/sbin/ifup eth1 If you are logged on to ClearOS console remotely you can issue the following command:ifdown ethx && ifup ethx