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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
This is probably a simple question. Is it normal that when I make a change to the routing table using 'route', for example 'route add default gw 192.168.1.1', that it should take a while for the changes to start working? When I make such a change, the routing table seems to be changed immediately, in that when I type 'route' again, and wait, eventually the whole thing is displayed... But it hangs on the route I just added, the default gw. Only after somewhere between 30 seconds to a few minutes, does the route start working.
Not sure how clear I'm being here. Basically, if I add a default gateway for example, "route add -net default gw 192.168.1.1 dev ra0", then try to ping 192.168.1.1 (my router), or some other host such as google.com, there is no response... If I try again in a minute or two, it is suddenly working.
Any explanations for this? Is this normal behaviour?
When you make an update to route (i.e. changing your gw [gateywa] address), do a quick route -n (the minus n will show IP addresses only, not resolved into hostnames -- thus, it's faster, more immediate). Are you deleting your previous gateway if one was set? Also, what kernel rev of Linux are you running? (just curious)
I'm running Debian with kernel 126.96.36.199 (soon to be 2.6.9 since I need to do a recompile for some other reason, and I figured I might as well go with the latest).
Actually I was a bit silly here. I don't know why I was so quick to assume it was the route that wasn't being updated quickly... It occured to me that even without that route in place, I should still be able to ping 192.168.1.1. However, I wasn't able to... So basically, what the problem actually is isn't anything to do with the route. It's that when I apply settings to my wireless adapter with iwconfig, *those* settings take a while to kick in.
That is, if my wireless interface is down, and I type:
Everything seems fine. It shows the MAC address of my access point, yet when I try to ping it (192.168.1.1) I get "Host Unreachable", or something like that. That is, until I wait a minute or so. Then suddenly it starts working.
If I type "ping 192.168.1.1" and just leave it, I get loads of errors, until all of a sudden I start getting replies, and after that starts happening, everything works fine... Until my connection with the router is lost for whatever reason. Then I have to undergo the same slow process again.
Any ideas why the connection is being slow to start working?
When its not working, do an ifconfig and a route -n -- save the outputs. When it is working correctly do the exact same commands and check the outputs against the time it wasn't working. If they're different, and you still can't figure it out, post both of the output files here.
As you can see, the differences are in the second half of the ifconfig output. I don't understand what that stuff is unfortunately... But it looks like the sort of thing that is supposed to change anyway.