IPV6 forwards FritzBox (DS-LITE) <-> OpenWrt <-> LAN machine

Try this:

uci set network.lan.ip6assign='62'
uci commit network
ifup lan

Still the same.
Interface in LUCI shows that now I have a /62 prefix on LAN.
ifstatus and odhcpd still show the same:

ifup wan6; sleep 10; ifstatus wan6; logread -e odhcpd
{
	"up": true,
	"pending": false,
	"available": true,
	"autostart": true,
	"dynamic": false,
	"uptime": 7,
	"l3_device": "eth1.2",
	"proto": "dhcpv6",
	"device": "eth1.2",
	"updated": [
		"addresses",
		"routes",
		"prefixes",
		"data"
	],
	"metric": 0,
	"dns_metric": 0,
	"delegation": false,
	"ipv4-address": [
		
	],
	"ipv6-address": [
		{
			"address": "2001:xxxx:xxxx:fe00:58ef:68ff:feb7:6acc",
			"mask": 64,
			"preferred": 3590,
			"valid": 7190
		}
	],
	"ipv6-prefix": [
		{
			"address": "2001:xxxx:xxxx:fef0::",
			"mask": 60,
			"preferred": 3593,
			"valid": 7193,
			"class": "wan6",
			"assigned": {
				
			}
		}
	],
	"ipv6-prefix-assignment": [
		
	],
	"route": [
		{
			"target": "2001:xxxx:xxxx:fe00::",
			"mask": 64,
			"nexthop": "::",
			"metric": 256,
			"valid": 7190,
			"source": "::/0"
		},
		{
			"target": "2001:xxxx:xxxx:fe00::",
			"mask": 64,
			"nexthop": "fe80::eadf:70ff:feea:d468",
			"metric": 512,
			"valid": 1790,
			"source": "::/0"
		},
		{
			"target": "::",
			"mask": 0,
			"nexthop": "fe80::eadf:70ff:feea:d468",
			"metric": 512,
			"valid": 1790,
			"source": "2001:xxxx:xxxx:fef0::/60"
		},
		{
			"target": "::",
			"mask": 0,
			"nexthop": "fe80::eadf:70ff:feea:d468",
			"metric": 512,
			"valid": 1790,
			"source": "2001:xxxx:xxxx:fe00:58ef:68ff:feb7:6acc/64"
		}
	],
	"dns-server": [
		"fd00::eadf:70ff:feea:d468"
	],
	"dns-search": [
		
	],
	"neighbors": [
		
	],
	"inactive": {
		"ipv4-address": [
			
		],
		"ipv6-address": [
			
		],
		"route": [
			
		],
		"dns-server": [
			
		],
		"dns-search": [
			
		],
		"neighbors": [
			
		]
	},
	"data": {
		"passthru": "0038001400010010fd00000000000000eadf70fffeead46800170010fd00000000000000eadf70fffeead46800560010200116b82dbdfe00eadf70fffeead468"
	}
}
Mon Jan  4 15:27:24 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 15:27:40 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 15:27:56 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 15:36:25 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 15:36:32 2021 daemon.info dnsmasq[5601]: read /tmp/hosts/odhcpd - 3 addresses
Mon Jan  4 15:39:14 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 15:41:35 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 15:51:18 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 16:00:20 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 16:04:11 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 16:10:52 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 16:16:01 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 16:19:56 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 16:27:36 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 16:35:34 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 16:39:19 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 16:48:30 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 16:54:08 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 16:58:28 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 17:07:36 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 17:12:04 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 17:18:23 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 17:23:40 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 17:28:04 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 17:35:22 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 17:39:19 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 17:45:38 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 17:53:29 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 17:58:35 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 18:02:20 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 18:09:28 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 18:14:00 2021 daemon.err odhcpd[2188]: setsockopt(IPV6_ADD_MEMBERSHIP): No such device
Mon Jan  4 18:14:00 2021 daemon.err odhcpd[2188]: setsockopt(SO_BINDTODEVICE): No such device
Mon Jan  4 18:14:00 2021 daemon.info dnsmasq[5601]: read /tmp/hosts/odhcpd - 3 addresses
Mon Jan  4 18:14:00 2021 daemon.info dnsmasq[5601]: read /tmp/hosts/odhcpd - 3 addresses
Mon Jan  4 18:14:01 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 18:14:01 2021 daemon.err odhcpd[2188]: Failed to send to ff02::1%lan@br-lan (Address not available)
Mon Jan  4 18:14:02 2021 daemon.info dnsmasq[5601]: read /tmp/hosts/odhcpd - 3 addresses
Mon Jan  4 18:14:17 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 18:14:33 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 18:14:49 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 18:16:04 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!

Remove this from wan6 interface...
And restore the ip6assign 60 on the lan.

I just did, but nothings seems to have changed (other than having a /60 prefix on LAN again).

uci show network.wan6; uci show network.lan; ifup wan6; ifup lan; sleep 10; ifstatus wan6; logread -e odhcpd

uci show network.wan6; uci show network.lan; ifup wan6; ifup lan; sleep 10; ifstatus wan6; logread -e odhcpd
network.wan6=interface
network.wan6.ifname='eth1.2'
network.wan6.proto='dhcpv6'
network.wan6.delegate='0'
network.wan6.reqaddress='try'
network.wan6.reqprefix='60'
network.lan=interface
network.lan.type='bridge'
network.lan.ifname='eth0.1'
network.lan.proto='static'
network.lan.ipaddr='192.168.1.1'
network.lan.netmask='255.255.255.0'
network.lan.force_link='0'
network.lan.ip6assign='60'
{
	"up": true,
	"pending": false,
	"available": true,
	"autostart": true,
	"dynamic": false,
	"uptime": 5,
	"l3_device": "eth1.2",
	"proto": "dhcpv6",
	"device": "eth1.2",
	"updated": [
		"addresses",
		"routes",
		"prefixes",
		"data"
	],
	"metric": 0,
	"dns_metric": 0,
	"delegation": false,
	"ipv4-address": [
		
	],
	"ipv6-address": [
		{
			"address": "2001:x:x:fe00:58ef:68ff:feb7:6acc",
			"mask": 64,
			"preferred": 3592,
			"valid": 7192
		}
	],
	"ipv6-prefix": [
		{
			"address": "2001:x:x:fef0::",
			"mask": 60,
			"preferred": 3595,
			"valid": 7195,
			"class": "wan6",
			"assigned": {
				
			}
		}
	],
	"ipv6-prefix-assignment": [
		
	],
	"route": [
		{
			"target": "2001:x:x:fe00::",
			"mask": 64,
			"nexthop": "::",
			"metric": 256,
			"valid": 7192,
			"source": "::/0"
		},
		{
			"target": "2001:x:x:fe00::",
			"mask": 64,
			"nexthop": "fe80::eadf:70ff:feea:d468",
			"metric": 512,
			"valid": 1792,
			"source": "::/0"
		},
		{
			"target": "::",
			"mask": 0,
			"nexthop": "fe80::eadf:70ff:feea:d468",
			"metric": 512,
			"valid": 1792,
			"source": "2001:x:x:fef0::/60"
		},
		{
			"target": "::",
			"mask": 0,
			"nexthop": "fe80::eadf:70ff:feea:d468",
			"metric": 512,
			"valid": 1792,
			"source": "2001:x:x:fe00:58ef:68ff:feb7:6acc/64"
		}
	],
	"dns-server": [
		"fd00::eadf:70ff:feea:d468"
	],
	"dns-search": [
		
	],
	"neighbors": [
		
	],
	"inactive": {
		"ipv4-address": [
			
		],
		"ipv6-address": [
			
		],
		"route": [
			
		],
		"dns-server": [
			
		],
		"dns-search": [
			
		],
		"neighbors": [
			
		]
	},
	"data": {
		"passthru": "0038001400010010fd00000000000000eadf70fffeead46800170010fd00000000000000eadf70fffeead46800560010200116b82dbdfe00eadf70fffeead468"
	}
}
Mon Jan  4 18:22:54 2021 daemon.info dnsmasq[5601]: read /tmp/hosts/odhcpd - 0 addresses
Mon Jan  4 18:22:54 2021 daemon.info dnsmasq[5601]: read /tmp/hosts/odhcpd - 0 addresses
Mon Jan  4 18:22:55 2021 daemon.err odhcpd[2188]: setsockopt(IPV6_ADD_MEMBERSHIP): No such device
Mon Jan  4 18:22:55 2021 daemon.err odhcpd[2188]: setsockopt(SO_BINDTODEVICE): No such device
Mon Jan  4 18:22:55 2021 daemon.info dnsmasq[5601]: read /tmp/hosts/odhcpd - 3 addresses
Mon Jan  4 18:22:56 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 18:22:56 2021 daemon.err odhcpd[2188]: Failed to send to ff02::1%lan@br-lan (Address not available)
Mon Jan  4 18:22:57 2021 daemon.info dnsmasq[5601]: read /tmp/hosts/odhcpd - 3 addresses
Mon Jan  4 18:23:12 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 18:23:24 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 18:23:29 2021 daemon.info dnsmasq[5601]: read /tmp/hosts/odhcpd - 0 addresses
Mon Jan  4 18:23:29 2021 daemon.err odhcpd[2188]: setsockopt(IPV6_ADD_MEMBERSHIP): No such device
Mon Jan  4 18:23:29 2021 daemon.err odhcpd[2188]: setsockopt(SO_BINDTODEVICE): No such device
Mon Jan  4 18:23:29 2021 daemon.info dnsmasq[5601]: read /tmp/hosts/odhcpd - 3 addresses
Mon Jan  4 18:23:30 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 18:23:30 2021 daemon.err odhcpd[2188]: Failed to send to ff02::1%lan@br-lan (Address not available)
Mon Jan  4 18:23:31 2021 daemon.info dnsmasq[5601]: read /tmp/hosts/odhcpd - 3 addresses
Mon Jan  4 18:23:46 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 18:23:53 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 18:29:24 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!
Mon Jan  4 18:30:31 2021 daemon.err odhcpd[2188]: setsockopt(IPV6_ADD_MEMBERSHIP): No such device
Mon Jan  4 18:30:31 2021 daemon.err odhcpd[2188]: setsockopt(SO_BINDTODEVICE): No such device
Mon Jan  4 18:30:31 2021 daemon.info dnsmasq[5601]: read /tmp/hosts/odhcpd - 3 addresses
Mon Jan  4 18:30:31 2021 daemon.info dnsmasq[5601]: read /tmp/hosts/odhcpd - 3 addresses
Mon Jan  4 18:30:32 2021 daemon.err odhcpd[2188]: Failed to send to ff02::1%lan@br-lan (Address not available)
Mon Jan  4 18:30:33 2021 daemon.info dnsmasq[5601]: read /tmp/hosts/odhcpd - 3 addresses
Mon Jan  4 18:30:37 2021 daemon.warn odhcpd[2188]: A default route is present but there is no public prefix on lan thus we don't announce a default route!

Seems that the option
network.wan6.delegate='0'
remains when I delete that in the WAN section.
Do I need an separate entry in "/etc/config/network" for WAN6?
If so, should I set any other options?

uci del network.wan6.delegate; uci commit network; ifup wan6; sleep 10; ifstatus wan6

uci set network.wan6.delegate='1'; uci commit network; ifup wan6; sleep 10; ifstatus wan6
{
	"up": true,
	"pending": false,
	"available": true,
	"autostart": true,
	"dynamic": false,
	"uptime": 6,
	"l3_device": "eth1.2",
	"proto": "dhcpv6",
	"device": "eth1.2",
	"updated": [
		"addresses",
		"routes",
		"prefixes",
		"data"
	],
	"metric": 0,
	"dns_metric": 0,
	"delegation": true,
	"ipv4-address": [
		
	],
	"ipv6-address": [
		{
			"address": "2001:x:x:fe00:58ef:68ff:feb7:6acc",
			"mask": 64,
			"preferred": 3590,
			"valid": 7190
		}
	],
	"ipv6-prefix": [
		{
			"address": "2001:x:x:fef0::",
			"mask": 60,
			"preferred": 3594,
			"valid": 7194,
			"class": "wan6",
			"assigned": {
				"lan": {
					"address": "2001:x:x:fef0::",
					"mask": 60
				}
			}
		}
	],
	"ipv6-prefix-assignment": [
		
	],
	"route": [
		{
			"target": "2001:x:x:fe00::",
			"mask": 64,
			"nexthop": "::",
			"metric": 256,
			"valid": 7190,
			"source": "::/0"
		},
		{
			"target": "2001:x:x:fe00::",
			"mask": 64,
			"nexthop": "fe80::eadf:70ff:feea:d468",
			"metric": 512,
			"valid": 1790,
			"source": "::/0"
		},
		{
			"target": "::",
			"mask": 0,
			"nexthop": "fe80::eadf:70ff:feea:d468",
			"metric": 512,
			"valid": 1790,
			"source": "2001:x:x:fef0::/60"
		},
		{
			"target": "::",
			"mask": 0,
			"nexthop": "fe80::eadf:70ff:feea:d468",
			"metric": 512,
			"valid": 1790,
			"source": "2001:x:x:fe00:58ef:68ff:feb7:6acc/64"
		}
	],
	"dns-server": [
		"fd00::eadf:70ff:feea:d468"
	],
	"dns-search": [
		
	],
	"neighbors": [
		
	],
	"inactive": {
		"ipv4-address": [
			
		],
		"ipv6-address": [
			
		],
		"route": [
			
		],
		"dns-server": [
			
		],
		"dns-search": [
			
		],
		"neighbors": [
			
		]
	},
	"data": {
		"passthru": "0038001400010010fd00000000000000eadf70fffeead46800170010fd00000000000000eadf70fffeead46800560010200116b82dbdfe00eadf70fffeead468"
	}
}

That seems to have done the job:

I have no on LAN a prefix, and my desktop gets assigned a public ipv6.

However, all the tests still fail:

ping ipv6.google.com resolves the address but times out...

Check with tcpdump what is going on:
opkg update; opkg install tcpdump; tcpdump -i any -evn icmp6
then start a ping from a lan host.

I had already tcpdump-mini package installed, so I used that.
On my LAN host I then did ping ipv6.google.com

ping ipv6.google.com                               
PING ipv6.google.com(fra15s24-in-x0e.1e100.net (2a00:1450:4001:820::200e)) 56 data bytes
^C
--- ipv6.google.com ping statistics ---
26 packets transmitted, 0 received, 100% packet loss, time 25581ms

And here are the last lines of the tcpdump output:

19:57:30.954322  In 70:85:c2:43:6d:9e ethertype 802.1Q (0x8100), length 124: vlan 1, p 0, ethertype IPv6, (flowlabel 0x5c3bf, hlim 255, next-header ICMPv6 (58) payload length: 64) 2001:x:x:fef0:c6d0:c48a:9ac5:92c2 > 2a00:1450:4001:820::200e: [icmp6 sum ok] ICMP6, echo request, seq 22
19:57:30.954322  In 70:85:c2:43:6d:9e ethertype IPv6 (0x86dd), length 120: (flowlabel 0x5c3bf, hlim 255, next-header ICMPv6 (58) payload length: 64) 2001:x:x:fef0:c6d0:c48a:9ac5:92c2 > 2a00:1450:4001:820::200e: [icmp6 sum ok] ICMP6, echo request, seq 22
19:57:30.954322  In 70:85:c2:43:6d:9e ethertype IPv6 (0x86dd), length 120: (flowlabel 0x5c3bf, hlim 255, next-header ICMPv6 (58) payload length: 64) 2001:x:x:fef0:c6d0:c48a:9ac5:92c2 > 2a00:1450:4001:820::200e: [icmp6 sum ok] ICMP6, echo request, seq 22
19:57:30.954368 Out 5a:ef:68:b7:6a:cc ethertype IPv6 (0x86dd), length 120: (flowlabel 0x5c3bf, hlim 254, next-header ICMPv6 (58) payload length: 64) 2001:x:x:fef0:c6d0:c48a:9ac5:92c2 > 2a00:1450:4001:820::200e: [icmp6 sum ok] ICMP6, echo request, seq 22
19:57:31.978276  In 70:85:c2:43:6d:9e ethertype 802.1Q (0x8100), length 92: vlan 1, p 0, ethertype IPv6, (hlim 255, next-header ICMPv6 (58) payload length: 32) fe80::7cb8:c30d:7eb0:f72b > fdd0:ca0e:f3b0::1: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has fdd0:ca0e:f3b0::1
	  source link-address option (1), length 8 (1): 70:85:c2:43:6d:9e
19:57:31.978276  In 70:85:c2:43:6d:9e ethertype IPv6 (0x86dd), length 88: (hlim 255, next-header ICMPv6 (58) payload length: 32) fe80::7cb8:c30d:7eb0:f72b > fdd0:ca0e:f3b0::1: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has fdd0:ca0e:f3b0::1
	  source link-address option (1), length 8 (1): 70:85:c2:43:6d:9e
19:57:31.978276  In 70:85:c2:43:6d:9e ethertype IPv6 (0x86dd), length 88: (hlim 255, next-header ICMPv6 (58) payload length: 32) fe80::7cb8:c30d:7eb0:f72b > fdd0:ca0e:f3b0::1: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has fdd0:ca0e:f3b0::1
	  source link-address option (1), length 8 (1): 70:85:c2:43:6d:9e
19:57:31.978343 Out 58:ef:68:b7:6a:cc ethertype IPv6 (0x86dd), length 80: (hlim 255, next-header ICMPv6 (58) payload length: 24) fdd0:ca0e:f3b0::1 > fe80::7cb8:c30d:7eb0:f72b: [icmp6 sum ok] ICMP6, neighbor advertisement, length 24, tgt is fdd0:ca0e:f3b0::1, Flags [router, solicited]
19:57:31.978348 Out 58:ef:68:b7:6a:cc ethertype IPv6 (0x86dd), length 80: (hlim 255, next-header ICMPv6 (58) payload length: 24) fdd0:ca0e:f3b0::1 > fe80::7cb8:c30d:7eb0:f72b: [icmp6 sum ok] ICMP6, neighbor advertisement, length 24, tgt is fdd0:ca0e:f3b0::1, Flags [router, solicited]
19:57:31.978357  In 70:85:c2:43:6d:9e ethertype 802.1Q (0x8100), length 124: vlan 1, p 0, ethertype IPv6, (flowlabel 0x5c3bf, hlim 255, next-header ICMPv6 (58) payload length: 64) 2001:x:x:fef0:c6d0:c48a:9ac5:92c2 > 2a00:1450:4001:820::200e: [icmp6 sum ok] ICMP6, echo request, seq 23
19:57:31.978357  In 70:85:c2:43:6d:9e ethertype IPv6 (0x86dd), length 120: (flowlabel 0x5c3bf, hlim 255, next-header ICMPv6 (58) payload length: 64) 2001:x:x:fef0:c6d0:c48a:9ac5:92c2 > 2a00:1450:4001:820::200e: [icmp6 sum ok] ICMP6, echo request, seq 23
19:57:31.978357  In 70:85:c2:43:6d:9e ethertype IPv6 (0x86dd), length 120: (flowlabel 0x5c3bf, hlim 255, next-header ICMPv6 (58) payload length: 64) 2001:x:x:fef0:c6d0:c48a:9ac5:92c2 > 2a00:1450:4001:820::200e: [icmp6 sum ok] ICMP6, echo request, seq 23
19:57:33.002286  In 70:85:c2:43:6d:9e ethertype 802.1Q (0x8100), length 124: vlan 1, p 0, ethertype IPv6, (flowlabel 0x5c3bf, hlim 255, next-header ICMPv6 (58) payload length: 64) 2001:x:x:fef0:c6d0:c48a:9ac5:92c2 > 2a00:1450:4001:820::200e: [icmp6 sum ok] ICMP6, echo request, seq 24
19:57:33.002286  In 70:85:c2:43:6d:9e ethertype IPv6 (0x86dd), length 120: (flowlabel 0x5c3bf, hlim 255, next-header ICMPv6 (58) payload length: 64) 2001:x:x:fef0:c6d0:c48a:9ac5:92c2 > 2a00:1450:4001:820::200e: [icmp6 sum ok] ICMP6, echo request, seq 24
19:57:33.002286  In 70:85:c2:43:6d:9e ethertype IPv6 (0x86dd), length 120: (flowlabel 0x5c3bf, hlim 255, next-header ICMPv6 (58) payload length: 64) 2001:x:x:fef0:c6d0:c48a:9ac5:92c2 > 2a00:1450:4001:820::200e: [icmp6 sum ok] ICMP6, echo request, seq 24
19:57:33.002334 Out 5a:ef:68:b7:6a:cc ethertype IPv6 (0x86dd), length 120: (flowlabel 0x5c3bf, hlim 254, next-header ICMPv6 (58) payload length: 64) 2001:x:x:fef0:c6d0:c48a:9ac5:92c2 > 2a00:1450:4001:820::200e: [icmp6 sum ok] ICMP6, echo request, seq 24
19:57:34.026296  In 70:85:c2:43:6d:9e ethertype 802.1Q (0x8100), length 124: vlan 1, p 0, ethertype IPv6, (flowlabel 0x5c3bf, hlim 255, next-header ICMPv6 (58) payload length: 64) 2001:x:x:fef0:c6d0:c48a:9ac5:92c2 > 2a00:1450:4001:820::200e: [icmp6 sum ok] ICMP6, echo request, seq 25
19:57:34.026296  In 70:85:c2:43:6d:9e ethertype IPv6 (0x86dd), length 120: (flowlabel 0x5c3bf, hlim 255, next-header ICMPv6 (58) payload length: 64) 2001:x:x:fef0:c6d0:c48a:9ac5:92c2 > 2a00:1450:4001:820::200e: [icmp6 sum ok] ICMP6, echo request, seq 25
19:57:34.026296  In 70:85:c2:43:6d:9e ethertype IPv6 (0x86dd), length 120: (flowlabel 0x5c3bf, hlim 255, next-header ICMPv6 (58) payload length: 64) 2001:x:x:fef0:c6d0:c48a:9ac5:92c2 > 2a00:1450:4001:820::200e: [icmp6 sum ok] ICMP6, echo request, seq 25
19:57:34.026343 Out 5a:ef:68:b7:6a:cc ethertype IPv6 (0x86dd), length 120: (flowlabel 0x5c3bf, hlim 254, next-header ICMPv6 (58) payload length: 64) 2001:x:x:fef0:c6d0:c48a:9ac5:92c2 > 2a00:1450:4001:820::200e: [icmp6 sum ok] ICMP6, echo request, seq 25
^C
124 packets captured
132 packets received by filter
1 packet dropped by kernel

Thank you so much for your help, this is way over my head :slight_smile:
Once we figure out what went wrong, if you are still motivated, you might help me understand what I am doing.
As I understand it, we are now trying to find out where or how far packets are going.

Seems quite alright to me. OpenWrt got the packet from the lan host on the lan interface (1st line) and sent it to the wan interface (2nd line). This pattern keeps repeating, but no reply back from google. You'll have to check somehow on the Fritz what happens to the packets.

How to capture packets on the Fritzbox:
http://service.avm.de/help/de/FRITZ-Box-7560/015/hilfe_support

section "Paketmitschnitt erstellen"

2 Likes

Thanks @mpa for this information.
So I did the tcpdump, pinged google and captured packages on the fritzbox:


(there is 17 different connection for which I can capture the packages, and I am not quite sure which ones to use, so I dumped multiple ones.)

The result are .eth dumps, which all are a couple of MB big after a couple of seconds.
I then open them in wireshark and try to find the the packages belonging to my ping.
I guess, good filter options would be google's ipv6 or the associated "flowlabel".

The problem is, I have never used wireshark before and am rather overwhelmed. Also I don't feel like posting entire dumps online.

However, after some manual searching, I think I found the corresponding package in the dump of the "LAN" connection:

If anyone has a hint how to do so with wireshark, it might help, even though I think I will figure it out eventually :wink:

Will come back as soon as I have more information.

ipv6.addr == 2001:abcd:ef01::1 <- the lan host address here.

I only find records of the hosts address in the "lan" packet dump, and they all look like the second screenshot I posted.

The first four under "internet" don't show packages originating from the host.
All of the ones under "Netzwerkschnittstellen" that I have tried (besides LAN) are empty.

I haven't looked at all possible dumps. Any idea where to look explicitly?

Or how to proceed with the package captured from LAN?

On a side note:
ping ipv6.google.com from the OpenWRT itself works fine...

Since you can capture the ping from the OpenWrt, you should know which are the lan and wan interfaces of the Fritz.

These are echo requests, the replies are missing.

This can be bad. The Fritz might be dropping the packets.
Also have a look here.

To narrow down the large amount of packets, enter this filter expression:

icmp or icmpv6

It is also possible to build a more specific filter from a packet's properties:
In the “Packet Details” Pane, right-click on a field, for example:

Type: Echo (ping) reply (129)

and choose one of the filtering options from the pop-up menu.

Documentation about Display Filters:

https://www.wireshark.org/docs/wsug_html_chunked/ChWorkBuildDisplayFilterSection.html

1 Like

Dear all,

thanks to everyone who tried to help me out here. Since I could not figure it out, I decided to change ISP to a company that gives me a public ipv4. So my problems are solved now by other means.

Sorry I could not report anything better and thanks again.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.