What steps will reproduce the problem?
1. A rogue DHCP server appears in the network on WAN side. (I know, this is
retarded, but it does happen on my campus network quite often)
2. udhcpc now randomly gets an address from either the new rogue server or the
correct one.
3. Try to use iptables -t raw to block these wrong servers (ideally by only
allowing the MAC address of the correct server).
What is the expected output? What do you see instead?
I expected that the iptables raw module is included, but it's not. This means I
cannot block the wrong servers. ebtables is included, but that only works for
bridged traffic. iptables -m mac --mac-source cannot be used in the filter
chain, because DHCP uses raw sockets.
Please include the iptables raw table module.
What version of the product are you using? On what operating system?
3.0.3.1-027
Original issue reported on code.google.com by B.Juha.K...@gmail.com on 10 Dec 2012 at 7:32
Original issue reported on code.google.com by
B.Juha.K...@gmail.com
on 10 Dec 2012 at 7:32