PATCH: wired eapol receive/send
Thu Sep 2 03:30:27 PDT 2004
> Is there any particular reason for parsing DHCP packets? One option
> would be to open packet socket on the same interface with Linux Socket
> filter to capture the packets and then take the layer 2 address from
> them. Then again, this may not end up being much simpler. Eventually, I
> would assume this could be replaced with something like iptables
> firewall queueing packets from unknown MAC addresses for user space
> processing and all devices would be noticed whenever they send the first
> packet, no matter whether it is DHCP or something else, i.e., static IP
> and non-IPv4 hosts would also be processed.
Iptables is the wrong place doing it. If you define a user process
doing packet filtering with target QUEUE you can match only IPV4 or
IPV6 packets. There is no way to match both classes or layer 2
packets! So you will NOT see dhcp packets in userspace process!
More information about the Hostap