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.
One thing...
Edit the following files..
/etc/sysctl.conf
In this file change the value of "net.ipv4.ip_forward" from 0 to 1
and also "net.ipv4.conf.default.rp_filter" 0 to 1
The above might help u if u have already not done that..
Also make sure that u r using correct dns server of your ISP because in windows ICS if you entered wrong DNS address- it works but take little long to resolve but if u have provided in wrong dns in LInux it never works..
I don't remember but same thing was with one of my friend a long time ago.. and at the end we found that it was only because of wrong DNS server address.
To know wht is ur exact dns server check ur /etc/resolv.conf file while u r connected to net and there entry "namerserver" will tell u the dns addres of your ISP.
Originally posted by Blindsight You can ping out fine from the linux box? Try pinging google from linux.
Also, when pinging from windows, try 'ping -t -w 5000 www.google.com' that way it'll wait 5 seconds before timing out. I have to do that from my network because I'm deployed in the middle of nowhere and it's about 2 seconds from here to anywhere else on the internet, heh.
If your DNS is pointed to your linux box, the windows machine may not be getting out to the internet at all, it may just be getting dns resolution from your linux box.
try traceroute -n www.google.com from the linux box and see how far it gets out, then try tracert -d www.google.com from your windows box and see how far it gets.
This'll aid in finding an answer, and keep the ball rolling..
Thanks for trying to help.
I can ping google from linux no problem.
And tried the ping -t -w 5000 command, but it still times out.
I've tried it without the linux box as a primary dns and with... either way it times out.
tracert from linux to google works fine. From windows it times out after getting to the linux gateway (192.168.1.1)
Originally posted by RickyJaff One thing...
Edit the following files..
/etc/sysctl.conf
In this file change the value of "net.ipv4.ip_forward" from 0 to 1
and also "net.ipv4.conf.default.rp_filter" 0 to 1
The above might help u if u have already not done that..
Also make sure that u r using correct dns server of your ISP because in windows ICS if you entered wrong DNS address- it works but take little long to resolve but if u have provided in wrong dns in LInux it never works..
I don't remember but same thing was with one of my friend a long time ago.. and at the end we found that it was only because of wrong DNS server address.
To know wht is ur exact dns server check ur /etc/resolv.conf file while u r connected to net and there entry "namerserver" will tell u the dns addres of your ISP.
Hi, I've checked my /etc/sysctl.conf file and those values are already set to 1.
And i've checked the DNS addresses are right, and they exactly match the ones in /etc/resolv.conf and /etc/ppp/resolv.conf
i used the iptables-script at the beginning of this list.
and a adjusted my network start-stop script.
coz every time i restarted my network it stopped
forwarding.. (and that was my prob)
so you might look at your init.d/network script and
find some parameter about the forwarding..!
sorry.. that was all for me.. rest works ok dokay now..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.