After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 523618 - DAAP client does not work with link-local IPv6 addresses
DAAP client does not work with link-local IPv6 addresses
Status: RESOLVED OBSOLETE
Product: banshee
Classification: Other
Component: DAAP
0.13.x
Other Linux
: Normal major
: 2.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-20 19:41 UTC by Sebastian Dröge (slomo)
Modified: 2009-05-31 08:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastian Dröge (slomo) 2008-03-20 19:41:59 UTC 
Hi,
with banshee from the stable branch the DAAP client feature doesn't work at all. It seems that banshee doesn't even try to open a connection to the share (it shows them though).

Using banshee as DAAP server works fine.
Comment 1 Sebastian Dröge (slomo) 2008-03-20 20:36:38 UTC 
Backtrace when adding a Console.WriteLine :)

System.Net.WebException: Error: ConnectFailure
  at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult) [0x00000] 
  at System.Net.HttpWebRequest.GetResponse () [0x00000] 
  at DAAP.ContentFetcher.FetchResponse (System.String path, Int64 offset, System.String query, System.Net.WebHeaderCollection extraHeaders, Int32 requestId, Boolean disableKeepalive) [0x00000] 
  at DAAP.ContentFetcher.Fetch (System.String path, System.String query, System.Net.WebHeaderCollection extraHeaders, Int32 requestId) [0x00000] 
  at DAAP.ContentFetcher.Fetch (System.String path) [0x00000] 
  at DAAP.Client..ctor (System.Net.IPAddress address, UInt16 port) [0x00000] 
  at DAAP.Client..ctor (DAAP.Service service) [0x00000] 
  at Banshee.Plugins.Daap.DaapSource+<>c__CompilerGenerated1.<Activate>c__15 () [0x00000] 
System.Net.WebException: Error: ConnectFailure
  at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult) [0x00000] 
  at System.Net.HttpWebRequest.GetResponse () [0x00000] 
  at DAAP.ContentFetcher.FetchResponse (System.String path, Int64 offset, System.String query, System.Net.WebHeaderCollection extraHeaders, Int32 requestId, Boolean disableKeepalive) [0x00000] 
  at DAAP.ContentFetcher.Fetch (System.String path, System.String query, System.Net.WebHeaderCollection extraHeaders, Int32 requestId) [0x00000] 
  at DAAP.ContentFetcher.Fetch (System.String path) [0x00000] 
  at DAAP.Client..ctor (System.Net.IPAddress address, UInt16 port) [0x00000] 
  at DAAP.Client..ctor (DAAP.Service service) [0x00000] 
  at Banshee.Plugins.Daap.DaapSource+<>c__CompilerGenerated1.<Activate>c__15 ()
Comment 2 Sebastian Dröge (slomo) 2008-03-20 21:12:23 UTC 
Ok, this is caused by the fact, that the shares all exist as IPv4 and IPv6 variant. For some reason the IPv6 variant is sometimes prefered and then things fail because I have no IPv6 network.

So it should either test all adresses that are given for a service or prefer IPv4 over IPv6...
Comment 3 Sebastian Dröge (slomo) 2008-03-20 22:15:38 UTC 
Ok, the problem is clear now. My IPv6 address is a link local address for which one needs to set the interface & the IP to do something useful.

So this is what should be done now:

Both, Bonjour and Avahi, give the interface index for their services. This should be exposed by Mono.Zeroconf at some place.

Then we need to create a connection where this interface index is used. It seems to be impossible with System.Net.HttpWebRequest but System.Net.Sockets.Socket seems to have a way: System.Net.Sockets.SocketOptionName.MulticastInterface.
Comment 4 Sebastian Dröge (slomo) 2008-03-20 23:46:51 UTC 
Ok, the part in Mono.Zeroconf should be fixed now... left is: https://bugzilla.novell.com/show_bug.cgi?id=372840
Comment 5 Gabriel Burt 2009-03-26 02:25:54 UTC 
Sebastian is this still a problem in 1.4?
Comment 6 Alexander Kojevnikov 2009-05-31 08:46:11 UTC 
Closing as OBSOLETE. Feel free to re-open if you are still seeing this issue.