Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I have a problem where there's no route found to a select set of seemingly random IP's on the internet.
Specifically, I have a router running linux 2.4.22, djbdns (for dns caching) and an iptables firewall. On the private side of the router sit 15 computers, and on the public side sits a cable modem. IP masquerading and packet filtering appear to work just fine-- you can connect to almost everything on the internet from the 15 computers on the private side of the router. This includes any number of websites, IRC, AIM, etc. to all kinds of places- servers in the US and abroad. However, there are a number of hostnames where either:
1. The hostname is not resolved because the dns cache cannot find a route to the computer hosting the appropriate dns record. However, a route does exist to the IP address of the host--- I just can't resolve it because no route exists to the dns server.
2. I can resolve the hostname to an IP address because a route exists to the computer hosting the dns records, but not route exists to the IP address of the host I'm looking for.
3. Both 1 & 2
In the case where no route exists to the IP address in question, traceroute reveals that packets don't make it past the gateway.
Any help would be greatly appreciated.
Last edited by Doug Melvin; 10-27-2004 at 12:13 PM.