the version you are using is older then the wiki. I think you should think about updating with a newer one.
lv426
chuggo wrote:
Am I missing something here? Just installed dd-wrt.v24_std_generic.bin (13064) on my wrt54g (the router database recommended it) and even though the wiki says radvd is included, it is not.
I installed that version as well (and reinstalled today just to double check). There is no radvd option on the webgui and I still get this message when trying to run radvd by sshing to the router:
So it seams that in your version of dd-wrt there is no IPv6 included, because you don't have ipv6.ko, sit.ko and radvd. The only valid conclusion is that the wiki is wrong in that point. Which bin file did you flash your router with?
So it seams that in your version of dd-wrt there is no IPv6 included, because you don't have ipv6.ko, sit.ko and radvd. The only valid conclusion is that the wiki is wrong in that point. Which bin file did you flash your router with?
lv426
I've tried 14896, 14929, 13064 and a couple others from the official ftps.
Posted: Thu Sep 30, 2010 20:43 Post subject: Re: How to test ipv6 firewall
lv426 wrote:
Hi lazytom,
thank you for posting the modules. I tested the ones I need and they work like charm.
[snip]
So that's it. I think this should be the updated firewall rules for kernel 2.6 and nf_conntrack_ipv6 enabled routers. By the way I use the 6to4 transition system (I thought about sixxs, but I did not want to install new software on my router).
lv426
I'm happy with the rules (modified for my SIXXS setup) you defined and with my (limited) knowledge the use of the nf_conntrack module seems very useful. It makes the job of defining rules quite a bit easier.
Also, oddly enough the K2.6 scripts also work even though this is just a K2.4 NEWD build. Any idea why that might be?
If you're talking about the firewall script, it doesn't depend on the kernel but on ip[6]tables and it's kernel modules. And iptables and it's modules - if available for your kernel - have the same interface (as long as its the same iptables version, etc.).
So, my understanding is that it is supposed to work on both (someone correct me if I'm wrong).
So, my understanding is that it is supposed to work on both (someone correct me if I'm wrong).
Yes you are right. One of the minor differences is that the mtu with kernel 2.4 is 1280 and with kernel 2.6 you can have 1480. But this also depends on your IPv6 provider (e.g. SIXXS wants 1280).
One of the minor differences is that the mtu with kernel 2.4 is 1280 and with kernel 2.6 you can have 1480.
Yeah, I was just surprised that the module still loaded despite it trying to load sit.ko instead (a la K2.6 script) and that having the 1480 MTU didn't seem to affect my kernel 2.4 build either.. IPv6 still worked! Switched to the appropriate 2.4 scripts just to be on the safe side, but I still thought it was peculiar that it worked regardless. And since I am talking about 6to4 in this instance, would 1480 have any benefit over 1280? Or vica versa?