[Click] encapsulating from IPEncap to EtherEncap exception
Hristo Asenov
njvsny at yahoo.com
Tue Apr 28 20:59:19 EDT 2009
Hello,
We are currently using CLICK to form our own packets, with the DATA field of IP packet set to our own value, which we get from an arbitrary socket. We are using IPEncap to encapsulate our data in a valid IP packet, then using EtherEncap to encapsulate it into an ethernet frame. Our script looks like:
Socket(TCP, 0.0.0.0, 7777)
-> Print("From Socket: ")
-> IPEncap(0, 192.168.0.2, 192.168.0.3)
-> Print("From IP: ")
-> IPPrint("From IP: ")
-> EtherEncap(0x0800, 0:0:0:0:0:0, 1:1:1:1:1:1)
-> Print("From Ethernet: ")
-> Queue
-> ToDevice(eth0);
Going from IPEncap to EtherEncap, we are getting the exception "expensive Packet::push; have 8 wanted 14". I have a feeling that the exception is inside IPEncap. The packet is still transmitted over the network, however we have no idea why that exception is being generated. If anyone can help us out, it would be appreciated.
Hristo
More information about the click
mailing list