>>  traceroute to pppclnttwo.knot.nl (193.78.85.31), 30 hops max, 38 byte
>>packets
>>   1  pppclnttwo.knot.nl (193.78.85.31)  298.355 ms !  299.539 ms !  256.886
>>ms
>>
>> What's the cause and/or sollution to such a problem?
>> ThanX
>> noud
>
>noud, you seem to have this annoying habit of not explaining yourself properly.

Thanx for the mirror.

>What problem are you talking about? The '!' in the output? Have you

pppd started on phone with pppporttwo:pppclnttwo proxyarp results in (on phone):

Destination      Gateway            Flags     Refs     Use  Interface
pppclnttwo.knot. pppporttwo.knot.nl UH          0        0  ppp0
pppclnttwo.knot. ae0:0.0.94.60.71.4 UHLS2       0        0  ae0

phone# traceroute pppclnttwo
traceroute to pppclnttwo.knot.nl (193.78.85.31), 30 hops max, 38 byte packets
 1  pppclnttwo.knot.nl (193.78.85.31)  299.705 ms !  282.087 ms !  257.515 ms !

dns# traceroute pppclnttwo
traceroute to pppclnttwo.knot.nl (193.78.85.31), 30 hops max, 38 byte packets
 1  phone.knot.nl (193.78.85.2)  4.616 ms  4.048 ms  4.063 ms
 2  * * *
 3  pppclnttwo.knot.nl (193.78.85.31)  293.851 ms !  286.958 ms !  294.302 ms !

So to be exact, i think my problem is that proxyarp creates a route that's
not valid.

>read the manual page? It would be nice if you mentioned these things in
>the body of the mail so that people know whether or not to treat you seriously

I've been reading those man pages since 1-10-95. That's not to say that i
understand everything in it or hence ask the right questions. What's more,
i also implement the things i read. I'm serious; does this look serious
enough?

>Anyway I'll assume you've rtfm'd, and that you intended something meaningful
>by "traceroute & !".

So yes, i read the funky manual. It sayes that it's a ttl problem (ttl<=1).
Could be the peer is sending non-decremented ttls back, could be something else.
For instance a ae0 route that goes before a ppp0 route (?).

>Try ping in verbose mode (rtfm) to see whats happening to the packets.
>! means some sort of error packet recv'd for the ICMP ECHO packet send'd.

For the manuals sake:
phone# ping pppclnttwo
PING pppclnttwo.knot.nl (193.78.85.31): 56 data bytes
64 bytes from 193.78.85.31: icmp_seq=0 ttl=60 time=304.832 ms
64 bytes from 193.78.85.31: icmp_seq=1 ttl=60 time=306.360 ms

phone# ping -v pppclnttwo
PING pppclnttwo.knot.nl (193.78.85.31): 56 data bytes
64 bytes from 193.78.85.31: icmp_seq=0 ttl=60 time=324.736 ms
64 bytes from 193.78.85.31: icmp_seq=1 ttl=60 time=273.929 ms

phone# ping -vdR -c 2 pppclnttwo
PING pppclnttwo.knot.nl (193.78.85.31): 56 data bytes
64 bytes from 193.78.85.31: icmp_seq=0 ttl=60 time=376.410 ms
....
NOP 39 of them
....
64 bytes from 193.78.85.31: icmp_seq=1 ttl=60 time=352.812 ms
....
NOP 39 of them
....

--- pppclnttwo.knot.nl ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 352.812/364.610/376.410 ms

btw: phone:pppclnttwo proxyarp gives the same problem.
~n


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
KnoT Foundation                                     Noud de Brouwer
People's Internet Domain +31-13                       Kerkstraat 86
                                                 5051 LC  GOIRLE NB
                                                    the Netherlands
e-mail: noud@knot.nl                          Tel.:   +31-13-342761
http:   //www.knot.nl/                    Fax./ARA:   +31-13-346945
talk:   noud@renning.knot.nl                   PPP:   +31-13-345057
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~