The ipip router at UCSD is not very busy (99% idle), but I am surprised at the number of dropped packets. It's higher than I would have hoped, suggesting there are a significant number of misconfigured routers on the network. - Brian
------------------------------------------------------------------ started at Tue May 2 20:49:25 2017 snapshot at Tue May 2 22:00:00 2017 uptime: 0+01:10:35 (4235 seconds) idle: 4194.615196 secs (99%)
packets/bytes ---------/--------- 181908/50252930 ipip encapped input 170575/45757610 forwarded out unencapsulated 1/56 dropped: no source gateway 1666210/125325363 unencapsulated input 1666196/125324029 encapped out
0/0 dropped: no destination gateway 5994/447291 dropped: encap to encap 0/0 ttl exceeded 0/0 icmp sent 0/0 dropped: packet too large
0/0 dropped: zero outer source address 0/0 dropped: broadcast outer destination address 0/0 dropped: packet too short 0/0 dropped: zero inner source address 481/66757 dropped: broadcast inner destination address
13/676 dropped: multicast inner destination address 4781/337160 dropped: non-44 inner source address 0/0 dropped: embedded encap protocol 35/1400 dropped: ip_len > MTU and DF 0/0 dropped: ip_len != packet size
0/0 dropped: output packet too short 0/0 dropped: output packet too long 4181/347878 dropped: output blocked by firewall 1/40 dropped: kernel send error 0/0 dropped: multicast inner source address
1171/1756463 outgoing encapped IPIP packet will be fragmented by kernel
2019413 route lookups took 1782499 microseconds (0.88 usec/lookup) 2 route table updates took 0.008852 seconds (4 msec each avg)
Thank you for sharing
May you provide gateways that packets are dropped from them in order that the gateways operator will be aware ? and maybe fix ?
if possible with additional info on what being dropped from etc gateway ?
Thanks In Advance
Thanks Forward
Ronen - 4Z4ZQ
Ronen Pinchooks (4Z4ZQ) WebSitehttp://www.ronen.org/ www.ronen.org ronen.org (Ronen Pinchooks (4Z4ZQ) WebSite) is hosted by domainavenue.com
________________________________ From: 44Net 44net-bounces+ronenp=hotmail.com@hamradio.ucsd.edu on behalf of Brian Kantor Brian@UCSD.Edu Sent: Tuesday, May 2, 2017 10:18 PM To: 44net@hamradio.ucsd.edu Subject: [44net] router stats
(Please trim inclusions from previous messages) _______________________________________________ The ipip router at UCSD is not very busy (99% idle), but I am surprised at the number of dropped packets. It's higher than I would have hoped, suggesting there are a significant number of misconfigured routers on the network. - Brian
------------------------------------------------------------------ started at Tue May 2 20:49:25 2017 snapshot at Tue May 2 22:00:00 2017 uptime: 0+01:10:35 (4235 seconds) idle: 4194.615196 secs (99%)
packets/bytes ---------/--------- 181908/50252930 ipip encapped input 170575/45757610 forwarded out unencapsulated 1/56 dropped: no source gateway 1666210/125325363 unencapsulated input 1666196/125324029 encapped out
0/0 dropped: no destination gateway 5994/447291 dropped: encap to encap 0/0 ttl exceeded 0/0 icmp sent 0/0 dropped: packet too large
0/0 dropped: zero outer source address 0/0 dropped: broadcast outer destination address 0/0 dropped: packet too short 0/0 dropped: zero inner source address 481/66757 dropped: broadcast inner destination address
13/676 dropped: multicast inner destination address 4781/337160 dropped: non-44 inner source address 0/0 dropped: embedded encap protocol 35/1400 dropped: ip_len > MTU and DF 0/0 dropped: ip_len != packet size
0/0 dropped: output packet too short 0/0 dropped: output packet too long 4181/347878 dropped: output blocked by firewall 1/40 dropped: kernel send error 0/0 dropped: multicast inner source address
1171/1756463 outgoing encapped IPIP packet will be fragmented by kernel
2019413 route lookups took 1782499 microseconds (0.88 usec/lookup) 2 route table updates took 0.008852 seconds (4 msec each avg)
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Hi Ronen, I'm not currently logging the per-packet error messages because there are too many of them. I'm working on a way to gather individual statistics for each gateway, but right now I don't have them, so I can't tell you which gateway is doing what wrong.
Sorry, that will have to come at a later date.
What I'm going to have to do is add an error table to the per-gateway structure and increment counters in it when they happen. That's not a lot of software to write but I haven't done it yet. Please be patient and I'll get to it. - Brian
On Wed, May 03, 2017 at 07:43:38AM +0000, R P wrote:
Thank you for sharing
May you provide gateways that packets are dropped from them in order that the gateways operator will be aware ? and maybe fix ?
if possible with additional info on what being dropped from etc gateway ?
Thanks In Advance
Thanks Forward
Ronen - 4Z4ZQ
Would Netflow not sort this out? There are open source packages for collecting Netflow data, that way you have a better understanding of the traffic passing to each gateway and protocols they pass
73,
Ruben - ON3RVH
-----Original Message----- From: 44Net [mailto:44net-bounces+on3rvh=on3rvh.be@hamradio.ucsd.edu] On Behalf Of Brian Kantor Sent: woensdag 3 mei 2017 10:32 To: AMPRNet working group 44net@hamradio.ucsd.edu Subject: Re: [44net] router stats
(Please trim inclusions from previous messages) _______________________________________________ Hi Ronen, I'm not currently logging the per-packet error messages because there are too many of them. I'm working on a way to gather individual statistics for each gateway, but right now I don't have them, so I can't tell you which gateway is doing what wrong.
Sorry, that will have to come at a later date.
What I'm going to have to do is add an error table to the per-gateway structure and increment counters in it when they happen. That's not a lot of software to write but I haven't done it yet. Please be patient and I'll get to it. - Brian
On Wed, May 03, 2017 at 07:43:38AM +0000, R P wrote:
Thank you for sharing
May you provide gateways that packets are dropped from them in order that the gateways operator will be aware ? and maybe fix ?
if possible with additional info on what being dropped from etc gateway ?
Thanks In Advance
Thanks Forward
Ronen - 4Z4ZQ
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
It probably would. I thought of it, but I'm not all that familiar with the storage requirements to gather netflow data. My initial impression was that it was rather large. I know at work we have a dedicated machine with a LOT of fast disk on it to gather and accumulate the netflow data from the various building and border routers. There is also the issue of how do you define a flow when all you ever see is stateless datagrams. At this point the router is not looking inside the packets it forwards. I'll have to look into it. - Brian
On Wed, May 03, 2017 at 08:45:19AM +0000, Ruben ON3RVH wrote:
Would Netflow not sort this out? There are open source packages for collecting Netflow data, that way you have a better understanding of the traffic passing to each gateway and protocols they pass 73, Ruben - ON3RVH
-
Brian Kantor -
R P -
Ruben ON3RVH