On Fri, Apr 18, 2008 at 04:46:02PM -0400, Janne Karhunen wrote: > On Fri, Apr 18, 2008 at 4:32 PM, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote: > > > > Sorry, not very clear. Perhaps statd should bind to the loopback > > > interface in addition to any other interfaces if it doesn't bind > > > to INADDR_ANY. > > > > Right, that's what would make the most sense to me. Janne, is there any > > reason that wouldn't solve your problem? > > I didn't get the idea. So the idea is to use multiple sockets, > one bound to LOOPBACK and one to external interface? I suppose so. One socket would be for communication for the local kernel nfsd, one for communication with statd peers. > Complicated and unclean in my opinion: one address > should suffice. The advantage is that it would require no changes to the kernel or kernel interfaces, and would also solve the problem for people that don't want to upgrade their kernels. The "rpc over lo" interface to the kernel's lockd is simple enough, and I'd rather not replace it with "rpc over either lo or the interface specified via sysctl" unless there's a really clear advantage. (Also, would your patch mean lockd could accept requests that could have spoofed source addresses?) --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
