Portmap does not recognize IP 127.0.1.1 as a local IP address

[Tormod Volden]

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

Instructions to reproduce:

- Open up Nautilus and then check the top panel in the menu, click on File and about halfway down you’ll see “Connect to Server”.
- Connect to 127.0.1.1

[Tormod Volden (tormodvolden)]

This patch seems to do the trick.

[Tormod Volden (tormodvolden)]

I've sent the patch to the upstream author for comments, waiting for response.

[Tormod Volden (tormodvolden)]

This is still needed in Lucid. I have asked upstream about it again, but meanwhile here is a debdiff.

[Gianfranco Costamagna (costamagnagianfranco)]

I agree with you, the 127.x.x.x is entirely private network.

Where are you trying to foward upstream? maybe you foward in a bad link or mail

[Gianfranco Costamagna (costamagnagianfranco)]

(sorry, I mean LOOPBACK network)

[Tormod Volden (tormodvolden)]

LocutusOfBorg, I have received a response from the upstream author. He suggested another patch but I haven't got around to test that one, IIRC. Good you reminded me about that. So it is in slow progress...

[Tormod Volden (tormodvolden)]

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.

[Evan Peck (colors)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 87611
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Once this has been done,
since this is can be reproduced AND it has at least on patch,
It can be confirmed.

BUT for now, since there is no error here,
this is the way it is supposed to be,
I will set it as Invalid until further notice.

Thank you very much.

[Tormod Volden (tormodvolden)]

I am not sure the last bug triager understood what this is about. I don't see how this can be reproduced with Nautilus.

[Evan Peck (colors)]

@Tormod I googled "Connect IP Ubuntu" and that was on the top hit page.

[Thomas Hotz (thotz-deactivatedaccount)]

Would be nice if we could apply the patch.

[Gianfranco Costamagna (costamagnagianfranco)]

Does this happens with lucid too? I see portmap has been removed since maverick, so this bug will expire with hardy [april 2013] and lucid [April 2015]
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Gianfranco Costamagna (costamagnagianfranco)]

And I don't understand how the bug can be reproduced, do I have to set up a virtual machine with lucid?

[Gianfranco Costamagna (costamagnagianfranco)]

(for Natty it will expire in 26 days)
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad