Subj : Re: Feature request: soft IPv6 force
To   : Andrei Dzedolik
From : Alexandr Kruglikov
Date : Fri Apr 20 2018 07:40 pm

Good ${greeting_time}, Andrei!

*** Answering a msg posted in area CarbonArea (Mail for me).

20 Apr 18 12:43, you wrote to me:

 AK>> 3. if possible to make the choice of IPv6-only by means of a
 AK>> binkd, then why impossible to make priorities? =\
 AD> Did I say it is impossible? I proposed to discuss and find a common
 AD> ground before proposing chnges to the code :) You are reading
 AD> RU.HUSKY/RU.BINKD and should know our FTN community is picky on
 AD> patches and if you don't want to end up with 'BinkD-Plus', you have to
 AD> be prepared to defend your position.

Course, I know this community rule very well (and all engineers): If it works 
fine - don't touch anything there. =))

 AD> As for IPv6-only and IPv4-only, this is made by choosing an address
 AD> family, like AF_INET4, AF_INET6 or AF_INET and these are mutually
 AD> exclusive. Only in case AF_INET is proveded to 'getaddrinfo' it will
 AD> give yuo full, ordered list of endpoints to connect to. And mentioned
 AD> RFC3484 says order should be respected (should, not must).

Thanks for the explanation! I'm poorly versed in programming, and this is very 
informative. But is it not possible to do a check, for example, like this (I 
repeat, I'm weakly programming):

while(ip_is_present)
    {
if(rp->ai_family == AF_INET6)
else if(rp->ai_family == AF_INET)
    session = socket(rp->ai_family, rp->ai_socktype, 0);
if (session == FAILURE)
    continue;
}

that is, first try to use AF_INET6 and in case of connection failure - AF_INET?

 AD> So, is this statement correct:
 AD> 1. Introduce new configuration option for FTN node object to force
 AD> IPv6 or IPv4 precedence, disrespecting the OS rules for this node
 AD> only;

Yes, that's what we want! =)

 AD> 2. Introduce new command line argument to force current IPv6 or
 AD> IPv4 precedence for binkd process;

I do not see much point in this option. In my humble opinion =) it is better to 
configure each node individually.

 AD> 3. Intruduce new global configuration option to force IPv6 or IPv4
 AD> precedence;

I do not see any point in this option. =)

 AD> Is this all or am I missing something?

That's all. Maybe Michael will add something?

With best regards, Alexandr.

--- "GoldED+/LNX 1.1.5-b20170303" ---
 * Origin: 24 hours in a day, 24 beers in a case, Hmmm... (2:5053/58)

.