From: jordi guri <jordi@northome.ca>
To: netfilter-devel@vger.kernel.org
Subject: Filtering invalid MAC addresses
Date: Sun, 27 Nov 2016 18:09:11 -0800 [thread overview]
Message-ID: <7e23d525adcd53f91eb6bf6db65a7e91@northome.ca> (raw)
Hi,
I was wondering if the newer nftables is able to deal with invalid MAC
addresses. iptables I don't think can deal with these. For example I
have the following showing up in my log (from some anonymous proxy port
scanner):
+++++
Nov 27 17:27:40 northome kernel: ** iptables-DROP ** IN=eth0 OUT=
MAC=f2:3c:91:9b:81:db:84:78:ac:0d:79:c1:08:00 SRC=183.
60.48.25 DST=23.92.27.236 LEN=40 TOS=0x00 PREC=0x20 TTL=51 ID=0 DF
PROTO=TCP SPT=12208 DPT=5902 WINDOW=8192 RES=0x00 SYN
URGP=0
Nov 27 17:31:50 northome kernel: ** iptables-DROP ** IN=eth0 OUT=
MAC=f2:3c:91:9b:81:db:84:78:ac:0d:a6:41:08:00 SRC=175.
194.186.44 DST=23.92.27.236 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=39168
PROTO=TCP SPT=24565 DPT=23 WINDOW=19941 RES=0x00 S
+++++
There are many such entries as the above (all day, every minute) for
various destination ports on my server, and (in this case) with the same
2 invalid MAC addresses.
What is interesting about this is that the first part of both of the
above MAC addresses in my iptables log are; "f2:3c:91:9b:81:db". This
happens to be the same MAC address as that of my server's eth0
interface. Therefore I cannot block these scan attempts via the MAC
address alone (even if I could in part).
So my question; Does/is nftables/iptables going to offer some sort of
solution to the above invalid MAC address problem, as iptables does
currently for invalid packets and IP addresses?
Thank-you for your time and your very fine work on this fantastic
firewall product.
Thanks and regards,
Jordi
next reply other threads:[~2016-11-28 2:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 2:09 jordi guri [this message]
2016-11-28 7:31 ` Filtering invalid MAC addresses Michal Kubecek
2016-11-28 7:33 ` Phil Sutter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7e23d525adcd53f91eb6bf6db65a7e91@northome.ca \
--to=jordi@northome.ca \
--cc=netfilter-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).