Re: routing prob
From: David Efflandt (efflandt_at_xnet.com)
Date: Fri, 25 Feb 2005 03:05:18 +0000 (UTC)
On Thu, 24 Feb 2005 20:41:26 +0100, Jens Hofmeier <firstname.lastname@example.org> wrote:
> "David Efflandt" <email@example.com> schrieb im Newsbeitrag
>> On Thu, 24 Feb 2005 19:11:28 +0100, Jens Hofmeier <firstname.lastname@example.org>
>> > 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
> 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.