[zeromq-dev] 0MQ/2.0-beta1 on OSX

Martin Sustrik sustrik at 250bpm.com
Sun Jan 17 19:48:16 CET 2010

Hi Asko,

> I had a look at this OS X PowerPC "issue" today, and it's not really  
> an issue at all.
> I was using "en0" blindly, without realizing it is wired Ethernet that  
> I don't have hooked up on this laptop. Using "en1" (wlan interface)  
> works.

Good to know it's not a bug!

> The trouble I see from your (ZeroMQ's) side is keeping first time  
> evaluators on a smooth run. Error messages for not getting the right  
> interface would work here - to make it look less like a bug / crash /  
> whatever. Something like:
> 	"Interface 'en0' is not currently available"
> And of course the mention you were placing on "eth0" vs. "en0" (on the  
> website) should cover "eth1" and "en1". At least.

This may be tricky. Interface name resolving is done in different ways 
on different OS platforms. On each platform you may get different set of 
errors. Still, we have to ensure that on 0MQ level the sematics of the 
error(s) are consistent across the platforms.

The quick hack would be to choose a single error code and document is as 
"error when resolving interface name". Any error encountered when 
resolving the name of the interface would then be converted into this error.

Would you like to have a look at this?

As for the text in HOWTO section on the website, it's planned to make it 
more detailed in the future. Discussion of interface naming on different 
platforms should certainly be included.

> *** Local looping on OS X:
> This is to clarify you how local looping works on OS X. Don't know if  
> this is important (maybe for initial evaluators it is):
> With "en0" or "en1" I must use the actual IP number. "localhost" or  
> won't work.
> For local looping there's a completely separate interface, "lo0":

Hm. Interesting. What's the IP of lo0 then? Maybe


More information about the zeromq-dev mailing list