On Wed, 3 Aug 2005, Sargon wrote:
Sveasoft's Talisman does.
"Yes, support is in Talisman/basic. Current support is CLI-based up to layer 3 and includes radvd. Web interface additions to configure IPv6 options are planned.
To enable support, do the following: nvram set ipv6_enable=1 nvram commit reboot"
Correct. You can create an in-memory startup script to do tunnel configuration, as well, with something like this: (make script as text file in /tmp; for example, I'll use /tmp/mystartup) $ nvram set rc_startup="$(cat /tmp/mystartup)" $ nvram commit As an in-use example, the contents of one such script I use is as follows. Note the explicit deletes, because the rc_startup can be run in a "warm boot" reset mode, where the interfaces are already up. I didn't bother masking any data from this list post, since anyone could look up my addresses via my Received: header, DNS, and traceroutes. <g> (Though I don't use 6to4 locally, I do have an outbound 6to4 interface -- something I recommend for all tunnelling users, so that 6to4 clients can get packets originating from your network more reliably/quickly.) ===== #!/bin/sh # tunnel to tunnelbroker.net with /64 ip tunnel del sit1 ip tunnel add sit1 mode sit ttl 250 remote 64.71.128.82 local 66.156.66.24 ip link set dev sit1 up ip -6 addr add 2001:470:1F00:FFFF::1E5/127 dev sit1 ip -6 route add 2001:470:1F00:FFFF::1E4/127 dev sit1 metric 1 # assign local /64 address to router ip -6 addr del 2001:470:1F00:342::1/64 dev br0 ip -6 addr add 2001:470:1F00:342::1/64 dev br0 # 6to4 outbound-only tunnel ip tunnel del tun6to4 ip tunnel add tun6to4 mode sit ttl 250 remote any local 66.156.66.24 ip link set dev tun6to4 up ip -6 addr add 2002:429c:4218::1/16 dev tun6to4 # default v6 route through tunnelbroker.net tunnel ip -6 route del default via 2001:470:1F00:FFFF::1E4 dev sit1 ip -6 route add default via 2001:470:1F00:FFFF::1E4 dev sit1 metric 1 -- -- Todd Vierling <tv@duh.org> <tv@pobox.com> <todd@vierling.name>