My D-Link DSL-504T is basically a pile of junk when it comes to Linux. There are tales of woe all over the world just a google search away. Ironically the modem/router is linux based but there you go..

So suggested replacement models based on this criteria would be brilliant:

• MUST be tested & have excellent compatibility with Kubuntu / Linux in general
• Cost under £50 ($95) ideally
• IPv6 compatible

Additional notes: My internet connection is UK based ADSL @ 1MB

Can you be more specific? Why do believe that this equipment is not working? Basically if it can handle ethernet connections, which it can, it should work fine.

Thing is that it doesn't really matter which os is receiving the packets from the router as a packet is a packet. So if you explain what problems you are having then the problem can be solved.

Solving the problems would be good, but i don't hold up much hope. If you have a browse through this thread:

http://www.linuxquestions.org/questi...d.php?t=478074

You can see the process i went through of getting the simplest of things done in linux, right through to the point where i realised it's not actually that hard for everyone, for some it "just works".

There are links on the thread to several other users who are having / have had problems with this model of modem router with Linux.

I really wish i couldn't, but i could probably find links to 10+ forums with someone having the same problems.

Well I've just googled for some spec on it, and I can't see why andy-k might be having problems.

I'm guessing that it's to do with manually setting up stuff ??? One of the reasons I use an static IP, is that I don't have to change anything like that (and under Kubuntu, the DHCP facility should work fine, because I tried it on my Aunts evesham 64bit AMD box this morning - the first time I've had a linux live distro connect straight through without having to meddle - on a bloody NTL ethernet modem).

Maybe he can explain what the problem is exactly, then we might be able to assist.

regards

John

I have two D-Link's (DSL-504T and DSL-G604T)and both work fine, I would not change it so quickly.

Solved it.

Computer > System Settings > Networking > DNS tab

Found my ISP's DNS nameservers from the routers system log file (earlier).

Put those two in, took 192.168.1.1 out.

Went to /etc/resolv.conf, made sure they were there and 192.168.1.1 was not.

Went to /etc/dhcp3/dhclient-script

Commented out a large chunk of unnecessary and shockingly everything worked straight away. For the first time i was able to understand what people were on about with the Adept repositories, and firefox didn't even need IPv6 disabled anymore, which was weird but there you go!

Success!

(Next newbie project is trying to understand why my NTFS Windows XP partition and NTFS Storage partition, or sda1 and sda5 are showing in the 'Storage Media' folder but i can't seem to find them using a terminal or Konqueror, or point fstab towards them so i can mount.. but that's another thread altogether)

Edit: Done that as well now. No idea why i could see those in /media/ as they didn't seem to exist. Did sudo mkdir /media/sda1 and same for sda5 and edited fstab and everything looked the same but i could mount. Go figure, but it's one less problem

You can also add the router address in resolv.conf as most routers do DNS caching so if the isp changes DNS you still have connectivity.

Hmm that could be a good tip. So by adding the router address (192.168.1.1) to resolv.conf this won't affect my connectivity right now? Because i was sure it needed to be at the very least commented out.

And bear in mind when it was set with that before i had very limited connectivity, and now i'm in an "if it ain't broke, don't fix it" frame of mind and dubious to mess.

By adding the line;
nameserver 192.168.1.1
to /etc/resolv.conf should, theoretically speedup name resolution. I have it in addition to the DNS servers specified by the isp. The router should be caching DNS and by using the router cache it reduces the hops required to resolve names.

I've added 'nameserver 192.168.1.1' under the ISP DNSs in resolv.conf and the repositories did seem to fetch updates slightly quicker.

Only time will tell. Thanks for the tips TigerOC