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.
While my WinXP box (in a test DMZ area, 192.168.1.15) can connect to my Debian (Sarge) server on my LAN (10.42.42.146), I cannot access other servers on the LAN. (Which, of course, is the whole purpose.)
I can ping over the VPN to the server (10.42.5.1), but I cannot ping to other internal boxes (e.g. 10.42.42.20, which is pingable within my LAN).
Since an initial connection and a direct ping work just fine, I belive my firewall is directing 220.127.116.11.75 UDP:1194 to 10.42.42.146 just fine.
I have executed the following on the Debian server, which should allow for packet forwarding:
key server.key # This file should be kept secret
server 10.42.5.0 255.255.255.0
push "route 10.42.42.0 255.255.255.0"
keepalive 10 120
remote 192.168.1.75 1194
0x1 ........................... MS TCP Loopback interface
0x2 ...00 ff 70 6c 63 de ...... TAP-Win32 Adapter V8 - Packet Scheduler Miniport