netdev - Re: routing policy based on u32 classifier

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <BAY103-DAV999F982646869B2E4AABAB26B0@phx.gbl>
Date:	Mon, 10 Dec 2007 16:20:49 +0100
From:	"Marco Berizzi" <pupilla@...mail.com>
To:	"Brian S Julin" <BJulin@...rku.edu>, <netdev@...r.kernel.org>
Subject: Re: routing policy based on u32 classifier

Brian S Julin wrote:

Marco wrote:

> > Hello everybody.
> > Kindly, I would like to know if the is any plan to add this feature
to a > > future kernel release.
> > I know that fwmark is able to do this, but there is the limitation
in
> > source ip address selection.

> Could you explain the limitation?

Indeed.
Here is an example:

    hdsl|  |adsl
    line|  |line
        |  |
      +------+
      |      |
      |SQUID |
      |      |
      +------+
          |
  internal|
    lan   |

The linux default gateway point to the hdsl
router. I want to redirect the squid http
traffic (running on the same host) to the adsl
line. So I create a routing table (adsl table)
and I put a default route to the adsl router.
I mark the http traffic. I insert a rule
based on fwmark which select the 'adsl table'.
So far, so good. But, squid will select the
source ip address from the hdsl network class,
because it is the default gateway.
Then, the local generated packets must be SNATed
with the adsl ip.
Is it clear?

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html