[Jool-list] Trying to route local traffic via SIIT instance

[Alberto Leiva]

> (I still haven't been able to get Jool in netfilter mode to work so that
> I can split traffic according to IPv6 origin between instances.
> So I use the iptables method for now)

Solution attached.
Note that I cheated and used iptables for a simple nat, but you should
be able to easily replace it with an nftables NAT if you want.

Still working on the python script.

On Thu, Jul 2, 2020 at 1:45 PM Michael Richardson <mcr+ietf at sandelman.ca> wrote:
>
>
> Alberto Leiva <ydahhrk at gmail.com> wrote:
>     >> I think that this (Jool in private network namespace) just needs a slightly
>     >> better documented set of examples.   Maybe some python that knows how to do all the
>     >> right system calls directly.
>
>     > Ok, I can give it a shot. (Just let me finish the 4.1.1 release
>     > first.) Which would you prefer: SIIT or NAT64?
>
> My usual interest is in NAT64.
>
>     >> (I still haven't been able to get Jool in netfilter mode to work so that
>     >> I can split traffic according to IPv6 origin between instances.
>     >> So I use the iptables method for now)
>
>     > Same question: SIIT or NAT64?
>
> NAT64.
> I find I'm always confused about the different SIIT uses, we need new names :-)
>
> I care most about DC:SIIT, where I want to expose a single IPv4 address
> for v4-only clients, so that they can reach IPv6 hosted server(s).
> I think we can do this, but I admit that I haven't tried.
>
> --
> Michael Richardson <mcr+IETF at sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: netfilter-split.tar.xz
Type: application/x-xz
Size: 1856 bytes
Desc: not available
URL: <http://mail-lists.nic.mx/pipermail/jool-list/attachments/20200706/4fd520f3/attachment.bin>