Comments for Thorsten on (mostly) Tech

Comment on IPv6 at home, Part 1: Overview, Teredo by John Fleuren

John Fleuren — Thu, 26 Nov 2009 10:24:19 +0000

If anyone is interested. I did get it to work and its much the same as for the Vista advice here. I just interpreted some things wrong.

Three things I did were:

1)add address 2002:A01:104::/48 to TCP/IPV6 item of wireless network adapter via the connection properties dialog. (note this is the Wireless Adapter LAN address 10.1.1.4)

2)Add IPV6 route to teredo with
netsh interface ipv6 add route ::/0 “Teredo Tunneling Pseudo-Interface”

3)Add IPV6 route to Wireless Network Connection with
netsh interface ipv6 add route ::/0 “Wireless Network Connection”

It works but its shaky.

For 1) I originally used the IPV6 equivalent of my WAN IP address. I thought it didn’t matter what that address was. But it didn’t work.

For 2) and 3) the naming convention for local adapters is changed from vista to be more descriptive. I don’t have Vista, so it took a long time to never find this Local Area Connection* xx. (Silly me)

Finally still looking for that ipv6 renew command that has dissapeared from windows 7. I am sure there must be a simple replacement for it.

Good luck everyone with IPV6 on windows 7.

Comment on IPv6 at home, Part 1: Overview, Teredo by John Fleuren

John Fleuren — Tue, 24 Nov 2009 12:08:08 +0000

Hi,

Is there any chance to update the teredo connectivity section to get it to work under windows 7.

There are so many obstacles that I just can’t get it to work. Mostly due to minor changes in the way windows 7 works. Even simple things like how to renew the ipv6 teredo connection I have not been able to do.

To the casual networker this is very hard to sift through and find answers

Comment on ipv6 at home, part 3: gogo6 (Hexago) tunnels, freenet6 by Joel ellegood

Joel ellegood — Sat, 31 Oct 2009 12:12:27 +0000

hey dude.. You always have great posts on IPv6, which is the IN think in networking today. Your post is really helpful for a layman like me to build my own network.

You were mentioning about connecting to IPv6 without a router and using the website go6.net. Even the instructions given by you are so clear it surely would be of great help to me… Joel

Comment on 1and1 .htaccess failures by Rolledtootight

Rolledtootight — Fri, 30 Oct 2009 11:15:52 +0000

Interesting. I am having issues with 1and1 and a typical .htaccess configuration also. Time to move to a co-located server I think.

Comment on ipv6 at home, part 3: gogo6 (Hexago) tunnels, freenet6 by oes tsetnoc

oes tsetnoc — Tue, 29 Sep 2009 07:09:03 +0000

Hi, Just like to tell you that this piece of info is one quick to the point, no nonsense, Thank you for the effort. Keep up the good work.

Comment on 1and1 .htaccess failures by Jeremy

Jeremy — Sat, 22 Aug 2009 21:18:56 +0000

wow… try to enter HTML in a comment and it messes up of course.. just remove the *’s in front of the brackets

*Directory /DIRECTORY/TO/SECURE/*
AllowOverride AuthConfig
AuthType Basic
AuthName “Password Required for this section of the Desert Penguin!”
AuthUserFile /DIRECTORY/pass.conf
Require user jeremy
*/Directory*

Comment on 1and1 .htaccess failures by Jeremy

Jeremy — Sat, 22 Aug 2009 21:16:11 +0000

Robert-

Sure, see below.. All you need to do it add this to the httpd.conf file:

”
AllowOverride AuthConfig
AuthType Basic
AuthName “Password Required for this section of the Web Site!”
AuthUserFile /DIRECTORY/pass.conf
Require user jeremy
”

Then the “pass.conf” password file is done by:

“htpasswd -c /DIRECTORY/password.conf USERNAME”

that’s to create it.. just man the htpasswd to use other things like MD5 hashing.. good luck!

Comment on 1and1 .htaccess failures by Robert Munson

Robert Munson — Sat, 22 Aug 2009 14:04:41 +0000

Could I please get the sample config file

Comment on ipv6 at home, Part 2: Tunnel brokers, Windows “AYIYA” tunnel by Christ Schlacta

Christ Schlacta — Fri, 14 Aug 2009 18:45:42 +0000

the setup of an ipv6 tunnel through sixxs is much simpler on any linux computer, be it router or otherwise. you can even have a static tunnel through a router to an endpoint inside your site if you have a static IP address, and it only requires a few commands.

0) (Only sometimes) add a repo to your package manager for aiccu
1) install aiccu (apt-get install aiccu, pacman -S aiccu, etc.)
3) configure aiccu vim /etc/aiccu.conf
4) start aiccu /etc/init.d/aiccu start

and if you’re on a machine behind a firewall, you simply configure your firewall to forward proto41 to wherever your endpoint is.

Comment on 1and1 .htaccess failures by Jeremy

Jeremy — Fri, 14 Aug 2009 17:34:53 +0000

So, it’s actually better security practice to stay away from using .htaccess files. In fact, making an ACL of sorts in the httpd.conf file referring to a hashed password file not in the httpd root is best…

Let me know if you want a sample config..