Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's pretty straightforward. On the router (assuming a recent Debian-based distro):

  mkdir /etc/jool
  echo '{"instance":"nat64-minimal","framework":"netfilter","global":{"pool6":"64:ff9b::/96"}}' > /etc/jool/jool.conf
  apt install jool-dkms jool-tools
On a box behind the NAT:

  curl --resolve one.one.one.one:443:64:ff9b::1.1.1.1 https://one.one.one.one
If you want DNS64, 1.1.1.1 and 8.8.8.8 offer 2606:4700:4700::64 and 2001:4860:4860::6464 respectively or you can configure unbound pretty easily.


  # apt search jool
  Sorting... Done
  Full Text Search... Done
  jool-dkms/stable 4.1.9-1 all
    kernel-based SIIT and NAT64 (IP/ICMP translation)

  jool-tools/stable 4.1.9-1 amd64
    userspace utilities for the Jool kernel modules
I suppose it is packaged, but dkms is still very much in the "why is does my router need a compiler installed" vibe.


    > one.one.one.one:443:64:ff9b::1.1.1.1
Is this a typo or a weird curl-specific address format I've never heard of?


It's the argument to --resolve, not the desired URL.

    --resolve <[+]host:port:addr[,addr]...>
              Provide a custom address for a specific host and port pair. Using this, you can make the curl requests(s)
              use a specified address and prevent the otherwise normally resolved address to be  used.  Consider  it  a
              sort  of  /etc/hosts  alternative provided on the command line.


I looked right past `--resolve`, so yes that now makes sense.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: