How do I configure 2 class c's on the same CENTOS 5 server?

Hello,
I am trying to configure 2 class c's on the same server. I have setup the base ip, and the ifcfg-eth0-range0 file for the first class c, and it works fine. However, when I add a second file (ifcfg-eth0-range1) with the second class c, I get this issue:

error in ifcfg-eth0-range1: already seen device eth0:250 in ifcfg-eth0-range0

I'd be interested in seeing your /etc/sysconfig/network-scripts/ifcfg-eth*
I would have thought you'd need your subnet mas in there, so the box "knows" that they are different networks. Surely you only

I'd be interested in seeing your /etc/sysconfig/network-scripts/ifcfg-eth*
I would have thought you'd need your subnet mas in there, so the box "knows" that they are different networks. Surely you only need to have something like:
# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
HWADDR=xx:xx:xx:xx:xx:xx
VLAN=yes
ONBOOT=yes
BOOTPROTO=static
IPADDR=212.117.218.3
NETMASK=255.255.255.0
and then the same thing for eth1, only with it's own subnet mask.
(I always thought CLONENUM was CLONENUM_START=)

By the way what point is there in assigning so many ips?
This in theory creates 502 ethernet alias interfaces......

There are possibly more scalable, less cluttered strategies like using IPTABLES
INPUT/PREROUTING DNAT rule locally or
a rule on an upstream router to NAT the entire class C to one ip,
so you don't have to list so many local interfaces, if you are doing something
simple...

Mysidia,
The reason for so many ips on one box is that I am working on a setting up standalone pc as a linux router, the idea being, that the public ips, mask to private ones, allowing us to filter ports on ips used by our customers. We will be using IPTABLES for these mappings, and chokes, but we had to get the ip ranges working first.

oh we arent connecting them, we are simply performing a proxy like pass through, a request to port 80 for instance comes in from the internet, the port is allowed, so the packet is routed to a predetermined local area address (ie 212.116.209.2 -> 192.168.0.1 on port 80). But lets say a request goes out from 192.168.9.1 on port 25, because we choke port 25, the request will be refused.

Featured Post

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Setting up Secure Ubuntu server on VMware
1. Insert the Ubuntu Server distribution CD or attach the ISO of the CD which is in the “Datastore”. Note that it is important to install the x64 edition on servers, not the X86 editions.
2. Power on th…

It’s 2016. Password authentication should be dead — or at least close to dying. But, unfortunately, it has not traversed Quagga stage yet. Using password authentication is like laundering hotel guest linens with a washboard — it’s Passé.

Learn several ways to interact with files and get file information from the bash shell.
ls lists the contents of a directory: Using the -a flag displays hidden files: Using the -l flag formats the output in a long list: The file command gives us mor…