> In Linux the bold can also set /proc/sys/net/ipv4/ip_nonlocal_bind to
1:[...]

Thanks Rune for that solution - it does indeed work and doesn't seem to
have any side-effects with having Spread, Wackamole, Pound, Apache and PHP
all on the same machine. This is such a useful tip, maybe it should go
in the Pound docs somewhere (or in the "Other Issues" section on the
Pound Web site)?

You can put it in your /etc/sysctl.conf on Red Hat-style distros too:

net.ipv4.ip_nonlocal_bind = 1

so that it'll be set as part of your next boot sequence. BTW, does anyone
know what apps would actually break by being able to bind to non-local
IPs (and if they are bound like that and the remote IP isn't a
Spread/Wackamole-style one that might eventually turn up, then that's
surely just a config error from whoever's setup that app?).

Richard K. Lloyd,           E-mail: rkl(at)connectinternetsolutions.com
Connect Internet Solutions,    WWW: http://www.connectinternetsolutions.com/
First Floor, Faraday House,
Liverpool Digital, 360 Edge Lane,
Liverpool,
Merseyside, UK. L7 9NJ

I think perhaps the worst that might happen is a daemon could bind to an
incorrect ip and you wouldn't receive an error.

So you have a little less protection from config mistakes... instead of
an immediately fatal condition, you'd just have something that looks
like it should work but doesn't.

Joseph Gooch
Sapphire Suite Product Manager
K12 Systems, Inc.
(866) 366-9540

[...]
[mailto:richard.lloyd(at)connectinternetsolutions.com][...]
to 1:[...]
to[...]
PHP[...]
anyone[...]
pound(at)apsis.ch.[...]