From: "Канивец Николай" <n_kanivets@futureservice.ru>
To: Jay Sprenkle <jsprenkle@gmail.com>, netfilter@lists.netfilter.org
Subject: Re: iptables/mac address filtering question
Date: Sat, 11 Aug 2007 22:41:13 +0400 [thread overview]
Message-ID: <001001c7dc47$31cb8a40$0534a8c0@Sklifer> (raw)
In-Reply-To: 1b5f39a10708111046w55a4b00axb39c018a0ab54fb9@mail.gmail.com
Of course they do.
You will have the source ip address unchanged (if you do not perfrom SNAT on
any on-the-way router), but you will receive the source MAC address of
router in the nearest to your destination Ethernet segment. In other words,
say you have 3 intermediate routers between your source and destination
machines. Your destination machine will "see" the MAC (ethernet) address of
the third-on-the-way router, not your original machine.
regards,
Nikolay.
С уважением,
Николай Канивец
e-mail: n_kanivets@futureservice.ru
----- Original Message -----
From: "Jay Sprenkle" <jsprenkle@gmail.com>
To: <netfilter@lists.netfilter.org>
Sent: Saturday, August 11, 2007 9:46 PM
Subject: iptables/mac address filtering question
> Good morning all,
>
> I'm already aware mac address is easily spoofed but I'd like to make
> it just a little bit harder to break into my system anyway. I'm trying
> to only allow a specific box to use scp to safely transfer data over
> the internet.
>
> I've put in a rule in my iptables chain but notice when I try to
> connect it's rejected. The mac address I'm getting is not the same as
> what iwconfig reports on my device. If a packet is passed through
> routers on it's way to my box do they change the mac address of the
> packet?
>
> Any suggestions would be welcome.
>
> Have a good weekend
>
next prev parent reply other threads:[~2007-08-11 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 17:46 iptables/mac address filtering question Jay Sprenkle
2007-08-11 18:41 ` Канивец Николай [this message]
2007-08-11 18:55 ` iptables/mac address filtering question (nfcan: to exclusive) Jim Laurino
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='001001c7dc47$31cb8a40$0534a8c0@Sklifer' \
--to=n_kanivets@futureservice.ru \
--cc=jsprenkle@gmail.com \
--cc=netfilter@lists.netfilter.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