Hi Sam,

In BS we have only one port configuration -- the one you're listening on. If a public IP connects to it, then BS advertises that same port.

While your example is technically correct, IMHO it seems like a pretty rare case that shouldn't interfere with the practical solution.

I suspect that even if you decided to ignore the population of users that forward different ports to their protected machines, surely you would convert so many firewalled users to direct-connect users that it would more than compensate for the mis-advertized hits.

FWIW, I don't recall any complaints from BS users for lack of this flexibility.

All this because I never remember to check the Force IP button until I've messed around with it for a couple of days...