Why debug a problem when you can upgrade, and have it go away? Why go into the hazzle of updating if it's unlikely to go away? Why update to 2.1.10 if the problem is known to be fixed in 2.1.9, which for me t's much easier to update to.

So I will have to take the hazzle of updating to 2.1.10 and see if the problem persists.

I guess you (a) didn't read my message, Sorry, I did read your message.

and (b) want to debug it yourself. That's sometimes the thing I end up with.

Exactly. So I upgraded and things got worse (or better, if you prefer consistency). Now, it doesn't honor the src_ipaddr setting no matter if I start with -sfxx -l stdout or whatever. What I gain are hundreds of messages like Failed binding to proxy address port 1000: Permission denied (note there are two spaces here^^, so this looks like an empty string surrounded by spaces) The only unusual thing I can find is that there is an interface alias address on the interface having as a primary address the src_ipaddr given. I'm somewhat, eh, reluctant to removing this alias at this time since this would mean losing one of my two DNS resolvers. What I could try later is using another interface's (one not having an alias) address as src_ipaddr and see if that is honoured or not. This all is on NetBSD/amd64 4.0.1 in case it matters.

I can post any configuration details or debugging output if that helps.

The alternative is to demand that *we* do the work to track it down. There seems to be some serious misunderstanding here. I was not asking for anybody to track down my problems. I'm used to track down my problems myself. I was simply asking whether this was a known issue or not. Had the problem gone away by upgrading to 2.1.10, it might have, in fact, still been there, only hidden by some random artifact. It might have reappeared with 2.1.11 or by some totally unrelated configuration change.

Failed binding to proxy address port 1000: Permission denied (note there are two spaces here^^ I' unsure why ip_ntoh fails (I don't get any "ip_ntoh: " errors), but turning off dns_lookups shows the default IP (the one to be used without ip_srcaddr) here.

Your configuration must be doing something odd. Yes. As specifying multiple identical src_ipaddr values for several home servers resulted in 2.1.7 not to start up properly, I (mis)understood the comment

# The rest of the configuration items listed here are optional, # and do not have to appear in every home server definition. as if you could specify the values in the "localhost" home_server definition and then every other home_server section would pick up them as default. No, that's not what the wording suggests, but apperantly, it's how 2.1.7 worked -- at least in case of src_ipaddr and -X. I thought I had tried moving the src_ipaddr definitions to the individual home server sections earlier the day after I upgraded to 2.1.10, but I must have made some mistake I cannot reproduce. As you already pointed out further up in this thread, I like to debug things myself. So at least, there is a patch attached adding more debug output to proxy listener allocation and home server selection so the day I wasted on the subject may serve somebody else.