default gateway is not showing up even though it is configured

Hi,

I just installed a linux box with two embeded intel 1000/CT nic cards,
I first enabled DHCP and everything looks fine. then I moved it into
lab and I have to change to static IP configuration. I assigned static
IP and default gateway on one of the nic and staic IP only on another
nic card. Then I can ping through hosts in these two subnets. but if I
want to cross these two subnets, it will fail. after I further
troubleshooting, I found the default gateway config is not taking
effect even though it is in the config file located at
/etc/sysconfiguration/networking/devices/ifcfg_eth0. Also, if I ust
route add default gateway x.x.x.x dev eth0, it will say it is already
in the config file. anyone knows what is going on here?

thanks in advance.

/zhenwu

On 2006-06-08, (E-Mail Removed) <(E-Mail Removed)> wrote:
> troubleshooting, I found the default gateway config is not taking
> effect even though it is in the config file located at
> /etc/sysconfiguration/networking/devices/ifcfg_eth0.

It sounds like you have some redhat or derivated distribution,
afaik the gateway is (or should be) in /etc/sysconfig/network

Davide

--
Are you scared of speed? If so, then try Windows 95.

(E-Mail Removed) writes:


>Hi,

>I just installed a linux box with two embeded intel 1000/CT nic cards,

No. You installed some specific version of Linux. Which was it.

>I first enabled DHCP and everything looks fine. then I moved it into
If you are going to assign static IPs why in the world do you enable dhcp?

>lab and I have to change to static IP configuration. I assigned static
>IP and default gateway on one of the nic and staic IP only on another

Yes, a computer can have only one default route.


>nic card. Then I can ping through hosts in these two subnets. but if I
>want to cross these two subnets, it will fail. after I further

No idea what you mean? If your computer is supposed to be the gateway, you
need to set it up as such. Tell us what you want to do in more detail.

>troubleshooting, I found the default gateway config is not taking
>effect even though it is in the config file located at
>/etc/sysconfiguration/networking/devices/ifcfg_eth0. Also, if I ust

What is the output of
route -n

>route add default gateway x.x.x.x dev eth0, it will say it is already
>in the config file. anyone knows what is going on here?

No idea what this is talking about. That error message is NOT an error
message from route. Please quote error messages EXACTLY, via cut and paste
prefereably.

Thanks for all your help. OK, let me describe this in more detail:

I installed Redhat 9.0, but my pc is new and the linux does not have
the driver for the embeded nics. Then I downloaded from intel website
and installed it followed by the instrcution. I first installed all
those in my cubic, that is why I have to use DHCP, and it works fine.
Then I moved it into lab since it will be my new server. In the lab, I
have to use static IP because of our lab gateway does not enable dhcp.
below is my configuraton:

eth0: 10.43.52.137, mask: 255.255.255.0, default gateway: 10.43.52.1
eth1: 192.168.255.2 mask 255.255.255.0

After I enable these two nics, I could reach any host belong to these
two subnets, like 10.43.52.1 and 192.168.255.1, but if I want to reach
other pc like 10.10.10.100, then it always fail. I notice another
problem, which is strange too, if disable any of this two cards, the
other one will also stop working. why it is that? Maybe it is related
this issue too. As you suggested, I did check route -n, the default
gateway is there.

hope it is clear enough for you to do further investigation.

thanks.

/zhenwu



Unruh wrote:
> (E-Mail Removed) writes:
>
>
> >Hi,
>
> >I just installed a linux box with two embeded intel 1000/CT nic cards,
>
> No. You installed some specific version of Linux. Which was it.
>
> >I first enabled DHCP and everything looks fine. then I moved it into
> If you are going to assign static IPs why in the world do you enable dhcp?
>
> >lab and I have to change to static IP configuration. I assigned static
> >IP and default gateway on one of the nic and staic IP only on another
>
> Yes, a computer can have only one default route.
>
>
> >nic card. Then I can ping through hosts in these two subnets. but if I
> >want to cross these two subnets, it will fail. after I further
>
> No idea what you mean? If your computer is supposed to be the gateway, you
> need to set it up as such. Tell us what you want to do in more detail.
>
> >troubleshooting, I found the default gateway config is not taking
> >effect even though it is in the config file located at
> >/etc/sysconfiguration/networking/devices/ifcfg_eth0. Also, if I ust
>
> What is the output of
> route -n
>
> >route add default gateway x.x.x.x dev eth0, it will say it is already
> >in the config file. anyone knows what is going on here?
>
> No idea what this is talking about. That error message is NOT an error
> message from route. Please quote error messages EXACTLY, via cut and paste
> prefereably.

(E-Mail Removed) writes:


>Thanks for all your help. OK, let me describe this in more detail:

>I installed Redhat 9.0, but my pc is new and the linux does not have
Old distro. NOt surprising. ^^^^^^ the kernel.

>the driver for the embeded nics. Then I downloaded from intel website
>and installed it followed by the instrcution. I first installed all
>those in my cubic, that is why I have to use DHCP, and it works fine.

What is your cubic? And I have no idea what the word "that" refers to.
There is nothing about a nic driver that demands the use of DHCP.


>Then I moved it into lab since it will be my new server. In the lab, I

Is lab the name of your computer? or a location in your research
establishment.

>have to use static IP because of our lab gateway does not enable dhcp.
>below is my configuraton:

>eth0: 10.43.52.137, mask: 255.255.255.0, default gateway: 10.43.52.1
>eth1: 192.168.255.2 mask 255.255.255.0

>After I enable these two nics, I could reach any host belong to these
>two subnets, like 10.43.52.1 and 192.168.255.1, but if I want to reach
>other pc like 10.10.10.100, then it always fail. I notice another

Well, your system says "I donot know what to do with this address. Therefor
I ship it off to 10.43.52.1 and let it handle it. " At that point it all
depends on 10.43.52.1. It may for example disable all pings and not let
them through. It may have a firewall which does not allow any connection.
Etc.


>problem, which is strange too, if disable any of this two cards, the
>other one will also stop working. why it is that? Maybe it is related

No idea what you mean by "disable" or by "not working"

>this issue too. As you suggested, I did check route -n, the default
>gateway is there.

I also suggested that you post it here. You admit you do not understand.
Thus your statements of interpretation cannot be trusted.


>hope it is clear enough for you to do further investigation.

Nope, sorry.




>Unruh wrote:
>> (E-Mail Removed) writes:
>>
>>
>> >Hi,
>>
>> >I just installed a linux box with two embeded intel 1000/CT nic cards,
>>
>> No. You installed some specific version of Linux. Which was it.
>>
>> >I first enabled DHCP and everything looks fine. then I moved it into
>> If you are going to assign static IPs why in the world do you enable dhcp?
>>
>> >lab and I have to change to static IP configuration. I assigned static
>> >IP and default gateway on one of the nic and staic IP only on another
>>
>> Yes, a computer can have only one default route.
>>
>>
>> >nic card. Then I can ping through hosts in these two subnets. but if I
>> >want to cross these two subnets, it will fail. after I further
>>
>> No idea what you mean? If your computer is supposed to be the gateway, you
>> need to set it up as such. Tell us what you want to do in more detail.
>>
>> >troubleshooting, I found the default gateway config is not taking
>> >effect even though it is in the config file located at
>> >/etc/sysconfiguration/networking/devices/ifcfg_eth0. Also, if I ust
>>
>> What is the output of
>> route -n
>>
>> >route add default gateway x.x.x.x dev eth0, it will say it is already
>> >in the config file. anyone knows what is going on here?
>>
>> No idea what this is talking about. That error message is NOT an error
>> message from route. Please quote error messages EXACTLY, via cut and paste
>> prefereably.

Sorry I used some terms.
My cubic is my office. my lab is where all of my equipment is.
I used etheral to capture all packets while I tried to send a ping
packet. I noticed that the dest mac is not correct. I correct something
on my internal switch. now it works fine.

thanks for you help.

/zhenwu


Unruh wrote:
> (E-Mail Removed) writes:
>
>
> >Thanks for all your help. OK, let me describe this in more detail:
>
> >I installed Redhat 9.0, but my pc is new and the linux does not have
> Old distro. NOt surprising. ^^^^^^ the kernel.
>
> >the driver for the embeded nics. Then I downloaded from intel website
> >and installed it followed by the instrcution. I first installed all
> >those in my cubic, that is why I have to use DHCP, and it works fine.
>
> What is your cubic? And I have no idea what the word "that" refers to.
> There is nothing about a nic driver that demands the use of DHCP.
>
>
> >Then I moved it into lab since it will be my new server. In the lab, I
>
> Is lab the name of your computer? or a location in your research
> establishment.
>
> >have to use static IP because of our lab gateway does not enable dhcp.
> >below is my configuraton:
>
> >eth0: 10.43.52.137, mask: 255.255.255.0, default gateway: 10.43.52.1
> >eth1: 192.168.255.2 mask 255.255.255.0
>
> >After I enable these two nics, I could reach any host belong to these
> >two subnets, like 10.43.52.1 and 192.168.255.1, but if I want to reach
> >other pc like 10.10.10.100, then it always fail. I notice another
>
> Well, your system says "I donot know what to do with this address. Therefor
> I ship it off to 10.43.52.1 and let it handle it. " At that point it all
> depends on 10.43.52.1. It may for example disable all pings and not let
> them through. It may have a firewall which does not allow any connection.
> Etc.
>
>
> >problem, which is strange too, if disable any of this two cards, the
> >other one will also stop working. why it is that? Maybe it is related
>
> No idea what you mean by "disable" or by "not working"
>
> >this issue too. As you suggested, I did check route -n, the default
> >gateway is there.
>
> I also suggested that you post it here. You admit you do not understand.
> Thus your statements of interpretation cannot be trusted.
>
>
> >hope it is clear enough for you to do further investigation.
>
> Nope, sorry.
>
>
>
>
> >Unruh wrote:
> >> (E-Mail Removed) writes:
> >>
> >>
> >> >Hi,
> >>
> >> >I just installed a linux box with two embeded intel 1000/CT nic cards,
> >>
> >> No. You installed some specific version of Linux. Which was it.
> >>
> >> >I first enabled DHCP and everything looks fine. then I moved it into
> >> If you are going to assign static IPs why in the world do you enable dhcp?
> >>
> >> >lab and I have to change to static IP configuration. I assigned static
> >> >IP and default gateway on one of the nic and staic IP only on another
> >>
> >> Yes, a computer can have only one default route.
> >>
> >>
> >> >nic card. Then I can ping through hosts in these two subnets. but if I
> >> >want to cross these two subnets, it will fail. after I further
> >>
> >> No idea what you mean? If your computer is supposed to be the gateway, you
> >> need to set it up as such. Tell us what you want to do in more detail.
> >>
> >> >troubleshooting, I found the default gateway config is not taking
> >> >effect even though it is in the config file located at
> >> >/etc/sysconfiguration/networking/devices/ifcfg_eth0. Also, if I ust
> >>
> >> What is the output of
> >> route -n
> >>
> >> >route add default gateway x.x.x.x dev eth0, it will say it is already
> >> >in the config file. anyone knows what is going on here?
> >>
> >> No idea what this is talking about. That error message is NOT an error
> >> message from route. Please quote error messages EXACTLY, via cut and paste
> >> prefereably.