News: This forum is now permanently frozen.
Pages: [1]
Topic: tracert or traceroute  (Read 2059 times)
« on: January 11, 2008, 23:07:42 »
johnny *
Posts: 3

Any ideas why when I run traceroute or tracert from a computer on the LAN through monowall I get Request timed out. Ping works fine. It's not a routing problem or routers on route. Traceroute from monowall works fine. Something to do with monowall blocking ICMP TIME_EXCEEDED response, my guess? Can I change this?

TIA
« Reply #1 on: January 11, 2008, 23:55:50 »
ChainSaw
Guest

You might try adding this WAN Rule:

Pass - WAN - ICMP - Time exceeded - any - any

CS...
« Reply #2 on: January 12, 2008, 02:54:20 »
johnny *
Posts: 3

Nope. Also tried Pass - WAN -any -any -any still get this


C:\Windows\system32>tracert www.google.com

Tracing route to www.l.google.com [66.249.93.147]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12    42 ms    41 ms    41 ms  ug-in-f147.google.com [66.249.93.147]

Trace complete.
« Reply #3 on: September 24, 2009, 21:50:32 »
woutermense *
Posts: 3

I know this is an old topic to kick, but I have the exact same problem. Even if I allow all incoming traffic through, tracert will timeout on all hops but the last. Any help on this?
« Last Edit: September 24, 2009, 22:59:41 by woutermense »
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines