DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
OK, back to basics then. It works when connected directly, that means the problem is in the router (duh ;-)) Reset the router to it's default settings, the manual should tell you how to do this. Next thing to check is if the ethernetcard of your PC is set to recieve it's IP from a DHCP server in the router. It probably has a fixed address, used by your ISP to connect you to their network. That IP address should be programmed into the router via it's web-interface. Then change the static IP address in your PC to DHCP, so the router can assign it an internal IP. When done, restart the networkcard.
I agree with DutchMaster.. it's the router
GlaucoME, can you really confirm that it only happens with the router?
Do you experience downloading problems from the web?
I'm using Debian now.
First i have installed Ubuntu and find this same problem, so i try the Debian.
My box is set to get IP from the DHCP Server on Router.
The cable modem get IP from DHCP too.
I agree that the problem is in Router, but i don't know where !!!!
I try again now, and i discovery something new:
I can't do 'apt-get update' connected to the router, but after do that connected directly in the cable-modem, i CAN do 'apt-get install xxxxx'.
That seems a little bizarre to me.
The outputs of resolv.conf:
cat:
nameserver 192.168.0.1 // Thats my router
ls -l:
-rw-r--r-- 1 root root 23 2007-07-06 09:43 /etc/resolv.conf
:~$cat /etc/resolv.conf
search dsl.inet.fi #my ISP
nameserver 193.210.18.18 #Primary ISP DNS
nameserver 193.210.19.19 #Secondary ISP DNS
nameserver 192.168.1.1 #My router
Sometimes routers don't give the isp's dns correctly to your linux box. Have a look at the modem and copy the dns addresses it has got from it's dhcp to your /etc/resolv.conf as in my example.
Ok. So my problem is solved.
What I did was the following:
1. I changed the MAC address of the ethernet adapter from FF:FF:FF:FF:FF:FF to 00:01:02:03:04:05
2. I ran dhclient. (IPs are assigned dynamically)
3. Rebooted my switch (optional, worked without it, so the problem is not the memory of the switch...)
This solved my problem, but I don't know why... but apt-get is working fine now...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.