[Click] ipmapper syntax problem?

[Erik VandeKieft]

Hi,

I have my own mapper class that extends IPMapper and Element that I use
inside an IPRewriter. In the constructor, I do both set_ninputs(0) and
set_noutputs(0), yet when I try to instantiate the router it keeps
insisting that inputs 0 and 1 and outputs 0 and 1 are unused. Why does it
keep insisting that there be two inputs and two outputs? Is this a
property of the IPMapper class?

Thanks,
--Erik Vandekieft

On Tue, 20 Jul 2004 kevin_mitchell at agilent.com wrote:

> I have a user-level click script running on machine A that sends a packet 50 bytes long to machine B.  Inserting a Print element immediately prior to sending the packet confirms it has this length.  On machine B I'm running a kernel-level click script.  If I insert a Print element immediately after receiving the packet, using FromDevice, it says the packet is now 60 bytes long.  If I know the payload contains an IP packet then I can insert a CheckIPHeader element, and this, as a side-effect, truncates the packet back down to the expected 50 bytes, by using the IP length in the header.  But I might not always have an IP header in the payload, so this won't always work.  Is this difference between the expected packet length, and the reported length, to be expected?
>
> Kevin
>
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>
>