This is automatically generated documentation. Edit after the "COMMENTS" heading; changes to the main body will be lost.
FromDevice.u -- Click element; reads packets from network device (user-level)
FromDevice(DEVNAME [, keywords SNIFFER, PROMISC, SNAPLEN, FORCE_IP, CAPTURE, BPF_FILTER, OUTBOUND])
Ports: no inputs, 1 output
Processing: push
Drivers: userlevel
Package: userlevel (core)
This manual page describes the user-level version of the FromDevice element. For the Linux kernel module element, read the FromDevice manual page. Reads packets from the kernel that were received on the network controller named DEVNAME. User-level FromDevice behaves like a packet sniffer by default. Packets emitted by FromDevice are also received and processed by the kernel. Thus, it doesn't usually make sense to run a router with user-level Click, since each packet will get processed twice (once by Click, once by the kernel). Install firewalling rules in your kernel if you want to prevent this, for instance using the KernelFilter element or FromDevice's SNIFFER false argument. Under Linux, a FromDevice element will not receive packets sent by a ToDevice element for the same device. Under other operating systems, your mileage may vary. Sets the packet type annotation appropriately. Also sets the timestamp annotation to the time the kernel reports that the packet was received. Keyword arguments are:
FromDevice(eth0) -> ...
FromDevice sets packets' extra length annotations as appropriate.
"<d", meaning at most d drops; or "??", meaning the number of drops is not known.IP', `ETHER', or `FDDI', for example.ToDevice.u, FromDump, ToDump, KernelFilter, FromDevice
Generated by 'click-elem2man' from '../elements/userlevel/fromdevice.hh' on 18/Sep/2007.