Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 3 subscribers
  • Views 6880 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to allow Traceroute from internal network?

Jui (Uwe Betz)
I just wanted to do a trace from an internal system using WS_PingPro and found that this doesn't work at all. The only machine I get an answer from is the Astaro Fw/Router itself.
So I opend my PacketFilter for ALL traffic, but it didn't help. Traces with the Traceroute-Tool on the firewall work just find, but why not from an internal Client? NAT shouldn't hjave anything to do with that or am I wrong?
With my SMC and a Netgear there were noe Problems like this. What do I have to configure to let internal machines Treceroute external machines?  


This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to norwich
    I have it enabled all the time. I have also Treceroute Forwarding enabled. 
    I get Timeouts on the route except the target.

    Trace www.peer.biz; Start time 03/06/03 19:42:58
    Tracing route to 62.146.19.130
    50 bytes from 62.146.19.130: time=82 ms
    Hop         Avg          Diff           Address
     1 3            3            192.168.1.1
     2 * * Timed out
     3 * * Timed out
     4 * * Timed out
     5 * * Timed out
     6 * * Timed out
     7 * * Timed out
     8 * * Timed out
     9 82           79           62.146.19.130
    End time 03/06/03 19:43:34
    host reached
      
  • 0 in reply to Jui (Uwe Betz)
    I should have checked the local system: There is a Personal firewall running in a stealth mode in background which was responsible for the problem.

    Sorry for my posting