-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
expensive Packet::push; have 0 wanted 14 #474
Comments
https://pdos.csail.mit.edu/pipermail/click/2007-April/005780.html It means there was not enough headroom (available space) to insert the headers. The default headroom is 28 bytes, which is probably being used by the UDPIPencap so when the EtherEncap wants to add another header in front of the packet, there is no free space. I have not tried this, but you could try recompiling click after changing the default headroom to say 48 bytes in 'include/click/packet.hh' |
I imagined that such a thing would be the cause. Does this affects the IPSec functionality? |
This does not affect the functionality but certainly kills the throughput. You can use the HEADROOM argument of FromDevice to allocate more headroom to incoming packets. Alternatively, DPDK packets come with 128 bytes of Headroom and it will be much faster too. |
Thank you @tbarbette. May I ask you a question, is it wrong for IPSec functionality if i don't use the UDPIPEncap and EtherEncap and have something like this?
|
Never used IPsec, sorry. |
The HEADROOM argument seems to be working. The warning stop. |
Hello everyone, I have the following IPSec configuration script:
When traffic(from FastUDPSource element) inserts in the click configuration I took the following warning but I don't know what does it really means.
I m kindly asking you for some input,
The text was updated successfully, but these errors were encountered: