routing prob

Hello,

this may be a newbie question, but since i'm new to linx, i'll give it a
try:
Where are the routing settings stored? Every time i restart the network
service with "service network restart"
some strange entries appear when typing "route":
It's a route to
169.254.0.0 * 0.0.0.0 U 0 0 0 eth1
I don't know where this comes from, since i've never entered it.

It also takes a few seconds until the last of the three entries there is
displayed (Dest=default), does anyone know why?
I'm using FC3 2.6.10

Tanks in advance,

Jens

On Thu, 24 Feb 2005 19:11:28 +0100, Jens Hofmeier <(E-Mail Removed)> wrote:
> Hello,
>
> this may be a newbie question, but since i'm new to linx, i'll give it a
> try:
> Where are the routing settings stored? Every time i restart the network
> service with "service network restart"
> some strange entries appear when typing "route":
> It's a route to
> 169.254.0.0 * 0.0.0.0 U 0 0 0 eth1
> I don't know where this comes from, since i've never entered it.

That might be the default IP range used by Windows boxes that fail to get
a DHCP IP.

> It also takes a few seconds until the last of the three entries there is
> displayed (Dest=default), does anyone know why?
> I'm using FC3 2.6.10

Most likely DNS timeout attempting to resolve IPs that do not resolve.
route -n is quicker and sometimes easier to interpret.

--
David Efflandt - All spam ignored http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/

In comp.os.linux.networking Jens Hofmeier <(E-Mail Removed)>:
> Hello,

> this may be a newbie question, but since i'm new to linx, i'll give it a
> try:
> Where are the routing settings stored? Every time i restart the network

/etc/sysconfig/network-scripts/ or so on redhat.

> service with "service network restart"
> some strange entries appear when typing "route":
> It's a route to
> 169.254.0.0 * 0.0.0.0 U 0 0 0 eth1
> I don't know where this comes from, since i've never entered it.

Your system did it for you, nothing to worry about, try
www.faqs.org and search for RFC 3330 for the complete story.

> It also takes a few seconds until the last of the three entries there is
> displayed (Dest=default), does anyone know why?
> I'm using FC3 2.6.10

route -n

Try 'man route' for more options.

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 17: fat electrons in the lines

"David Efflandt" <(E-Mail Removed)> schrieb im Newsbeitrag
news:(E-Mail Removed)...
> On Thu, 24 Feb 2005 19:11:28 +0100, Jens Hofmeier <(E-Mail Removed)>
wrote:
> > Hello,
> >
> > this may be a newbie question, but since i'm new to linx, i'll give it a
> > try:
> > Where are the routing settings stored? Every time i restart the network
> > service with "service network restart"
> > some strange entries appear when typing "route":
> > It's a route to
> > 169.254.0.0 * 0.0.0.0 U 0 0 0 eth1
> > I don't know where this comes from, since i've never entered it.
>
> That might be the default IP range used by Windows boxes that fail to get
> a DHCP IP.
>
> > It also takes a few seconds until the last of the three entries there is
> > displayed (Dest=default), does anyone know why?
> > I'm using FC3 2.6.10
>
> Most likely DNS timeout attempting to resolve IPs that do not resolve.
> route -n is quicker and sometimes easier to interpret.

I don't think it's a DNS Problem; the entry that causes the delay is the
following:
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth1

or, using route -n
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
any other suggestions? Furtheron i need to know where the network service
fetches its settings from

On Thu, 24 Feb 2005 20:41:26 +0100, Jens Hofmeier <(E-Mail Removed)> wrote:
> "David Efflandt" <(E-Mail Removed)> schrieb im Newsbeitrag
> news:(E-Mail Removed)...
>> On Thu, 24 Feb 2005 19:11:28 +0100, Jens Hofmeier <(E-Mail Removed)>
> wrote:
>> > Hello,
>> >
>> > this may be a newbie question, but since i'm new to linx, i'll give it a
>> > try:
>> > Where are the routing settings stored? Every time i restart the network
>> > service with "service network restart"
>> > some strange entries appear when typing "route":
>> > It's a route to
>> > 169.254.0.0 * 0.0.0.0 U 0 0 0 eth1
>> > I don't know where this comes from, since i've never entered it.
>>
>> That might be the default IP range used by Windows boxes that fail to get
>> a DHCP IP.
>>
>> > It also takes a few seconds until the last of the three entries there is
>> > displayed (Dest=default), does anyone know why?
>> > I'm using FC3 2.6.10
>>
>> Most likely DNS timeout attempting to resolve IPs that do not resolve.
>> route -n is quicker and sometimes easier to interpret.
>
> I don't think it's a DNS Problem; the entry that causes the delay is the
> following:
> default 192.168.1.1 0.0.0.0 UG 0 0 0 eth1

The fact that 192.168.1.1 shows as an IP instead of name (no reverse DNS)
could easily explain a DNS timeout delay.

> or, using route -n
> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
> any other suggestions? Furtheron i need to know where the network service
> fetches its settings from

Is route -n quicker (say yes)?

Which network service? Configuration of interfaces is usually something
in /etc/sysconfig. Resolving names is related to settings in /etc/ files
nsswitch.conf, host.conf, hosts and resolv.conf (and possibly your own
named.conf if doing your own DNS). Networking and network deamons are
usually started by scripts in /etc/init.d (or /etc/rc.d) symlinked in an
rc#.d subdir, where # is runlevel. Other network services may be launched
on the fly by inetd or xinetd. Status for commands like ifconfig, route
and arp are obtained from /proc.