Debian Administration

Posted by nicolas06 (192.84.xx.xx) on Fri 25 May 2007 at 21:41
[ Send Message ]

Hi Steve,

I can ping your IPv6 address using my tunnel broker freenet6.net. I can telnet on port 80, unfortunately I'm unable to see the web site using FF on your IPv6 address.

For tinydns you can add this line into your data file:

6www.debian-administration.org:200104701F00402000000000000000001: 86400

nico

[ Parent | Reply to this comment ]

Posted by Steve (62.30.xx.xx) on Fri 25 May 2007 at 22:46
[ Send Message | View Steve's Scratchpad | View Weblogs ]

That is a shame. I wonder if it is because I didn't restart apache2 after updating the virtual host(s)?

I've done that now, so if that makes a difference it'd be nice.

I'll upload DNS records over the weekend when I get the chance to work on things without interruption; but thanks for giving feedback!

Posted by Steve (62.30.xx.xx) on Sat 26 May 2007 at 23:25
[ Send Message | View Steve's Scratchpad | View Weblogs ]

Note for my own reference - one too many 0s there!

Otherwise seems to be working perfectly now. Thanks again.

Posted by ClausHC (2002:0xx:0xx:0xxx:0xxx:0xxx:xx) on Sat 26 May 2007 at 22:28
[ Send Message ]

Great work Steve,

It's working perfectly here from Denmark (Northern Europe), both ping6, telnet -6 and browser are connecting to the site. This comment should even be submitted through IPv6!

All we need now are the DNS entries.

[ Parent | Reply to this comment ]

Posted by ClausHC (2002:0xx:0xx:0xxx:0xxx:0xxx:xx) on Sat 26 May 2007 at 22:39
[ Send Message ]

And then a small warning...

You might want to redo the IP anonymizing feature. Currently, my full IPv4 address is visible in the IPv6-address. When the IPv6-address starts with 2002, then the next four bytes are the IPv4 address. In my case "50a6:076e" corresponds to "80.166.7.110".

It's not a problem for me, but since you're already hiding parts of the IPv4 address, then you might want to continue doing that.

Posted by Steve (62.30.xx.xx) on Sat 26 May 2007 at 22:55
[ Send Message | View Steve's Scratchpad | View Weblogs ]

D'oh

Fixed now.

#15

Posted by ClausHC (2002:0xx:0xx:0xxx:0xxx:0xxx:xx) on Fri 27 Jul 2007 at 21:48
[ Send Message ]

It looks like the IPv6 address is still visible when you do a preview of a reply to the message. I'm not sure if it's related to previewing a message formatted with textile.

#16

Posted by Steve (62.30.xx.xx) on Fri 27 Jul 2007 at 22:34
[ Send Message | View Steve's Scratchpad | View Weblogs ]

This is a known issue, the same is true for IPv4 addresses IIRC.

At that point your disclosing your own information only to yourself - so there is no leak - it should be fixed. I'll try to get it done over the weekend.

#17

Posted by ClausHC (2002:0xx:0xx:0xxx:0xxx:0xxx:xx) on Sat 28 Jul 2007 at 00:03
[ Send Message ]

Ok, if it's not a leak, then there's no reason for you to fix it, unless you want to avoid paranoid fools like me who complain about that kind of problems :-)

Posted by Steve (62.30.xx.xx) on Sat 26 May 2007 at 22:55
[ Send Message | View Steve's Scratchpad | View Weblogs ]

Thanks for letting me know it was OK - I've uploaded the DNS data now too :)

Posted by irwan (2001:0xx:0xx:0xxx:0xxx:0xxx:xx) on Mon 28 May 2007 at 05:16
[ Send Message ]

Hi,

I'm posting from Malaysia, using IPv6 provided by Freenet6. I just want to let you know that I'm able to ping, telnet and connecting to this site.

Congrats on having an IPv6-enabled website :) I think I'm going to blogging about this soon.

Posted by Steve (62.30.xx.xx) on Mon 28 May 2007 at 14:09
[ Send Message | View Steve's Scratchpad | View Weblogs ]

Great - thanks for the confirmation.

#10

Posted by Anonymous (2001:0xx:0xx:0xxx:0xxx:0xxx:xx) on Mon 28 May 2007 at 21:12

I can see it via native IPv6 ADSL in the UK it seems, though you appear to be using a tunnel through the US rather than native connectivity? I thought Bytemark did native IPv6...

-- Jonathan McDowell

[ Parent | Reply to this comment ]

#11

Posted by Steve (62.30.xx.xx) on Mon 28 May 2007 at 21:31
[ Send Message | View Steve's Scratchpad | View Weblogs ]

They / we do. However I'm testing the tunnel=broker for use elsewhere.

Adding IPv6 for this site was mostly done on a whim, once I'd gotten the hang of it.

#12

Posted by Anonymous (2001:0xx:0xx:0xxx:0xxx:0xxx:xx) on Mon 28 May 2007 at 21:41

So what you've ended up doing is making the site worse for me. If I use IPv4 I get sub 20ms times to you, for IPv6 it ends up as over 200ms thanks to going back and forth across the Atlantic. Can I strongly recommend you either use the native IPv6 connectivity available to you or don't advertise a AAAA at all; using badly chosen tunnels with significantly worse rounds trips than the alternative IPv4 is one of the things that gives IPv6 a bad name.

-- Jonathan McDowell

#13

Posted by Steve (62.30.xx.xx) on Mon 28 May 2007 at 21:43
[ Send Message | View Steve's Scratchpad | View Weblogs ]

I will look to moving to a "local" range shortly.

Initially I was more interested in having it work than having it work optimally, but your comment is valid and sensible.

#14