RARE user and assistance email list

["mc36" <>]

-------- Forwarded Message --------
Subject: Re: additional lib needed for builds
Date: Tue, 5 Jul 2022 22:09:12 +0200
From: mc36 <>
Reply-To: 
To: 

hi,

On 7/4/22 13:09, mc36 wrote:
> > Can ping show mdev as in linux and more precise values than jus 0?

sid#ping www repeat 1111
2022-07-05 21:58:11.579
resolving www for ipv6 ok!
pinging 2001:db8:1101::10, src=2001:db8:1101::227:227, vrf=v1, cnt=1111, 
len=64, df=false, tim=1000, gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, 
sweep=false, multi=false
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
result=100.0%%, recv/sent/lost/err=1111/1111/0/0, took 1169, min/avg/max/dev 
rtt=0/1.0/31/2.6, ttl 255/255/255/0.0, tos 0/0.0/0/0.0
sid#

regarding the more precise values, and as we're talking about java, imho no 
reason to switch from ms to us:
snoopy.vhpc#show watchdog timer
         1000|############################################################
         1000|############################################################
         1000|############################################################
         1000|############################################################
         1000|############################################################
         1000|############################################################
         1000|############################################################
         1000|############################################################
         1000|############################################################
         1000|############################################################
         1000|############################################################
          bps|0---------10--------20--------30--------40--------50-------- 
seconds

         1010|   *                                *
         1009|   *                                *
         1008|************************************************************
         1007|************************************************************
         1006|************************************************************
         1005|************************************************************
         1004|************************************************************
         1003|************************************************************
         1002|************************************************************
         1001|************************************************************
         1000|############################################################
          bps|0---------10--------20--------30--------40--------50-------- 
minutes

         1200|                                    *
         1180|            *                       *
         1160|            *                       *
         1140|            *   *   *               *  **
         1120|            *   *   *    *         **  **
         1100|            *   *   *    *         **  **
         1080|            *   *   *    *         **  **            *
         1060|           **   *   *    *         **  **            *
         1040|           ** * *   *    *     *   **  **  *         **
         1020|           ** * *  **    *     *   **  **  *         **
         1000|############################################################
          bps|0---------10--------20--------30--------40--------50-------- 
hours


snoopy.vhpc#

it's the regular grapher in freerouter, you can attach these to sensors or by 
default,
you have them for interface bandwidth like "disp int eth1 hist" and friends, 
but here,
it lives within a subroutine doing the interface history processing, which is 
constant
time, then sleep(1000ms) then agian... as you can see, regardless of the 
advancements
in the gc in modern java (maybe i had to enable them? :)) there is still some 
stop the
world like events happening randomly... some of them take as much as 200ms..:(



> > Question about traceroute.
> > What it shows on first hop?
> >
> > r1#traceroute 2.2.2.3 vrf v1
> > tracing 2.2.2.3, src=null, vrf=v1, prt=0/33440, tim=1000, tos=0, flow=0, 
> > len=64
> > 1 1.1.1.5 time=4
> > 2 2.2.2.3 time=73
> > r1#traceroute 2.2.2.4 vrf v1
> > tracing 2.2.2.4, src=null, vrf=v1, prt=0/33440, tim=1000, tos=0, flow=0, 
> > len=64
> > 1 1.1.1.5 time=0
> > 2 2.2.2.4 time=246
> >
> > In both cases on firs hop here ip address of local interfce ethernet1.
the first box who answers to the ttl=1... it's normally itself... it's useful 
to konw the outgoing interface...
https://github.com/rare-freertr/freeRtr/blob/798f2801645306cebcb947c3cf3bf72f1b2a5bc4/src/net/freertr/user/userExec.java#L3407

> > But I expect to see at least different numbers of hops in this two
> > outputs because ttl in ping for 2.2.2.3 is 255 and for 2.2.2.4 is 254
> >
> > r1#ping 2.2.2.3 vrf v1
> > pinging 2.2.2.3, src=null, vrf=v1, cnt=5, len=64, df=false, tim=1000,
> > gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, sweep=false, multi=false
> > !!!!!
> > result=100%, recv/sent/lost/err=5/5/0/0, rtt min/avg/max/sum=0/1/2/8,
> > ttl min/avg/max=255/255/255, tos min/avg/max=0/0/0
> > r1#ping 2.2.2.4 vrf v1
> > pinging 2.2.2.4, src=null, vrf=v1, cnt=5, len=64, df=false, tim=1000,
> > gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, sweep=false, multi=false
> > !!!!!
> > result=100%, recv/sent/lost/err=5/5/0/0, rtt min/avg/max/sum=1/2/3/10,
> > ttl min/avg/max=254/254/254, tos min/avg/max=0/0/0
> >
> > So why number of hops the same?
wait a bit, when you ping itself (.3), then it's 255,
when you ping the other (.4) then it's 254....
these are not the same...


> > Is there functioality as in linux tracepath for detecting pmtu?
not yet, but that will be the next... :)

thanks,
cs


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#370): https://groups.io/g/freertr/message/370
Mute This Topic: https://groups.io/mt/92201568/6413194
Group Owner: 
Unsubscribe: https://groups.io/g/freertr/unsub []
-=-=-=-=-=-=-=-=-=-=-=-