hi guys,
19342 installed, ipv6 on WAN interface seems to work, but i dont want to use it without ip6tables.. and here is the problem.. it seems like some modules ipv6/netfilter.. are missing in kernel. have someone solved this? wiki says, i should try compile own kernel modules.. will this source work for wr1043nd? http://svn.dd-wrt.com/browser/src/linux/universal/linux-3.3/net/ipv6/netfilter (probably these modules are missing) i assume brcm and atheros versions (mips/mipsel) of ip6tables are different.. is there someone with compiled these modules for atheros mips?
anybody interested? world ipv6 day 2012 is behind us.. my ISP provides me a dualstack, and can have own subnet too..
thx for response _________________ TP-Link TL-WR1043ND (v24 preSP2 build 19519)
Hi, i've been using 18740 so far (hw v1.0) but these days the wifi keep turning off randomly... so how is 19327? Is there something more stable?
Thank you all
I have next configuration: wr1043nd + DD-WRT v24-sp2 (12/20/11) std - build 18024 + L2TP and a problem that when connection is dropped (once in 3 – 4 days) router can’t restore it.
In log it looks like permanent restart of xl2tpd and pppd – the following records are repeated «xl2tpd : L2TP daemon successfully stopped» (if i click Connect), «pppd 2.4.4 started by root, uid 0» (if router attempts to restore connection by himself).
Find out that restart the udhcpc «kill -USR1 $(head -n 1 /var/run/udhcpc.pid)» usually helps to get WAN IP (but sometimes even with WAN IP there is not internet connection), in other cases it has no effect.
Do anybody heave such a problem?
Should I try another version of dd-wrt?
I'm running the eko BrainSlayer DD-WRT v24-sp2 (06/08/12) std r19342 build and have the following two issues:
WiFi drops all the time when using DNSmasq for DHCP, disabling this in Setup > Basic Setup fixes the problem.
Port forwardings cannot be accessed using the external IPv4 address from an internal host, although they seem to be applied right in the iptables. Accessing them from an external host (i.e. not in the LAN) works fine. Adding the following line to a firewall script fixes the problem: