Hello,

Quote:
3) In previous versions, if a /server -46 switch was not specified but you specified an ipv4/ipv6 address, /server remained neutral and used the global ipv4/ipv6 setting. In the next version, if -46 is not specified, /server will base its ipv4/ipv6 context on the IP address type. This will affect the context of /dns, /sockopen, etc.
Some feedbacks:

/server wasn't so much neutral before, the global setting allows for ipv4 resolution, that is, /dns domain.com can be resolved to ipv4 (no -4 switch on /dns) but /server with an ipv6 address wasn't making this /dns works. It was with the -4 switch, which is still the case currently.

Quote:
/server will base its ipv4/ipv6 context on the IP address type
I don't know what this means but something is certain, this context is a different mode than the others two:

global mode:
(1)connected to ipv4 address or non connected: can access ipv4 addresses without -4 switch
(2)connected to ipv6 address: can access ipv4 address with -4 switch only

(3)local mode: cannot access ipv4 at all.


I don't understand why this context (2) results in people not being able to resolve ipv4 without -4, is this by design or a bug?

It looks like -4 is useful only in this (2) mode, where its meaning is to 'force ipv4 resolution when in mode (2)'.

I believe the purpose of the global mode is to always have a fallback on ipv4, this is not the case here, is it incorrect to think that?



Last edited by Wims; 26/11/18 11:06 PM.
#mircscripting @ irc.swiftirc.net == the best mIRC help channel