7 Aug
2015
7 Aug
'15
9:50 p.m.
Lynwood,
my tunl0 interface shows the following values:
tunl0 Link encap:IPIP Tunnel HWaddr
inet addr:44.134.32.240 Mask:255.0.0.0
UP RUNNING NOARP MULTICAST MTU:1480 Metric:1
RX packets:827174 errors:0 dropped:0 overruns:0 frame:0
TX packets:50426 errors:757836 dropped:0 overruns:0 carrier:0
collisions:757836 txqueuelen:0
RX bytes:75933090 (72.4 Mb) TX bytes:4817617 (4.5 Mb)
I'm not able to analyze what kinda packets are concerned on
producing collisions...
gus
On 08/07/2015 03:51 PM, lleachii--- via 44Net wrote:
> (Please trim inclusions from previous messages)
> _______________________________________________
>
> Gus,
>
> I had errors and collisions before I reviewed my configuration. Now that's
everything properly configured, I don't see them.
>
> It may be helpful to note the only TWO reasons the collision and error count
increases on a tunnel interface:
>
>
>
> If the next hop of the encapsulated packet is the same tunnel interface: ipip.c line
437.
>
> If the path MTU of the next hop for the encapsulated packet is less than 68:ipip.c
line 447.
>
>
>
>
> - Lynwood
>
>
>
> -----Original Message-----
> note that (I'm not aware why) on the tunl0 interface there are
> many errors/collisions on the TX tunnel side.
>
>
>