|
Ticket ID: SIXXS #1212507 Ticket Status: User PoP: gblon02 - Goscomb Technologies (London)
Cant ping remote end of tunnel
![[au]](/s/countries/au.gif) Shadow Hawkins on Thursday, 24 September 2009 10:11:11
I have read and followed the "Reporting Problems" section on the Contact page.
I am removing these five pre-filled lines to demonstrate that I really read it.
I am providing the full details as requested on the mentioned Contact page.
If I do not remove this, then please ignore this message as I didn't read it anyway.
------------------------------------------------------------------------------>8
Hi,
I have read through as much documentation as I can, and still have not been able to solve my problem.
Username: TFA1-SIXXS
Tunnel: T23108
I am unable to ping the remote end of the tunnel from either Windows XP running aiccu graphical, or ubuntu apt-get install aiccu,and set configs on both to be behind NAT.
In Windows XP, AICCU grapical shows relevant information, however the Test button is greyed out. (does that indicate an issue)
I am not sure if the tunnel has ever actually been up.
ipconfig.
Windows IP Configuration
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.127.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::250:56ff:fec0:8%4
Default Gateway . . . . . . . . . :
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.48.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::250:56ff:fec0:1%5
Default Gateway . . . . . . . . . :
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 10.1.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::2a0:c9ff:fe99:17b0%6
Default Gateway . . . . . . . . . : 10.1.1.1
10.10.10.1
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%7
Default Gateway . . . . . . . . . :
Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.127.1%2
Default Gateway . . . . . . . . . :
Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.48.1%2
Default Gateway . . . . . . . . . :
Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::5efe:10.1.1.2%2
Default Gateway . . . . . . . . . :
Under linux (ubuntu) I have apt-get install aiccu, and it appears to start correctly and the ipv6 interface shows up as sixxs as IPv6-in-IPv4. However aiccu test dies when attempting part 6/8. Saying your end of the tunnel is unreachable. Pings my local IPv6 address fine though.
For testing, I have no firewall on the windows or Ubuntu boxes. Its running through a Cisco 1801 router, also with no firewall configured.
Here's hoping you can offer me some kind of a clue as to what could be going wrong.
Thank You
Tim Fraser
tef@iinet.net.au
Cant ping remote end of tunnel
You seem to have two VMWare interfaces with RFC1918 addresses, but also your main interface has that:
Ethernet adapter Local Area Connection: [..] IP Address. . . . . . . . . . . . : 10.1.1.2
As you have a static tunnel configuration, you will in that case need to configure the box that performs the NAT for you.
Easier way to solve your problem: use AYIYA.
Cant ping remote end of tunnel
Shadow Hawkins on Friday, 25 September 2009 06:09:23
I have read and followed the "Reporting Problems" section on the Contact page.
I am removing these five pre-filled lines to demonstrate that I really read it.
I am providing the full details as requested on the mentioned Contact page.
If I do not remove this, then please ignore this message as I didn't read it anyway.
------------------------------------------------------------------------------>8
Changing it to AYIYA has made it worse, I can't even ping a local IPv6 address now, and it appears none of my interfaces have the correct IPv6 address. ( 2a01:348:9:266::1 )
Windows IP Configuration
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.127.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::250:56ff:fec0:8%4
Default Gateway . . . . . . . . . :
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.48.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::250:56ff:fec0:1%5
Default Gateway . . . . . . . . . :
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 10.1.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::2a0:c9ff:fe99:17b0%6
Default Gateway . . . . . . . . . : 10.1.1.1
10.10.10.1
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%7
Default Gateway . . . . . . . . . :
Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.127.1%2
Default Gateway . . . . . . . . . :
Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.48.1%2
Default Gateway . . . . . . . . . :
Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::5efe:10.1.1.2%2
Default Gateway . . . . . . . . . :
So far I have tried
(1)setting up a tunnel from my Cisco 1801 router, router said tunnel was up, but I couldn't ping the remote end.
(2) Running AICCU graphical in windows, first with a static IP (which my ISP assigns), I managed to get my local IPv6 address, and be able to ping it, however I still couldn't ping the remote end of the tunnel
(3) Changed to AYIYA in windows, AICUU box comes up and looks like all should be working showing a heartbeat interval of 60seconds. Dont see errors anywhere to indicate any problems
(4) Run AICCU from the command line in Ubuntu, it did configure a sixxs interface and assigned it my IPv6 address. However, was still unable to ping the remote end of the tunnel . aiccu test died at 6/8 (pinging the remote end)
I'm not sure what else I can try, are you 100% there is no issue with the remote end of the tunnel?
Thank You
Tim Fraser
Tunnel ID T23108
Login: TFA1-SIXXS
Cant ping remote end of tunnel
it appears none of my interfaces have the correct IPv6 address.
Did you install the Tun/Tap driver? I guess you did not.
Clearly, as can be seen from the first few lines of your post, you are not even reading the ticket posting instructions. Please do so. They contain a very handy reference to a page of things you can check.
State change: user
The state of this ticket has been changed to user
|
![[ch]](/s/countries/ch.gif)
on Thursday, 24 September 2009 10:55:41
Posting is only allowed when you are