MSGID: 2:240/5824.1@fidonet f81e88d8   
   REPLY: 2:280/5555 61d369e9   
   PID: OpenXP/5.0.51 (Linux) (x86_64)   
   CHRS: ASCII 1   
   TZUTC: 0100   
   Am 03.01.22 schrieb Michiel van der Vlist@2:280/5555 in IPV6:   
      
   Hallo Michiel,   
      
   AN>> This whole geolocation stuff is just meeehh...   
      
   MvdV> I had no problems since I got native IPv6 fom my provider six years ago.   
   MvdV> I only had problems with the he.net tunnel.   
   MvdV> The SixXs tunnel gave no problems.   
      
   I did not use SixXs, but it stopped its service anyway some years ago.   
   The he.net tunnel ran fine for many, many years - and I had my fixed     
   prefix where I even could provide my reverse DNS for.   
      
   The native IPv4+IPv6 connection from Telekom does work, but as it's     
   only a consumer-grade connection, I don't get fixed addresses or a     
   fixed prefix. But I found a workaround using Dynv6 :)   
      
   So my router (Fritz!Box) calls a script on one of my rented vServers     
   (via a https request), which in turn sets the IPv4 address and the     
   IPv6 prefix on Dynv6 and on my own DNS zone. And it seems to work fine     
   :)   
      
   Regards,   
   Anna   
      
   --- OpenXP 5.0.51   
    * Origin: Imzadi Box Point (2:240/5824.1)   
   SEEN-BY: 1/123 15/0 90/1 105/81 120/340 123/131 153/7715 226/30 229/424   
   SEEN-BY: 229/426 428 550 664 700 240/5138 5411 5824 5832 5853 249/206   
   SEEN-BY: 249/317 400 266/512 280/464 5555 282/1038 301/1 310/31 317/3   
   SEEN-BY: 320/219 322/757 342/200 396/45 633/280 2452/250 2454/119   
   PATH: 240/5824 5832 229/426