Quote:
|
Originally Posted by NoodleKnight
I don't quite understand, it was serving DHCP, there isn't really other common way to run a router, except for ad-hoc (which I'll vouch, wasn't the case).
To get to FSN you had to connect to and IP which had port 80 forwarded. Unless you have two machines set up for DNS hosting along with your server, there isn't a way to access a server within the LAN via easy-to-remember domain name, if that's what you're talking about.
Correct me if I'm wrong, which I think I probably am.
|
DHCP (Dynamic Host Control Protocol) is the process by which IP addresses are served to devices that connect to a network, unless they already have a static IP assigned to them for that subnet.
DNS (Domain Name Service) is a service that translates Domain Name to IP address. This is used extensively on the INTERNET, but seldom if ever on a small private, or SOHO network, which is the case here. (SOHO stands for Small Office Home Office).
In the case of serving FSN at the regionals, there is no need to use DNS or port forwarding. All you have to do is point a browser to "http://<serverip>" where "<serverip>" is the IP of the server. The web server should automatically serve FSN if it is set up correctly.
Please feel free to come by our pit, I would love to answer any question you might have regarding this.
As far as your router is concerned, I'm not surprised. Lynksys WRT54G's have a nasty habit of locking up at the worst possible time. A simple power cycle or reset usually brings them back to life. What effect your modifications had on it I'm not sure. If we can find some time, maybe we can test it.