He changed the default ip range. Thats a change security freaks like to do cus they dont want the default linksys one. It means your average dumbass can't grab a manual ip easily. This is usualy done in conjunction with disabling DHCP. Im guessing this wasnt done...
Either way, it should not affect as long as you have the forwarding set right.
Heres one thing though... sometimes i get firewalled messages with amule even though im not. They go away the next day.
Heres what you should do to check:
As I recall there are some easier ways to do this, some web based utilities to tell you if your port forwarding is working... maybe google it. Otherwise:
Disable all port forwarding(optional, DMZ will still work). And enable DMZ for your Ip address.
Check with a different application if you can get into your computer:
You can do this with another p2p app.
Or you can enable remote login or ftp file sharing then from a computer outside your router/NAT connect to it. To do this you need to use the external ip. For example. if internal ip is 10.0.0.2 and external is 204.23.24.25, you could use a free shell account to ssh into your connection if oyu have remote login turned on. You could also do this from a friends computer, keep in mind though it has to be outside your NAT(network address translation, this means your router, firewall, modem, however you feel like referring to it).
Simply type: ssh
USER@204.23.24.25It will ask you to verify that the RSA signature is ok. hit yes. Or simply ask for your password. IF you get to that theres no problem. Port forwarding is working.
If amule still says you are firewalled, then its simply confused. This happens, external connections in will still work i think(not sure bout this actually, maybe one of the amule dev people can tell you).
You can disable DMZ and re-enable port forwarding if you like after this.
