Hi, guys! We need to setup our both network device on centos-4.5 as follow: eth0: IP: 192.168.1.0/24 GW 192.168.1.1 eth1: IP: 192.168.10.0/24 GW 192.168.10.1 We don't know how to create our setup files for both network (eth0, eth1 and their routes)? Help us, please. Thx Adriano
On Tue, 2007-09-25 at 15:37 -0300, Hapia IN wrote:> Hi, guys! > > We need to setup our both network device on centos-4.5 as follow: > > eth0: IP: 192.168.1.0/24 GW 192.168.1.1 > > eth1: IP: 192.168.10.0/24 GW 192.168.10.1 > > We don't know how to create our setup files for both network (eth0, > eth1 and their routes)?---- only 1 'default' gateway put gateway address in /etc/sysconfig/network and make sure that there are no gateway addresses in any /etc/sysconfig/network-scripts/ifcfg-ethX # cat /etc/sysconfig/network NETWORKING=yes NETWORKING_IPV6=yes HOSTNAME=your_hostname.your_domain.your_tld GATEWAY=192.168.1.254 GATEWAYDEV=eth0 #this is probably a good idea too if you need more advanced routing, we need more details to be of help -- Craig White <craig at tobyhouse.com>
First, some light reading: http://lartc.org/howto/ Secondly, take a look at how RedHat/CentOS uses network startup scripts: http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/en-US/Reference_Guide/pt-network-services-reference.html Thirdly, READ THIS ENTIRE DOCUMENT. Seriously. Not kidding. /usr/share/doc/initscripts-7.93.29.EL/sysconfig.txt ... paying close attention to this section: /etc/sysconfig/network-scripts/route-<interface-name> You cannot configure a RedHat/CentOS box with more than one *default* route in it's basic networking configuration. You can, however, create two custom routing tables, create different default routes on THOSE tables, then use "ip rule" and IPTABLES mangling to tell packets where to go. See the above documents for reference. Regards, Ken> Hi, guys! > > We need to setup our both network device on centos-4.5 as follow: > > eth0: IP: 192.168.1.0/24 GW 192.168.1.1 > > eth1: IP: 192.168.10.0/24 GW 192.168.10.1 > > We don't know how to create our setup files for both network (eth0, > eth1 and their routes)? >
Salam!!! Dear the information you are giving is not enough..... describe what do u want....>From my understanding u have two LAN Cards with two different Subnets...Now what do u want plz explain???? Regards, Umair Shakil ETD On 9/25/07, Hapia IN <harpiain at gmail.com> wrote:> > Hi, guys! > > We need to setup our both network device on centos-4.5 as follow: > > eth0: IP: 192.168.1.0/24 GW 192.168.1.1 > > eth1: IP: 192.168.10.0/24 GW 192.168.10.1 > > We don't know how to create our setup files for both network (eth0, > eth1 and their routes)? > > Help us, please. > > Thx > > Adriano > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070926/2f5e3418/attachment-0001.html>
Hi all, I'm searching a CentOS based solution to have a control over the number of connections to various services depending on overall used bandwidth. To give you a more accurate representation of what i mean, let's say we have some live WEB video feeds (M$ WME, embedded in WEB Pages hosted on an Apache server), a Darwin streaming on demand server (Links on WEB pages, Apache), FTP server and regular WEB traffic. I'm already doing traffic shaping so the real time traffic has higher QoS (we use pfSense firewall). The problem, as you know, is that traffic shaping is not enough to ensure real time traffic will get through when bandwidth gets maxed out. The problem arise when the number of connections to streaming servers gets higher than the capacity of the link. I need to limit the number of connections to a safe maximum. The link is a symmetric 10 Mbps and we are not in a position to raise that for now. I'd see something like a "traffic director" that sense the used bandwidth and controls the amount of connections to servers. Is there something that looks like that in CentOS? And how to inform the clients to connect later if their connection is temporarily refused (a timeout is not very elegant!)? I heard that their are some commercial products that does about that but i'm searching for an open source solution if it exists. Thanks! Guy Boisvert IngTegration inc.