search for: portmapper

An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20120304/04099724/attachment.html>

Hi, I'm resending since I got no feedback: I assume that the message was lost... The attached patch fixes a few bugs related to the spoofing portmapper used by nfsmount. Regards, Louis -- Dr Louis Rilling Kerlabs Skype: louis.rilling Batiment Germanium Phone: (+33|0) 6 80 89 08 23 80 avenue des Buttes de Coesmes http://www.kerlabs.com/ 35700 Rennes -------------- next part -------------- A non-text attachment was scrubbed... Name: fix-d...

...quot; # Optional arguments passed to rpc.svcgssd. See rpc.svcgssd(8) #RPCSVCGSSDARGS="" # # To enable RDMA support on the server by setting this to # the port the server should listen on #RDMA_PORT=20049 And rpcinfo -p: program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100003 4 tcp 2049 nfs 100003 4 udp 2049 nfs 100021 1 udp 557...

...ig] 0-vol_dr-client-3: changing port to 49155 (from 0) I ran gluster volume info and here are the options configured: Options Reconfigured: nfs.disable: off performance.readdir-ahead: on nfs.exports-auth-enable: on # rpcinfo -p program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 54233 status 100024 1 tcp 32813 status 100005 2 ud...

...g as well. But as I say, as soon as I disable the firewall, it mounts fine. Google search results reveal a lot of different ports, like 4000:4004, 83xxxx (something, I forgot) but it still doesn't help. root at saturn:[~]$ rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 48996 nlockmgr 100021 3 udp 48996 nlockmgr 100021 4 udp 48996 nlockmgr 100021 1 tcp 47195 nlockmgr 100021 3 tcp 47195 nlockmgr 100021 4 tcp 47195 nlockmgr 100011 1 udp...

...nfs_server = ''10.10.24.141 <http://10.10.24.141>'' nfs_root=''/nfsroot'' extra = "2" /etc/exports on NFS server ************************* /nfsroot *(rw,sync,no_root_squash) rpcinfo -p output on NFS server program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100021 1 udp 1090 nlockmgr 100021 3 udp 1090 nlockmgr 100021 4 udp 1090 nlockmgr 100021 1 tcp 1036 nlockmgr 100021 3 tcp 1036 nlockmgr 100021 4 tcp 1036 nlockmgr 100005 1 udp 738 moun...

...ons lockd nlm_udpport=1011 options lockd nlm_tcpport=1011 and then restarting the pormap service. I've even tried restarting the network service, but unfortunately nothing seems affected: [root at stallion:/etc/init.d] $ rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 55394 nlockmgr 100021 3 udp 55394 nlockmgr 100021 4 udp 55394 nlockmgr 100021 1 tcp 33704 nlockmgr 100021 3 tcp 33704 nlockmgr 100021 4 tcp 33704 nlockmgr 100024 1 udp...

Hello all, I have a server on my private network that is configured as an NIS server and mapped to a "public" IP address on a firewall. All other TCP ports (SSH, iperf, you name it) are visible from the outside - but the portmapper-managed ports (port 111 itself and the YPSERV/YPXFRD ports, etc.) are not visible from the outside - even though they are alive and well on the internal network. So, here's the question: is there anything special as far as portmapper's networking/security setup that is at play here? Thank...

...the kernel loads successfully and I can log in and use the system as you'd expect. I have done this before, however this time I decided to try using ClusterNFS so that the diskless clients can share the boot server's filesystem. Unfortunately during system boot up to test whether the RPC portmapper is loaded, the boot scripts run "rpcinfo -p" which causes the PC to sit there for about ten minutes and then eventually time out and continue with the boot process. This happens three times during boot, which needless to say means there's a *long* wait before I can log in. Does anyo...

...: next DNS query will return: ip-192.168.1.19 port-24007 [2017-08-20 20:30:40.466480] D [MSGID: 0] [common-utils.c:348:gf_resolve_ip6] 0-resolver: next DNS query will return: ip-192.168.1.19 port-24007 [2017-08-20 20:30:40.466482] D [socket.c:3050:socket_fix_ssl_opts] 0-glusterfs: disabling SSL for portmapper connection [2017-08-20 20:30:40.466490] D [socket.c:3050:socket_fix_ssl_opts] 0-glusterfs: disabling SSL for portmapper connection [2017-08-20 20:30:40.466699] I [MSGID: 101190] [event-epoll.c:602:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 [2017-08-20 20:30:40.466699] I [MSGI...

Hi all, I'm extremely puzzled by the behaviour of one of my Samba servers. It's been working fine for yonks, and this morning (abuout 11:32) it just stopped. (mostly) Connecting to shares still works. Navigating the tree till works. Changing (DOS) attributes still works. But actually opening files and reading the contents doesn't work. The client just times out (Win 3.11, and

...d 892/tcp statd 662/tcp rquotad 875/udp lockd 32803/udp lockd 32769/udp mountd 892/udp statd 662/udp [root at centos sy rpcinfo -p seems fine (although I understand that is not relevent with nfs4) [root at centos sysconfig]# rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 662 status 100024 1 tcp 662 status 100011 1 udp 875 rquotad 100011 2 udp 875 rquotad 100011 1 tcp 875 rquotad 100011 2 tcp 875 rquotad 100003 2 udp 2049 nf...

Are there any known vulnerabilities in portmap (redhat''s portmap-4.0-7b)? I''ve been receiving a lot of attempts to access the portmap port on some linuxppc machines I administer by various machines which clearly have no business with mine, and I wonder if this is an attempt to break in to my machines. I''ve searched some archives, but I haven''t yet found any

I have tried to replace these lines from ipchains to work with shorewall. # /NFS requires 111/tcp (sunrpc/portmapper) and *all* UDP ports./ # ipchains -A input -p tcp -s $SUBNET -i eth0 -d 0/0 111 -j ACCEPT ipchains -A input -p udp -s $SUBNET -i eth0 -d 0/0 -j ACCEPT # /These ports are required by bootp, tftpd, and PXE./ # /There are also a handful of udp ports that need to/ # /be open, but we''ve...

...l return: ip-192.168.1.19 port-24007 > [2017-08-20 20:30:40.466480] D [MSGID: 0] [common-utils.c:348:gf_resolve_ip6] > 0-resolver: next DNS query will return: ip-192.168.1.19 port-24007 > [2017-08-20 20:30:40.466482] D [socket.c:3050:socket_fix_ssl_opts] > 0-glusterfs: disabling SSL for portmapper connection > [2017-08-20 20:30:40.466490] D [socket.c:3050:socket_fix_ssl_opts] > 0-glusterfs: disabling SSL for portmapper connection > [2017-08-20 20:30:40.466699] I [MSGID: 101190] [event-epoll.c:602:event_dispatch_epoll_worker] > 0-epoll: Started thread with index 1 > [2017-08-20...

...the server > end of the connection and the client end. It is unclear if you have any > SMB clients and I'm not sure what is on port 599. No, no smb, only nfsv3. Port 599 is the lockd: [root at smtcfc0247 ~]# rpcinfo -p program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100005 1 udp 597 mountd 100005 1 tcp 597 mountd 100005 2 ud...

Below is my firewall rules for iptables. everything is working fine except for NFS I cannot mount my drive. If I turn off iptables I can mount. Looking at this : http://www.centos.org/docs/5/html/Deployment_Guide-en-US/ch-nfs.html Important In order for NFS to work with a default installation of Red Hat Enterprise Linux with a firewall enabled, IPTables with the default TCP port 2049

Hi Uli, [Sorry for slow response, life is busy...] On Mon, 13 Feb 2023 15:06:26 +0000, Ulrich Sibiller via samba <samba at lists.samba.org> wrote: > we are using ctdb 4.15.5 on RHEL8 (Kernel > 4.18.0-372.32.1.el8_6.x86_64) to provide NFS v3 (via tcp) to RHEL7/8 > clients. Whenever an ip takeover happens most clients report > something like this: > [Mon Feb 13 12:21:22

...to try to hunt it down, let me save you some time. I am using an 0.0.6b ext3 kernel on a Red Hat 7.0 system. I was finding that if my system did not get shutdown nicely, upon reboot it would of course do journal recoveries. When it was starting the system services after the recoveries, the "portmapper" and "nfslock" startup scripts were taking for ever to complete -- up to a minute or two each. After much investigation (strace and "set -x" in bash scripts) and many times hitting the power switch) I finally figured it out. The portmapper and nfslock scripts are the firs...

...0 0 localhost:filenet-rpc localhost:filenet-rpc > ESTABLISHED 1980/postmaster > > > > > > It looks like you need to deconfigure portsentry from listening on that > port and then you should be good to go. IOW, portsentry is ok to run, but > not on your portmapper port when you need to run portmapper. > > > > -geoff > > > > --------------------------------- > Geoff Galitz > Blankenheim NRW, Germany > http://www.galitz.org/ > http://german-way.com/blog/ > > _______________________________________________ > awesom...