From: Martijn Lievaart <m@rtij.nl>
To: Grant Taylor <gtaylor@riverviewtech.net>
Cc: Mail List - Netfilter <netfilter@lists.netfilter.org>
Subject: Re: NAT on stateless firewall ?
Date: Mon, 06 Aug 2007 07:01:25 +0200 [thread overview]
Message-ID: <46B6AB25.3050906@rtij.nl> (raw)
In-Reply-To: <46B673A5.6030303@riverviewtech.net>
Grant Taylor wrote:
> You stated "... arp makes the packet arrive ...", which I must disagree
> with. The sending host sends the traffic to the target hosts / gateways
> NIC. Arp is used by the sending host to learn the MAC address of the
> target host / gateway in the event that the sending host does not
> already know it. Other than converting an IP address to MAC address,
> ARP has nothing to do with the communications between two systems.
>
The sender wants to send a packet. It uses arp to find out which MAC to
send to. It sends it. The packet arrives at the destination nic. That's
all I ment, not more, not less.
However, having arrived at the nic, the packet is then transfered to the
stack. If the stack does not know about the destination IP, the packet
is dropped by routing, iirc. However, before routing (in PREROUTING) the
destination is changed to something the stack does know about. So how
comes it does not work?
M4
next prev parent reply other threads:[~2007-08-06 5:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 23:08 NAT on stateless firewall ? Florin Andrei
2007-08-03 1:49 ` Gregory Carter
2007-08-03 3:30 ` Florin Andrei
2007-08-03 4:10 ` Grant Taylor
2007-08-03 9:55 ` Pascal Hambourg
2007-08-03 18:23 ` Florin Andrei
2007-08-03 19:11 ` Florin Andrei
2007-08-03 19:15 ` Martijn Lievaart
2007-08-03 19:56 ` Florin Andrei
2007-08-03 20:37 ` Martijn Lievaart
2007-08-03 20:51 ` Grant Taylor
2007-08-05 20:16 ` Martijn Lievaart
2007-08-06 1:04 ` Grant Taylor
2007-08-06 5:01 ` Martijn Lievaart [this message]
2007-08-06 14:11 ` Grant Taylor
2007-08-03 19:23 ` Grant Taylor
2007-08-03 19:53 ` Pascal Hambourg
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=46B6AB25.3050906@rtij.nl \
--to=m@rtij.nl \
--cc=gtaylor@riverviewtech.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.