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.
OK, the d-link supports virtual servers. The help page indicates that I can get to the server (port 80?) from the WAN. I think that my DSL provider will block that, but I really want to run an internal server anyway.
How do I tell the Linux box what name to respond to on the LAN (inside the router)? (How do you put a DHCP IP number in the /etc/hosts file?)
Your name doesn't really matter on your LAN, because your computers won't be able to resolve that name to an IP unless all of them have your IP recorded in their hosts files. Windows computers I know do not refer to their host file most of the time, just go straight to the ISP. Linux computers will, but I don't see much point in putting a name in all of your LAN's computers.
Apache doesn't really care what your name is, it just responds to whatever's on port 80 or whatever you set it up as.
So if you really wanna put a server name into Apache, I'd just put your LAN IP.
For the other LAN computers to connect to the Apache computer, just type in the IP address unless there's a big problem with doing so.
I'm not a frequent user. Is it necessary for me to query the Apache server before I know what IP to point my browser to? This is what buggers me about DCHP. The computers on my LAN are a Mac (OS-9), Win-XP, and the FC2 server.
It looks like I will have to get used to logging into my router (admin passworded) to find out what IP numbers are in use today. I am really not excited about teaching my Mac user how to do this, just to see the web pages....
As I have admitted to being a newbie, "make the IP static" is like magic to me. Does FC2 have a wizard to help, or must I muddle through man "everything netlike" to find the obscure set of commands to do this?
as i said, it should be a setting in your router. i have one of the most basic d-link routers, dl-604, and it has the option to use the router as a DHCP server for the lan and to set IPs statically. maybe your router doesn't allow that, but afaik, most routers do allow it. read the documentation for your router, or post the model if you can't figure it out so someone can help you do it.