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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
Now, if I connect the server to the Netgear Wireless router directly (CAT5), it connects without a problem. But when ever I try to make it connect using the setup shown above, it can't connect and gives me the following error:
Determining IP information for eth1...PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
Nice picture - but he's correct, you need a router splitting the Cox connection. The reason is this - your cable company probably limits you to 1 ip address (check your EULA). Well, if the switch is allowing concurrent connections without subnetting it, it's allowing the use of more than 1 global IP - can't (well, can, but Cox ain't gonna let it) happen. You need to replace the DLink switch with a router, and the wireless router with a wireless switch. Know what I'd do? Take the DLinka nd the Netgear back, and get a DLink wireless router - all problems solved.
You will have to connect the server to the router, then do port forwarding (port 80, 8080, etc..) in order to run the webserver. I think that you router is also a firewall, check your manual. To learn more about routing go here.. http://www.ox.compsoc.net/~steve/portforwarding.html