[Pidgin] #17156: getsockname: Windows socket error #10014

[Pidgin]

#17156: getsockname: Windows socket error #10014
----------------------+------------------------------
 Reporter:  roti_343  |       Owner:  datallah
     Type:  defect    |      Status:  new
Milestone:            |   Component:  winpidgin (gtk)
  Version:  2.11.0    |  Resolution:
 Keywords:            |
----------------------+------------------------------

Comment (by stefanb):

 Another user reported the same issue and I have been able to reproduce it
 on my Windows VM with an IPv6 tunnel. I root caused it to
 `purple_network_get_port_from_fd()` being broken for IPv6 sockets on
 Windows, i.e. it always generates the mentioned error message and returns
 the default port 0. The SIP server then rejects our REGISTER requests
 immediately with error 504.

 I have implemented a workaround in SIPE using the guidance from the
 stackoverflow question for the Windows error. For details please see:

 * [https://stackoverflow.com/questions/861154/winsock-error-code-10014
 stackoverflow question about Windows socket error #10014]
 * [https://sourceforge.net/p/sipe/bugs/338/ SIPE bug #338]

 The libpurple code should be fixed using the same approach.

--
Ticket URL: <https://developer.pidgin.im/ticket/17156#comment:1>
Pidgin <https://pidgin.im>
Pidgin