|
Ticket ID: SIXXS #4818797 Ticket Status: User PoP: hubud01 - DIGI Kft (Budapest)
newly created tunnel seems not to function after type change
![[hu]](/s/countries/hu.gif) Shadow Hawkins on Tuesday, 31 May 2011 11:14:16
Hello,
I requested a tunnel recently to hubud01. Unfortunately, when created, I only entered a static IP but the radio button was set to AYIYA. When it was approved, I changed the type to static, but there were no RX packets on the tunnel. I tried to move it to another IP, losing some ISK, but still no RX packets, I don't think it's a misconfiguration because a tunnel to simbx01 worked well with the very same config.
When I try to traceroute from another tunnel, the following is seen, which is very odd in my opinion:
Tracing route to cl-11.bud-01.hu.sixxs.net [2a01:368:e000:a::2]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms gmrb.goodman.hu [2a01:368:e104:f00d:20c:42ff:fe5e:e5c5]
2 4 ms 5 ms 5 ms gw-6.bud-02.hu.sixxs.net [2a01:368:e100:5::1]
3 5 ms 6 ms 5 ms 2a01:368:ff01:16::1
4 5 ms 5 ms 6 ms hubud01.sixxs.net [2a01:368:ff01:16::2]
5 Destination host unreachable.
Trace complete.
My configuration is the following:
/interface 6to4
add disabled=no local-address=79.120.183.201 mtu=1280 name=SiXXS remote-address=94.21.7.130
/ipv6 address
add address=2a01:368:e000:a::2/128 advertise=no disabled=no eui-64=no interface=SiXXS
/ipv6 route
add disabled=no distance=1 dst-address=::/0 gateway=SiXXS scope=30 target-scope=10
This same config with the corresbonding tunnel to hubud02 works without problems on a same brand RouterOS device.
Please take a look into the tunnel, is it configured as static on the tunnelserver?
Daniel
State change: user
The state of this ticket has been changed to user
newly created tunnel seems not to function after type change
/interface 6to4
Although this might be a misnomer for the configuration language that your host is using, the protocol is called 6in4 or protocol-41. 6to4 uses addresses out of 2002::/16.
For the rest, please provide all the ACTIVE interfaces, addresses, routing tables and further details requested by that big yellow/orange box.
newly created tunnel seems not to function after type change
Shadow Hawkins on Tuesday, 31 May 2011 11:38:04
Interface type 6to4 is ok with mikrotik.
FAQ:
newly created tunnel seems not to function after type change
Shadow Hawkins on Tuesday, 31 May 2011 11:40:17
Interface type 6to4 is ok with RouterOS.
FAQ: http://www.sixxs.net/wiki/RouterOS
newly created tunnel seems not to function after type change
Shadow Hawkins on Tuesday, 31 May 2011 11:54:59
Hello Jeroen,
Yes, MikroTik is confusingly using 6to4 for protocol 41 tunnels. I followed the RouterOS SiXXS FAQ when I set up this tunnel, and another tunnel was working on that host, also another is happily working now on another routerboard, too. I suppose this issue should be somehow related to the fact I created the tunnel as AYIYA THEN changed to static.
If I change the IP addresses of the interfaces and tunnel to my simbx01 tunnel, the connection immediately start working
[admin@MikroTik] > /ipv6 route print
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, o - ospf, b - bgp, U - unreachable
# DST-ADDRESS GATEWAY DISTANCE
0 A S ::/0 SiXXS 1
1 ADC 2a01:368:e000:a::2/128 SiXXS 0
2 ADC 2a01:368:e003:feed::/64 vlan110 0
[admin@MikroTik] > /ipv6 address print
Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local
# ADDRESS INTERFACE ADVERTISE
0 G 2a01:368:e000:a::2/128 SiXXS no
1 G 2a01:368:e003:feed:20c:42ff:fe73:db4/64 vlan110 yes
2 DL fe80::4f78:b7d2/128 SiXXS no
(link-local subinterfaces cut from here)
IPv6 firewalling is disabled now. IPv4 protocol 41 is allowed from/to the tunnel. Again, I suppose this is due to the tunneltype change from ayiya to static.
Daniel
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 31 May 2011 11:30:49
Posting is only allowed when you are