comp.os.linux.networking

sb5309@yahoo.com writes:

>My company's Linux server has the following interfaces:

>eth0, eth1, eth3, lo (I don't know why eth2 is missing).


>Their settings:

>eth1:
>DEVICE=eth1
>BROADCAST=218.111.104.107
>IPADDR=218.111.104.106
>NETMASK=255.255.255.255
>NETWORK=218.111.104.104
>ONBOOT=yes
>TYPE=Ethernet
>GATEWAY=218.111.104.105

>eth0:
>DEVICE=eth0
>ONBOOT=yes
>BOOTPROTO=static
>IPADDR=192.168.42.1
>NETMASK=255.255.255.0
>GATEWAY=218.111.104.106

>eth3:
>DEVICE=eth3
>ONBOOT=yes
>IPADDR=192.168.43.1
>NETMASK=255.255.255.0
>GATEWAY=218.111.104.106

>There are 2 network segments; one segment with IPs type 192.168.42.*,
>default gateway 192.168.42.1; the other of IP type 192.168.43.*,
>default gateway 192.168.43.1.

>I guess that eth0 and eth3 route thier internet traffic to eth1, which
>I believe (not sure) is connected to an external ADSL modem (Lucent
>CellPipe).

>When I unplug the network cable from the modem, the server shows "eth1
>NIC down".

>When I plug in a Belkin G Wireless Router, the server shows "eth1 NIC
>UP 100Mbps".

>To the Belkin router (with 4 ports and a WAN port) I then connect a
>wireless broadband modem via its WAN port (supposedly up to 1Mbps) for
>internet access (wireless internet access, not wireless LAN). The
>Belkin is configured with the user name and password.

>I cannot access the internet via LAN. I am told the Belkin has a fixed
>IP 192.168.1.1, which I fail to ping from the server. A laptop
>connected directly to the Belkin port shows the router to have IP
>192.168.1.1, and it has no problem accessing the internet.

>I am think of changing the gateway of eth1 to 192.168.1.1. But I
>suppose it is pointless if I can't ping the router.

>Could somebody help ? Thanks.

While you give lots of info, which is great, the key bit of info is
missing, what is the output of
route -n

That tells you where packets are sent to.
I have no idea why your are unplugging eth1 and plugging in a new router
and wireless boadband. Ie, you descibe things you do, but not why.