PPPoA or PPPoE is the protocol used by the ISP, the modem/router must support it to work, the problem in your case is not here, it is the NAT... your modem only support NAT, i will try to explain it in a simple way.
In your modem you have 2 interfaces, the modem and ethernet, the modem connects to your ISP using either PPPoA or PPPoE depends on which your ISP supports, after the connection is established the modem gets the Internet IP. Now, since you have an ethernet interface aswell, it must get another IP address, which is known as the local IP, 192.168.X.X ... now for both interfaces to be connected to each other, NAT is a must, it is the only way to connect both interfaces, ofcourse this is the case with any device, be it a router or a modem with a server and clients, like my network.... NAT has many problems, mainly it dosen't know how to forward or connect ports for any application, you must tell it yourself, that is why you find features like the port forwarding in many other routers, and this is the problem in your case, your modem ONLY supports NAT, and the other features that is designed to help solve NAT's problems dose not exist. Leaving NAT without rules is like having a very stupid firewall, thats why many thinks that Routers has internal firewall.
Of course this is the case with many routers that is sold in Egypt, you know we always like to import the cheapest and the worst, and that is why i always say don't buy a router, get a server... with a server you are essentially giving the NAT task to a computer, which is fool proof, you can't go wrong that way, besides you can limit, block, download...etc with it. Basically, you will get the options that is only found in Routers that cost an arm and a leg lol.
As for the modem that you mentioned, yes i think this one is okay, take a look here
ftp://ftp.dlink.co.uk/dsl_routers_mo...rev_bx_QIG.pdf
This is the modem i bought before i get my PCI modem, i don't think the DSL-210 differs, take a look at page 15-29....this is what you need, with this, the computer itself will be assigned the internet IP, and then you can use the ethernet card and NAT to "route" the packets to the clients on the network with the server, the easiest way to do this is just enable windows internet connection sharing and the windows will do the rest, it will enable its built in DHCP server and the clients will be assigned with Local IP addresses, for applications like P2P you can add the required rules and ports in the connection properties, thats it, of course any application running on the server itself will not require any special rule, it will run normally just like using a dial up modem.
المفضلات