REPLY: 2:280/5555 605c645a   
   MSGID: 2:221/6 605c9356   
   CHRS: UTF-8 4   
   TZUTC: 0200   
   TID: hpt/lnx 1.9.0-cur 2021-03-14   
   Hi Michiel.   
      
   25 Mar 21 11:02, you wrote to me:   
      
    TK>> ===   
    TK>> proxy privoxy.localnet:8118   
    TK>> ===   
      
    MV> Ah, now I get it. You use the http proxy feature of binkd! I never thought   
    MV> about that. I always skipped that section in the docs, thinking "I will   
   most   
    MV> likely never need that". I never realised it could be used for a 4to6   
   proxy as   
    MV> well. And the reason for that in turn is because I do not need a 4to6   
   proxy for   
    MV> my binkd. It handles IPv6 natively...   
      
    MV> Of course this trick only works for binkd. We see two "IO" flags in   
    MV> the list of   
    MV> IPv6 nodes. It is my understanding that they use a 6to4 relay for   
   incoming.   
    MV> They have no outgoing IPv6 for their binkd client. They both run Radius.   
   Your   
    MV> trick won't work for them...   
      
   Radius can use http proxy as well. I have tested it. The only problem with it   
   is that it tries to resolve the address and it does not understand IPv6   
   address. I can poll you with Radius later when I get back home. :)   
      
   'Tommi   
      
   --- GoldED+/LNX 1.1.5-b20180707   
    * Origin: nntps://news.fidonet.fi (2:221/6)   
   SEEN-BY: 1/123 90/1 105/81 120/340 123/131 124/5016 154/10 203/0 221/0   
   SEEN-BY: 221/1 6 226/30 227/702 229/424 426 550 664 700 1016 240/5138   
   SEEN-BY: 240/5411 5824 5832 5853 249/206 317 400 280/464 5003 5006   
   SEEN-BY: 280/5555 282/1038 292/854 8125 310/31 317/3 320/219 322/757   
   SEEN-BY: 335/364 342/200 423/120 460/58 256 777 1124 5858 633/280   
   SEEN-BY: 712/848 770/1 2452/250 2454/119 4500/1 5020/545 1042 5054/30   
   PATH: 221/6 460/58 280/464 240/5832 229/426