If you want to use your routed /48 on the NIC instead, you can just carve a /64 out of it. Now you put an address from your routed /64 or a /64 subnet of your routed /48 on the inside interface of the router:įor instance, if HE assigns you a routed /64 of something like " 2001:db8:1234:56::/64", you might put the address " 2001:db8:1234:56::1/64" on your network interface. You just have to figure out what's stopping it from working. If not, well, make sure 6in4 can pass your firewall, etc, etc. Now you can ping the other side of the tunnel to see if the 6in4 tunnel is working. They look very similar but are different by one character. Let the NAT device NAT it for you.Īlso, don't mix up the routed /64 and the Server and Client IPv6 addresses. If your IPv4 address is 192.168.1.1, use that if you're behind a NAT device not the public IPv4 address. Also, if this router is behind a NAT, and doesn't have a public IPv4 address, you must use the real IP address that's on the interface for the client IPv4 address. You may need to do a "modprobe sit" first if it gives you trouble with the ip tunnel command. Ip tunnel add he-ipv6 mode sit remote local ttl 255 You first need to set up the tunnel itself. I'm not super familiar with how the DD-WRT setup and config files work, but Linux is Linux, and if it has the "iproute2" tools the process of setting up an HE tunnel will be the same as other Linuxes. Iptables and ip6tables, aka "netfilter" is the firewall, which you really need also for security, but you can set things up and get them working without setting up a iptables policy. You need the kernel module to simply have IPv6, because that's what implements the IPv6 stack in the OS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |