#250 special handling for localhost

[Michael Richardson]

This is a feature request.
(I may try to implement it this weekend)

We keep our files, etc. on my wife's computer/desktop.
I also use it as compute server. My laptop moves around.
So, I ssh to her box usually, and run gtk-gnutella.
Often she runs it, and usually just leaves it running.
(That's good for the network, as we have a stable,
public IP and lots of bandwidth)

When I start it, of course, it can't bind port 6346.
What I'd like it to do, is attempt to *CONNECT* to port
127.0.0.1:6346 as a peer. I'd like her copy to
recognize that I'm coming from 127.0.0.1 (or IPv6, ::)
, and allow me to connect regardless of limits (okay,
maybe a new limit should apply).

At that point, I don't need to connect anywhere else,
and there no advantage of my copy doing anything else.
(not even answering searches). I submit searches, and
that's all.

[Christian Biere]

Logged In: YES
user_id=643728

Add ::1 or 127.0.0.1 (not ::) to ~/.gtk-gnutella/whitelist
and update to recent CVS.

[Christian Biere]

Logged In: YES
user_id=643728

Have you tried what I suggested? If yes, does it work for
you. If no, what problems occurred?

[Christian Biere]

Logged In: YES
user_id=643728
Originator: NO

I think this can be considered implemented. gtk-gnutella no longer rejects incoming local connections. The only special configuration you need is adding the one (or two) lines to the whitelist, so that the local connection has higher priority than others and is not rejected in case all slots are in use.