Ticket ID: SIXXS #697474 Ticket Status: Invalid PoP: simbx01 - Amis (Maribor)
POP does not route packets from my subnet
Shadow Hawkins on Thursday, 27 March 2008 15:56:20
Setup:
Home router acting as NAT between my LAN and ISP (ADSL connection).
heartbeat mode tunnel endpoint running on the same router.
tunnel id is T14647
I also have a subnet : R6338
the router runs radvd and my LAN host (usually) have working IPv6.
Problem:
After a DSL breakup everything works again except some IPv6 issues.
ping ipv6.google.com from the router : WORKS
On a host on the LAN :
ping cl-363.mbx-01.si.sixxs.net WORKS
ping gw-363.mbx-01.si.sixxs.net WORKS
ping ipv6.google.com does NOT work
I had a similar problem before and posted on the forum : https://noc.sixxs.net/forum/?msg=setup-694393
There Jeroen Massar said, that restarting the tunnel is not the correct solution and I should create a ticket instead.
- "aiccu test" results, all check (note: my router has no traceroute6, I used ping6 to test noc.sixxs.net and www.kame.net accessibility)
- OS info :
router: OpenWRT 1.0 (White Russian)
host: Windows 2003
- interface, routing and firewall tables
on the router :
# ifconfig sixxs
sixxs Link encap:UNSPEC HWaddr 5C-25-37-5B-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::5c25:375b/64 Scope:Link
inet6 addr: 2001:15c0:65ff:16a::2/64 Scope:Global
inet6 addr: fe80::c0a8:c801/64 Scope:Link
inet6 addr: fe80::a04:101/64 Scope:Link
inet6 addr: fe80::c0a8:101/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:384 (384.0 B) TX bytes:200 (200.0 B)
ifconfig br0 br0 Link encap:Ethernet HWaddr 00:13:D4:24:F6:4B
inet addr:192.168.200.1 Bcast:192.168.200.255 Mask:255.255.255.0
inet6 addr: fe80::213:d4ff:fe24:f64b/64 Scope:Link
inet6 addr: 2001:15c0:669b:1234::33/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5838894 errors:0 dropped:0 overruns:0 frame:0
TX packets:6655062 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2419926145 (2.2 GiB) TX bytes:1565696693 (1.4 GiB)
ip -f inet6 route 2001:15c0:65ff:16a::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220
2001:15c0:669b:1234::/64 dev br0 metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1220
fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1220
fe80::/64 dev br0 metric 256 mtu 1500 advmss 1220
fe80::/64 dev vlan0 metric 256 mtu 1500 advmss 1220
fe80::/64 dev vlan1 metric 256 mtu 1500 advmss 1220
fe80::/64 dev wds0.49153 metric 256 mtu 1500 advmss 1220
fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220
ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1220
ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1220
ff00::/8 dev br0 metric 256 mtu 1500 advmss 1220
ff00::/8 dev vlan0 metric 256 mtu 1500 advmss 1220
ff00::/8 dev vlan1 metric 256 mtu 1500 advmss 1220
ff00::/8 dev wds0.49153 metric 256 mtu 1500 advmss 1220
ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220
default via 2001:15c0:65ff:16a::1 dev sixxs metric 1024 mtu 1280 advmss 1220
cat /etc/radvd.conf
interface br0
{
AdvSendAdvert on;
# Disable Mobile IPv6 support
AdvHomeAgentFlag off;
prefix 2001:15c0:669b:1234::/64
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr off;
};
};
I have no IPv6 related firewalling on the router.
host setup :
C:\Documents and Settings\Administrator>route print
IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 1e 8c 07 41 53 ...... Marvell Yukon 88E8056 PCI-E Gigabit Ethernet
Controller
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.200.1 192.168.200.20 10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.200.0 255.255.255.0 192.168.200.20 192.168.200.20 10
192.168.200.20 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.200.255 255.255.255.255 192.168.200.20 192.168.200.20 10
224.0.0.0 240.0.0.0 192.168.200.20 192.168.200.20 10
255.255.255.255 255.255.255.255 192.168.200.20 192.168.200.20 1
Default Gateway: 192.168.200.1
===========================================================================
Persistent Routes:
None
IPv6 Route Table
===========================================================================
Interface List
5 ...ff ff ff ff ff ff ff ff Teredo Tunneling Pseudo-Interface
4 ...00 1e 8c 07 41 53 ...... Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Con
troller
3 ...00 1e 8c 07 ............ 6to4 Pseudo-Interface
2 ...c0 a8 c8 14 ............ Automatic Tunneling Pseudo-Interface
1 ........................... Loopback Pseudo-Interface
===========================================================================
===========================================================================
Active Routes:
If Metric Network Destination Gateway
2 1004 fe80::5efe:192.168.200.20/128
fe80::5efe:192.168.200.20
4 1004 2001:15c0:669b:1234:21e:8cff:fe07:4153/128
2001:15c0:669b:1234:21e:8cff:fe07:4153
4 1008 2001:15c0:669b:1234::/64 On-link
4 1256 ::/0 fe80::213:d4ff:fe24:f64b
5 1004 fe80::ffff:ffff:fffd/128 fe80::ffff:ffff:fffd
4 1008 ff00::/8 On-link
4 1004 fe80::21e:8cff:fe07:4153/128
fe80::21e:8cff:fe07:4153
1 1004 ::1/128 ::1
1 1008 ff00::/8 On-link
1 1004 fe80::1/128 fe80::1
===========================================================================
Persistent Routes:
None
C:\Documents and Settings\Administrator>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : lan
IP Address. . . . . . . . . . . . : 192.168.200.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 2001:15c0:669b:1234:21e:8cff:fe07:4153
IP Address. . . . . . . . . . . . : fe80::21e:8cff:fe07:4153%4
Default Gateway . . . . . . . . . : 192.168.200.1
fe80::213:d4ff:fe24:f64b%4
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%5
Default Gateway . . . . . . . . . :
Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . : lan
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.200.20%2
Default Gateway . . . . . . . . . :
NOTE: while running "aiccu test" for this report, somehow my tunnel broke (the sixxs interface disappeared). So I had no choice but to restart it ("aiccu stop ; aiccu start"), which, as described in the forum post, solved the problems.
PS: I have an idea how to simulate this situation again. Please advise.
State change: invalid
Jeroen Massar on Thursday, 27 March 2008 16:27:07
The state of this ticket has been changed to invalid
POP does not route packets from my subnet
Jeroen Massar on Thursday, 27 March 2008 16:29:39
It has nothing to do with the PoP. It is a problem in the AICCU client which has been resolved but has to be released for non-Windows platforms:
"Don't use a connected UDP socket for AYIYA and heartbeat traffic"
The "Tunnel Restart" you mentioned is a *CLIENT* restart, while the way you write it it looks like you are doing a tunnel up/down through the webinterface.
As you are behind a NAT you should be using AYIYA.
POP does not route packets from my subnet
Shadow Hawkins on Thursday, 27 March 2008 18:51:27
I am not behind a NAT.
POP does not route packets from my subnet
Jeroen Massar on Friday, 28 March 2008 11:11:51
You have to, as you have RFC1918 addresses on your interface, and they really won't work on the global internet.
POP does not route packets from my subnet
Shadow Hawkins on Friday, 28 March 2008 13:46:45
My tunnel endpoint is not behind NAT.
But it _is_ dynamic, that's why I use the heartbeat protocol instead of static.
Currently my IP address is 92.37.52.118 and as you will surely see, it does "work on the global internet". You can test by telnetting to it.
POP does not route packets from my subnet
Shadow Hawkins on Friday, 28 March 2008 13:48:48
By "it" in the second line I mean "the IP address of the host running aiccu".
POP does not route packets from my subnet
Jeroen Massar on Thursday, 10 April 2008 15:25:19
There are only RFC1918 addresses in your routing output.
As such, you can't have a public address on the localmachine, and you are behind a NAT.
POP does not route packets from my subnet
Shadow Hawkins on Monday, 19 May 2008 13:54:02
The PC is behind an IPV4 NAT.
The router is not.
I am at my workplace ;-)
I (and others, see forum) have this problem again. Is the new version of aiccu available yet ? http://downloads.openwrt.org/backports/0.9/ still has the old version.
Should I just restart aiccu ?
Regards,
David
Posting is only allowed when you are logged in. |