There's been a lot of discussion in the last few weeks and months about IPV6 connectivity, given that we are running out of address space on the Internet whilst using the original IPV4 protocol. For those who are not up to speed on this, there are several interesting threads within the Community including: Aitch's thread here, gcmartin's thread over here, and Flash's thread right here.
Some Community members: TerryPhi, myself, and others have tried running Miredo in other distributions such as debian, Mepis, and Ubuntu, and have found that it works quite well... with some adjustments. This technology is not new. It's been around for a few years now, and in fact is based on Microsoft technology called Teredo tunneling. Given the publicity and run-up to World IPV6 launch day on June 6th, IPV6 connectivity solutions are now in the limelight...
That said, I have decided to "pick up the ball and run with it" for a bit... and this How to thread is not a complete answer but rather, it is a work in progress.... At this time, I have Miredo running in Wary Puppy 5.3 with a score of 7/10. I hope I can bring it up to 10/10 --maybe by adjusting the gateway setting... I have not tested Miredo in any other version or breed of Puppy.
System Requirements
First, recent Puppies such as: Wary/Racy, Lupu, and Slacko should come with the basic system requirements and this includes the IPV6 stack, and the tun driver. However, these modules are disabled by default. To enable them, --> /etc/rc.d/modulesconfig and edit the ADDLIST section of the text to include the line: ADDLIST='ipv6 tun' Note the space between the modules ipv6 and tun and that the single quotation marks are included. Save your changes and re-boot... you should notice that these modules are being loaded on the screen as Puppy is booting.
Second, you need the devx package for your breed of Puppy, and it needs to load on boot-up. This is easily done if you already have a frugal install or the devx package is installed on a separate partition that you can boot... I am not going to explain further here, as there is plenty of information available on how to do this.
Third, you need to download the source-code for Miredo from here. I recommend choosing Merido-1.2.4 tarball because that is what I used... and it works
Compiling the Source Code
In my home directory, I created a folder called: source-code and I extracted the downloaded file to it. You have a lot of choice here, and ./configure will pick it up... You might want to choose /tmp in case you are concerned about certain changes being made to your setup as a result of compiling the source code. Note that if things don't go quite right:
Code: Select all
cd /path/to/source-code
make uninstall
Initial attempts at compiling the source code turned up some errors, but here is what worked for me --finally.
Code: Select all
cd /root/source-code/merido-1.2.4
./configure --libdir=/usr/local/lib/miredo
make check
make
make installcheck
make install
Additional adjustments and configuration
For Teredo tunneling to work, a new route is established called: iproute2 However, despite the checks during compilation, the pathway for this protocol is set incorrectly. So, --> /usr/local/etc/miredo/ and open up the script client-hook (as text) and where it says:
Code: Select all
Linux iproute2 path:
IP="/sbin/ip"
Code: Select all
IP="/bin/ip"
Code: Select all
cd /usr/local/sbin
./miredo -f
Miredo runs as two instances which you can check in Pprocess which is the process manager:-->Menu-->System-->Pprocess. The first instance is as "root", and the second instance is called "nobody". The second child process allows any user the permission needed to run Miredo. If you want to quit Miredo select each instance in Pprocess and choose "quit" or "kill" as there doesn't seem to be a command that will do so in the console. Note that Miredo must have root privileges to start with.
Lastly, rather than deal with using the command line to run Miredo, I threw a Sym-link in the Startup folder, and I found that it's pre-loading fine.
Future Considerations
I did not have to tweak any firewall settings, but that is not to say that Puppy's firewall is fully IPV6 ready. Someone with greater expertise than me should look at this.
A PET you ask... I haven't gotten that far yet... and I might need a bit of help here.... I will see how it goes.
Anyhow, for those who want to give this a go, I believe any feedback you can give could be most valuable to the Puppy Community, even if only to confirm that it works (or doesn't work) in your particular breed.
Cheers,
Monsie