Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#9629 - fam & portmap should listen on local interfaces by default

Attached to Project: Arch Linux
Opened by Sarunas Krisciukaitis (sarunas) - Wednesday, 20 February 2008, 16:40 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 16 April 2008, 08:45 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Tom Killian (tomk)
Architecture All
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
Followed http://wiki.archlinux.org/index.php/Beginners_Guide and installed Arch Linux i686 version. Installed KDEmod as GUI. After that run netstat -tapn and found that 2 processes were waiting for signal on all interfaces.
netstat -tapn
tcp 0 0 0.0.0.0:748 0.0.0.0:* LISTEN 8628/famd
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 8625/portmap

Suggest to make those daemons listen on local by default, by changing 2 files:
1. /etc/fam/fam.conf (line 28):
#
# local_only makes famd ignore requests from remote clients & remote fams.
# Note that this is ignored if famd is started by inetd.
#
# The -L command-line argument overrides this option.
#
<local_only = false
>local_only = true

2. /etc/rc.d/portmap (line 10):
< [ -z "$PID" ] && /sbin/portmap
> [ -z "$PID" ] && /sbin/portmap -l

After that just restart fam and portmap daemons and got such netstat report:
netstat -tapn
tcp 0 0 127.0.0.1:111 0.0.0.0:* LISTEN 8668/portmap
tcp 0 0 127.0.0.1:791 0.0.0.0:* LISTEN 8671/famd

Additional info:
* package version(s)
core/portmap 6.0-2
extra/fam 2.7.0-10
* config and/or log files etc.
/etc/fam/fam.conf
/etc/rc.d/portmap

Steps to reproduce:
Install Arch from scratch on new PC.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 16 April 2008, 08:45 GMT
Reason for closing:  Won't implement
Comment by Sarunas Krisciukaitis (sarunas) - Thursday, 21 February 2008, 19:43 GMT
Same issue is true on AMD64 system.
[root@namai ~]# netstat -tapn
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 7649/portmap
tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN 6618/X
tcp 0 0 0.0.0.0:863 0.0.0.0:* LISTEN 5775/famd
Comment by Gavin Bisesi (Daenyth) - Tuesday, 11 March 2008, 18:08 GMT
I've also seen this issue on my system.
Comment by Gavin Bisesi (Daenyth) - Friday, 11 April 2008, 19:03 GMT
Just wanted to note that FAM is currently orphaned.
Comment by Jan de Groot (JGC) - Wednesday, 16 April 2008, 08:45 GMT
Starting random daemons on your system can open them to the world yes. The default of fam and portmap are to listen on 0.0.0.0:*, this is the upstream default when installing from source. In case of portmap, the main usage of this daemon is to setup NFS. How would you like to see your NFS mounts aren't working because portmap listens only on localhost by default because of some new default option?

Loading...