[6bone] IPv6 only Website.

Gav old_mc_donald@hotmail.com
Wed, 14 May 2003 22:55:42 +0800


----- Original Message ----- 
From: "Daniel Austin"



| Hi Gav,
|
| We have our PHP mirror running successfully on both v4 and v6 using Apache
2.0.45 at http://uk.php.net/

Almost, I couldnt get on it when I tried. :(

|
| Apache2 requires --enable-ipv6 on the configure line,

Until I get a spare computer with a *nix flavour put on I am using Windows
XP , but I found the equivant command and the service is installed, but
again comes up with resolver errors to do with my 2002: address (see below)

and then the configuration is the same as IPv4 except that v6 addresses must
| be surrounded by square brackets.
|
| for example (from our apache2 config):
|
| --cut--
| Listen [3ffe:4005:fefe::80:4]:80
| NameVirtualHost [3ffe:4005:fefe::80:4]:80
| <VirtualHost [3ffe:4005:fefe::80:4]:80>
|
<snip>

| With Thanks,
|
| Daniel Austin,
| Managing Director,
| Kewlio.net Limited.
| <daniel@kewlio.net>
|

Thanks for the reply, Ok so I now need to give you a bit more info as the
above did not work for me, neither did Marco's (couger?) thanks for your
reply also.

At the moment I am using the wildcard catch all for my addresses as I have 4
sites running in VirtualHost containers and I have a dynamic IP, but correct
me if I am wrong, I keep the same IPv6 address I have been given don't I ?
Otherwise I need a v6 capable dynamic updater. (Or wait until I get a
permanent v4 allocation in November).

So I have

Listen 80 (Apache docs say this will catch v6 addresses also, then mentions
using Listen [::]:80 which didn't work either)
NameVirtualHost *
<VitrualHost *>
..
..
..
</VirtualHost>

I have tried adding ip address based lines for Listen, NameVitrualHost and
VirtualHost , leaving the others available on *. The Server does not start.

The v6 address I am trying to use is 2002:9089:e04a::9089:e04a.

Now , if I miss out the Listen directive and leave the rest in, the server
will start, but the site does not work, opens the default site instead.
The logs are telling me "No host data of that type was found: Cannot resolve
host name [0000:0000:9089:e04a] --- ignoring!"

I don't think the prognosis is a good one

My setup is a bit of a mess at the minute, but I don't know any better how
to set up my v6 side of things, you will notice a bridge etc :-



Ethernet adapter Local Area Connection 5:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 144.137.224.74
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        IP Address. . . . . . . . . . . . : fe80::4645:53ff:fe54:7777%4
        Default Gateway . . . . . . . . . : 144.137.224.74

Ethernet adapter Network Bridge (Network Bridge):

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 192.168.0.1
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        IP Address. . . . . . . . . . . . :
2002:c0a8:1:5:3da1:f127:4d8c:bba3
        IP Address. . . . . . . . . . . . :
2002:c0a8:1:5:d02a:edf6:49be:edba
        IP Address. . . . . . . . . . . . : 2002:c0a8:1:5:40:d0ff:fe2a:af71
        IP Address. . . . . . . . . . . . : fe80::40:d0ff:fe2a:af71%5
        Default Gateway . . . . . . . . . : 192.168.0.1

Tunnel adapter 6to4 Tunnelling Pseudo-Interface:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 2002:9089:e04a::9089:e04a
        Default Gateway . . . . . . . . . : 2002:c058:6301::
                                            2002:836b:213c:1:e0:8f08:f020:8

Tunnel adapter Automatic Tunnelling Pseudo-Interface:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : fe80::5efe:144.137.224.74%2
        Default Gateway . . . . . . . . . :

Tunnel adapter Automatic Tunnelling Pseudo-Interface:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : fe80::5efe:192.168.0.1%2
        Default Gateway . . . . . . . . . :


Interface 5: Ethernet: Network Bridge (Network Bridge)
{1B48439E-824B-4AFE-B2B8-D8149CF2AEA2}
  zones: link 5 site 2
  uses Neighbor Discovery
  uses Router Discovery
  sends Router Advertisements
  forwards packets
  link-layer address: 02-40-d0-2a-af-71
    preferred global 2002:c0a8:1:5:3da1:f127:4d8c:bba3, life
47h53m52s/23m52s (a
nonymous)
    deprecated global 2002:c0a8:1:5:d02a:edf6:49be:edba, life 47h53m52s/0s
(anon
ymous)
    preferred global 2002:c0a8:1:5:40:d0ff:fe2a:af71, life 47h53m52s/23m52s
(pub
lic)
    preferred link-local fe80::40:d0ff:fe2a:af71, life infinite
    multicast interface-local ff01::1, 1 refs, not reportable
    multicast link-local ff02::1, 1 refs, not reportable
    multicast link-local ff02::1:ff2a:af71, 2 refs, last reporter
    multicast interface-local ff01::2, 1 refs, not reportable
    multicast link-local ff02::2, 1 refs, last reporter
    multicast site-local ff05::2, 1 refs, last reporter
    multicast link-local ff02::1:ffbe:edba, 1 refs, last reporter
    multicast link-local ff02::1:ff00:0, 1 refs, last reporter
    anycast global 2002:c0a8:1:5::
    multicast link-local ff02::1:ff8c:bba3, 1 refs, last reporter
  link MTU 1500 (true link MTU 1500)
  current hop limit 128
  reachable time 22000ms (base 30000ms)
  retransmission interval 1000ms
  DAD transmits 1
Interface 4: Ethernet: Local Area Connection 5
{DD381E0E-7F09-45B7-8539-C531BEAD0731}
  uses Neighbor Discovery
  uses Router Discovery
  link-layer address: 44-45-53-54-77-77
    preferred link-local fe80::4645:53ff:fe54:7777, life infinite
    multicast interface-local ff01::1, 1 refs, not reportable
    multicast link-local ff02::1, 1 refs, not reportable
    multicast link-local ff02::1:ff54:7777, 1 refs, last reporter
  link MTU 1454 (true link MTU 1454)
  current hop limit 128
  reachable time 28500ms (base 30000ms)
  retransmission interval 1000ms
  DAD transmits 1
Interface 3: 6to4 Tunneling Pseudo-Interface
{A995346E-9F3E-2EDB-47D1-9CC7BA01CD73}
  does not use Neighbor Discovery
  does not use Router Discovery
  forwards packets
  routing preference 1
    preferred global 2002:9089:e04a::9089:e04a, life infinite
  link MTU 1280 (true link MTU 65515)
  current hop limit 128
  reachable time 30000ms (base 30000ms)
  retransmission interval 1000ms
  DAD transmits 0
Interface 2: Automatic Tunneling Pseudo-Interface
{48FCE3FC-EC30-E50E-F1A7-71172AEEE3AE}
  does not use Neighbor Discovery
  does not use Router Discovery
  forwards packets
  routing preference 1
  EUI-64 embedded IPv4 address: 0.0.0.0
  router link-layer address: 0.0.0.0
    preferred link-local fe80::5efe:144.137.224.74, life infinite
    preferred link-local fe80::5efe:192.168.0.1, life infinite
  link MTU 1280 (true link MTU 65515)
  current hop limit 128
  reachable time 19000ms (base 30000ms)
  retransmission interval 1000ms
  DAD transmits 0
Interface 1: Loopback Pseudo-Interface
{6BD113CC-5EC2-7638-B953-0B889DA72014}
  does not use Neighbor Discovery
  does not use Router Discovery
  link-layer address:
    preferred link-local ::1, life infinite
    preferred link-local fe80::1, life infinite
  link MTU 1500 (true link MTU 4294967295)
  current hop limit 128
  reachable time 31000ms (base 30000ms)
  retransmission interval 1000ms
  DAD transmits 0

Can this be improved, I am trying to use the correct v6 address ?

Thanks for your help.

Gav...



---
Checked for Viruses (Viri) , Gav...
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.478 / Virus Database: 275 - Release Date: 6/05/2003