Manual entry to bib table looks like the right approach. I tried it today. 100.127.255.253 is the interface on the IPv4 side of my jool machine, and we are successfully doing NAT64 of a /96 block towards the IPv4 side...
So as a test I am trying to see if we can get clients who connect to 100.127:255:253#80 to get the HTTP server at 2607:f8b0:4002:c02::8a#80 (which is google, but again it's just a test) So the command appears to be: jool bib add --tcp 2607:f8b0:4002:c02::8a#80 100.127.255.253#80 And the error response is: Error: The kernel module returned error 22: The transport address '100.127.255.253#80' does not belong to pool4. Please add it there first. So I tried: jool pool4 add --tcp 100.127.255.253 80 jool bib add --tcp 2607:f8b0:4002:c02::8a#80 100.127.255.253#80 This works for outbound connections, but it broke the NAT64 inbound connections. Does jool support pool6 IPv6-->IPv4 and manual bib IPv4-->IPv6 at the same time? From: Alberto Leiva <[email protected]> Woops, I meant sudo jool bib add cafe::1#80 203.0.113.1#80 On Wed, Feb 17, 2021 at 12:29 PM Alberto Leiva <[email protected]<mailto:[email protected]>> wrote: Try sudo jool bib add <Address of IPv6 server>#<Port of IPv6 server> <IPv4 address of Jool>#<Port of Jool mask> sudo jool bib add cafe::1#80 203.0.113.1:80<https://urldefense.com/v3/__http:/203.0.113.1:80__;!!LG9nLpOADg!B0yOLRqgb1DOljIz2V9bEd4Mmh0WJBBI_7SohIfZjT5ahPhvAWSGwHfF995pmBnNuw$>
_______________________________________________ Jool-list mailing list [email protected] https://mail-lists.nic.mx/listas/listinfo/jool-list
