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 hopefull I can get a bit of help from someone here and make some contacts in the Linux department.
I have no connectivity whatsoever
I have pinged my IP and get results but if say for example I ping google.com I get host unknown.
Please tell me what I've done wrong or just not done
Gone through configs etc (/etc/sysconfig/network.conf)
Done setup the GUI version allocated IP and DNS ( I may have buggered that up but I checked with google and other search engine as to correct DNS locations).
I must have missed something
Also I get the command not found error alot, can someone please tell me what that is about ?
I have checked with Redhat and they say repository but I cant get repository without network connection. Im sure you see the dillema.
Many thanks for any help you can provide and all the best with whatever your doing
The first step to narrowing the problem, is to run a series of tests to define exactly what your system can, and cannot, do in terms of network communication.
Assuming for example, you have a system with an IP address of 192.168.1.5 /24, you'll want to first test your network by pinging something on the same layer two network, preferably hanging off of the same access layer switch. (For example something with an IP of 192.168.1.6, etc.)
If that does not work, stop troubleshooting DNS, and look closer at your actual IP address configuration with the command 'ifconfig'
Make sure you can ping your gateway. If your DNS servers are on the other side of your gateway, keep holding off on those. If your gateway can be reached, you want to ping the nearest ip address on the other side (for example, your own public IP address if you're NATing, etc.)
Only once you've confirmed routing is working, should start troubleshooting DNS. Try some of the following commands:
Code:
traceroute <dns ip>
dig @<dns ip> google.com
Below are some common files to check your ip settings
Just a heads up, I'm not too familiar with the desktop interface, I find myself using the command line more often than not, so I can't really advise there. Good luck, and if you need further help, run as many tests as you can think of, and post as many details.
To try and help with your connectivity problem, could you please give us some additional information? Please post:
* The output of the "ip addr" command
* The output of the "ip route" command
* The output of the "/etc/resolv.conf" file
* The output of the "iptables -L" command
You could also try 2 quick tests so long.
Firstly, look at the output of the "ip route" command for a line similar to this:
Quote:
default via 192.168.1.1 dev eth4
This shows the IP address of your default gateway (192.168.1.1 in my example). Try and ping that IP address.
Secondly, in the /etc/resolv.conf file there should be one or more lines similar to this:
Quote:
nameserver 192.168.200.1
These are your DNS server(s). Try and ping these too.
To try and help with your connectivity problem, could you please give us some additional information? Please post:
* The output of the "ip addr" command
* The output of the "ip route" command
* The output of the "/etc/resolv.conf" file
* The output of the "iptables -L" command
You could also try 2 quick tests so long.
Firstly, look at the output of the "ip route" command for a line similar to this:
This shows the IP address of your default gateway (192.168.1.1 in my example). Try and ping that IP address.
Secondly, in the /etc/resolv.conf file there should be one or more lines similar to this:
These are your DNS server(s). Try and ping these too.
Thank you
Just a little update as the issue is not fully resolved I did the IP pings and URL pings got result of URL of host unknown which led me to hours of research online and I can't believe this conclusion but it seems we have software bug issue.
I also tried networkmanager or should I say Network Manager which came up with no such command.
After much frustration I decided to give it a rest and installed a new VBox this time RedHat 6.1 dashboard thought it might have the same issue but wanted to compare for myself now I went through the install process for my setup and entered my network details, setup took 3 hours I'm runing a crap system at present. In system network setup my LAN and WiFi but still no joy, turned my firewall on and off. Then thought to give NetworkManager ago, after that network connectivity is fine and can browse the net. I need help in understanding this though as I want to use CLI to learn the commands and techniques correctly so the GUI (Desktop) is cool but not sufficient for running my webserver. I've just had a fumble with x11 quite the same as in mac OS X however not quite the same as bash.
Also in my server install I couldn't get startX and quite a few other programs runing.
All help and advice is highly appreciated
Many Thanks
What you need to understand is that, like in your other thread, all you've done so far is talk about the problem. Without posting any relevant information, even if asked, your threads will go on and on without resolution. And you can post all the theories about software bugs you want but until you stop destroying evidence and do as asked I maintain the only real problem is PEBCAK.
What you need to understand is that, like in your other thread, all you've done so far is talk about the problem. Without posting any relevant information, even if asked, your threads will go on and on without resolution. And you can post all the theories about software bugs you want but until you stop destroying evidence and do as asked I maintain the only real problem is PEBCAK.
Okay.
What is PECAK ?
I see your point, not my theory its what's been documented by Red Hat.
It's a rare condition in which one of the symptoms is one person telling others they "seem to misunderstand the english language", "misjudge the spelling" or not reading the posts" while disregarding any advice. Also see "user error".
Quote:
Originally Posted by MalikAsim
Thanks for your support ?
I can't imagine you would require any support we could possibly give but OK, since you've asked, what kind of support would you expect?
It's a rare condition in which one of the symptoms is one person telling others they "seem to misunderstand the english language", "misjudge the spelling" or not reading the posts" while disregarding any advice. Also see "user error".
I can't imagine you would require any support we could possibly give but OK, since you've asked, what kind of support would you expect?
Do you mean to say you said all that instead of 'Predicted error between chair and keyboard' wow!
Also I meant thanks for the info/ support etc
I have taken ur advice and the tests came up with command not recognised bs, so I don't know what to do if the commands u lads are asking me to key are not being understood by the software.
And its unlikely its a bug its just if you were sitting on the chair insteaad of me it would work lol
can you read the other thread u refer to then please
Quote:
Originally Posted by MalikAsim
Do you mean to say you said all that instead of 'Predicted error between chair and keyboard' wow!
Also I meant thanks for the info/ support etc
I have taken ur advice and the tests came up with command not recognised bs, so I don't know what to do if the commands u lads are asking me to key are not being understood by the software.
And its unlikely its a bug its just if you were sitting on the chair insteaad of me it would work lol
Don't mean to burst your over inflated bubble but can you read the other thread please, as I'm sure you should get it.
I asked someone who told me to type ' ls -l /etx/....
If he meant type it as he spelt it or as you were telling me too and as I have been doing since I started. The wtf referd to the not having permission thing.
Then one of you guys started going off one a tangent over it which seemed a bit odd-bally to me
It's a rare condition in which one of the symptoms is one person telling others they "seem to misunderstand the english language", "misjudge the spelling" or not reading the posts" while disregarding any advice. Also see "user error".
I can't imagine you would require any support we could possibly give but OK, since you've asked, what kind of support would you expect?
Read the other thread please - Page 2 - top post I think mate
I'm sorry to have to do this, and I'm sure that the OP won't appreciate me pointing this out, be there are three threads started by the OP and all are going the same way (and it seems as if the only possibility, albeit a distant one, of getting these threads back on track is to intervene in this way).
The way that they are going is that the OP says some stuff about a problem, someone suggests particular commands to run and the OP says there is still a problem (scattered with a few mis-typings and marginal mis-understandings).
What there isn't is a direct 'I typed exactly this' (where 'this' is a correct command as given by those trying to advise) and exactly this other thing is the response. The outcome is that the advisers are not convinced that the correct things have not been typed (and you do have to type exactly the right thing for it to be effective, the command line being notoriously unforgiving of mistakes); to cut and paste the transaction removes this uncertainty, and that hasn't happened.
What then happens is that the OP posts a '...but the problem isn't solved...' kind of comment and everyone else thinks '...well, of course it isn't, you still haven't typed the right thing...' and/or '...you were asked for the output from this command, and all you've done is say that it hasn't worked, that's not helpful...'.
My suggestion is that, for better or worse, you re-read roger_heslop's response, concentrating on that first paragraph until you understand why that was written, and you feel that you can follow that approach to the letter. Then move on to cliffordw's post, try every command that he has suggested that you try and cut and paste the command along with its output back here.
We will then be in a position to start making progress (and, while it does sound like a DNS problem, as suggested, I'm sure that it is possible to misconfigure several things which lead to a DNS problem, so it might not be as obvious as a straightforward mis-configuration of the DNS service itself).
I'm sorry to have to do this, and I'm sure that the OP won't appreciate me pointing this out, be there are three threads started by the OP and all are going the same way (and it seems as if the only possibility, albeit a distant one, of getting these threads back on track is to intervene in this way).
The way that they are going is that the OP says some stuff about a problem, someone suggests particular commands to run and the OP says there is still a problem (scattered with a few mis-typings and marginal mis-understandings).
What there isn't is a direct 'I typed exactly this' (where 'this' is a correct command as given by those trying to advise) and exactly this other thing is the response. The outcome is that the advisers are not convinced that the correct things have not been typed (and you do have to type exactly the right thing for it to be effective, the command line being notoriously unforgiving of mistakes); to cut and paste the transaction removes this uncertainty, and that hasn't happened.
What then happens is that the OP posts a '...but the problem isn't solved...' kind of comment and everyone else thinks '...well, of course it isn't, you still haven't typed the right thing...' and/or '...you were asked for the output from this command, and all you've done is say that it hasn't worked, that's not helpful...'.
My suggestion is that, for better or worse, you re-read roger_heslop's response, concentrating on that first paragraph until you understand why that was written, and you feel that you can follow that approach to the letter. Then move on to cliffordw's post, try every command that he has suggested that you try and cut and paste the command along with its output back here.
We will then be in a position to start making progress (and, while it does sound like a DNS problem, as suggested, I'm sure that it is possible to misconfigure several things which lead to a DNS problem, so it might not be as obvious as a straightforward mis-configuration of the DNS service itself).
I have connected my Install to the network ! Yippee
Through desktop, no config required - if any of you know why it works in GUI but not in CLI then I'm happy for you - you should post it, it may help someone. I've ran lots of tests and found repos weren't installed maybe that's y commands have not worked for me - I DON'T KNOW.
The first step to narrowing the problem, is to run a series of tests to define exactly what your system can, and cannot, do in terms of network communication.
Assuming for example, you have a system with an IP address of 192.168.1.5 /24, you'll want to first test your network by pinging something on the same layer two network, preferably hanging off of the same access layer switch. (For example something with an IP of 192.168.1.6, etc.)
If that does not work, stop troubleshooting DNS, and look closer at your actual IP address configuration with the command 'ifconfig'
Make sure you can ping your gateway. If your DNS servers are on the other side of your gateway, keep holding off on those. If your gateway can be reached, you want to ping the nearest ip address on the other side (for example, your own public IP address if you're NATing, etc.)
Only once you've confirmed routing is working, should start troubleshooting DNS. Try some of the following commands:
Code:
traceroute <dns ip>
dig @<dns ip> google.com
Below are some common files to check your ip settings
Just a heads up, I'm not too familiar with the desktop interface, I find myself using the command line more often than not, so I can't really advise there. Good luck, and if you need further help, run as many tests as you can think of, and post as many details.
I have done this
Code:
Vi /etc/resolv.conf
Result
# Generated by NetworkManager
domain home
search home
nameserver 192.168.1.254
~
~
~
"/etc/resolv.conf" 4L, 79C
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Red had 6.1 connectivity issue
Thank you for helping
