new member - test post

new member - test post

[Jake Ravenwood]

new member - test post. pls ignore.


      

wrong default route

[Jake Ravenwood]

I have a server out there that i remotely manage.  i had a downtime the other day when we
restarted network services. then we found a wrong default route is laoded on the server
upon restart. i have the configs below. The defaultroute should be 
GATEWAY=192.168.65.142  but it loaded GATEWAY=10.2.1.14 upon restart.
Could it be the sequence the interfaces are enabled from eth0 then eth1 then eth5, the
last interface activated its own gateway as the default?

Should i delete the gateway on eth0 and eth5 such that it would make sure only the
defaultgateway on eth1 is loaded upon restart?

i just can't restart network services and see what happens, the server is in production
and it takes a lot of authorization before i can restart it. 

thanks,
june


/etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
ONBOOT=no
BOOTPROTO=static
IPADDR=10.11.13.150
NETMASK=255.255.255.192
GATEWAY=10.11.13.129
HOSTNAME=web2003
HWADDR=00:19:BB:AB:CD:EF
ETHTOOL_OPTS="speed
100 duplex full autoneg off"


/etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE=eth1
HWADDR=00:19:BB:AA:DD:CC
ONBOOT=yes
TYPE=Ethernet
IPADDR=192.168.65.131
NETMASK=255.255.255.240
GATEWAY=192.168.65.142
HOSTNAME=web2003.domain.net
ETHTOOL_OPTS="speed
100 duplex full autoneg off"


/etc/sysconfig/network-scripts/ifcfg-eth5
DEVICE=eth5
HWADDR=00:18:FE:BB:CC:DD
ONBOOT=yes
TYPE=Ethernet
BOOTPROTO=static
IPADDR=10.2.1.1
NETMASK=255.255.255.240
GATEWAY=10.2.1.14
HOSTNAME=web2003.domain.net
ETHTOOL_OPTS="speed
100 duplex full autoneg off"



      

Fwd: wrong default route

[Herta Van den Eynde]

Apologies for using "Reply" instead of "Reply to all".  I'm used to
mailinglists putting the mailinglist's address in the reply-to field.
Any reason why this mailing list does not do that?

Anyway, below is my first reply.

Kind regards,

Herta


---------- Forwarded message ----------
From: Herta Van den Eynde <herta.vandeneynde@gmail.com>
Date: 2008/7/8
Subject: Re: wrong default route
To: jakeravenwood@yahoo.com


2008/7/8 Jake Ravenwood <jakeravenwood@yahoo.com>:
> I have a server out there that i remotely manage.  i had a downtime the other day when we
> restarted network services. then we found a wrong default route is laoded on the server
> upon restart. i have the configs below. The defaultroute should be
> GATEWAY=192.168.65.142  but it loaded GATEWAY=10.2.1.14 upon restart.
> Could it be the sequence the interfaces are enabled from eth0 then eth1 then eth5, the
> last interface activated its own gateway as the default?
>
> Should i delete the gateway on eth0 and eth5 such that it would make sure only the
> defaultgateway on eth1 is loaded upon restart?
>
> i just can't restart network services and see what happens, the server is in production
> and it takes a lot of authorization before i can restart it.
>
> thanks,
> june
>
>
> /etc/sysconfig/network-scripts/ifcfg-eth0
> DEVICE=eth0
> ONBOOT=no
> BOOTPROTO=static
> IPADDR=10.11.13.150
> NETMASK=255.255.255.192
> GATEWAY=10.11.13.129
> HOSTNAME=web2003
> HWADDR=00:19:BB:AB:CD:EF
> ETHTOOL_OPTS="speed
> 100 duplex full autoneg off"
>
>
> /etc/sysconfig/network-scripts/ifcfg-eth1
> DEVICE=eth1
> HWADDR=00:19:BB:AA:DD:CC
> ONBOOT=yes
> TYPE=Ethernet
> IPADDR=192.168.65.131
> NETMASK=255.255.255.240
> GATEWAY=192.168.65.142
> HOSTNAME=web2003.domain.net
> ETHTOOL_OPTS="speed
> 100 duplex full autoneg off"
>
>
> /etc/sysconfig/network-scripts/ifcfg-eth5
> DEVICE=eth5
> HWADDR=00:18:FE:BB:CC:DD
> ONBOOT=yes
> TYPE=Ethernet
> BOOTPROTO=static
> IPADDR=10.2.1.1
> NETMASK=255.255.255.240
> GATEWAY=10.2.1.14
> HOSTNAME=web2003.domain.net
> ETHTOOL_OPTS="speed
> 100 duplex full autoneg off"
>

Add the default gateway to /etc/sysconfig/network.  Use static routes
for the others.

Kind regards,

Herta

--
"Life on Earth may be expensive,
 but it comes with a free ride around the Sun."



-- 
"Life on Earth may be expensive,
 but it comes with a free ride around the Sun."

Re: Fwd: wrong default route

[Glynn Clements]

Herta Van den Eynde wrote:

> Apologies for using "Reply" instead of "Reply to all".  I'm used to
> mailinglists putting the mailinglist's address in the reply-to field.
> Any reason why this mailing list does not do that?

Because the Reply-To header "belongs" to the author.

Occasionally, it may be desirable to post private replies, and
"stealing" the Reply-To header prevents that (mail clients won't let
you reply to the From address if a Reply-To header exists).

Not only does a forced Reply-To header prevent the message from being
sent directly to the user, but will cause it to be sent to a public
mailing list instead. If the reply was intending to be private, the
message may well contain information which shouldn't be made public.

The author can always choose to add their own Reply-To header if they
never want to receive off-list replies.

Having the mailing list set its own Reply-To header is a workaround
for "non-technical" lists, where many of the subscribers may not
understand the difference between "reply" and "follow-up".

Presumably the vger admins (naïvely) assumed that a list targeted to
Linux sysadmins doesn't need such workarounds.

-- 
Glynn Clements <glynn@gclements.plus.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: wrong default route

[Jake Ravenwood]

thanks for the answers. can you confirm that the should be default route eth1 was overwritten by eth5 gateway? 



      

Fwd: wrong default route

[Herta Van den Eynde]

And this was my second.

Kind regards,

Herta


---------- Forwarded message ----------
From: Herta Van den Eynde <herta.vandeneynde@gmail.com>
Date: 2008/7/8
Subject: Re: wrong default route
To: jakeravenwood@yahoo.com


2008/7/8 Jake Ravenwood <jakeravenwood@yahoo.com>:
> thanks for the answers. can you confirm that the should be default route eth1 was overwritten by eth5 gateway?
>

Yes, it did.  You can check the startup script /etc/init.d/network
yourself.  It does a 'cd /etc/sysconfig/network-scripts' followed by a
'ls ifcfg*', so it will process the ifcfg files in alphabetical order.
/var/log/messages should also show you the startup order.

Kind regards,

Herta

--
"Life on Earth may be expensive,
 but it comes with a free ride around the Sun."



-- 
"Life on Earth may be expensive,
 but it comes with a free ride around the Sun."