I am trying to setup my RedHat 9 with 2.4.20-28.9 kernel to connect to IPv6 domains. The
ipv6 module is loaded at boot but I can't ping6 any IPv6 domains. My D-Link DFE-530TX+ NIC
is connected to a cable modem. Not knowing what might be helpful I've included everything
I could find. I will provide any additional information that you need to provide suggestions.

/etc/sysconfig/network
NETWORKING=yes
HOSTNAME=localhost.localdomain
NETWORKING_IPV6=yes


/etc/sysconfig/networking/devices/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes


ping cox.net
------------
PING cox.net (68.1.17.9) 56(84) bytes of data.
64 bytes from www.cox.net (68.1.17.9): icmp_seq=1 ttl=247 time=42.7 ms
64 bytes from www.cox.net (68.1.17.9): icmp_seq=2 ttl=247 time=47.4 ms
64 bytes from www.cox.net (68.1.17.9): icmp_seq=3 ttl=247 time=41.1 ms

--- cox.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2020ms
rtt min/avg/max/mdev = 41.130/43.755/47.420/2.681 ms


ifconfig -a
-----------
eth0 Link encap:Ethernet HWaddr 00:0D:88:1D:48:98
inet addr:68.228.166.2 Bcast:68.228.167.255 Mask:255.255.248.0
inet6 addr: fe80::20d:88ff:fe1d:4898/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15282 errors:4 dropped:0 overruns:0 frame:0
TX packets:637 errors:0 dropped:0 overruns:0 carrier:0
collisions:27 txqueuelen:100
RX bytes:1361030 (1.2 Mb) TX bytes:71290 (69.6 Kb)
Interrupt:9 Base address:0x3000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:700 (700.0 b) TX bytes:700 (700.0 b)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


netstat -nr
-----------
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
68.228.160.0 0.0.0.0 255.255.248.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 68.228.160.1 0.0.0.0 UG 0 0 0 eth0


ping6 -I eth0 fe80::20d:88ff:fe1d:4898
--------------------------------------
PING fe80::20d:88ff:fe1d:4898(fe80::20d:88ff:fe1d:4898) from ::1 eth0: 56 data bytes
64 bytes from fe80::20d:88ff:fe1d:4898: icmp_seq=1 ttl=64 time=0.057 ms
64 bytes from fe80::20d:88ff:fe1d:4898: icmp_seq=2 ttl=64 time=0.046 ms

--- fe80::20d:88ff:fe1d:4898 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.046/0.051/0.057/0.009 ms


ping6 -s 2000 -I eth0 fe80::20d:88ff:fe1d:4898
----------------------------------------------
PING fe80::20d:88ff:fe1d:4898(fe80::20d:88ff:fe1d:4898) from ::1 eth0: 2000 data bytes
2008 bytes from fe80::20d:88ff:fe1d:4898: icmp_seq=1 ttl=64 time=0.070 ms
2008 bytes from fe80::20d:88ff:fe1d:4898: icmp_seq=2 ttl=64 time=0.054 ms

--- fe80::20d:88ff:fe1d:4898 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.054/0.062/0.070/0.008 ms


ping6 newszilla6.xs4all.nl
--------------------------
PING newszilla6.xs4all.nl(newszilla6.xs4all.nl) 56 data bytes
From ::1 icmp_seq=1 Destination unreachable: Address unreachable
From ::1 icmp_seq=2 Destination unreachable: Address unreachable
From ::1 icmp_seq=3 Destination unreachable: Address unreachable

--- newszilla6.xs4all.nl ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3618ms

-
Corwin

Corwin Burgess wrote:
> I am trying to setup my RedHat 9 with 2.4.20-28.9 kernel to connect to
> IPv6 domains. The ipv6 module is loaded at boot but I can't ping6 any
> IPv6 domains. My D-Link DFE-530TX+ NIC is connected to a cable modem.
> Not knowing what might be helpful I've included everything I could find.
> I will provide any additional information that you need to provide
> suggestions.
>
> /etc/sysconfig/network
> NETWORKING=yes
> HOSTNAME=localhost.localdomain
> NETWORKING_IPV6=yes
>
>
> /etc/sysconfig/networking/devices/ifcfg-eth0
> DEVICE=eth0
> BOOTPROTO=dhcp
> ONBOOT=yes
>
>
> ping cox.net
> ------------
> PING cox.net (68.1.17.9) 56(84) bytes of data.
> 64 bytes from www.cox.net (68.1.17.9): icmp_seq=1 ttl=247 time=42.7 ms
> 64 bytes from www.cox.net (68.1.17.9): icmp_seq=2 ttl=247 time=47.4 ms
> 64 bytes from www.cox.net (68.1.17.9): icmp_seq=3 ttl=247 time=41.1 ms
>
> --- cox.net ping statistics ---
> 3 packets transmitted, 3 received, 0% packet loss, time 2020ms
> rtt min/avg/max/mdev = 41.130/43.755/47.420/2.681 ms
>
>
> ifconfig -a
> -----------
> eth0 Link encap:Ethernet HWaddr 00:0D:88:1D:48:98
> inet addr:68.228.166.2 Bcast:68.228.167.255 Mask:255.255.248.0
> inet6 addr: fe80::20d:88ff:fe1d:4898/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:15282 errors:4 dropped:0 overruns:0 frame:0
> TX packets:637 errors:0 dropped:0 overruns:0 carrier:0
> collisions:27 txqueuelen:100
> RX bytes:1361030 (1.2 Mb) TX bytes:71290 (69.6 Kb)
> Interrupt:9 Base address:0x3000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:10 errors:0 dropped:0 overruns:0 frame:0
> TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:700 (700.0 b) TX bytes:700 (700.0 b)
>
> sit0 Link encap:IPv6-in-IPv4
> NOARP MTU:1480 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
>
> netstat -nr
> -----------
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window irtt
> Iface
> 68.228.160.0 0.0.0.0 255.255.248.0 U 0 0 0
> eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> eth0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 0.0.0.0 68.228.160.1 0.0.0.0 UG 0 0 0
> eth0
>
>
> ping6 -I eth0 fe80::20d:88ff:fe1d:4898
> --------------------------------------
> PING fe80::20d:88ff:fe1d:4898(fe80::20d:88ff:fe1d:4898) from ::1 eth0:
> 56 data bytes
> 64 bytes from fe80::20d:88ff:fe1d:4898: icmp_seq=1 ttl=64 time=0.057 ms
> 64 bytes from fe80::20d:88ff:fe1d:4898: icmp_seq=2 ttl=64 time=0.046 ms
>
> --- fe80::20d:88ff:fe1d:4898 ping statistics ---
> 2 packets transmitted, 2 received, 0% packet loss, time 999ms
> rtt min/avg/max/mdev = 0.046/0.051/0.057/0.009 ms
>
>
> ping6 -s 2000 -I eth0 fe80::20d:88ff:fe1d:4898
> ----------------------------------------------
> PING fe80::20d:88ff:fe1d:4898(fe80::20d:88ff:fe1d:4898) from ::1 eth0:
> 2000 data bytes
> 2008 bytes from fe80::20d:88ff:fe1d:4898: icmp_seq=1 ttl=64 time=0.070 ms
> 2008 bytes from fe80::20d:88ff:fe1d:4898: icmp_seq=2 ttl=64 time=0.054 ms
>
> --- fe80::20d:88ff:fe1d:4898 ping statistics ---
> 2 packets transmitted, 2 received, 0% packet loss, time 999ms
> rtt min/avg/max/mdev = 0.054/0.062/0.070/0.008 ms
>
>
> ping6 newszilla6.xs4all.nl
> --------------------------
> PING newszilla6.xs4all.nl(newszilla6.xs4all.nl) 56 data bytes
> From ::1 icmp_seq=1 Destination unreachable: Address unreachable
> From ::1 icmp_seq=2 Destination unreachable: Address unreachable
> From ::1 icmp_seq=3 Destination unreachable: Address unreachable
>
> --- newszilla6.xs4all.nl ping statistics ---
> 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3618ms
>
> -
> Corwin
>

IPv6 is not supported in the internet yet. If you want to send ipv6 packages
over the internet, you will have to tunnel them in an ipv4 tunnel. try "man
ifconfig" and search for the keyword "tunnel". Keep in mind, that the other side
of the connection will also have to support ipv6, which is not obvious.

ipv6 support in the internet is currently being discussed and will be introduced
step by step in the near future.

greets Boris

Boris Glawe wrote:
> Corwin Burgess wrote:
>
>> I am trying to setup my RedHat 9 with 2.4.20-28.9 kernel to connect to
>> IPv6 domains. The ipv6 module is loaded at boot but I can't ping6 any
>> IPv6 domains. My D-Link DFE-530TX+ NIC is connected to a cable modem.
>> Not knowing what might be helpful I've included everything I could
>> find. I will provide any additional information that you need to
>> provide suggestions.
>>
>> /etc/sysconfig/network
>> NETWORKING=yes
>> HOSTNAME=localhost.localdomain
>> NETWORKING_IPV6=yes
>>
>> -
>> Corwin
>>
>
> IPv6 is not supported in the internet yet. If you want to send ipv6
> packages over the internet, you will have to tunnel them in an ipv4
> tunnel. try "man ifconfig" and search for the keyword "tunnel". Keep in
> mind, that the other side of the connection will also have to support
> ipv6, which is not obvious.
>
> ipv6 support in the internet is currently being discussed and will be
> introduced step by step in the near future.
>
> greets Boris

I finally found the information in the form that I could understand. All I had to do was
add NETWORKING_IPV6=yes to /etc/sysconfig/network and then run the script that I found at
the following link. If you compare my script with his you will see that I had to make a
slight change.

http://www.altocumulus.org/IPv6/

-- script --
#!/bin/bash

### Get the global IPv4 address for your host from the command line:
GLOB_IP4=$1

### Compute the 6TO4 tunnel IPv6 address:
GLOB_IP6TO4=$(printf "2002:%02x%02x:%02x%02x::1" $(echo $GLOB_IP4 | tr . ' '))

### Setup the tunnel
ip tunnel add tun6to4 mode sit remote any local $GLOB_IP4 ttl 64
ip link set dev tun6to4 up
ip addr add $GLOB_IP6TO4/16 dev tun6to4
ip route add 2000::/3 via ::192.88.99.1 dev tun6to4 metric 1
-- end script --

--
Corwin

Boris Glawe wrote:
>
> IPv6 is not supported in the internet yet. If you want to send ipv6
> packages over the internet, you will have to tunnel them in an ipv4
> tunnel. try "man ifconfig" and search for the keyword "tunnel". Keep
> in mind, that the other side of the connection will also have to
> support ipv6, which is not obvious.
>
> ipv6 support in the internet is currently being discussed and will be
> introduced step by step in the near future.
>
> greets Boris

Please excuse my bluntness, but if it's not useable o nthe internet,
then what the hell point is there in even using it, as it seems it can
only be used on provate lans/intranets. IPv4 is very clean and familiar
and IPv6 is anything but clean. Since I first heard of it I have been
really hardpressed to find any real good reason to even use it over the
current 1.2.3.4 norm.