Two Network cards

[sorocco]

ok.. i have done like this ..

 

my dsl modem/router--->>linksys access point---->>linux box and winx px

from linux i am from three NIC as eth0 connected to linksys , adn eth1 connected to switch for other neteork 10.0.0.0/24 and eth2 is for 172.120.0.0/24 connected to VOIP gizmo..

 

see my ifconfig

 

eth0 Link encap:Ethernet HWaddr 00:E0:4C:15:40:43

inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0

inet6 addr: fe80::2e0:4cff:fe15:4043/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:908320 errors:0 dropped:0 overruns:0 frame:0

TX packets:678639 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:1158851933 (1105.1 Mb) TX bytes:82552179 (78.7 Mb)

Interrupt:3 Base address:0xc400

 

eth1 Link encap:Ethernet HWaddr 00:E0:4C:10:06:7D

inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0

inet6 addr: fe80::2e0:4cff:fe10:67d/64 Scope:Link

UP BROADCAST MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:1001 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 B) TX bytes:238123 (232.5 Kb)

Interrupt:5 Base address:0xc800

 

eth2 Link encap:Ethernet HWaddr 00:E0:4D:77:78:11

inet addr:172.20.0.1 Bcast:172.20.0.255 Mask:255.255.255.0

inet6 addr: fe80::2e0:4dff:fe77:7811/64 Scope:Link

UP BROADCAST MULTICAST MTU:1500 Metric:1

RX packets:6128 errors:0 dropped:0 overruns:0 frame:0

TX packets:4665 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:1254537 (1.1 Mb) TX bytes:695035 (678.7 Kb)

Interrupt:11 Base address:0xe000

[scoonma]

Sorocco, your config does not look wrong but well, a bit strange. Is there any good reason why you chose three totally different IP home network ranges? I'd have configured as follows:

 

eth0 192.168.2.2

eth1 192.168.2.3

eth2 192.168.2.4

 

Generally, I'd put all network devices within your local domain into the 192.168.*.* range.

[Phil Edwards]

Just to ensure I understand your setup, eth0 is connected to your cable modem and eth1 to your internal LAN, right? If not, just transpose eth0 and eth1 in what I've got below...

 

Also, to clarify this 'gateway' concept that seems to be confusing a few people. Forget about whether individual NICs have their own gateways or not - for 99.9% of what you would want to do with a Linux box, this is irrelevant.

 

All you're interested in is the default gateway address. In a nutshell, this tells Linux which of the networks it is connected to has the most machines. In the majority of cases, the network with the most machines will be the Internet itself, so you should set the default gateway to be the IP address of your cable modem. Note that this will be the LAN-side address rather than the Internet facing IP that your service provider assigns to you when your modem connects to them. In most cases you can even forget about having to do that, since it is handled for you when all the DHCP stuff happens.

 

As I've already said in another post on here tonight, try to invest some time in learning to admin Linux from the command line rather than using the GUI tools, nice though they are.

 

So, assuming eth0 and eth1 are connected as described above, open a terminal session and get root privileges by typing 'su -' and entering your root password when prompted. Type 'cd /etc/sysconfig/network-scripts' - this is the place where the config details for your network cards are ultimately stored, regardless of which tool you use to maintain them. Using your favourite text editor, ensure you have this in a file called 'ifcfg-eth0':

 

DEVICE=eth0

BOOTPROTO=dhcp

ONBOOT=yes

TYPE=Ethernet

 

Save that file and then ensure that you have this in a file called 'ifcfg-eth1':

 

DEVICE=eth1

BOOTPROTO=static

IPADDR=192.168.5.10

NETMASK=255.255.255.0

NETWORK=192.168.5.0

ONBOOT=yes

TYPE=Ethernet

 

Save that file too. Now do 'cd /etc/sysconfig' and edit a file called 'network'. You should ensure that it just has this line in it:

 

NETWORKING=yes

 

Save that file and ensure that your cable modem is connected to your ISP. Last of all, do 'urpmi dhclient' to make sure you have the dhcp tools installed. I'd be surprised if you didn't, but best to make sure!

 

You should now find that if you type 'service network restart', you'll get your internet connection going out on eth0 and your LAN connection on eth1. Try pinging www.google.com - this will prove that you have a functional internet connection using your service providers DNS servers, which would have been configured by the dhcp stuff. Then try a ping of something on your internal LAN to ensure that works.

 

Post some more details here if that doesn't work. Good luck! :-)

Edited October 13, 2007 by Phil Edwards