Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to set up a public NAT64 server? #254

Closed
wtongze opened this issue Nov 2, 2017 · 2 comments
Closed

How to set up a public NAT64 server? #254

wtongze opened this issue Nov 2, 2017 · 2 comments

Comments

@wtongze
Copy link

wtongze commented Nov 2, 2017

Hi guys,
I currently have a VPS on Vultr and I want to run a public NAT64 server just like these guys did:

Jool NAT64 with BIND9 DNS64: set your DNS to 2001:67c:27e4:15::64
Jool NAT64 implementation is running in a virtual container on proxmox server.
NAT64 routed prefix: 2001:67c:27e4:1064::/64
Quick ping6 test if up&running: ping6 2001:67c:27e4:1064::5bef:6015

>NAT64/DNS64 public test<

My server info:
Ubuntu 16.04.3
Kernel 4.4.0-87-generic x86_64
IPv4: 45.77.184.213
IPv6: 2001:19f0:ac01:413::1/64

I have successfully installed jool and allowed IPv4 & IPv6 forwarding in sysctl.conf.

However, when I run these commands, I got an error on the ping6 command:
root@vultr:~# /sbin/modprobe jool_siit pool6=2001:19f0:ac01:413::/96

root@vultr:~# ping6 2001:19f0:ac01:413::8.8.8.8

PING 2001:19f0:ac01:413::8.8.8.8(2001:19f0:ac01:413::808:808) 56 data bytes

From 2001:19f0:ac01:413::1 icmp_seq=1 Destination unreachable: Address unreachable

From 2001:19f0:ac01:413::1 icmp_seq=2 Destination unreachable: Address unreachable

From 2001:19f0:ac01:413::1 icmp_seq=3 Destination unreachable: Address unreachable

^C
--- 2001:19f0:ac01:413::8.8.8.8 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4015ms

Can anybody help me out? Do I need to setup something like DHCPv6 server?

Thanks

@ydahhrk
Copy link
Member

ydahhrk commented Nov 2, 2017

No, you don't need a DHCP server.

Jool can currently only translate traffic being forwarded. A ping that's sourced from the NAT64 is completely unaware of Jool.

This will be fixed when Jool 4 is released (the issue is #140). In the meantime, if you want Jool to translate its own machine's traffic, you can always enclose the NAT64 instance behind a virtual interface and translate through there: formal documentation, example. But most likely you don't need this, as a public NAT64 probably only really needs to translate forwarding traffic.

@ydahhrk
Copy link
Member

ydahhrk commented Nov 24, 2017

I'm assuming that's all there is to this issue. Feel free to reopen if you still have a problem.

@ydahhrk ydahhrk closed this as completed Nov 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants