Date: Sat, 20 Oct 2001 14:45:02 -0700 (PDT) From: Frank Tobin <ftobin@neverending.org> To: freebsd-gnats-submit@FreeBSD.org Subject: bin/31393: portmap(1) cannot be bound solely to 127.0.0.1 Message-ID: <200110202145.f9KLj2K22260@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 31393 >Category: bin >Synopsis: portmap(1) cannot be bound solely to 127.0.0.1 >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Oct 20 14:50:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Frank Tobin >Release: 4.4-STABLE >Organization: >Environment: FreeBSD palanthas.neverending.org 4.4-STABLE FreeBSD 4.4-STABLE #6: Tue Sep 25 17:00:03 EDT 2001 root@palanthas.neverending.org:/usr/obj/usr/src/sys/PALANTHAS i386 >Description: It is not possible to start portmap listening solely to the localhost (127.0.0.1). The problem is that portmap always appends 127.0.0.1 to every list of -h options (addresses) passed in, and then dies when tryin to bind to the localhost port the second time. >How-To-Repeat: Run "portmap -h 127.0.0.1". portmap will die. >Fix: One solution would be to have portmap not add 127.0.0.1 automatically to its list; this functionality is probably not a good design. But due to backwards compatibility, a more desirable option would be to just have to check if 127.0.0.1 is in hosts[] before adding it a second time to the list of addresses to bind to. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110202145.f9KLj2K22260>