[Jool-list] not NAT64ing packets

[Brian J. Murrell]

On Tue, 2020-01-07 at 12:45 -0600, Alberto Leiva wrote:
> 
> Will try to create a new OpenWRT VM.

I am using OpenWRT on a router.  It would be non-trivial to try to
replace that with an OpenWRT VM.

> - Does your translator have a route towards 1.1.1.1?

Yes.

From a dual-stack node in the same network as the IPv6-only node where
both have the OpenWRT/jool router as their default gateway:

$ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=58 time=30.7 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=58 time=29.4 ms

Or maybe to put it more clearly, if I add an IPv4 address to the node
that failing to reach 64:ff9b::1.1.1.1 and then ping 1.1.1.1, it works,
so the OpenWRT translator node certainly has a path to 1.1.1.1.

> (Can you ping
> both 2001:123:ab:123:16da:e9ff:fe48:f99e and 1.1.1.1 from the
> translator when Jool isn't modprobed?)

Yes.

> - Is Jool printing something in dmesg?

Nothing other than it's:

NAT64 Jool: NAT64 Jool v3.5.6.0 module inserted.

when loading the module.

Does the jool kernel module have any option/ability to print debugging
messages about what it's doing?

Cheers,
b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://mail-lists.nic.mx/pipermail/jool-list/attachments/20200107/ecef3e3e/attachment.bin>