Originally Posted by FunnyHarry
I am not sure what "network" option to use, wired or DSL,
I am not clear quite what you are asking; is the question 'what settings do i use on my computer, to configure the (presumably wired) connection to my ADSL Modem/router?', or is it 'What settings do I need in my Modem/Router to connect to my ISP?'.
Originally Posted by FunnyHarry
...where to place my username and password...
Most m/routers have an internal web page that you can log into, to perform configuration. This is normally something like 192.168.0.0 or 192.168.0.0, but should be described in the manual for the device. This will allow you perform all the configuration that the box itself needs. You may need some details from the ISP - your user ID, your password, the protocol that this particular ISP uses (normally, the ISP will be quite good at supplying this information, otherwise their cust support would be overloaded, trying to cope). Note that this all concerns the connection between the m/r and the ISP, and there is no point in fiddling with the connection between the ISP and your m/r, if the problem is your connection to the m/r from your computer.
You will need to get the connection between your computer and the m/r to do any configuring of the m/r, so work on that first.
One way or another, your m/r will want to get DNS details: these can sometimes be obtained 'automagically' from the ISP or entered manually, but you do not have to use your ISP's servers for this and can use an alternative. Some ISPs do a really bad job at running nameservers, and if 'dig' shows up poor look-up times, particularly on a first look-up (not from cache), consider either changing or using a local cache.
Even if DNS is not working/not configured correctly, you should be able to 'ping' by ip address any other network devices which exist local to your network;
should give you a response, if there is a device on 192.168.0.1 (an address local to your network, presumed your m/r) listening and ready to talk.
will fail, if DNS is not working. So, if a 'ping' to an external network address, eg Google's DNS servers on 22.214.171.124 and 126.96.36.199, works, but www.google.com
fails, you have a DNS problem.
(Note; if your m/r performs something like mDNS/Avahi/Bonjour, and i think that they more-or-less all do, these days, it may well set up some of this for you; this protocol allows the m/r to 'advertise' its capabilities, and, assuming that you are running an appropriate client, you should pick up the fact that it can do DNS resolution and that it should be your default gateway to the internet. If you are running Networkmanager or WiCD on your computer, that should mean that this all happens 'automagically', and that it would continue to happen automagically if you moved to another network, even though the addresses might change.)
(Yet another 'note also': the name resolution (DNS) can be performed (I actually mean cached, but that's a slightly subtle distinction) on your computer or on your m/r; in terms of getting things working, it probably makes no difference. To get your m/r to do it, enter the ip address of the m/r as your DNS server, on your computer's network settings (probably easiest, assuming that your model of m/r does this). Alternatively, use, eg, the Google ips above or your ISPs versions on your computer. If the latency of the lookups is a real problem, run a caching program (eg, DNSMASQ) on your computer, and hook it up to, eg, Google's DNS.)
(Other providers exist, apart from Google (eg, OpenDNS), but they'll probably function adequately, unless blocked by your Government, in most locations.)