|
Problem with tunnel
![[hu]](/s/countries/hu.gif) Shadow Hawkins on Thursday, 28 July 2011 15:37:16
I'm having a problem with setting up a tunnel on a router which has OpenWrt on it.
I'm connecting to the internet through one router at home.
I can ping sixxs.net, the PoP and the endpoint, but on the details page it shows that 'Your IPv4AYIYA, currently unknow' and the statistics are empty too.
I'm not really an expret in this, so please help me in the way how can it be solved on my router.
Also I noticed that if I can add the 41 protocol to the router, then the heartbeat tunnel could be good, if I'm correct.
So if this is the case and it is better in this way (or the ayiya should be good too?), then could someone (maybe Jeroen) change this?
If it is just for credits (and it is need to be changed), then could it be possible to earn bonus credits if I provide links to my linkedin and xing profile?
http://www.linkedin.com/profile/view?id=132483012
https://www.xing.com/profile/SandorImre_Xaver
Feedback is welcome.
Thanks in advance
Problem with tunnel
I can ping sixxs.net, the PoP and the endpoint,
IPv4 or IPv6? Also, do you have a traceroute?
on the details page it shows that 'Your IPv4AYIYA, currently unknow'
As that states, it is currently unknown as the website can't ask the PoP what it is. Nothing wrong with that though.
the statistics are empty too.
Are you sure that you are sending traffic over the tunnel and that your endpoint properly pings?
Also I noticed that if I can add the 41 protocol to the router, then the heartbeat tunnel could be good, if I'm correct.
If you have a public IPv4 address and that then terminates the tunnel, then indeed a proto-41 tunnel, either with or without heartbeat option can work just fine.
So if this is the case and it is better in this way (or the ayiya should be good too?), then could someone (maybe Jeroen) change this?
You can move endpoints and change tunnel types using the webinterface.
Problem with tunnel
Shadow Hawkins on Thursday, 28 July 2011 16:49:14
I have a public IPv4 address, yes.
Not really sure what could be the problem, I'm not an expert just followed the instructions.
xav@router:/# ping6 -I sixxs0 sixxs.net
PING sixxs.net (2001:960:800::2): 56 data bytes
64 bytes from 2001:960:800::2: seq=0 ttl=57 time=40.973 ms
64 bytes from 2001:960:800::2: seq=1 ttl=57 time=38.793 ms
64 bytes from 2001:960:800::2: seq=2 ttl=57 time=38.626 ms
64 bytes from 2001:960:800::2: seq=3 ttl=57 time=37.965 ms
^C
--- sixxs.net ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 37.965/39.089/40.973 ms
xav@router:/# ping6 -I sixxs0 2a01:368:e100:d::1
PING 2a01:368:e100:d::1 (2a01:368:e100:d::1): 56 data bytes
64 bytes from 2a01:368:e100:d::1: seq=0 ttl=64 time=7.116 ms
64 bytes from 2a01:368:e100:d::1: seq=1 ttl=64 time=7.033 ms
64 bytes from 2a01:368:e100:d::1: seq=2 ttl=64 time=6.882 ms
64 bytes from 2a01:368:e100:d::1: seq=3 ttl=64 time=5.704 ms
^C
--- 2a01:368:e100:d::1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 5.704/6.683/7.116 ms
xav@router:/# ping6 -I sixxs0 2a01:368:e100:d::2
PING 2a01:368:e100:d::2 (2a01:368:e100:d::2): 56 data bytes
64 bytes from 2a01:368:e100:d::2: seq=0 ttl=64 time=0.729 ms
64 bytes from 2a01:368:e100:d::2: seq=1 ttl=64 time=0.286 ms
64 bytes from 2a01:368:e100:d::2: seq=2 ttl=64 time=0.264 ms
^C
--- 2a01:368:e100:d::2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.264/0.426/0.729 ms
My configuration is the following:
aiccu:
config aiccu
option username 'SIX1-SIXXS'
option password 'xxxxx'
option protocol 'tic'
option server 'tic.sixxs.net'
option interface 'sixxs0'
option tunnel_id 'T75254'
option requiretls '0'
option defaultroute '1'
option nat '1'
option heartbeat '1'
--
network:
config interface loopback
option ifname lo
option proto static
option ipaddr 127.0.0.1
option netmask 255.0.0.0
config interface lan
option ifname eth0.1
option type bridge
option proto static
option ipaddr 192.168.1.1
option netmask 255.255.255.0
config interface wan
option ifname eth1
option proto pppoe
option username xxxxx
option password xxxxx
config interface sixxs
option ifname sixxs0
option proto 6in4
option peeraddr 94.21.7.131
option ip6addr 2a01:368:e100:d::2/64
--
firewall:
config defaults
option syn_flood 1
option input ACCEPT
option output ACCEPT
option forward REJECT
config zone
option name lan
option network 'lan'
option input ACCEPT
option output ACCEPT
option forward REJECT
config zone
option name wan
option network 'wan sixxs'
option input REJECT
option output ACCEPT
option forward REJECT
option masq 1
option mtu_fix 1
config forwarding
option src lan
option dest wan
config rule
option _name DHCPFIX
option src wan
option proto udp
option dest_port 68
option target ACCEPT
option family ipv4
config rule
option _name ICMP
option src wan
option proto icmp
option icmp_type echo-request
option family ipv4
option target ACCEPT
config rule
option _name ICMP6
option src wan
option dest *
option proto icmp
list icmp_type echo-request
list icmp_type destination-unreachable
list icmp_type packet-too-big
list icmp_type time-exceeded
list icmp_type bad-header
list icmp_type unknown-header-type
option limit 1000/sec
option family ipv6
option target ACCEPT
config include
option path /etc/firewall.user
config 'rule'
option _name 6TO4
option 'target' 'ACCEPT'
option 'src' 'wan'
option 'proto' '41'
--
firewall.user:
iptables -A forwarding_rule -i ppp+ -j ACCEPT
iptables -A forwarding_rule -o ppp+ -j ACCEPT
Problem with tunnel
Those are configuration settings and pings, but what is the actual running configuration and the route (traceroute6) that the packets are taking?
Problem with tunnel
Shadow Hawkins on Thursday, 28 July 2011 17:06:49
xav@router:/# traceroute6 sixxs.net
traceroute to sixxs.net (2620:0:6b0:a:250:56ff:fe99:78f7) from 2a01:368:e100:d::2, 30 hops max, 16 byte packets
1 gw-14.bud-02.hu.sixxs.net (2a01:368:e100:d::1) 7.832 ms 7.915 ms 6.437 ms
2 2a01:368:ff01:16::1 (2a01:368:ff01:16::1) 7.483 ms 8.107 ms 6.853 ms
3 2a02:2f09:10:0:8708:20:845:1 (2a02:2f09:10:0:8708:20:845:1) 6.659 ms 8.353 ms 6.745 ms
4 cr01.v6.timisoara.rdsnet.ro (2a02:2f00:8708::2001:6) 12.962 ms 42.842 ms 15.265 ms
5 xr01.v6.amsterdam.rdsnet.ro (2a02:2f00:8708::4001:252) 41.739 ms 41.653 ms 43.607 ms
6 ams-ix1.ams1.network6.solcon.net (2001:7f8:1::a501:2414:1) 41.193 ms 41.834 ms 43.297 ms
7 20gigabitethernet1-3.core1.ams1.ipv6.he.net (2001:7f8:1::a500:6939:1) 43.357 ms 42.084 ms 41.588 ms
8 fr3.ams.llnw.net (2001:7f8:1::a502:2822:1) 43.907 ms 48.135 ms 50.017 ms
9 tge1-3.fr3.lga.ipv6.llnw.net (2607:f4e8:1:97::1) 119.163 ms 117.266 ms 119.893 ms
10 tge8-4.fr3.ord.ipv6.llnw.net (2607:f4e8:1:15::2) 180.786 ms 141.386 ms 150.498 ms
11 ve8.fr3.ord4.ipv6.llnw.net (2607:f4e8:1:2b::2) 140.369 ms 143.829 ms 150.086 ms
12 GW01.ORD07.CYMRU.COM (2001:504:0:4:0:2:3028:1) 141.43 ms 141.751 ms 141.366 ms
13 uschi03.sixxs.net (2620:0:6b0:a:250:56ff:fe99:78f7) 143.186 ms 143.219 ms 144.616 ms
xav@router:/# traceroute6 2a01:368:e100:d::1
traceroute to 2a01:368:e100:d::1 (2a01:368:e100:d::1) from 2a01:368:e100:d::2, 30 hops max, 16 byte packets
1 gw-14.bud-02.hu.sixxs.net (2a01:368:e100:d::1) 6.235 ms 6.648 ms 5.662 ms
xav@router:/# traceroute6 2a01:368:e100:d::2
traceroute to 2a01:368:e100:d::2 (2a01:368:e100:d::2) from 2a01:368:e100:d::2, 30 hops max, 16 byte packets
1 cl-14.bud-02.hu.sixxs.net (2a01:368:e100:d::2) 0.549 ms 0.225 ms 0.163 ms
xav@router:/# ip r s
default via 10.0.0.1 dev pppoe-wan
10.0.0.1 dev pppoe-wan proto kernel scope link src 94.21.148.49
169.254.0.0/16 dev wlan1 proto kernel scope link src 169.254.1.1
192.168.1.0/24 dev br-lan proto kernel scope link src 192.168.1.1
xav@router:/# ip -6 r s
2a01:368:e100:d::/64 dev sixxs0 proto kernel metric 256
2a01:368:e100:d::/64 via :: dev 6in4-sixxs proto kernel metric 256
fe80::/64 dev eth0 proto kernel metric 256
fe80::/64 dev br-lan proto kernel metric 256
fe80::/64 dev eth1 proto kernel metric 256
fe80::/64 dev wlan1 proto kernel metric 256
fe80::/64 dev sixxs0 proto kernel metric 256
fe80::/64 via :: dev 6in4-sixxs proto kernel metric 256 mtu 1280
default via 2a01:368:e100:d::1 dev sixxs0 metric 1024
default dev 6in4-sixxs metric 1024
xav@router:/# uci -P /var/state show network
network.loopback=interface
network.loopback.ifname=lo
network.loopback.proto=static
network.loopback.ipaddr=127.0.0.1
network.loopback.netmask=255.0.0.0
network.loopback.device=lo
network.loopback.up=1
network.loopback.connect_time=32
network.lan=interface
network.lan.type=bridge
network.lan.proto=static
network.lan.ipaddr=192.168.1.1
network.lan.netmask=255.255.255.0
network.lan.up=1
network.lan.connect_time=35
network.lan.ifname=br-lan
network.lan.device=eth0.1 wlan0
network.wan=interface
network.wan.proto=pppoe
network.wan.username=XXXXX
network.wan.password=XXXXX
network.wan.device=eth1
network.wan.ipaddr=94.21.148.49
network.wan.gateway=10.0.0.1
network.wan.dns=193.110.57.4 193.110.56.8
network.wan.resolv_dns=193.110.57.4 193.110.56.8
network.wan.up=1
network.wan.connect_time=43
network.wan.ifname=pppoe-wan
network.guest=interface
network.guest.proto=static
network.guest.ipaddr=169.254.1.1
network.guest.netmask=255.255.0.0
network.guest.up=1
network.guest.connect_time=48
network.guest.ifname=wlan1
network.sixxs=interface
network.sixxs.proto=6in4
network.sixxs.peeraddr=94.21.7.131
network.sixxs.ip6addr=2a01:368:e100:d::2/64
network.sixxs.wan_device=pppoe-wan
network.sixxs.auto=0
network.sixxs.ipaddr=94.21.148.49
network.sixxs.defaultroute=1
network.sixxs.up=1
network.sixxs.connect_time=47
network.sixxs.ifname=6in4-sixxs
network.@switch[0]=switch
network.@switch[0].name=rtl8366s
network.@switch[0].reset=1
network.@switch[0].enable_vlan=1
network.@switch[0].blinkrate=2
network.@switch[0].max_length=3
network.@switch_vlan[0]=switch_vlan
network.@switch_vlan[0].device=rtl8366s
network.@switch_vlan[0].vlan=1
network.@switch_vlan[0].ports=0 1 2 3 5t
network.@switch_port[0]=switch_port
network.@switch_port[0].device=rtl8366s
network.@switch_port[0].port=1
network.@switch_port[0].led=6
network.@switch_port[1]=switch_port
network.@switch_port[1].device=rtl8366s
network.@switch_port[1].port=2
network.@switch_port[1].led=9
network.@switch_port[2]=switch_port
network.@switch_port[2].device=rtl8366s
network.@switch_port[2].port=5
network.@switch_port[2].led=2
Problem with tunnel
The first one shows that stuff works doesn't it? :)
Problem with tunnel
Shadow Hawkins on Thursday, 28 July 2011 17:28:38
xav@router:/# ifconfig
6in4-sixxs Link encap:IPv6-in-IPv4
inet6 addr: fe80::5e15:9431/128 Scope:Link
inet6 addr: 2a01:368:e100:d::2/64 Scope:Global
UP POINTOPOINT RUNNING NOARP MTU:1280 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)
br-lan Link encap:Ethernet HWaddr C0:3F:0E:8D:95:BF
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::c23f:eff:fe8d:95bf/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2672727 errors:0 dropped:0 overruns:0 frame:0
TX packets:1554358 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1624754370 (1.5 GiB) TX bytes:126201651 (120.3 MiB)
eth0 Link encap:Ethernet HWaddr C0:3F:0E:8D:95:BF
inet6 addr: fe80::c23f:eff:fe8d:95bf/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:8173 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:667201 (651.5 KiB)
Interrupt:4
eth0.1 Link encap:Ethernet HWaddr C0:3F:0E:8D:95:BF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:8164 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:632814 (617.9 KiB)
eth1 Link encap:Ethernet HWaddr C0:3F:0E:8D:95:C0
inet6 addr: fe80::c23f:eff:fe8d:95c0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1553764 errors:0 dropped:0 overruns:0 frame:0
TX packets:2666005 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:134093344 (127.8 MiB) TX bytes:1681181643 (1.5 GiB)
Interrupt:5
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:152 errors:0 dropped:0 overruns:0 frame:0
TX packets:152 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:16768 (16.3 KiB) TX bytes:16768 (16.3 KiB)
mon.wlan0 Link encap:UNSPEC HWaddr C0-3F-0E-8D-95-BF-00-48-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:30128 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5059717 (4.8 MiB) TX bytes:0 (0.0 B)
pppoe-wan Link encap:Point-to-Point Protocol
inet addr:94.21.148.49 P-t-P:10.0.0.1 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:1552951 errors:0 dropped:0 overruns:0 frame:0
TX packets:2665665 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:99874242 (95.2 MiB) TX bytes:1622526298 (1.5 GiB)
sixxs0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: 2a01:368:e100:d::2/64 Scope:Global
inet6 addr: fe80::68:e100:d:2/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1
RX packets:151 errors:0 dropped:0 overruns:0 frame:0
TX packets:161 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:16240 (15.8 KiB) TX bytes:13640 (13.3 KiB)
wlan0 Link encap:Ethernet HWaddr C0:3F:0E:8D:95:BF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2672923 errors:0 dropped:0 overruns:0 frame:0
TX packets:1562671 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1662193994 (1.5 GiB) TX bytes:158117989 (150.7 MiB)
wlan1 Link encap:Ethernet HWaddr C6:3F:0E:8D:95:BF
inet addr:169.254.1.1 Bcast:169.254.255.255 Mask:255.255.0.0
inet6 addr: fe80::c43f:eff:fe8d:95bf/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:10316 (10.0 KiB)
Problem with tunnel
Shadow Hawkins on Thursday, 28 July 2011 19:27:19
Indeed, now it works great.
I don't know what was the problem, because I didn't change anything.
|
![[ch]](/s/countries/ch.gif)
on Thursday, 28 July 2011 15:40:52
Posting is only allowed when you are