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.
I'm 97% towards getting networking to fly on this ibm t23 laptop with redhat 8, but something strange is failing.
ping to an ip address works
host to an ip name works (returns the ip address)
dig to an ip name works and properly reports the dns servers
ping to an ip name does not work
somehow the resolver is not using whatever host uses to resolve the address
other configuration data: wireless lan on eth1 (orinico card) talking to an orinoco residential gateway, connected to verizon dsl. eth0 is out of the picture.
are you pinging/host'ing the fqdn (ping host.domain.com) or just the host (ping host) ? whichever way you're doing it, i'm assuming your doing the same way for both ping AND host/dig ..
does your /etc/resolv.conf have the 'search' line ? i.e
search domain.com
nameserver 65.65.65.65
if all looks ok so far i would suggest taking a packet trace (tcpdump or ethereal (gui)) to help narrow down where the prblm is..
yes, I am using the fqdn.
Thanks for the suggestion.
Getting closer. dig tells me the nameserver. I put that in /etc/resolv.conf
(without a search line) and all works fine ... for a few minutes. Then some process rewrites /etc/resolv.conf to have a bogus search line and a bogus nameserver line. How interesting.
(it's putting 10.0.1.1, the router, as the nameserver, but of course the nameserver lives on the other (public) side of the router)
Then some process rewrites /etc/resolv.conf to have a bogus search line and a bogus nameserver line.
most likely this is dhcp ... check to see if this host is dhcp enabled, and if so, check to see that the dhcp server is configured to supply the correct parameters (default gw, nameserver, etc) .. maybe your router/access point or whatever this box connects to is acting as the dhcp server for your network?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.