Also, you should NEVER bind a network/host definition to a specific interface unless specifically instructed to do so by an Astaro engineer. Change all your definitions to 'Interface: >', except for the "Internet" definition supplied by Astaro that cannot be edited.
And, in general, you're confusing "External (Address)" with "Internet". "External (Address)" is a special host object created by WebAdmin when you define the External interface. It has only a single IP and will never be a source for traffic that comes into your Internal network(s).
Finally, another comment that might help explain how S/DNATs work. You can replace your two xbox DNATs with a single one that uses the two xbox service definitions in a services group in the traffic selector. That way, both types of traffic are selected by the DNAT and, since you correctly left the 'Destination service' blank, both are forwarded unchanged to your xbox.
Also, you should NEVER bind a network/host definition to a specific interface unless specifically instructed to do so by an Astaro engineer. Change all your definitions to 'Interface: >', except for the "Internet" definition supplied by Astaro that cannot be edited.
And, in general, you're confusing "External (Address)" with "Internet". "External (Address)" is a special host object created by WebAdmin when you define the External interface. It has only a single IP and will never be a source for traffic that comes into your Internal network(s).
Finally, another comment that might help explain how S/DNATs work. You can replace your two xbox DNATs with a single one that uses the two xbox service definitions in a services group in the traffic selector. That way, both types of traffic are selected by the DNAT and, since you correctly left the 'Destination service' blank, both are forwarded unchanged to your xbox.
After much hair loss trying to set up utorrent myself over the last few days I realized a few things. I had managed to open the service port successfully as per Open Port Check Tool and other sites and yet my speeds were very poor and in some cases the torrent wouldn't start at all.
In fact, there were several trackers whose torrents would not start at all. I examined the live logs and discovered that the firewall was blocking my machine from communicating with the torrent tracker (only some of them). You can see from within the client what port a particular tracker is listening on and inspect the firewall logs with this in mind. I then created the necessary rules and this solved the problem.
I had checked many of the threads on this subject and not once was this solution mentioned. I believe it may solve many users problems with torrenting. Any feedback on this point is welcomed and appreciated/
