https://bugzilla.novell.com/show_bug.cgi?id=546632 https://bugzilla.novell.com/show_bug.cgi?id=546632#c53 --- Comment #53 from Reinhard Max <max@novell.com> 2010-10-07 17:30:14 CEST --- (In reply to comment #50)
I do not see what the whole isssue has to do with Xvnc.
Well, this bug report here was about remote administration based on Xvnc. Only during debugging it turned out that the the problem was caused by the xdmcp client code in X.org. By posting your patches here, you proposed them as a fix to that particular problem. We tested them and found that they didn't fix the problem at hand, so we didn't use them. Also, they looked to me more like a workaround rather than a fix (one shouldn't have to hand-craft IPv4 mapped addresses), but I didn't have a closer look, because they didn't fix our problem and I wasn't aware that you meant them to fix something else.
If Xvnc cannot handle IPv6 then this is a bug in Xvnc that should be fixed. There is no reason why xdm or kdm should not get the IPv6 address.
It is not Xvnc itself, but the xdmcp implementation in the X.org server code that was using IPv6 link local addresses (FE80::/64) as display addresses. But these addresses are only meant to be used during IPv6 auto configuration and are mostly unusable for normal network communication (details available on request). That's why we changed the xdmcp client code to skip these addresses. Other types of IPv6 addresses are not affected by this change, i.e. the X server still uses them as potential display addresses when building the list for the display manager. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.