Skip to main content

Adventures with IPv6

I spent the past couple of days, tinkering with an old Linux box, trying to set up a fully functional IPv6 network, complete with an IPv6 webserver, nameserver, mailserver, network router and firewall.
The job is partly done.
The nameserver, webserver, network router and firewall are working quite well.
The website can be accessed here you have IPv6 connectivity). It runs on a rickety PIII running Ubuntu 8.04.1 and connected to my friend's home ADSL connection. Power failure are quite a common affair in our region (in almost the whole country, to be honest!) and there is no power backup for the server, so if it appears to be down, kindly check back sometime later.
The nameserver manages the DNS records for the subdomain
I hope to get the mailserver up and running quite soon.
I'll also come up with a detailed documentation on how I got the things running, sometime in the near future.
Anyway for this half-crappy IPv6 implementation, I got this from Hurrican Electric Internet Services:

(It is a certificate, but removed the JScript, as it was causing the page to load slowly)
It started with "newbie" level, and is improving!
More on IPv6 soon... may be in a day or two.


Popular posts from this blog

Force an application to use VPN, using iptables in Linux

Enforcing an application, for example a torrent client like Transmission, to always use the VPN interface or any particular network interface for that matter, is trivially simple using iptables on Debian, Ubuntu or any other GNU/Linux distro.
Personally, I am running Debian Sid on the Raspberry Pi. Occasionally I use it for downloading files ( legal stuff, seriously, believe me :D  ) using Transmission Bittorrent client over a VPN connection. Sometimes it happens that the VPN connection fails and doesn't reconnect for whatever reason and Transmission continues pulling stuff directly over my internet connection, which I would like to avoid. Fortunately it is very straightforward to enforce rules based on application owner UID. Transmission runs under the owner debian-transmission in Debian (use htop to check this) and the following two lines of iptables ensures that any process with owner having UID, debian-transmission, will not use any other network interface apart from the Open…

Some more fun with SSH port forwarding and socks proxy

Few days ago I made the following post:

Prologue: Our Institute has several nice Dual Core Machines deployed for the students. Unfortunately the machines are behind a NAT with no port forwarded for external SSH access. Student's hostel is a bit far off from the computational centre. As such if someone felt the need of accessing the machines during non-office hours, it was a wee bit difficult. The sysadmin would not have agreed to forward any ports. Something had to be done....

SSH has a very useful feature - Remote and Local Port Forwarding. We have an old rickety PIII running Ubuntu 8.04.1 in the Hostel, it is connected to the net and is accessible via SSH from the internet. Using a tiny little shell script running on one of the machines in the Institute, I managed to make the old PIII an intermediate gateway for gaining SSH access to the Institute's machines from anywhere in the internet. The script is of few lines, but nevertheless powerful enough to serve our purpose.


Rendering LaTeX in Blogger.

Rendering LaTeX in Blogger is pretty easy thanks to the JavaScript LaTeX equation render engine from
To enable LaTeX rendering go to the Blogger Dashboard --> Layout --> Edit HTML . Then add the line
<script> type="text/javascript" src=""></script>
<script type="text/javascript" src=""></script>
just before <body/>. Half the job is now done.
Then, for example to render:
\int_{0}^{\pi}\frac{x^{4}\left(1-x\right)^{4}}{1+x^{2}}dx =\frac{22}{7}-\pi
Use the code:
<pre lang="eq.latex">
The LaTeX code will now be displayed as:
Ofcourse Javascript needs to be enabled in the Browser for the renderer to work.