________________________________ if the encap process add more bits and thats explain why inbond encap is bigger then then the inbond raw why it is not opposit in the following graph ?
https://gw.ampr.org/router/encapvsrawbytes.svg
the un encapped traffic (that goes out) shouldn't be without all the headers that come into it ? and in the graph they are almost same size input and encaped input ....
Ronen - 4Z4ZQ
------------------
Remember that encapsulating a packet makes it longer by the size of the added IP header, that is, by 20 bytes. The byte counts include the entire size of the packet, including all headers.
The outbound encap traffic packet count is slightly higher than the inbound that causes it because large incoming packets are fragmented into two packets after having grown in size by the addition of the second IPIP encapsulation header.
The byte count is significantly higher because the majority of the inbound traffic is connection requests i.e., packets that consist only of an IP and a UDP or TCP header, no data. Adding the IPIP header to this makes the packet significantly larger, increasing its byte count. - Brian