Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Sep 2024 08:41:32 +0000
From:      bugzilla-noreply@freebsd.org
To:        net@FreeBSD.org
Subject:   [Bug 280648] Traffic leak between fibs
Message-ID:  <bug-280648-7501-nVd9g6U9cD@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-280648-7501@https.bugs.freebsd.org/bugzilla/>
References:  <bug-280648-7501@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280648

--- Comment #14 from Tatsuki Makino <tatsuki_makino@hotmail.com> ---
Hmmm.... :)

I don't know how far the fib that can be set on the network interface will =
be
used, but if it cannot be set at least there, it will be difficult to route
packet forwarding (which sysctl net.inet.ip.forwarding is set to 1).

A process launched in an environment where the fib is 0 inherits that the f=
ib
is 0.
If the process switches FIBs in the middle, setfib or setsockopt should be
running somewhere, but in that case, there is a config for that somewhere.

I don't think there is a function to recognize the FIB of the network inter=
face
where the packet arrived and select the FIB of the packet to be sent. [cita=
tion
needed]

...Therefore, it seems that the service for packets passing through the rou=
te
of fib 1 should be set to use fib 1. single-mindedly :)

And since lo0 is also a route that can be passed through various ways, it is
sometimes better to create lo1 or lo2 and separate them. I don't know if it
really is.

I think that's what it means, but I don't think it's on target :)

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-280648-7501-nVd9g6U9cD>