[Click] Problem with the lo interface

[Eddie Kohler]

Hi Venu,

>  I have been trying to print nfs packets that are recieved by the machine.
> I have both the nfs client and server on the same achine. Hence I have to
> use the lo interface. When I use 'tcpdump -i lo port 2049' I am able to
> get the packet info, but when i use the following click configuration the
> lo interface doesn't respond. The same configuration with the interface lo
> being replaced by etho, doesn't hang when I use ping and ssh... Is there
> anything that I am missing.

The lo interface avoids most of the regular input stack. Kernel Click will
not see packets sent to loopback. You should be able to see the packets
with user-level Click, however.

Eddie