DrayTek UK Users' Community Forum

Help, Advice and Solutions from DrayTek Users

Traceroute first hop timeout

  • simrgrs
  • Topic Author
  • Offline
  • New Member
  • New Member
More
20 Nov 2012 17:06 #74280 by simrgrs
Traceroute first hop timeout was created by simrgrs
Hi, has anyone come across the first hop (which should be the draytek router) timing out - example trace to the BBC website below..

Web browsing works fine, I can ping the local IP of the router itself which is 192.168.0.1 but never see a traceroute response from it.

So far tried turning firewall / data filter off, Accept large incoming fragmented UDP or ICMP packets, DOS defence on and off - no difference.

Can anyone shed any light on this and how to resolve?

Thanks in advance!

Tracing route to www.bbc.net.uk [212.58.246.91]
over a maximum of 30 hops:

1 * * * Request timed out.
2 11 ms 11 ms 22 ms losubs.subs.dsl3.wh-man.zen.net.uk [62.3.83.27]

3 68 ms 11 ms 11 ms ge-2-1-0-116.cr1.wh-man.zen.net.uk [62.3.80.193]

4 25 ms 18 ms 28 ms ge-3-0-0-0.cr2.th-lon.zen.net.uk [62.3.80.45]
5 29 ms 17 ms 33 ms ge-2-0-0-0.cr1.th-lon.zen.net.uk [62.3.80.41]
6 18 ms 17 ms 17 ms 82.71.254.134
7 * * * Request timed out.
8 19 ms 19 ms 33 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
9 19 ms 21 ms 22 ms 132.185.255.165
10 19 ms 18 ms 19 ms bbc-vip012.cwwtf.bbc.co.uk [212.58.246.91]

Trace complete.

Please Log in or Create an account to join the conversation.

  • simrgrs
  • Topic Author
  • Offline
  • New Member
  • New Member
More
20 Nov 2012 17:28 #74281 by simrgrs
Replied by simrgrs on topic Re: Traceroute first hop timeout
to add to this, syslog entry shows as below: -

Local User: 212.58.244.66 -> 192.168.0.161 (ICMP) Time Exceeded

Please Log in or Create an account to join the conversation.

More
20 Nov 2012 18:47 #74284 by babis3g
Replied by babis3g on topic Re: Traceroute first hop timeout
Not sure is this causing from MTU packets or ICMP (getting frangment)
It s usually happens when using wifi or from the machine to router... i think s long as the hop passes next stages is fine
It happens to me with an other connection abroad and is not in use any draytek there

Please Log in or Create an account to join the conversation.

More
20 Nov 2012 18:49 #74285 by asimm.it
Replied by asimm.it on topic Re: Traceroute first hop timeout
well the first hop would expected to be the Lan address of the router which is 192.168.0.1? and i'm guessing your local ip address of the computer issuing the tracert is the one displayed in the syslog (192.168.0.161)

and any traceroute request should show the lan address of the router as the first hop, if it doesn't then there are definitely some issues that need addressing locally.

do you receive a ping reply to 192.168.0.161 when pinging your router @ 192.168.0.1?

also what model of vigor are you using and what firmware version?

Please Log in or Create an account to join the conversation.

  • simrgrs
  • Topic Author
  • Offline
  • New Member
  • New Member
More
20 Nov 2012 20:21 #74288 by simrgrs
Replied by simrgrs on topic Re: Traceroute first hop timeout
Hi,

Thats correct router at 192.168.0.1 and machine i'm testing from is 192.168.0.161, I can ping the router from any machine on the network wired and wireless, on both types of connection the first hop to the draytek times out on every machine I try from

Model Name : Vigor2830
Firmware Version : 3.3.7_2471201
Build Date/Time : Feb 9 2012 18:20:40

Web browsing works as you can see from the rest of the traceroute but agreed theres something not right if its going ttl exceeded from local machine to the router and dropping on the first hop

I did change the MTU from 1492 to 1442 but had to effect on the traceroute

Please Log in or Create an account to join the conversation.

More
23 Nov 2012 12:57 #74316 by asimm.it
Replied by asimm.it on topic Re: Traceroute first hop timeout
are your wired and wireless client ip settings dynamic ip's via dhcp or static ip's also could you do an ipconfig /all and paste the results so I can see the setup from the 192.168.0.161 pc?

I'm thinking that perhaps for some weird reason your local DNS settings or the router firewall settings will be one of the culprits but if these are all correct then possibly a firmware bug.

Please Log in or Create an account to join the conversation.

Moderators: Sami