In order for push requests to work when using NAT, we need to be able to force the local IP address. If not, it will be reported incorrectly to the computer to which we are attempting to do the push, and it will not be successful.

I am using Xolox 1.11, and push requests (I use NAT) never work because of this missing feature. Please include it in 1.12!

Clayton

hi,

even if my ip could be set in a config file it would be nice. all clients behind firewalls can't download to me!

please put this in the next release!
thanks

Hi, propably it would be more secure to let find XoloX the real IP, propably an option in the network settings.

Something similar is done in IRC clients (for example mIRC). The local clients performs an request, and the server in the internet gets automatically the "real IP" (through TCP/IP headers) which it tells back the client. If this explanation is too short and more technical details needed, feel free to ask more.

Cya, Moak

Automatic configuration is nice but id like to be able to change
it manually when it fails,
xolox needs to allow me to force its ip and listening port like limewire and gnotella does so i can configure it to work through my NAT.
not everyone who uses a NAT have a soucks proxy when it is much simpler to set up socket forwarding...

Propably let Xolox find your IP once and you can still edit if you need?

In my case I have a dynamic IP, which means Xolox definitely should find it out... it changes often. Suggestion: How about an editbox in the (advanced) network preferences to enter a "forced IP", with an checkbox "On startup allways get (dynamic) IP".
As long as the checkbox is enabled (default), the editbox is greyed out and filled with the current IP (on startup and when loosing all connects, this might be a temporary internet disconnect which results in a new dynamic IP).

Cya, Moak

PS: It might be very usefull to add a command line option /forceip=x.x.x.x. This gives the opportunity to start Xolox via a start script, for example I could ask my Linux router for the current IP (the router knows it for sure) and start Xolox with that more secure. Ah and btw better don't allow any private network address to be "forced", right or not?