Well, the router is redirecting ports to itself. It just sounds... funny.
I just had the weeeeeeeeeeirdest idea. I wonder if aMule is taking 192.168.1.1 as your IP address, or if it may be taking the actual external IP of your router.
If it's choosing the external interface, the ports will fail to open on the application because the router is redirecting them to itself ( ? ). We do have a config option to force an specific interface.
Please close aMule, then edit amule.conf, and find the line that says:
Address=
and change it to
Address=192.168.1.1
Save the file, then open amule again. It's important that amule is closed while you edit the file, or it'll be overwritten.
If that doesn't work, another option is to do exactly the opposite of that. Disable uPnP in aMule, then go to the router config and remove all forwarded ports if any, and write down your external IP address (let's say a.b.c.d). Then close aMule, and edit amule.conf to change the Address line to:
Address=a.b.c.d
Save the file, and start aMule again. Test ports again.
If neither of those work, then it may be worth checking the debug logs for the application. We'll cross that bridge if we have to.