#46 No auto-connection to more than one Waste client on same IP

[Hotdog]

If two Waste clients share an IP address but run on
different ports (as might be the setup with two clients
running on two different machines behind the same port-
forwarding firewall), other Waste clients will never try to
connect to "the other" of them, when they've
connected to "the first" of them.

For instance:

Machine A runs Waste on port 1339.
Machine B runs Waste on port 1341.
Machine C is the firewall for A and B.
Machine C forwards port 1339 from the internet to
machine A.
Machine C forwards port 1341 from the internet to
machine B.

When a client outside the firewall has made a
connection to machine A (port 1339), it will never try to
connect to machine B (port 1341).

It seems that Waste clients only differentiate other
clients by their IP address, not by the pair (IP address,
port).

[Richard Aspden]

Logged In: YES
user_id=498159

I'm noticing the same problem here.

[Gonzo Granzeau]

Logged In: YES
user_id=328

Try turning on 'Advertise port on private network'. That
should allow machine A to broadcast to machine B.

And to be honest, that's a broken implementation as you've
described. You don't want machine B to ever try to connect
to machine C, which is what machine A should be telling it
to do. You want to just connect via the internal IP, not
the external firewall IP. I'd highly recommend you only
advertise one WASTE machine externally, and let the other
internal one connect to remote stable machines. This would
make there no contest to see who gets the incoming traffic.

Best of luck.

[Chris]

Logged In: YES
user_id=573676

I agree with goninzo, there is no reason to connect to both
clients. It generally only makes sense to have one routing
client per internet link. If you have a special reason for
this scenario I'd be interested to hear it, but as far as I
can tell this isn't a bug but a misuse. I will close this
report if I don't hear back.