Bug 403192 - IPV6 : fix local_only support
IPV6 : fix local_only support
Status: RESOLVED FIXED
Product: vino
Classification: Applications
Component: Server
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Vino Maintainer(s)
Vino Maintainer(s)
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2007-02-01 12:22 UTC by Mark McLoughlin
Modified: 2011-11-22 22:27 UTC (History)
6 users (show)

See Also:
GNOME target: ---
GNOME version: ---


Attachments
Fix localonly with protocol independent code. (2.47 KB, patch)
2008-09-10 18:39 UTC, Andreas Henriksson
none Details | Diff | Review
Fix localonly with protocol independent code (v2). (2.53 KB, patch)
2008-09-11 06:22 UTC, Andreas Henriksson
none Details | Diff | Review

Description Mark McLoughlin 2007-02-01 12:22:10 UTC
At the moment, with IPv6 enabled we only bind to the IPv6 loopback address in local_only mode. We also need an IPv4 socket to bind to the IPv4 loopback address.

Fix will be similar to that for bug #403183
Comment 1 Andreas Henriksson 2008-09-10 18:39:41 UTC
Created attachment 118456 [details] [review]
Fix localonly with protocol independent code.

Replace ipv6/ipv4 code with protocol independent code fixes the issue (atleast on linux, hopefully by explicitly disabling the IPV6_V6ONLY also BSD will be happy).

Patch against 2.22, but it looks like the code is the same in subversion trunk.
Comment 2 Andreas Henriksson 2008-09-11 06:22:06 UTC
Created attachment 118496 [details] [review]
Fix localonly with protocol independent code (v2).

Same patch as before, but don't forget to free memory (getaddrinfo -> freeaddrinfo).
Comment 3 Andreas Henriksson 2008-11-24 10:59:21 UTC
*poke*

Please consider applying the patch. =)
Comment 4 Jonh Wendell 2008-12-12 20:01:19 UTC
Patch committed in bug 403183 fixed this bug.
Comment 5 Sean Cavanaugh 2011-11-22 20:28:16 UTC
is this actually fixed?  I am seeing this error on Fedora 13 (I do a "lsof -i -P | grep -i "listen") and I can see the IPv6 port is binding instead of both ipv4 and ipv6... what is the fix, I don't understand how to patch this?  I did a "yum update vino" and it says all is ok... (super noob here)
Comment 6 David King 2011-11-22 22:27:03 UTC
Sean, this bug should have been fixed in Vino versions 2.26.0 and above. There was a related bug (bug 604809) that was fixed in Vino 3.0.1 and above (and 2.32.2). You may have to update to a newer version of Fedora if you wish to use an updated Vino version.

In future, please file a bug with your distribution first, as commenting on an old bug can create noise for those CCd on the bug

Note You need to log in before you can comment on or make changes to this bug.