ping -R output?

Julian Elischer julian at freebsd.org
Wed Oct 14 09:07:19 UTC 2020


thanks! that's really interesting. Different from what I was expecting 
but what I'd expect from
the code dropping into Fuchsia.

It's such a pity our ping doesn't support ping -T (timestamps)
but Linux does and I'd love to see [(Linux) 'ping -T tsandaddr 
{machine B}'] ---->[FreeBSD  A] -----> [FreeBSD B]

If anyone can do that, I'd really appreciate it..
Actually all three machines as Linux would be an interesting 
comparison as well (for both -T and -R).

Linux adds an entry for both reception and transmission on the far end 
and the sender..
FreeBSD only does sender on the intermediate and far end, and receiver 
on the local.
I don't know what Linux does on the intermediate hosts. My reading of 
the RFC agrees with BSD for RR.
but you only get 9 slots so Linux is limited to a full distance of 2 
(and return) if they use 2 slots for each hop.
I can't say if we get Timestamp right as we can't do it.

J


On 10/14/20 1:25 AM, Peter Libassi wrote:
> like this? ( ping from 192.168.3.1 -> (192.168.3.2/172.16.42.1) -> 
> 172.16.42.2
>
> root at bsd1:~ # ping -R 172.16.42.2
> PING 172.16.42.2 (172.16.42.2): 56 data bytes
> 64 bytes from 172.16.42.2: icmp_seq=0 ttl=63 time=1.280 ms
> RR: 172.16.42.1
> 172.16.42.2
> 192.168.3.2
> 192.168.3.1
> 64 bytes from 172.16.42.2: icmp_seq=1 ttl=63 time=1.238 ms(same route)
> 64 bytes from 172.16.42.2: icmp_seq=2 ttl=63 time=1.100 ms(same route)
> 64 bytes from 172.16.42.2: icmp_seq=3 ttl=63 time=1.210 ms(same route)
> 64 bytes from 172.16.42.2: icmp_seq=4 ttl=63 time=1.156 ms(same route)
>
> /Peter
>
>> 14 okt. 2020 kl. 09:05 skrev Julian Elischer <julian at freebsd.org 
>> <mailto:julian at freebsd.org>>:
>>
>> Can someone send me the output of a ping -R , starting with FreeBSD 
>> machine, through a second FreeBSD machine and bouncing back from a 
>> third FreeBSD machine?  I don't have three in a row like that 
>> anywhere. Probably best to send it back through the list so I 
>> people can see if i get an answer.
>>
>>
>> Thanks, Julian
>>
>>
>>
>> _______________________________________________
>> freebsd-net at freebsd.org <mailto:freebsd-net at freebsd.org> mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-net
>> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
>



More information about the freebsd-net mailing list