From: Ido Schimmel <idosch@idosch.org>
To: Swarm NameRedacted <thesw4rm@pm.me>
Cc: Andrew Lunn <andrew@lunn.ch>, netdev@vger.kernel.org
Subject: Re: Packet not rerouting via different bridge interface after modifying destination IP in TC ingress hook
Date: Thu, 6 Aug 2020 09:33:36 +0300 [thread overview]
Message-ID: <20200806063336.GA2621096@shredder> (raw)
In-Reply-To: <20200805201204.vsnav57fmgqkkpxf@chillin-at-nou.localdomain>
On Wed, Aug 05, 2020 at 08:12:08PM +0000, Swarm NameRedacted wrote:
> All fair points, I'll address them one by one.
> 1) The subnet size on everything is /16; everything is on the same
> subnet (hence the bridge) except for the client which sends the initial
> SYN packet. Modifying the destination MAC address was definitely
> something I overlooked and that did get the packet running through the
> correct interface. I got a bit thrown off that the bridge has it's own
> MAC address that is identical to the LAN interface and couldn't
> visualize it as an L2 switch. However, the packet is still being
> dropped; I suspect it might be a checksum error but the only incorrect
> checksum is TCP. Might have accidentally disabled checksum offloading. I'm not
> sure
You might need to enable hairpin on eth0:
# ip link set dev eth0 type bridge_slave hairpin on
next prev parent reply other threads:[~2020-08-06 11:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 8:19 Packet not rerouting via different bridge interface after modifying destination IP in TC ingress hook Swarm NameRedacted
2020-08-05 13:39 ` Andrew Lunn
2020-08-05 20:12 ` Swarm NameRedacted
2020-08-06 6:33 ` Ido Schimmel [this message]
2020-08-06 7:00 ` Swarm NameRedacted
2020-08-06 7:49 ` Ido Schimmel
2020-08-06 8:33 ` Swarm NameRedacted
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=20200806063336.GA2621096@shredder \
--to=idosch@idosch.org \
--cc=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
--cc=thesw4rm@pm.me \
/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.