|
Tunnelendpoint not pingable
![[de]](/s/countries/de.gif) Shadow Hawkins on Wednesday, 24 November 2010 22:15:18
Hi,
I have a problem and need your help.
Yesterday, I have registered a 2nd Tunnel.
Tunnel Id : T46817
PoP Name : decgn01 (de.netcologne [AS8422])
SixXS IPv6 : 2001:4dd0:ff00:3f9::1/64
Your IPv6 : 2001:4dd0:ff00:3f9::2/64
SixXS IPv4 : 78.35.24.124
Tunnel Type : Dynamic (heartbeat)
Now, I have configured my 2nd router for the 2nd tunnel, like my config for the 1st tunnel (which are working fine).
But I can not ping the tunnelendpoint.
Interface-config:
sixxs
Link encap:IPv6-in-IPv4
inet6 addr: 2001:4dd0:ff00:3f9::2/64 Scope:Global
inet6 addr: fe80::c0a8:105/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:640 errors:0 dropped:0 overruns:0 frame:0
TX packets:804 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:66560 (65.0 KiB) TX bytes:83616 (81.6 KiB)
root@OpenWrt:~# ping6 2001:4dd0:ff00:3f9::1
PING 2001:4dd0:ff00:3f9::1 (2001:4dd0:ff00:3f9::1): 56 data bytes
^C
--- 2001:4dd0:ff00:3f9::1 ping statistics ---
75 packets transmitted, 0 packets received, 100% packet loss
The output of the tcpdump during the "ping6 2001:4dd0:ff00:3f9::1"
root@OpenWrt:~# tcpdump -ni sixxs
tcpdump: WARNING: sixxs: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on sixxs, link-type RAW (Raw IP), capture size 96 bytes
listening on sixxs, link-type RAW (Raw IP), capture size 96 bytes
19:34:22.808615 IP6 2001:4dd0:ff00:3f9::2 > 2001:4dd0:ff00:3f9::1: ICMP6, echo request, seq 0, length 64
19:34:23.814065 IP6 2001:4dd0:ff00:3f9::2 > 2001:4dd0:ff00:3f9::1: ICMP6, echo request, seq 1, length 64
19:34:24.824103 IP6 2001:4dd0:ff00:3f9::2 > 2001:4dd0:ff00:3f9::1: ICMP6, echo request, seq 2, length 64
19:34:25.834117 IP6 2001:4dd0:ff00:3f9::2 > 2001:4dd0:ff00:3f9::1: ICMP6, echo request, seq 3, length 64
19:34:26.844130 IP6 2001:4dd0:ff00:3f9::2 > 2001:4dd0:ff00:3f9::1: ICMP6, echo request, seq 4, length 64
---> no reply from "2001:4dd0:ff00:3f9::1" (Tunnelendpoint)
Do you have any idea?
For me that looks like, there is a problem in the Tunnelendpoint ?
Many Thanks
Best regards
Michael
Tunnelendpoint not pingable
![[us]](/s/countries/us.gif) Shadow Hawkins on Thursday, 25 November 2010 04:03:06
Afraid that isn't the case
[carl@mars ~]$ ping6 2001:4dd0:ff00:3f9::1
PING6(56=40+8+8 bytes) 2001:470:c27d:e000:20c:29ff:fe8a:1618 --> 2001:4dd0:ff00:3f9::1
16 bytes from 2001:4dd0:ff00:3f9::1, icmp_seq=0 hlim=54 time=150.532 ms
16 bytes from 2001:4dd0:ff00:3f9::1, icmp_seq=1 hlim=54 time=149.655 ms
16 bytes from 2001:4dd0:ff00:3f9::1, icmp_seq=2 hlim=54 time=149.945 ms
16 bytes from 2001:4dd0:ff00:3f9::1, icmp_seq=3 hlim=54 time=149.652 ms
^C
--- 2001:4dd0:ff00:3f9::1 ping6 statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 149.652/149.946/150.532/0.359 ms
And, I can ping ::2, so you must have got it working
Tunnelendpoint not pingable
Shadow Hawkins on Thursday, 25 November 2010 06:52:32
Hi Carl,
you are right. :-)
Yesterday evening, I have stoppt my aiccu and radvd programms for my 1st tunnel.
This morning, I see the 2nd tunnelendpoint are pingable. But if I start the aiccu for my 1st tunnel I can not ping the 1st tunnelendpoint :-(
I want to use both Tunnels from the same Home-Internet-connection at the same time. Is that possible.
Both tunnel ends at the same PoP
1st Tunnel
Tunnel Id : T36641
PoP Name : decgn01 (de.netcologne [AS8422])
TIC Server : tic.sixxs.net (which is the default in AICCU)
SixXS IPv6 : 2001:4dd0:ff00:244::1/64
Your IPv6 : 2001:4dd0:ff00:244::2/64
SixXS IPv4 : 78.35.24.124
Tunnel Type : Dynamic (heartbeat)
2nd Tunnel
Tunnel Id : T46817
PoP Name : decgn01 (de.netcologne [AS8422])
TIC Server : tic.sixxs.net (which is the default in AICCU)
SixXS IPv6 : 2001:4dd0:ff00:3f9::1/64
Your IPv6 : 2001:4dd0:ff00:3f9::2/64
SixXS IPv4 : 78.35.24.124
Tunnel Type : Dynamic (heartbeat)
Is that the problem?
Now, I have stoppt my 2nd tunnel again, because I want to get my IPv6 network back on the 1st tunnel.
Any Idea?
Many thanks
Best regards
Michael
Tunnelendpoint not pingable
![[dk]](/s/countries/dk.gif) Shadow Hawkins on Thursday, 25 November 2010 07:22:36
Why two tunnels?
You can't bundle two connections together.
The most you can do is by cleverly doing manual routing using ine tunnel for some hosts and the other for the rest of the internet.
Tunnelendpoint not pingable
Shadow Hawkins on Thursday, 25 November 2010 07:46:43
Hi Leif,
the reason why I want to use a 2nd tunnel is, I want to setup a 2nd IPv6 network for tests in my home.
I can use this 2nd network, if I want to show e.g. the working of IPv6 in our Linux-User-Group (workshops).
My 1st tunnel and ipv6 network are woring fine.
My 2nd tunnel is not pingable if the 1st tunnel is up.
After the 2nd tunnel is working I will request a 1pv6 net for the 2nd tunnel, for test and demostration/workshops.
Thanks
Michael
Tunnelendpoint not pingable
Shadow Hawkins on Thursday, 25 November 2010 15:41:35
If it's for testing, then I think you should set the second tunnel to terminate on another machine than the first.
As AYIYA can work through (most) firewalls, it need not run on your borderrouter.
You might have to make the second machine not get an ipv6-address from the first tunnel.
Tunnelendpoint not pingable
Shadow Hawkins on Thursday, 25 November 2010 20:18:57
Hi Leif,
thanks for you feedback.
If it's for testing, then I think you should set the second tunnel to terminate on another machine than the first.
yes, that is allready done. If have set up the 2nd tunnel on a other device.
But if the 1st tunnel is working and the tunnelendpoint ist answer for ping, I can not ping from the 2nd tunnel the 2nd tunnelendpoint-IP.
But if I shutdown the 1st tunnel and wait few minutes, than I can ping the 2nd tunnelendpoint-IP from my 2nd tunnel device.
As AYIYA can work through (most) firewalls, it need not run on your borderrouter.
I use heartbeat with the aiccu client on both tunnels and as I write one of the tunnel are pingable and one not at the same time. So I thing the heartbeat works in my firewall-setup.
You might have to make the second machine not get an ipv6-address from the first tunnel.
I only have configured the IP's from the 1st tunnel to the 1st device and the IP's from the 2nd tunnel to the 2nd device.
I think, the PoP see there come from the same dyn. IP-Address (DSL -Line) 2 tunnel-connection, but only 1 is allowed and ignore the 2nd connection.
What think about you?
Thanks
Best regards
Michael
Tunnelendpoint not pingable
Shadow Hawkins on Thursday, 25 November 2010 15:42:42
I forgot to notice: Change the tunnel type to AYIYA on the second tunnel.
Tunnelendpoint not pingable
Shadow Hawkins on Thursday, 25 November 2010 21:47:01
Hi Leif,
I forgot to notice: Change the tunnel type to AYIYA on the second tunnel.
do you think about, that 2 heartbeat tunnels via the same external IP (DSL uplink) to the same PoP do not work at the same time?
I hope I have enough ISK's to change the tunnel type to AYiYA and it work after that ;-)
Thanks
Michael
Tunnelendpoint not pingable
Shadow Hawkins on Thursday, 25 November 2010 22:25:20
Hi Leif,
you are the greatest!!!
My 2nd tunnel are running, after I change from heartbeat to AYIYA :-)
But, now my ISK counts is "-6" :-(
So I can not request a new subnet for my 2nd tunnel :-(
But I need the new subnet for my 2nd tunnel for a workshop in our Linux-User-Group this weekend :-(
I think I need to wait until I get more ISK's ....
Many Thanks for your help
Best regards
Michael
Tunnelendpoint not pingable
Shadow Hawkins  on Friday, 26 November 2010 11:01:39
Please see your account.
Kind regards,
Stefan Neufeind
Tunnelendpoint not pingable
Shadow Hawkins on Friday, 26 November 2010 11:38:43
Hi,
many, many thanks :-)
I have now requested the subnet.
Thank you very much
Best regards
Michael Schleicher
Tunnelendpoint not pingable
Shadow Hawkins on Friday, 26 November 2010 10:49:52
I believe you can "borrow" ISK, if you ask nicely.
|
Posting is only allowed when you are