From: Marcin Szewczyk <marcin.szewczyk@wodny.org>
To: Eliezer Croitor <ngtech1ltd@gmail.com>
Cc: 'Netfilter Users Mailing list' <netfilter@vger.kernel.org>
Subject: Re: re-routing multicast pkts after mangle table marking
Date: Wed, 2 Dec 2020 19:04:38 +0100 [thread overview]
Message-ID: <X8fXNs9Qt6XfwqlA@flatwhite> (raw)
In-Reply-To: <004f01d6c8d1$7c068350$741389f0$@gmail.com>
On Wed, Dec 02, 2020 at 07:35:07PM +0200, Eliezer Croitor wrote:
> There is a difference between packets which are dropped to the nic itself
> and traffic which is bounded to a specific ip address.
> From what I remember( and my memory is not the best as it was..) the last
> time I checked on Debian jessie you couldn't do any routing
> decision on a bounded socket.
> Maybe on newer versions of the kernel or another OS it's not the same.
But remember that `ip rule dport…` works (available in Buster) and it
interacts with the same sockets as fwmark does but `ip rule fwmark…`
doesn't work. So evidence suggest that there are indeed routing
decisions being made for those sockets.
Also note that I have done tests on sockets with sendto() without
explicit binding with any address or interface.
--
Marcin Szewczyk
http://wodny.org
next prev parent reply other threads:[~2020-12-02 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 20:14 re-routing multicast pkts after mangle table marking Brian Aanderud
2020-12-01 18:49 ` Marcin Szewczyk
[not found] ` <CAF4tN+_YNz+0iCQzW7Fd+P5ZkDkU5g95Jv5fdHPNcqhzWtOOng@mail.gmail.com>
[not found] ` <X8bE6GMR6U37cfH/@flatwhite>
[not found] ` <CAN_K0LS+U95rxmhCtiE3sX_hdjEQySnV1HBB9sF1qrrVAz0n-w@mail.gmail.com>
2020-12-02 11:23 ` Marcin Szewczyk
2020-12-02 12:10 ` Eliezer Croitor
2020-12-02 12:36 ` Marcin Szewczyk
2020-12-02 15:57 ` Eliezer Croitor
2020-12-02 16:12 ` Marcin Szewczyk
2020-12-02 16:30 ` Fatih USTA
2020-12-02 17:03 ` Marcin Szewczyk
2020-12-02 17:35 ` Eliezer Croitor
2020-12-02 18:04 ` Marcin Szewczyk [this message]
2020-12-03 8:39 ` Fatih USTA
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=X8fXNs9Qt6XfwqlA@flatwhite \
--to=marcin.szewczyk@wodny.org \
--cc=netfilter@vger.kernel.org \
--cc=ngtech1ltd@gmail.com \
/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.