Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
"Connecting to irc.freenode.net (1.0.0.0) port 6667"
"[admin@(none) root]$ ping freenode.net
PING freenode.net (140.211.166.2): 56 data bytes
64 bytes from 140.211.166.2: icmp_seq=0 ttl=51 time=178.3 ms"
Separate ADSL Modem 192.168.1.10
- doesn't have much in the way of diagnostics. It's a linksys ADSL2 modem
^ connects through
Router 192.168.1.20
- /etc/resolv.conf is set to 192.168.1.10
^ connects through
Client PC 192.168.1.101
- Firefox doesn't resolve DNS queries. Konqueror kind of works but
slow DNS requests.
- yet, ping works fine resolving DNS perfectly
- /etc/resolve.conf is set to 192.168.1.20 (router), and ping only works if it is set to
this and not 192.168.1.10 (modem)
- gateway is set to router (192.168.1.20) by DHCP
- same symptoms on Windows and Linux, conected by ethernet cable
- can't ping the modem (192.168.1.10)
- apt-get fails to update as well
Other Windows only client PC:
- works fine connected by cable or wireless
if i'm right, this sounds a lot like similar issues (well.. they wouldn't be similar otherwise would they??) which came down to very bizzare ipv6 issues with the adsl router and the certain patterns of dns lookups being done by clients. try disabling ipv6 on your box and see where that gets you. i still don't understand the "why", but the "how" seems to do the job.
The linksys ADSL2 looks to be a combination modem, and router.
Then you have another router on top of that, and both are on the same subnet from what you posted
"Separate ADSL Modem 192.168.1.10"
"Router 192.168.1.20"
If NAT is enabled on two devices, and they share the same subnet there will most likely be problems. If you want to use both routers you will need to do some config changes on the 2nd device.
no, i don't think so. actually it was the 1.0.0.0 dns resolutions too that fitted in with it. regardless of network topology, if DNS works on one app on a client, it *should* work on all of them.
it's not a function of the laptop, it's the operating system which dos the support. normally it's just a case of removing, or not loading the "ipv6" module on boot.
The modem only has one ethernet port on the back, and client PCs can't ping the modem.
Thats because they share they same subnet, and are being NATed by seperate devices.
Modem 192.168.1.10
Router 192.168.1.20
Any clients that are plugged into the router are not going to send their packets to 192.168.1.20 to reach 192.168.1.10, or any other IPs that share that subnet.
They will do a arp lookup asking who has 192.168.1.10, and wont get a answer because 192.168.1.10 is not a configured IP that is in their collision domain.
Now if the modem had a IP on another subnet then the clients would look in their routing table, and see that the IP is not on the same subnet they are, send packets to their default route of 192.168.1.20.
IPv6 may have something to do with this, but I have little experience with it. Either way, you will still want to get your network straightened out.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.