Confusing error message with sockets creation

Some users seem to be confused with ipv4/ipv6 warnings (damn, they've never used SSH ???).

added Component::Input: network streams Difficulty::easy Severity::trivial Type::bug Version::master git + 1 deleted label

(In [12232]) Don't print EAFNOSUPPORT error when the given name/address does not even resolve to IPv6 - though cosmetic that seemed to confuse a guy on the mailing list - refs #320 (closed).

A cleaner more clever solution would be better.

(In [12266]) Don't print EAFNOSUPPORT error - refs #320 (closed)

damn, do you really think more than 1% of our users already used SSH ??? and do you really think than more than 20% of this % already saw these messages, as they generally don't have IPv6 ???

You have a point. That said, only users of SAP or users of an IPv6-enabled server with an IPv6-unable VLC client would ever see the messages...

(In [12583]) * print unreachable host as an error in net_OpenTCP (refs #320 (closed))

• don't print IPv6 unreachable warning when IPv4 works fine
• don't attempt SOCKS negociation when TCP connection failed
• use "%s port %d" rather than "%s:%d" because the latter is confusing with IPv6 adresses
• removed trailing spaces

The only issue left is with UDP sockets handling that may cause "Destination unreachable" warnings when there is an IPv6 stack with no IPv6 connectivity, and a working IPv4 stack.

To fix this, network plugins have to be suppressed and merged in the core (not a good idea during a feature freeze), so I'm postponing this bug to the next version.

added Difficulty::hard label and removed Difficulty::easy label

changed milestone to %0.8.5-final

changed milestone to %0.8.5-test3

Still the same problem. As the bug is a side-effect of the modules stuff, reassigning to paradize

changed milestone to %Bugs paradize

changed milestone to %0.8.6

(In [14703]) Clean up ListenTCP error handling (refs #320 (closed))

unassigned @Courmisch

changed milestone to %Bugs paradize

added Status::fixed label

closed