Hi, I was unaware of the rcpinfo option. I knew nmap does RPC, but it is sometimes more comfortable to run it from rpcinfo than nmap. Cheers, On Wed, Jul 4, 2012 at 5:17 PM, Myklebust, Trond <Trond.Myklebust@xxxxxxxxxx> wrote: > On Wed, 2012-07-04 at 08:11 +0100, Leandro Meiners wrote: >> Sorry, I just noticed I replied to Chuck but forgot to CC the list. >> >> Cheers, >> Leandro >> >> >> ---------- Forwarded message ---------- >> From: Leandro Meiners <lmeiners@xxxxxxxxx> >> Date: Mon, Jul 2, 2012 at 3:52 PM >> Subject: Re: RPC rpcinfo command PATCH >> To: Chuck Lever <chuck.lever@xxxxxxxxxx> >> >> >> Hi, >> >> Guess I did it to follow the same convention as clnt_com_create(), but >> for no other particular reason. Basically it was useful because I used >> it to determine that the firewall was not filtering UDP connections to >> the portmapper (111/udp) but was filtering connections to the TCP >> portmapper (111/tcp). This allowed me to enumerate the RPC services >> running on the host and determine that the firewall was not blocking >> everything it should. > > 'rpcinfo -T udp hostname sunrpc' should suffice as a firewall probe. > 'nmap' has similar functionality. > > Cheers > Trond > -- > Trond Myklebust > Linux NFS client maintainer > > NetApp > Trond.Myklebust@xxxxxxxxxx > www.netapp.com > -- Leandro Federico Meiners -- 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
