HE's Tunneling on Ubuntu 10.04

stevekreitzer · July 26, 2011, 04:33:33 PM

Hello HE,

I cannot get the tunneling to work without doing this > From 2001:470:1f10:1177::2 icmp_seq=1 Destination unreachable: Address unreachable

This is all my networking addresses etc.

he-ipv6 Link encap:IPv6-in-IPv4
inet6 addr: 2001:470:1f10:1177::2/64 Scope:Global
inet6 addr: fe80::4628:f4e6/128 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:92 dropped:0 overruns:0 carrier:92
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

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:2424 errors:0 dropped:0 overruns:0 frame:0
TX packets:2424 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:367515 (367.5 KB) TX bytes:367515 (367.5 KB)

wlan0 Link encap:Ethernet HWaddr 90:4c:e5:1e:88:3d
inet addr:192.168.2.3 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::924c:e5ff:fe1e:883d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6971 errors:0 dropped:0 overruns:0 frame:0
TX packets:7194 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5638119 (5.6 MB) TX bytes:1853874 (1.8 MB)

And how I setup the script the he-ipv6

#!/bin/sh

LOCAL=70.40.244.230 (This is my IP address)
ADDR=2001:470:1f10:1177::2/64
REMOTE=209.51.181.2

ip tunnel del he-ipv6
ip tunnel add he-ipv6 mode sit remote ${REMOTE} local ${LOCAL} ttl 255
ip link set he-ipv6 up
ip addr add ${ADDR} dev he-ipv6
ip route add ::/0 dev he-ipv6

Thanks!

cholzhauer · July 27, 2011, 05:10:53 AM

Did you change the 70.40.244.230 to 192.168.2.3 when you ran those commands?

You should also assign an IPv6 address from your routed /64 to your wlan0 interface

stevekreitzer · July 27, 2011, 10:44:37 PM

Tried the 192.168.2.3 (Those other results were tested with the script on my real ip)

This is now what happens.

root@Steven-Computer:/etc/init.d# ping6 ipv6.google.com
PING ipv6.google.com(qw-in-x69.1e100.net) 56 data bytes
^C
--- ipv6.google.com ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 5002ms

root@Steven-Computer:/etc/init.d# ifconfig
he-ipv6 Link encap:IPv6-in-IPv4
inet6 addr: 2001:470:1f10:1177::2/64 Scope:Global
inet6 addr: fe80::c0a8:203/128 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:1978 (1.9 KB)

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:10376 errors:0 dropped:0 overruns:0 frame:0
TX packets:10376 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1624706 (1.6 MB) TX bytes:1624706 (1.6 MB)

wlan0 Link encap:Ethernet HWaddr 90:4c:e5:1e:88:3d
inet addr:192.168.2.3 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: 2001:470:1f11:1177::/64 Scope:Global
inet6 addr: fe80::924c:e5ff:fe1e:883d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:368096 errors:0 dropped:0 overruns:0 frame:0
TX packets:340772 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:213306761 (213.3 MB) TX bytes:45427874 (45.4 MB)

And the script:

#!/bin/sh

LOCAL=192.168.2.3 # Client IPv4 address
ADDR=2001:470:1f10:1177::2/64 # Client IPv6 address
REMOTE=209.51.181.2 # Server IPv4 address

ip tunnel del he-ipv6
ip tunnel add he-ipv6 mode sit remote ${REMOTE} local ${LOCAL} ttl 255
ip link set he-ipv6 up
ip addr add ${ADDR} dev he-ipv6
ip route add ::/0 dev he-ipv6

cholzhauer · July 28, 2011, 05:03:04 AM

Is your router blocking protocol41?

And that's not really an address on wlan0...you just defined the subnet. Turn it into 2001:470:1f11:1177::1/64 or something

stevekreitzer · July 28, 2011, 08:14:11 AM

Opened port 41, like you said.

Changed the wlan0 v6 address to 2001:470:1f11:1177::1/64, then 2001:470:1f11:1177::2/64

None work, any ideas?

cholzhauer · July 28, 2011, 08:15:12 AM

Nope, not port41, protocol41 Most routers won't let you forward a protocol, so you have to use the DMZ mode instead (although on some routers, this doesn't work either)

stevekreitzer · July 28, 2011, 09:02:02 PM

Turned on the DMZ on my 192.168.2.3, no help.

I have BusyBox bash shell on my router if there is a command that would help?

cholzhauer · August 01, 2011, 05:32:31 AM

what router do you have?

News:

HE's Tunneling on Ubuntu 10.04