On Tue, 8 Jun 2004, Michael Blandford wrote: > Jeff Moyer wrote: > > >mlblandf> Would this patch cause problems for those of us who have icmp > >mlblandf> blocked? If so, could we make it a run time option to > >mlblandf> enable/disable? > > > >Wow, you block icmp internally? This would incur a timeout for every host > >listed in your replicated server entry, and with Ian's patch, it would > >incur a timeout for non-replicated servers, as well. In fact, for the > >non-replicated server case, I think it would give a false negative, failing > >the mount even though the server is up. > > > >Is this really how you have things configured? NFS clients can't ping > >their servers? > > > > > > In a large environment it wouldn't be uncommon to have NFS mounts that > span across a WAN. Using NFS over TCP seems to make the most sense in > that situation. > > As packets traverse the WAN, there may be routers that block icmp. This > is the type of situation where replicated server would make the most > sense - find the fastest server. >
I was thinking that we could make disabling ICMP ping a configure option. What do you think? Still, I can't see why an internal WAN would block ICMP. It's needed for proper operation of your net. If your talking about NFS over the public network you really should be using a VPN. In which case you don't need to (and probably shouldn't) block ICMP. Ian _______________________________________________ autofs mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/autofs
