Good questions.

1. I did work for telenet some time, but i wasn’t involved in any of their network roadmap, i did work on their e-services desk, which provided the telenet website, zita, garagetv, 9lives and some streaming events.
Now Since they have DOCSIS 3 (protocol they use on the cable modems) i pretty sure they will provide IPV6 in 2011, cause they will have to, estimates state that IPV4 adresses will be gone, so they all will be allocated, around february 2011, the estimates are also that providers have around 6 months of spare ip’s. so the day Telenet get’s the message of RIPE (the europe ip organ) that they can’t get any ipv4 adresses, they have 2 choices, buy on the secondary market or implement ipv6.
long term they will need to install ipv6, so i guess there is no way avoiding it. (and i’m not even willing to give the option of NAT their network, that’s pure evil)

I’ve been youtubing a lot of ipv6 related video’s this week, geek conferences, google techtalks, etc
and they give 2 main options
-Dual stack: so ipv4 and ipv6, to have an timespan to let content providers migrate to ipv6
-NAT64: end user only get’s ipv6 address, and their ipv4 connections will be gated through a gateway, not that secure, but it will work.
i’ll update my post later and add a interesting comment about my post, i’ve learned a lot of a certain video

2. just add “|grep -v inet6″ just after the “|grep inet”
dirty, but it works
NOTE: if your internet interface is not eth0, change it in the script

3. the trick should work on desktops (linux in this example)
BUT you need an external internet adress, so not an BOGON ip for example 192.168.1.2, this is an local adress, that can’t be tunneled this way.
I recommend to use a tunnelbrocker like sixxs.net for a hopping notebook, i have a fix for the aiccu for mac in my previous post.

I hope i answered your questions correctly

1. For some time, there was an entry in Telenet FAQ related to IPv6 deployment. It was around the corner, as it sounded. Oddly though, this entry is now unavailable. Do you know more about their plans in that respect?

2. The identification of the IPv4 address fails in Fedora 12 because a link-local IPv6 address FE80::/10 is assigned by default. This IPv6 address survives the “grep inet”. A slight change might help, though I am afraid it could be platform-dependent:

ipv4=$(ifconfig eth0 | grep inet | grep “adr:” | cut -d : -f 2 | cut -d \ -f 1)

3. Is it a trick you applied on desktops only, or on laptops as well? Mine is used to hop between Wi-Fi hotspots, at home (Telenet), at the office (not Telenet) and on the road. I am wondering whether this trick would not prevent me from connecting away from Telenet.

Bedankt voor jouw antwoorden,
LS

I have an old k8000 collecting dust.
The reason was that I could not get it to work since not knowing C, and drivers were not working so good in Ubuntu, and I had no Windows machines anymore, only Ubuntu and OSX.

I fiddled a bit with Python, and if there will be a Python library for k8000, I might actually dig it out again.