Quote:
Originally Posted by
3happypenguins
I was totally lost when you said this:
It'd make more sense if you've ever built your own kernel. You get a list of options to choose from, and get to pick whether device drivers are disabled (n), built-in(y), or put in modules to load later(m). /proc/config.gz is a list of what options were picked when the kernel was made.
The point is, this kernel has built-in support for mac filtering.
Does the AF+ documentation say to use $IPTABLES instead of iptables, or did you pick that up from an example somewhere? Try plain 'iptables'.
Quote:
Not sure if this has to do with anything, but I enabled logs in AFWall+, but when I go to look, it always says "Log is Empty," even if I browse around on the internet. It's always just empty.
I know nothing about AF+, so I couldn't say. iptables itself doesn't log unless told, but a firewall generator which talks to iptables could do who-knows-what.
My suggestion would be:
1) Turn off AF+
2) Type
iptables -A INPUT -m mac --mac-source 00:00:00:00:00:00 -j DROP and
iptables -A FORWARD -m mac --mac-source 00:00:00:00:00:00 -j DROP into a root console
3) See if that works
If
that works, you might just be fighting your firewall generator.
P.S: There's probably not much reason to obscure your MAC address. That's not useful to anyone outside your local network.