Forum - FreeBSD as IPv6 router using aiccu :: SixXS

FreeBSD as IPv6 router using aiccu

Shadow Hawkins on Friday, 18 April 2008 08:51:21

I've been pulling my hair out for the last few days trying to find the information I need to get my newly acquired subnet working on my home network. Not that I want hand holding, but that this point I'll take it, I'm hoping someone can help me out here. Perhaps point me in the right direction, or at least tell me 'hey, that's not going to work you need to do this instead'. I'm using a WRT54G v2 for my home NAT, which is running dd-wrt v23 std. The v2 doesn't have enough nvram to install the tunnel there, so that's out. I have a FreeBSD box that I use for DHCP and DNS which is currently running 6.0 stable generic kernel (this machine has two NICs, but I'm only using one at the moment). There is also a WRT54GS v5 running dd-wrt v24 RC6.2 in client bridge mode, but that could be phased out if needed. I don't have a static IP, though it doesn't change much, so using FreeBSD's gif interface (to my knowlage) isn't going to work, as the FreeBSD box would have to be connected to the outside if I'm right? I have had aiccu running without trouble on a OS X 10.5 machine, and now have it running on the FreeBSD machine. I can use all available IPv6 services from either machine when aiccu is running. What I want to do is make the FreeBSD machine act as the IPv6 router for my network and use the aiccu configured tunnel. None of the instructions I can find even touch on this, let alone make since in this context. They want me to use gif, and then even assuming that everything else was okay rtadvd doesn't seem to do anything. Now I know that I haven't really provided any info about the configuration files, routing, ect, but I feel that I have most likely done a lot of things wrong, and would prefer to revert my config files back to their state before I started all of this and just do it right the first time rather than fixing it over and over until it works then not really understand HOW it works. If someone you get me going the right way, or give me other options. I 'could' use the FreeBSD machine as the NAT and just use the WRT54G as a switch/AP but I have NO experience in setting up NAT. Not to mention that the WRT54G is acting as outbound access restrictions for a teenager that doesn't know when enough is enough. so... please... help?

FreeBSD as IPv6 router using aiccu

Jeroen Massar SixXS Staff

on Friday, 18 April 2008 11:00:17

See FAQ: How do I give connectivity to other hosts on my subnet? KAME based: OpenBSD / FreeBSD / NetBSD - Router Just run aiccu on the FreeBSD host, that gives you a tunnel and thus connectivity to the outside world. Then as per the above mentioned FAQ configure radvd and presto the rest of your network has IPv6. IPv4 and IPv6 routing can go over different places, they are independent. With the above the WRT will take of IPv4 and perform NAT on it, while the FreeBSD box will route IPv6, sending it through a tunnel to the rest of the world. AYIYA is probably the tunnel type you want to use for this situation.

FreeBSD as IPv6 router using aiccu

Shadow Hawkins on Friday, 18 April 2008 16:52:05

He might also need to manually assign a global IPv6 address (from the subnet) to the local (LAN) interface. Or does that happen automatically on BSD ? (on linux it doesn't)

FreeBSD as IPv6 router using aiccu

Shadow Hawkins on Friday, 18 April 2008 16:29:09

One thing to watch out for is whether you have an IPv6 firewall active. There may be rules set that are blocking the traffic. A simple test is to try to temporarily disable it. If it makes a difference, then reactive it and adjust the rules as necessary. Additionally checking the FAQ might handy and looking at some of the instructions in the Wiki: https://noc.sixxs.net/wiki/Aiccu . Feel free to update the Wiki if you see any issues the instructions.

FreeBSD as IPv6 router using aiccu

Shadow Hawkins on Saturday, 19 April 2008 03:53:22

I know I know, replying to my own post, but this issue should be considered resolved. I really had made a mess of things. So I replaced all my relevant config files with the ones I had before starting (backup, and backup your backups) then did exactly as was said, and somehow, even though I was ssh`ing in from work and taking calls in between working on it, I managed to get everything more or less working. I didn't know I had until I got home and found that my Win XP and OS X 10.5 machines had gotten addresses which are working. Now it seems I will have to assign the FreeBSD box an address manually, which makes sense as it can't run as a router and a host (self config routers would be cool, but that's something else altogether) but it seems that all the machines are talking to the router via the routers self assigned local address. Now I'm not sure if the machines that talk through the WRT54GS in bridge mode will work, but my TiVo doesn't support v6 and my PS3 doesn't need it, and could talk wireless direct to the AP if needed. So that will be another thread if needed. I will still need to setup a firewall on the router box as that is actually running wide open at the moment, but the only services that are open are ssh, plus webmin. And if those were going to be compromised they already would have been because they're port forwarded to over v4 now and have been for years. Thanks all of you... have a lot more reading to do, but it's working in 'well enough' mode for now. Have Monday and Tuesday off to play with it more, but for now it's all good. Thanks again for the quick responce, and for giving me a RTFM in a polite way. :)

Please note Posting is only allowed when you are logged in.