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 trying to use Coyote Linux (www.coyotelinux.com), which is basically Linux Router Project with an easier config script to build a floppy. I've had no problem connecting to the outside via a dialup or ethernet using DHCP, but can't quite get it to negotiate the connection to my inside network. I can get other machines running on it with no problems, as I am using static IP addresses. Any suggestions?
I got Coyote Linux to connect up to the inside and outside.... now a new problem....no routing.
I don't have a firewall on inside machines, and when I request the outside network, the router dials up and connects, but doesn't route any data between my home LAN and the Internet.
The main thing is that you set it up to forward
run this command...
cat /proc/sys/net/ipv4/ip_forward
you should see this...
1
if not run this command...
echo 1 > /proc/sys/net/ipv4/ip_forward
you will have to put the in your firewall scripts or rc.local or somewhere that will run it when you boot if you want it to work all the time.
the other thing is your ip addresses for the internal machines, are you using ip MASQ?
if you have non-routable ip addresses like most people you will not be able to use them on the internet. You will have to always use the routers ip address. This requires ip MASQ to be set in your firewall rules
use the internet interface name in the place of ppp0 if it's not the right interface name.
for iptables...
iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE
for ipchains...
ipchains -A forward -i ppp0 -j MASQ
check the security forum or lookup rc.firewall on google.com for some rules. These are just the masq rules and should not be taken to mean that this is all you need to use.
Make sure your policies are not set to restrict all traffic
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.