[bind10-dev] BIND10 build failing on OS X

Jeremy C. Reed jreed at isc.org
Thu Feb 24 14:52:58 UTC 2011


On Thu, 24 Feb 2011, Stephen Morris wrote:

> Jeremy
> 
> As you know, the asiolink unit tests are failing on the OS/X system.
> 
> The problem I have is that they work on my MacBook Pro.  However, I do
> notice that when I run the tests I get the "application firewall" dialog
> flashing up (and disappearing), presumably because these tests are
> setting up sockets and communicating over them.  For that reason, I'm
> wondering whether the problem on the Mac test system is a firewall
> setting rather than a problem with the code.
> 
> I believe that there are two firewalls in OS X, the main one controlled
> by ipfw(8) and an application one, accessible from the system
> preferences panel. (I believe the latter controls incoming connections
> only.)  I suspect that it is the application firewall causing the
> problem: could you try disabling that and re-running the test?  If you
> can't access system preferences over the network, it appears to be
> possible to disable it globally - see
> http://hints.macworld.com/article.php?story=20080110103812947.
> 
> If this still fails, can you create an account on that machine for me
> (eight steps to do that if I recall the Jabber conversation between
> Jelte and yourself correctly) and I'll go in and look at it there.
> 
> Thanks
> 
> Stephen

(I replied to private email with permission.)

The box does have a ipfw ruleset, but timestamps (-t) are empty and 
counters are "0" -- it is not used. I also have:

# defaults read /Library/Preferences/com.apple.alf globalstate 
0

The test appears to use 127.0.0.1 port 5301. Just to make sure, I am 
able to use b10-auth on that fine.

(I am creating an account for Stephen.)

  Jeremy C. Reed
  ISC



More information about the bind10-dev mailing list