Skip to contentSkip to conversation

udp port sunrpc unreachable

DISCUSSION Ingo Lantschner 3 participants 8 messages Feb 2, 2006 – Feb 3, 2006

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Hi all,
I have a propably simple problem here - but can not find a solution:
NFS-Client wslisi should mount a directory from NFS-Server wsvideo. Potmaper und nfs-common are installed on both machines. The server has nfs-kernel-server installed:
-------------------------------------------------------------------------
wsvideo$ env LANG=C dpkg -l nfs*
...

un  nfs-client                       <none>
ii  nfs-common                       1.0.6-3.1ubuntu1
ii  nfs-kernel-server                1.0.6-3.1ubuntu1

--------------------------------------------------------------------------

But I still can not connect - tcpdump says that port 111 (sunrpc) is not reachable:
-------------------------------------------------------------------------

# tcpdump -t not port 22
IP wslisi.696 > wsvideo.sunrpc: S 727126627:727126627(0) win 5840 <mss 1460,sackOK,timestamp 2256871 0,nop,wscale 2>
IP wsvideo.sunrpc > wslisi.696: R 0:0(0) ack 727126628 win 0
IP wslisi.697 > wsvideo.sunrpc: UDP, length: 56
IP wsvideo > wslisi: icmp 92: wsvideo udp port sunrpc unreachable
IP wsvideo.32803 > fw.domain:  29191+ PTR? 13.4.168.192.in-addr.arpa. (43)
IP wslisi.698 > wsvideo.sunrpc: S 724474935:724474935(0) win 5840 <mss 1460,sackOK,timestamp 2256872 0,nop,wscale 2>
IP wsvideo.sunrpc > wslisi.698: R 0:0(0) ack 724474936 win 0
IP fw.domain > wsvideo.32803:  29191* 1/0/0 (64)
IP wsvideo.32803 > fw.domain:  29192+ PTR? 12.4.168.192.in-addr.arpa. (43)
IP fw.domain > wsvideo.32803:  29192* 1/0/0 (63)
IP wsvideo.32803 > fw.domain:  29193+ PTR? 254.4.168.192.in-addr.arpa. (44)
IP fw.domain > wsvideo.32803:  29193* 1/0/0 (60)
arp who-has wsvideo tell wslisi
arp reply wsvideo is-at 00:0c:76:71:02:09
arp who-has fw tell wsvideo
arp reply fw is-at 00:4f:4e:05:d1:bd
--------------------------------------------------------------------------

netstat sees tcp open:

--------------------------------------------------------------------------

$ env LANG=C netstat -an | grep 111
tcp        0      0 127.0.0.1:111           0.0.0.0:*           LISTEN
udp        0      0 127.0.0.1:111           0.0.0.0:*
--------------------------------------------------------------------------

Any idea? TIA Ingo.

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs

#1 lore raw
Quoted 37 lines · Ingo Lantschner

Hi all,
I have a propably simple problem here - but can not find a solution:
NFS-Client wslisi should mount a directory from NFS-Server wsvideo. Potmaper und nfs-common are installed on both machines. The server has nfs-kernel-server installed:
-------------------------------------------------------------------------
wsvideo$ env LANG=C dpkg -l nfs*
...

un  nfs-client                       <none>
ii  nfs-common                       1.0.6-3.1ubuntu1
ii  nfs-kernel-server                1.0.6-3.1ubuntu1

--------------------------------------------------------------------------

But I still can not connect - tcpdump says that port 111 (sunrpc) is not reachable:
-------------------------------------------------------------------------

# tcpdump -t not port 22
IP wslisi.696 > wsvideo.sunrpc: S 727126627:727126627(0) win 5840 <mss 
1460,sackOK,timestamp 2256871 0,nop,wscale 2>
IP wsvideo.sunrpc > wslisi.696: R 0:0(0) ack 727126628 win 0
IP wslisi.697 > wsvideo.sunrpc: UDP, length: 56
IP wsvideo > wslisi: icmp 92: wsvideo udp port sunrpc unreachable
IP wsvideo.32803 > fw.domain:  29191+ PTR? 13.4.168.192.in-addr.arpa. (43)
IP wslisi.698 > wsvideo.sunrpc: S 724474935:724474935(0) win 5840 <mss 
1460,sackOK,timestamp 2256872 0,nop,wscale 2>
IP wsvideo.sunrpc > wslisi.698: R 0:0(0) ack 724474936 win 0
IP fw.domain > wsvideo.32803:  29191* 1/0/0 (64)
IP wsvideo.32803 > fw.domain:  29192+ PTR? 12.4.168.192.in-addr.arpa. (43)
IP fw.domain > wsvideo.32803:  29192* 1/0/0 (63)
IP wsvideo.32803 > fw.domain:  29193+ PTR? 254.4.168.192.in-addr.arpa. (44)
IP fw.domain > wsvideo.32803:  29193* 1/0/0 (60)
arp who-has wsvideo tell wslisi
arp reply wsvideo is-at 00:0c:76:71:02:09
arp who-has fw tell wsvideo
arp reply fw is-at 00:4f:4e:05:d1:bd
--------------------------------------------------------------------------
Quoted 7 lines

netstat sees tcp open:

--------------------------------------------------------------------------

$ env LANG=C netstat -an | grep 111
tcp        0      0 127.0.0.1:111           0.0.0.0:*           LISTEN
udp        0      0 127.0.0.1:111           0.0.0.0:*
--------------------------------------------------------------------------

Portmap appears only to be listening on the loopback adddress. Are you perhaps starting it before the external network comes up?

Cheers,
Trond

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs

#2 lore raw
Quoted 2 lines · Trond Myklebust

Portmap appears only to be listening on the loopback adddress. Are you perhaps starting it before the external network comes up?

I think that's actually the debian default setting these days; with the debconf verbosity at the default, it should have asked you about this when portmap was installed. Just edit /etc/default/portmap to comment out the obvious line.

--b.

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs

#3 lore raw
Quoted 8 lines · J. Bruce Fields
Quoted 2 lines · Trond Myklebust

Portmap appears only to be listening on the loopback adddress. Are you perhaps starting it before the external network comes up?

I think that's actually the debian default setting these days; with the debconf verbosity at the default, it should have asked you about this when portmap was installed. Just edit /etc/default/portmap to comment out the obvious line.

If true, then that would appear to be a rather ridiculous default. Have they put out a rationale for this?

Cheers,
Trond

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs

#4 lore raw
Quoted 5 lines · Trond Myklebust
Quoted 4 lines · J. Bruce Fields
Quoted 2 lines · Trond Myklebust

Portmap appears only to be listening on the loopback adddress. Are you perhaps starting it before the external network comes up?

Quoted 7 lines
Quoted 4 lines

I think that's actually the debian default setting these days; with the debconf verbosity at the default, it should have asked you about this when portmap was installed. Just edit /etc/default/portmap to comment out the obvious line.

If true, then that would appear to be a rather ridiculous default. Have they put out a rationale for this?

Nope, I'm wrong, the default is the opposite. So probably someone chose the more secure-sounding option at install time and then forgot about it....

--b.

Template: portmap/loopback
Type: boolean
Default: false
_Description: Should portmap be bound to the loopback address?
Portmap by default listens to all IP addresses. However, if you are not using RPC services that connect to remote servers (like NFS or NIS) you can safely bind it to the loopback IP address 127.0.0.1. .
This will allow RPC local services (like FAM) to work properly while preventing remote systems from accessing your RPC services. .
You can change this configuration also by editing the OPTIONS line in the /etc/default/portmap file. If you just don't specify the -i option it will bind to all interfaces.

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs

#5 lore raw
Quoted 11 lines · J. Bruce Fields
Quoted 10 lines · Trond Myklebust
Quoted 8 lines · J. Bruce Fields
Quoted 2 lines · Trond Myklebust

Portmap appears only to be listening on the loopback adddress. Are you perhaps starting it before the external network comes up?

I think that's actually the debian default setting these days; with the debconf verbosity at the default, it should have asked you about this when portmap was installed. Just edit /etc/default/portmap to comment out the obvious line.

Quoted 5 lines
Quoted 2 lines

If true, then that would appear to be a rather ridiculous default. Have they put out a rationale for this?

Nope, I'm wrong, the default is the opposite. So probably someone chose the more secure-sounding option at install time and then forgot about it....

Right. That makes a lot more sense.

Cheers,
Trond

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs

#6 lore raw

SOLVED: udp port sunrpc unreachable

Hi all!
Thanks for your help - you hit the nail!! After comenting the obvious (and only) line in /etc/default/portmap anything went fine.

Quoted 10 lines · Trond Myklebust
Quoted 10 lines
Quoted 7 lines
Quoted 4 lines

I think that's actually the debian default setting these days; with the debconf verbosity at the default, it should have asked you about this when portmap was installed. Just edit /etc/default/portmap to comment out the obvious line.

If true, then that would appear to be a rather ridiculous default. Have they put out a rationale for this?

Nope, I'm wrong, the default is the opposite. So probably someone chose the more secure-sounding option at install time and then forgot about it....

No, it IS the default - I have never been asked (installed with apt-get install portmap). I use ubuntu Hoary. May be, because it targets the desktop-user the default is only loopback.
Anyway, now its fine, thanks again to all who answered and helped.

Regards, Ingo.

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs

#7 lore raw

Re: SOLVED: udp port sunrpc unreachable

Quoted 3 lines · Ingo Lantschner

No, it IS the default - I have never been asked (installed with apt-get install portmap). I use ubuntu Hoary. May be, because it targets the desktop-user the default is only loopback.
Anyway, now its fine, thanks again to all who answered and helped.

just got the information that in Ubuntu Breezy (successor of Ubuntu Hoary) this line is no more present.

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs