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.
Having computer problems. Anyone have an idea what is wrong? My landlords did some work thing where they had to cut off power. When the power came back on something was screwed up, my main system no longer has a connection. It was working just fine, I had rebooted the computer a few times earlier with no problem, but I hadn't rebooted the server.
I use iptables to route the traffic through the server (which I am typing this on now) to my main system using:
The server has an internet connection fine. ifconfig shows the above command fine. I have my main system set to 192.168.0.2 with the gateway of 192.168.0.1. From the server I can ping .0.2 just fine (when the main system is on), but the main computer can not ping .0.1.
I added some prerouting to forward the port so I could stream my webcam, and I thought that might be the problem:
I have the connection coming straight from my cable modem to eth0 then from eth1 to the main computer. The only changes that I made recently was to ass the rule to forward the port as listed above, but it was working just fine, and even forwarding the port fine, until the server was rebooted.
so I left that off when I rebooted the server and still nothing. I'm just about to say screw it and reinstall the server, but then I would lose my webpage and all of that, which would be a hassle.
its an obvious question, but just in case... did you load the iptables rules? also on your main system are you sure its set up to use 192.168.0.1 as your gateway? maybe theres no route on your gateway to find your lan?
Originally posted by phek its an obvious question, but just in case... did you load the iptables rules? also on your main system are you sure its set up to use 192.168.0.1 as your gateway? maybe theres no route on your gateway to find your lan?
yeah, I actually never have to reboot my server, so I never got around to making it load the iptables info automatically since it takes like 30 seconds to type that in. So I do the ifconfig and the iptables commands whenever I boot up the server, so I'm pretty sure it's loading.
Also when I do an iptables -L -t nat it lists the pre and postrouting there.
And I'm pretty sure the gateway information was fine since it has always worked before. I'm at a loss because one minute it was working fine, then the server got rebooted and now all of a sudden nothing.
it was the ip_forward. For some reason it decided to get pissy with me and set itself to 0. It never had done that before and I had forgotten about that little setting. What would cause it to randomly go from 1 to 0?
/proc doesn't actually exist on your hard disk, it's a virtual filesystem so files in there are not automatically saved on a reboot. There are programs such as sysctl that will save some data from /proc when the machine is shutting down, then reload it when the machine starts back up, but since your machine didnt get to run init 0/6 when the power went off,
the data couldn't be reloaded. It would be a good idea to put
echo "1" > /proc/sys/net/ipv4/ip_forward
into your firewall script.