TID: FMail-W32 2.1.3.7-B20170919   
   TZUTC: 0200   
   CHRS: CP850 2   
   PID: GED+W32 1.1.5-b20170303   
   MSGID: 2:280/5555 61745a68   
   Hello Binkd team,   
      
   The bindaddr keyword is used to select the IP address for making outgoing   
   calls in case there is more than one IP address that the system can use. This   
   is usefull in case one has more binkd clients running on one and the same   
   system or when one wants to override the system default in order to present a   
   2001:DB8::f1d0:zone:net:node address instead of a SLAAC or random privacy   
   address.   
      
      
   The problem.   
   ------------   
      
   bindaddr works fine in a single stack envionment (IPv4 or IPv6 only) but it   
   encounters problems in a dual stack environment.   
      
   bindaddr accepts a literal address (IPv4 or IPv6) or a hostname. Specifying   
   multiple bindaddr lines in the config does not result in an error, but only   
   the last takes effect.   
      
   specifying:   
      
   bindaddr fido.vlist.eu   
      
   or   
      
   bindaddr [2001:1c02:1103:2a00:f1d0:2:280:5555]   
      
   Results in binkd using that address for outgoing IPv6 calls.   
      
   In the windows version it results in a warning when making outgoing IPv4   
   calls: "bind: {W32 API error 10049} The requested address is not valid in its   
   context" or ."bind -- getaddrinfo: Der angegebene Host ist unbekannt.  (11001)"   
      
   In the Linux version, the literal address must be specified without the square   
   brackets and attempts to make outgoing IPv4 calls fail. So one can not use   
   bindaddr to specify an outgoing IPv6 address without breaking outgoing IPv4   
   capability.   
      
      
   Proposed solution   
   -----------------   
      
   To remedie the situation I suggest to split up the bindaddr in an IPv6 and an   
   IPv4 part.   
      
   bindaddr6    
      
   This only affects the IPv6 address used for outpoing calls.   
      
   bindaddr4    
      
   This only affects the IPv4 address used for outgoing calls.   
      
   For backward compatibility bindaddr is an alias of bindaddr4   
      
   Or alternatively:   
      
   bindaddr -6    
      
   bindaddr -4    
      
      
   How about it?   
      
      
   Cheers, Michiel   
      
   ---   
    * Origin: http://www.vlist.eu (2:280/5555)   
   SEEN-BY: 1/123 14/0 30/0 80/1 90/1 103/705 105/81 114/709 120/340   
   SEEN-BY: 123/131 129/305 154/10 203/0 218/700 221/1 6 226/30 227/114   
   SEEN-BY: 229/200 424 426 550 664 700 240/1120 5832 249/109 206 307   
   SEEN-BY: 249/317 261/38 280/464 5003 5555 282/464 1038 292/854 301/0   
   SEEN-BY: 301/1 101 113 123 812 322/757 341/66 342/200 633/280 712/848   
   SEEN-BY: 920/1 5019/40 5020/1042 5053/58 5058/104   
   PATH: 280/5555 301/1 229/426