TZUTC: -0400   
   MSGID: 191.fidonet_ipv6@1:142/103 25cafe84   
   REPLY: 3:770/100 31122f42   
   PID: Synchronet 3.18a-Linux  Aug 23 2020 GCC 6.3.0   
   TID: SBBSecho 3.11-Linux r3.177 Aug 23 2020 GCC 6.3.0   
   CHRS: ASCII 1   
   -=> Paul Hayton wrote to Tommi Koivula <=-   
      
    PH> On 11 Oct 2021 at 08:43p, Tommi Koivula pondered and said...   
      
    TK> His tunnel is working, he can make outbound connections. So the protocal   
    TK> 41 is open to the tunnel endpoint computer. (PI).   
      
    PH> I can also ping the Debian box via the Pi endpoint tunnel using IPv6...   
    PH> so I figure things must almost be working as I can reach the system   
    PH> from the internet via IPv6 and the tunnel using ping   
      
   Question:   
   Is one native IPv6 and the other endpoint a 6-to-4 tunnel? This *may* be an   
   issue. Using IPv4 as a test would help. I know natively on my access node   
   I can not ssh to it using it's tunneled IPs because the MTU doesn't match. If   
   I use a direct IP connection there's no issues at all... and again the MTU   
   matches at 1500 not 1480 as a tunneled link would. Could this perhaps be   
   an issue? Just thinking out loud :)   
      
   ... MultiMail, the new multi-platform, multi-format offline reader!   
   --- MultiMail/Linux v0.52   
    * Origin: SBBS - Carnage! 2001:470:8a1e::3 (1:142/103)   
   SEEN-BY: 1/19 123 16/0 30/0 80/1 90/1 105/81 120/340 123/130 131 124/5016   
   SEEN-BY: 142/0 103 153/757 154/10 201/0 203/0 2 124 221/0 1 6 226/30   
   SEEN-BY: 227/702 229/424 426 428 550 664 700 230/0 240/1120 5832 249/206   
   SEEN-BY: 249/317 400 261/38 280/464 5003 5006 5555 282/464 1038 292/854   
   SEEN-BY: 292/8125 301/0 1 101 113 812 310/31 317/3 320/119 219 319   
   SEEN-BY: 322/0 757 342/200 423/120 460/58 633/280 712/848 770/1 920/1   
   SEEN-BY: 2452/250 3634/24 5020/545 1042 5058/104   
   PATH: 142/103 320/219 203/0 280/464 301/1 229/426