Re: route or ipforward problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks,

Adding a host name to /etc/hosts solved the slow "netstat -r" but not my access problems to the router. Doing an arp gives the following result:

[root@odin root]# arp -a -n
? (192.168.1.1) at 00:90:96:4E:70:0B [ether] on eth1
? (192.168.1.6) at 00:0F:3D:0A:8D:C1 [ether] on eth1

So MAC address are known by my FC server. I suspect the router has been modified by our telecom, else I have no clue

Ciao
Poul

John DeDourek wrote:



Poul Moller wrote:

...clip...

NOTE: the last line (default gw) in the "netstat -r" command takes 10 sec to display !!!!!!!!!


....clip...

[root@odin root]# netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
10.0.0.0 * 255.255.255.0 U 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth1


That's usually a nameserver problem. Note that in the
"default" line, 192.168.1.1 is displayed rather than a
name.

If "netstat -rn" displays without a delay, than the delay
was caused by netstats attempt to convert the 192,168.1.1
address to a name using the configured nameservers, and the
inability to do this. Thus, this MAY OR MAY NOT be unrelated
to the problems you are haveing.



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux