[Bug 87611] Re: portmap doesn't recognize 127.0.1.1 as local

[Tormod Volden]

The upstream author Neil Brown thinks it is ill advised to use any other
address than 127.0.0.1 for loopback. It is unclear to us both what the
third-party application  is doing in my case, it does not seem to create
a second loopback interface as far as ifconfig can tell. He suggested
another patch instead, but it did not work. After reporting this in July
2010 I never heard back from him again. I am losing hope about getting
it fixed...

I still need the patched portmap to use the application in question -
this is an old, unsupported, closed-source application. Maybe I'll add
the patched portmap to my PPA to make it easier for others in the same
situation.

** Changed in: portmap (Ubuntu)
       Status: In Progress => New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to portmap in Ubuntu.
https://bugs.launchpad.net/bugs/87611

Title:
  portmap doesn't recognize 127.0.1.1 as local

Status in “portmap” package in Ubuntu:
  New

Bug description:
  Binary package hint: portmap

  (portmap 5.24 from feisty)
  AFAIK, all addresses on 127.x.x.x are local. However, portmap complains when a local application tries to connect from 127.0.1.1:

  server: about do a switch
  portmap[28098]: connect from 127.0.1.1 to set(1577513772): request from non-local host

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/87611/+subscriptions