There is clearly a need for a thread like this. I'll work on filling it in over the next while.
Topics to be covered:
- Cable vs ADSL vs Dial-Up vs Satellite
- Routers vs Hubs
- LAN vs WAN
- DHCP
- DNS
- Static lan configuration
- NAT / port forwarding
- why pings should be allowed
- UDP and TCP
- Latency vs Bandwidth
- Software firewalls, how to use them and when.
- Where to find manuals and why you should read them in full.
- Workgroups, Domains and Subnets
Those who have the expertise, feel free to help out and correct me where I'm wrong and suggest additional topics. I don't have the patience for working on it today, but this needs to be done.
Handled in the following :
Cable vs ADSL vs Dial-Up vs SatelliteMore to come...
Routers vs HubsDefinitions:
ROUTER: A device that determines the next network point to which a data packet should be forwarded enroute toward its destination. The router is connected to at least two networks and determines which way to send each data packet based on its current understanding of the state of the networks it is connected to. Routers create or maintain a table of the available routes and use this information to determine the best route for a given data packet
HUB: The point on a network where a bunch of circuits are connected. Also, a switching node. In Local Area Networks, a hub is the core of a star as in ARCNET, StarLAN, Ethernet, and Token Ring. Hub hardware can be either active or passive. Wiring hubs are useful for their centralized management capabilities and for their ability to isolate nodes from disruption.
So, the difference? A router must have TWO networks to function, a HUB simply re-transmits the packet on
all available nodes. A router routes the packets to and from separate networks.
ADDENDUM: Perhaps a more apt comparison would be the following:
HUBS VS SWITCHES
I'll add that on when I'm done with this list.
LAN vs WANLAN : Local Area Network. The term LAN describes a local network. This LAN can consist of one network, or seperate networks connected via a router.
WAN: Wide Area Network. This is a network that spans a large geographical distance and interconnects two or more LANS or MANs. The internet is the largest WAN in existance.
ADDENDUM : MAN - Metropolitan Area Network: A data network designed for a town or city. In terms of geographic breadth, MANs are larger than local-area networks (LANs), but smaller than wide-area networks (WANs). MANs are usually characterized by very high-speed connections using fiber optical cable or other digital media.
DHCPDHCP : Dynamic Host Configuration Protocol (DHCP) is a communications protocol that lets network administrators manage and automate the assignment of Internet Protocol (IP) addresses in an organization's network. DHCP allows devices to connect to a network and be automatically assigned an IP address. Essentially this allows for better management and utilization of IP addresses, as well as lowering costs associated. Using DHCP, a client connects to the DHCP server and asks for an IP address. This is set on the
scope, along with other information such as DNS servers, NTP servers, and WINS server addresses. The client then receives a IP address, and the DHCP server records this "registration" of the indicated IP address in it's table. It also records the time / date when that registration is tombstoned, or revoked if the client doesn't "check back in" (this is specified in the DHCP server options, not to be mistaken as included in the scope options) within the set time period (usually 1-7 days). The DHCP
client will usually actually check for the client on the network 1/2 of the expiry set - so if it's set for 7 days, then in actuality it will perform it's first check in 3 1/2 days. This allows the maximum usability of a given subnet without wasting any IPs - especially valuable for ISP's who recycle their IP addresses constantly.
DNSDNS stands for Domain Naming System, and is the process used to translate IP addresses into human friendly web addresses. Think of your IP address similiar to your mailing address. The Postmaster would have a helluva time delivering mail to your house if every other house on the block had the same mailing address. Thus, each and EVERY device on a network MUST have a UNIQUE IP address. That being said, it would suxxors to have to type in "
http://216.109.112.135/default.htm" to access
www.yahoo.com, and it would make
Host Headers used in website hosting useless.
Thus, DNS was born. DNS translates those human friendly names like "
www.dynaverse.net" into the actual IP address and then connects to the authorative DNS server for that root domain to get the necessary information regarding the sites/data available there. Let's track the actual process utilizing D.Net as the target.
1. User types in "
www.dynaverse.net" in the browser URL window. The browser looks at the current TCP settings and obtains the DNS servers the client is mapped to. Before querying those servers, it checks it's
cache to see if it already has looked up that URL (Uniform Resource Locator) and translated it to an IP address. If it has, skip to step 4.
2. System queries the DNS servers the client's TCPIP stack has assigned to it, either via
DHCP or statically assigned for the IP address of the site. IF the DNS server does not have the information in IT'S cache, then it queries the ROOT Servers, of which there are 13, to find out what DNS server is
authorative for the DNS
ZONE. It then sends a query to the authorative server for the requested resource.
3. The authorative server responds, the client machines transparently maps that to the URL, and the browser contacts the IP address of the resource as stated in the DNS ZONE for a webserver at port 80.
4. The webserver then replies back, a connection is made, and you are surfing the website !
I'll include a zone dump when I am in the office for D.Net so you can see what a DNS Zone looks like.
Static lan configurationSimply put, this is when a user or Administrator specifies the information for the TCPIP stack, I.E. Default Gateway (the path out of the network to other networks), DNS servers, WINS servers and IP address. Having a statically assigned IP address of course means you're not using
DHCP. Servers are almost always statically assigned IP's as having servers aquire IP addresses via DHCP would render DNS useless.
NAT / port forwardingNAT stands for Network Address Translation. Port forwarding is actually a different subject, I will cover both here.
NAT: This is what allows a home user to have more than one computer behind a
ROUTER while using only 1 IP address. Essentially, it's like this:
The Router has a external, or WAN interface. This is a single IP address usually obtained via DHCP from the IP scope of the users ISP. Since Routers, by our above definitions, require two networks to operate, NAT creates those two networks by utilizing
non-routable address blocks, such as 10.0.X.X, 192.168.X.X, or 172.16.X.X. These non-routable classes will NEVER be on the internet, as they are reserved for internal private networking. The end user would then set up the Router's internal , or LAN scope. By default on most routers this is the 192.168.X.X subnet. Then, the internal network gets it's IP address via DHCP from either the router or a local DHCP server, and specifies the router as the default gatway for traffic OFF the 192.168.X.X subnet. Thus, you can have up to 253 computers on the internal network - the 1st address and last address of any given subnet is ALWAYS reserved for the network address and broadcast address, respectively. As a packet goes out from the internal network , the router records the IP address of who it was from, where it's going, and waits for a returning packet that is addressed to the "original sender". It then routes the packet to the correct internal IP address of the client whom sent the data.
Thus, as one could imagine, you've now allowed many many internal clients to connect to the internet behind ONE IP address on the router. We'll leave the positives and negatives to this approach for a later discussion.
Port ForwardingWIP