According to http://www.tldp.org/HOWTO/Multicast-HOWTO-6.html: "If the h... - #9
According to http://www.tldp.org/HOWTO/Multicast-HOWTO-6.html: "If the h...#9znek wants to merge 2 commits into
Conversation
|
Hey, could you list your OS X and FreeBSD machines interfaces? I'll do some testing when I have a test system with multiple interfaces |
|
The OS X 10.9.5 desktop: znek@optimist:(~)$ ifconfig -a The FreeBSD 10.1-STABLE server: znek@creutzfeld:(~)$ ifconfig -a |
|
@znek This's not forgotten - I had some other stuff to deal with but I think I'll merge this change with some configurability added soon (there are some differences between Windows, Linux and OS X/BSD as far as setsockopt is concerned and I'd like it to be as platform independent as possible). |
|
FYI it's in master now. |
|
FreeBSD didn't work out of the box, unfortunately. I've just pushed f84720e which solves an "Address already in use" conflict on a single interface from the list of all interfaces. Curiously, no interface has that IP address in the list assigned and I'm left to only guessing that this somehow has to do with the bridge configuration, but really I don't have a clue. |
|
I've also pushed 4c2a479 which iterates on all interfaces instead of just the default interface, because that's necessary on my server to conduct the builtin tests. Is there any specific good reason, why the Zeroconf class shouldn't iterate on all interfaces by default? Zeroconf is all about adhoc networkability, thus I don't see any real need to restrict it to just the default interface. This should remain optional, but not as a default IMO. |
|
@znek Sorry for the long delay, I'll sort out the issues you mentioned. There's no particular reason I set it to default interface only, I just kept the previous behaviour by default but after consideration I think I'll make it use all interfaces and release version with the changes soon. |
|
Just tested 44fa62a, appears to work fine. |
|
Thank you, I'll close this one then. |
These changes are required as a prerequisite on my FreeBSD box. I'v tested this on OS X as well (see comments). I don't expect these changes to break anything.
However, my original observation still stands: the Zeroconf class needs to iterate on all existing interfaces in order to work properly. The trick with the UDP connect catches just a single interface, which in my (special) case is the wrong (external) interface.