Pi Relay ipv6 - FritzBox

Support Relay Operator
1

Hello,

I decided to activate ipv6 on my pi relay (raspi 3b+, debian). Please help me configuring my network accordingly (FritzBox settings, torrc …)

  1. Tor-Projekt | Relay-Nachinstallation und bewährte Praktiken - Test fails: “tor-pi@tor-relay-pi:~ $ ping6 -c2 2001:858:2:2:aabb:0:563b:1526 && ping6 -c2 2620:13:4000:6000::1000:118 && ping6 -c2 2001:67c:289c::9 && ping6 -c2 2001:678:558:1000::244 && ping6 -c2 2001:638:a000:4140::ffff:189 && echo OK.
    PING 2001:858:2:2:aabb:0:563b:1526(2001:858:2:2:aabb:0:563b:1526) 56 data bytes

— 2001:858:2:2:aabb:0:563b:1526 ping statistics —
2 packets transmitted, 0 received, 100% packet loss, time 1027ms”

I investigated a couple of hours now and can`t find the issue. Please help.

  1. Hereby my FritzBox-settings, please advise if ok or need to be adjusted.

grafik
grafik1051×818 36.1 KB

  1. From provider-side, ipv6 is fixed. Do I manually need to make the suffix static in the FritzBox?

  2. Is it possible to leave the IPv6 (similar to IPv4) empty and the relay finds it on its own (e.g. if suffix is changing, see 3)? Or do I need to “hard-code” the ipv6 in the torrc?

Thanks and best regards

2

  1. Could you show us the output of ip a and ip -6 route show on your Pi?

  2. The setting “Firewall für delegierte IPv6-Präfixe dieses Gerätes öffnen” is only needed if your Pi acts as router and has its own ipv6 network. The portforwarding looks good.

  3. Not if the Fritzbox correctly gets the network through other means like dhcp from your provider.

  4. In my experience the relay will correctly find the ipv6 address when you start it, but for me ipv6 stops working, when the ipv6 address changes while the relay is running.

3

Hi,

yesterday I activated ipv6, but the pirelay stopped working and showed this flag: StaleDesc. ipv6 never showed up. So I just deactivated it again in the torrc.

….@….:~ $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether b8:27:eb:57:2c:72 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.36/24 brd 192.168.178.255 scope global dynamic noprefixroute eth0
valid_lft 65180sec preferred_lft 65180sec
inet6 2a02:578:85c0:1f00:3d5a:aea2:b315:73e8/64 scope global dynamic noprefixroute
valid_lft 7151sec preferred_lft 3551sec
inet6 fe80::93a8:bfb:ac5f:15e/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether b8:27:eb:02:79:27 brd ff:ff:ff:ff:ff:ff

….@….:~ $ ip -6 route show
2a02:578:85c0:1f00::/64 dev eth0 proto ra metric 100 pref medium
2a02:578:85c0:1f00::/56 via fe80::3a10:d5ff:febc:7527 dev eth0 proto ra metric 100 pref medium
fe80::/64 dev eth0 proto kernel metric 1024 pref medium
default via fe80::3a10:d5ff:febc:7527 dev eth0 proto ra metric 100 pref medium

4

The ipv6 address of your pi does not match the one you opened the port for on your fritzbox.

5

How do I solve that? Which IPv6 do I need to enter in the torrc?

6

You have to change the Address on your fritzbox to the actual IP you configured on your pi. You don’t need to configure the IP in your torrc, the relay will find it automatically, but if you do you have to use the IP configured on the pi.