28 Apr
2017
28 Apr
'17
1:09 p.m.
I've spent the last few hours adding some instrumentation
(various counters) to the ipip daemon. Here's a sample of
some of the data I now have available. This is a work in
progress.
The counters are packets/bytes.
- Brian
started at Thu Apr 27 22:51:19 2017
uptime: 0+00:08:41
15940/8895013 encapped input
13516/8414203 forwarded out
0/0 no source gateway
158252/9266766 raw input
159062/9316591 encapped out
0/0 no destination gateway
1613 discarded
0 ttlexceeded
614 routes (614 ipip, 0 udpip) loaded 521 seconds ago at Thu Apr 27 22:51:19 2017
28 Apr
28 Apr
2:03 p.m.
Is there option to add two more things ?
1) every gateway ammount of data it is passing (inbond and outbond) ? and if possible max
kb/s data ?
Total data of the encap interface (inbond and outbond) ?
________________________________
From: 44Net <44net-bounces+ronenp=hotmail.com(a)hamradio.ucsd.edu> on behalf of Brian
Kantor <Brian(a)UCSD.Edu>
Sent: Thursday, April 27, 2017 11:09 PM
To: 44net(a)hamradio.ucsd.edu
Subject: [44net] amprgw stats
(Please trim inclusions from previous messages)
_______________________________________________
Here's a sample of
some of the data I now have available.
6:49 p.m.
On Fri, Apr 28, 2017 at 07:03:53AM +0000, R P wrote:
Is there option to add two more things ?
1) every gateway ammount of data it is passing (inbond and outbond) ? and if possible
max kb/s data ?
Total data of the encap interface (inbond and outbond) ?
1. Like this? I didn't want to include all 614 lines.
614 routes (614 ipip, 0 udpip) loaded 10761 seconds ago at Fri Apr 28 01:30:39 2017
entry subnet encap gateway outpkts outbytes inpkts inbytes
----- ------------------- ----- ---------------- --------- --------- --------- ---------
0 44.0.0.1/32 ipip 169.228.66.251 21 1639 0 0
1 44.2.2.0/24 ipip 24.52.189.1 1041 67985 0 0
2 44.2.7.0/30 ipip 73.185.12.233 57 3675 0 0
3 44.2.10.0/29 ipip 104.49.12.130 849 58246 152 11743
4 44.2.50.0/29 ipip 75.140.109.173 406 25351 0 0
5 44.4.2.152/29 ipip 173.167.109.217 327 20899 18 1146
etc
The problem with reporting kb/s data per gateway is that the routes
table is cleared and reloaded every time a new encap file is installed,
so there could only be the last few hours averages shown and the
time period would vary on when the encap file last changed. It
would be inconsistent.
2. Well, the input and output of the encap interface is shown;
you could just add them together. I don't see much value in
displaying that total myself.
started at Thu Apr 27 23:22:26 2017
snapshot at Fri Apr 28 04:30:00 2017
uptime: 0+05:07:34 (18454 seconds)
packets/bytes
---------/---------
583528/282364618 ipip encapped input
494571/264411172 forwarded out
12/672 no source gateway
4917904/336332360 raw input
4947670/338423143 encapped out
0/0 no destination gateway
59143 discarded
0 ttlexceeded
10:08 p.m.
________________________________
Yes thats excellent
as for the problem of the encap file if the time makes problem to calculate kb/s maybe
to add max KB/S ?
---------------------------------
1. Like this? I didn't want to include all 614 lines.
614 routes (614 ipip, 0 udpip) loaded 10761 seconds ago at Fri Apr 28 01:30:39 2017
entry subnet encap gateway outpkts outbytes inpkts inbytes
----- ------------------- ----- ---------------- --------- --------- --------- ---------
0 44.0.0.1/32 ipip 169.228.66.251 21 1639 0 0
1 44.2.2.0/24 ipip 24.52.189.1 1041 67985 0 0
2 44.2.7.0/30 ipip 73.185.12.233 57 3675 0 0
3 44.2.10.0/29 ipip 104.49.12.130 849 58246 152 11743
4 44.2.50.0/29 ipip 75.140.109.173 406 25351 0 0
5 44.4.2.152/29 ipip 173.167.109.217 327 20899 18 1146
etc
The problem with reporting kb/s data per gateway is that the routes
table is cleared and reloaded every time a new encap file is installed,
so there could only be the last few hours averages shown and the
time period would vary on when the encap file last changed. It
would be inconsistent.
2. Well, the input and output of the encap interface is shown;
you could just add them together. I don't see much value in
displaying that total myself.
started at Thu Apr 27 23:22:26 2017
snapshot at Fri Apr 28 04:30:00 2017
uptime: 0+05:07:34 (18454 seconds)
packets/bytes
---------/---------
583528/282364618 ipip encapped input
494571/264411172 forwarded out
12/672 no source gateway
4917904/336332360 raw input
4947670/338423143 encapped out
0/0 no destination gateway
59143 discarded
0 ttlexceeded
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
11:07 p.m.
The problem is that the time would vary. The period would sometimes
be only a few seconds, other times it would be hours. That would be
inconsistent and make the statistic of limited value, so I chose
not to calculate it.
- Brian
On Fri, Apr 28, 2017 at 03:08:10PM +0000, R P wrote:
Yes thats excellent
as for the problem of the encap file if the time makes problem to calculate kb/s maybe
to add max KB/S ?
2795
days inactive
2795
days old
4 comments
2 participants
participants (2)
-
Brian Kantor -
R P