________________________________ 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