TID: FMail-W32 2.1.3.7-B20170919   
   RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: CP850 2   
   MSGID: 2:280/5555 605c645a   
   REPLY: 2:221/360.0 605adaba   
   Hello Tommi,   
      
   On Wednesday March 24 2021 08:22, you wrote to me:   
      
    >> Where does that port 8118 come from?   
      
    TK> From the binkd configuration, of course. :)   
      
    TK> Port 8118 is the default port of privoxy.   
      
    TK> ===   
    TK> proxy privoxy.localnet:8118   
    TK> ===   
      
   Ah, now I get it. You use the http proxy feature of binkd! I never thought   
   about that. I always skipped that section in the docs, thinking "I will most   
   likely never need that". I never realised it could be used for a 4to6 proxy as   
   well. And the reason for that in turn is because I do not need a 4to6 proxy   
   for my binkd. It handles IPv6 natively...   
      
   Of course this trick only works for binkd. We see two "IO" flags in the list   
   of IPv6 nodes. It is my understanding that they use a 6to4 relay for incoming.   
   They have no outgoing IPv6 for their binkd client. They both run Radius. Your   
   trick won't work for them...   
      
      
   Cheers, Michiel   
      
   --- GoldED+/W32-MSVC 1.1.5-b20170303   
    * Origin: he.net certified sage (2:280/5555)   
   SEEN-BY: 1/123 19/10 90/1 105/81 120/340 123/131 203/0 221/0 6 226/30   
   SEEN-BY: 227/702 229/424 426 550 664 700 1016 240/5138 5411 5824 5832   
   SEEN-BY: 240/5853 249/206 317 400 250/1 280/464 5003 5006 5555 282/1038   
   SEEN-BY: 310/31 317/3 320/219 322/757 342/200 460/58 633/280 640/1384   
   SEEN-BY: 712/848 2452/250 2454/119 5019/40 5020/545 1042 12000 5053/58   
   PATH: 280/5555 240/5832 229/426