Sitecom 300N X4 WLR-4000 Wireless router review

What does a router do ?

For those of you that understand roughly what a router does and have some grasp of the countless abbreviations that seem to clutter this subject, just skip over to the next section.

For the rest, lets start easily. You are reading this webpage through a link called guru3d.com, this link relates to an ip address (if you don't believe me, open a dos / command prompt and type ping guru3d.com). The ip address relates back to a physical machine in the world, which hosts this text. Your computer has a very similar setup.

The way your PC connects to guru, is through (amongst other things) routers. You are connected to your ISP through cable/dsl/dialup, now I pretty much guarantee that you are then passed through some form of router, which combines you and everyone else connected to the ISP, into another ip address. This (very simplified model) happens in both directions between you and guru3d. This process is called network address translation or NAT, and can be found in every off the shelf router. One last point about NAT is that there are two sides to it. The local side, and the world side. You are on the local side of your ISP and guru is on the world side of your ISP. When you get a router, you will be on the local side of the router, guru (and your ISP) will be on the world side of your router. The local side is referred to as the LAN side (local area network) while the world side is referred to as the WAN side (Wide area network).

e.g. PC A (192.168.0.1) <----> (192.168.0.254 - LAN Side) Router (38.22.22.1 - WAN Side) <----> Internet

NAT can be built on to provide various options that can be adjusted inside a router, and depending on how good the designers of the hardware are, many administration functions are born e.g. Blocking access to the internet for certain machines on your network.

NAT is often referred to as a hardware firewall, this is my pet hate, NAT is NOT a firewall. Pure NAT does protect your machine from attacks, but only because the attacker does not have the required information to locate your machine. i.e. The attacker may have your routers address of 38.22.22.1, but hasn't got the routing information to get to your 192.etc address. A firewall can often be included in your router, however referring to NAT as a firewall is wrong (Rant over!).

Back to the networking primer
Along with IP addresses, there are also MAC addresses. MAC addresses can be referred to as physical addresses as they are usually only accessible on local networks (lets keep it simple eh) and few MAC addresses can be changed. In fact, MAC addresses are set by the manufacturer of the hardware and should be unique. Although MAC addresses are used heavily in routing, we will only cover them here for simple uses.

The first time you should have come across a MAC address (if you are on something like cable) is when you registered your modem. You would have had to tell a server somewhere (via an operator maybe) that this modem exists and requires service. With a router, you need to clone the MAC address of the modem for NAT to work properly. After that, the WAN side of the router needs to have its IP address set (usually automatically), which leaves the realm of MAC addressing so we stop there!

The next time you may see MAC addressing is when you are dealing with local machines. Like we discussed earlier, many routers have administration functions, for instance blocking access to the net for one or many computers. This is very easy to do, and in one form or another uses MAC addressing.

Every network card also has a MAC address, the router can control what access is allowed via these MAC addresses because every request must go through the router.

In a generic example, a router dishes out IP addresses to clients via a DHCP service (how ISP’s work for 100% of dialup users). A simple use of MAC addressing, is to split the IP range up and assign the same IP address(es) to a / many selected PC(s). Whats the use of that I hear you ask. Well this means now, that if any ports need to be opened on the firewall, you can open the port to only one machine, and therefore not exposing anyone else on the network to this open port. Because you have made the machine(s) in question have the same address, you can be 100% sure that it is only those machines that you are distributing the service to. This is also a handy reference because a MAC address is hard to remember, where as a 3 digit number is much easier in comparison. Only 3 digits because most routers only assign 253 IP addresses, e.g. 192.168.0.1 -> 192.168.0.253 so you only need to remember the last three octets.

Anyway, that is the basic set of networking that you really need for this review. Have a look at the networking section in our forums if you have any other questions, there are a few links for general information, or you can ask questions if you are still unsure of a few points.