So it's not kept as part of the packet's internal housekeeping? I don't think that I've ever worked on a router where that wasn't part of a packet's state.
What would be involved in adding it as part of the intrinsic state? On 1/1/11 1:47 PM, Pekka Nikander wrote: > A typical way of doing that is to Paint the packet soon after receiving it > from the interface, before muxing it with other traffic. You can the use a > PaintSwitch to demux it according to the interface it came through. > > --Pekka > > On 2011-01 -01, at 22:26 , Philip Prindeville wrote: > >> (Forgive the newbie questions... I'm having to learn Click in a hurry as I >> ramp up on a project.) >> >> Is there a built-in element that returns the ingress interface of a packet? >> >> I'm trying to write an elementclass in Click that modifies a packet and then >> sends it back out the same interface it came in on, but don't want to have >> one instance of it per-interface that it is used on. >> >> Thanks. >> >> -Philip _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click
