Category: Linux

Static Routes On RedHat

July 6, 2006

Here’s the docs from redhat on how to setup static routes:


/etc/sysconfig/network-scripts/route-<interface-namegt;

  Contains lines that specify additional routes that should be added when the
  associated interface is brought up.

  The files are processed by the ifup-routes script and uses the /sbin/ipcalc
  utility for all network masks and numbers. Routes are specified using the
  syntax:

    ADDRESSn=<network>
    NETMASKn=<network/prefix mask>
    GATEWAYn=<next-hop router/gateway IP address>

  The "n" can be any integer number, but is expected to be monotonically
  increasing and counting starts from 0. For example:

    ADDRESS0=192.168.2.0
    NETMASK0=255.255.255.0
    GATEWAY0=192.168.1.1

  adds a network route to the 192.168.2.0 network via the gateway at
  192.168.1.1. Since you must already have a route to the network of the
  gateway, there is no need to specify a device.

  Note: The ifup-routes script also supports an older syntax designed to be
  used directly as an argument to "/sbin/ip route add". This syntax is
  deprecated, but if no "ADDRESSn" lines are found the following will still
  work:

  192.168.2.0/24 dev ppp0

  adds a network route to the 192.168.2.0 network through ppp0.

/etc/sysconfig/network-scripts/route-<interface-namegt;

Contains lines that specify additional routes that should be added when the

associated interface is brought up.

The files are processed by the ifup-routes script and uses the /sbin/ipcalc

utility for all network masks and numbers. Routes are specified using the

syntax:

ADDRESSn=<network>

NETMASKn=<network/prefix mask>

GATEWAYn=<next-hop router/gateway IP address>

The "n" can be any integer number, but is expected to be monotonically

increasing and counting starts from 0. For example:

ADDRESS0=192.168.2.0

NETMASK0=255.255.255.0

GATEWAY0=192.168.1.1

adds a network route to the 192.168.2.0 network via the gateway at

192.168.1.1. Since you must already have a route to the network of the

gateway, there is no need to specify a device.

Note: The ifup-routes script also supports an older syntax designed to be

used directly as an argument to "/sbin/ip route add". This syntax is

deprecated, but if no "ADDRESSn" lines are found the following will still

work:

192.168.2.0/24 dev ppp0

adds a network route to the 192.168.2.0 network through ppp0.

Let’s say you want to add two static routes to eth1. The first routes 10.10.10.0/255.255.255.0 to 10.10.10.1 and the second routes traffic from 10.10.11.0/255.255.255.0 to 10.10.11.1. To accomplish this create a file at:


/etc/sysconfig/network-scripts/route-eth1

/etc/sysconfig/network-scripts/route-eth1

And place the following lines in the file:


    ADDRESS0=10.10.10.0
    NETMASK0=255.255.255.0
    GATEWAY0=10.10.10.1
    ADDRESS1=10.10.11.0
    NETMASK1=255.255.255.0
    GATEWAY1=10.10.11.1

ADDRESS0=10.10.10.0

NETMASK0=255.255.255.0

GATEWAY0=10.10.10.1

ADDRESS1=10.10.11.0

NETMASK1=255.255.255.0

GATEWAY1=10.10.11.1

Then restart networking with:


    /sbin/service network restart

/sbin/service network restart

Increase Max Process Memory Allocation

August 26, 2005

Use this command to increase the max memory that a single process can use:

/sbin/sysctl -w kernel.task_size=3221225472

1	/sbin/sysctl -w kernel.task_size=3221225472

Add to /etc/sysctl.conf to reload on each boot.

DVD Backup With BackupEdge

April 3, 2005

On a server with a Sony DVD R/W drive and BackupEdge software – this tech note was used to configure the drive: http://www.microlite.com/support/edgefax65.ts.html Here’s a link to site that is full of DVD info: http://fy.chalmers.se/~appro/linux/DVD+RW/

OpenNMS Install

March 4, 2005

OpenNMS is a great network monitoring tool. Here’s the OpenNMS site: http://www.opennms.org In this case I’m going to do an install on to a RedHat Fedora Core 1 server. Here’s the installation guide: https://sourceforge.net/docman/display_doc.php?docid=23937&group_id=4141 The first step is to install the various prerequisites: – Java 2 SDK 1.4.2 or later from http://java.sun.com We did a stock install of the 1.4.2_07 tar/gz package to /usr/local/. Don’t forget to export the JAVA_HOME environment variable:

export JAVA_HOME=/usr/local/j2sdk1.4.2_07/

1	export JAVA_HOME=/usr/local/j2sdk1.4.2_07/

– Tomcat 4 from http://jakarta.apache.org/tomcat/index.html We did a standard install of the 4.1.31 tar/gz package following the instructions here: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/RUNNING.txt The install was placed at /usr/local/jakarta-tomcat-4.0. We added the following lines to /etc/rc.local to start Tomcat on bootup and open the appropriate firewall ports:


   # tomcat startup
   export JAVA_HOME=/usr/local/j2sdk1.4.2_07
   export CATALINA_HOME=/usr/local/jakarta-tomcat-4.0
   $CATALINA_HOME/bin/startup.sh
   iptables -A INPUT -p tcp --dport 8080 -j ACCEPT

# tomcat startup

export JAVA_HOME=/usr/local/j2sdk1.4.2_07

export CATALINA_HOME=/usr/local/jakarta-tomcat-4.0

$CATALINA_HOME/bin/startup.sh

iptables -A INPUT -p tcp --dport 8080 -j ACCEPT

At this point Tomcat was accessible at http://{myipaddress}:8080 – RRDTool from http://people.ee.ethz.ch/~oetiker/webtools/rrdtool/ We used the 1.0.49 source tar/gz package and built it using the instructions in the enclosed README file. The package