![dd wrt v24 sp2 vpn small dd wrt v24 sp2 vpn small](https://cdn.neow.in/forum/uploads/monthly_12_2013/post-70004-0-70741900-1387281764.png)
To configure an IPv6 firewall, I’ve installed the following packages to /jffs:įor some reason the ipkg in v24 won’t download from URLs, so I was forced to download them elsewhere and copy the packages in using scp.
#Dd wrt v24 sp2 vpn small windows
However, this leaves IPv6 without a firewall, which is critical especially for Windows which listens to MSRPC (port 135) on IPv6. Machines on the local net now autoconfigure using Stateless Address Autoconfiguration. These steps were sufficient to get DD-WRT routing IPv6 to my local net. Iptables -I INPUT 2 -p ipv6 -i vlan1 -j ACCEPT In the “Firewall” section of Administration/Commands I’ve added this line, which allows incoming packets using the IPv6-over-IPv4 protocol to flow to my tunnel: The same network prefix is used as above on line 9: I’ve entered the following in “Radvd config” on the Administration/Management panel. The second run will simply exit, so there should be correct behavior (one running radvd) regardless of the race. It seems that the radvd enabled by the GUI option starts in a different thread from the startup script, so that it exits immediately upon discovering IPv6 missing in the kernel or an incomplete config. Line 11 guarantees that radvd is run after this configuration is complete.Line 10 enables packet forwarding between IPv6 networks.This could instead be in a /64 subnet of a /48 allocated by HE.
#Dd wrt v24 sp2 vpn small plus
This is based on the /64 prefix allocated by HE for the local net plus the MAC address of br0, encoded in the standard IPv6 way.
![dd wrt v24 sp2 vpn small dd wrt v24 sp2 vpn small](http://www.pcwintech.com/files/screenshots/dd-wrt_24_sp2/thumbs/005_thumb.png)
Line 9 sets the IPv6 address on the local LAN/WLAN bridge.Line 8 sets a default route to the tunnel for IPv6 traffic.Line 7 sets the local IPv6 address on the small tunnel network supplied by HE.Lines 5 and 6 configure the IPv4 tunnel between the appropriate server at HE and the local static IP address.Line 1 loads the critical IPv6 kernel module, followed by the IPv6 filter modules, discussed below.echo 1 > /proc/sys/net/ipv6/conf/all/forwarding.insmod /jffs/lib/modules/2.4.34/ip6t_multiport.o.insmod /jffs/lib/modules/2.4.34/ip6table_filter.o.In the Administration/Commands panel I’ve set the following Startup script (these aren’t my real addresses, but in the pattern of an HE tunnel): I have a static IPv4 address, so I’ve configured DD-WRT to connect a tunnel to Hurricane Electric. Also, I’ve set “Radvd enabled” to “Enable”, even though this doesn’t guarantee that radvd will start at the proper time, but it does create /tmp/nf from the entered config, which is useful. I’ve set “IPv6” to “Enable”, although this doesn’t seem to load the IPv6 module. I see that the IPv6 kernel module and the radvd daemon are in the build, and that the Administration/Management panel provides a few IPv6 options. I’m running this variant so that I’ll have some JFFS space for packages: I’m using Eko’s v24 TNG build 9856 on my Buffalo WHR-HP-G54 (4MB flash). More detail about many of these steps can be found in the wiki and other docs. Since “working for me” can mean anything, I’m posting exactly what I needed to do to get IPv6 working for me. UPDATE: For Eko's v24 TNG build 14583 you will need 2.4.37 ip6tables modules. The following information was provided by forum member crushedhat:įurther info on this subject can be found here and here UPDATE: If you are just trying to get IPv6 working (6to4) on v24 sp1, please view this page: