slow dsl/traceroute doesn't work

Hi,

I'm using SuSE Linux 8.2. My computer is connected to a router
(DrayTek 2500) which is to connected to the internet with an internal
dsl modem. The connection works great with win95, but it is kinda slow
on linux (7-10k/sec). Additionally, traceroute seems not to work
properly. Output:

nico@Red:~> /usr/sbin/traceroute www.google.com
traceroute to www.google.com (66.102.9.104), 30 hops max, 40 byte
packets
1 192.168.1.1 0.445 ms 0.413 ms 0.367 ms
2 * * *
3 * * *
4 * * *
5 * * *

192.168.1.1 is my router, there are never entries after it. I guess
something is not configured the way it should be, but I don't know
what (linux newbie...). Do you have any ideas?

nico@Red:~> cat /etc/resolv.conf
domain WG
nameserver 194.25.2.129

Red:/home/nico # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
192.168.1.0 * 255.255.255.0 U 0 0
0 eth0
default 192.168.1.1 0.0.0.0 UG 0 0
0 eth0

I hope you can help me

TIA,
Nico

On Fri, 23 Apr 2004 05:38:46 -0700, Nicolas Weber wrote:

> Hi,
>
> I'm using SuSE Linux 8.2. My computer is connected to a router
> (DrayTek 2500) which is to connected to the internet with an internal
> dsl modem. The connection works great with win95, but it is kinda slow
> on linux (7-10k/sec). Additionally, traceroute seems not to work
> properly. Output:
>
> nico@Red:~> /usr/sbin/traceroute www.google.com
> traceroute to www.google.com (66.102.9.104), 30 hops max, 40 byte
> packets
> 1 192.168.1.1 0.445 ms 0.413 ms 0.367 ms
> 2 * * *
> 3 * * *
> 4 * * *
> 5 * * *

/...KNIP.../

> TIA,
> Nico

There are routers which doesn't support traceroutes
The lucent cellpipe doesn't.

--
Chaos, panic & disorder - my work here is done

http://beginnerslinux.org
http://repo.mine.nu

hi

> Nicolas Weber wrote:

> nico@Red:~> /usr/sbin/traceroute www.google.com

Tried the ICMP-version?

/usr/sbin/traceroute -I www.google.com

see man traceroute


--
good luck

peter

Nicolas Weber wrote:

> nico@Red:~> cat /etc/resolv.conf
> domain WG
> nameserver 194.25.2.129

One thing I can tell You is that "194.25.2.129", which is "dns03.btx.\
dtag.de", has been extremely slow over the last period of time (three
days or so). - Depending on how long You tried, You might have met ex-
actly that period, resulting in long delays before the names were re-
solved which may end up in a timeout for traceroute. Try traceroute
with the "-n" option and tell us what You got.

You'd be better off using peer-dns, which most likely Your Win does.
Upon connection, T-Online will negotiate one or more dns servers to be
used for the session.

If You want one static dns server, try another one. From T-Online, per-
haps (e. g. 194.25.2.130, .131 etc.), or even from a different provider.


Cheers, Jack.

--
----------------------------------------------------------------------
My personal reading of the string "MicroSoft" expands to "NanoWeak"...