Its not that you router will not have enough "flexibility" per-se as the
issue is how many ports you can have "mapped" based on a small amount of
memory those routers contain. Meaning... you are basically running a
mini-DHCP server on those routers. That DHCP capability requires memory (to
hold the algorithms to even perform such a task) as well as memory for
holding the "customizations" you desire. Those customizations traditionally
are "Port Mapping Tables".
If you play only a couple of games, that use limited ports, you'll be fine.
However, if your games/apps require a large number of ports (and port
ranges)... you'll reach a critical plateau of what you can do... since you
are now limited int he total number of ports you can map.
This plateau is the sole reason why the DMZ (short for DeMilitarized Zone)
concept exists on those routers. The concept is simple... we have limited
memory to house/store the port mapping tables... so we assign a small
portion of the memory for a "master rule" which basically tells the router
"If it isn't in the port mapping table... forward it to the DMZ for
processing/handling".
However, this can have grave security issues... since the DMZ is a "High
Level Rule" that basically renders your "NAT firewall properties" null &
Void. The reason behind this is simple.... your NAT "Firewall" isn't really
a firewall at all. In fact... all it does is rely on the fundamentals of how
a hacker would enter your system.
Meaning:
For a person to enter your system.. he needs to be "let in". This means he
has to first find a "Port" that is open. If the port is open, and there is a
process handling/listening for requests on that port... it will send back a
"return handshake". After the handshake is established... the hacker can
pass data to the process that is listening (he now has a process that is
willing to listen to him), and if the hacker knows a specific vulnerability
in that particular process... he can exploit the system.
So... all the NAT is doing is basically not replying, unless it is in the
port mapping table. No reply = no entry possibilities. The funnier thing
is... your computer already functions this way!
This is also why I find it somewhat comical that Zone Alarm even tells
known to scan certain ports on its own customers to ensure that they are not
hosting servers (like FTP servers) which is a violation of their Licensing
Agreement. You can scan a computer until the cows come home, and even pound
on the door as hard as possible (regardless of OS)... it has no effect
unless something on your puter REPLIES, and then (only then) the hacker must
now hope that the replying program has a vulnerability that he is aware of.
All Zone Alarm does is rely on the ignorance of its users to form a false
sense of security and need. I mean... how many times in here have I heard
guys say "Oh thank goodness I have Zone Alarm... I had 50 attempts to get
into my system just last week... Zone Alarm told me so!". It is simply
purposely invoked hysteria by Zone Alarm to try to up their value/need in
the end user's eyes. Zone Alarm is about as useful as an Ice Salesman at the
North Pole. If you have given Zone Alarm permission to allow programs to
listen on ports, and those programs have vulnerabilities.... Zone Alarm is
100% useless.
Think about it... you give access to ICQ to listen on ports (because Zone
Alarm prompted you, identified it as ICQ as the requesting program to open
the port for, and you said YES)... Say now that ICQ has a vulnerability...
THAT is where the hacker attacks... the PROGRAM. Its the same thing with
email... you open ports 25 and 110 for email. After that.. anything that
comes through those ports is allowed (directed to email prog), if the email
prog has a vulnerability... Zone Alarm is useless... and the attacker gets
in.
Basically, a hacker can beat on the door all day long, and not get anywhere,
since he is not getting a "return handshake" since nothing is listening on
that port. COMPUTERS are not vulnerable to attack... PROCESSES/PROGRAMS are.
So... knowing this.. the moment you set up a DMZ (because of the memory
limitations inherit in 99% of the Home Based Routers on the market)... is
the moment that you tell the router to "ship it off to the afore-told
computer for processing" (or lack thereof). This is also why it is called a
"DeMilitarized Zone"... since that is exactly the effect it has on
security.... it is a security detour of sorts.
This is why I all hardware home routers "limited". They don't really do
much, except allow basic functionability. A software proxy on another
machine is far more robust, and still posesses all of the security features
(and more) than hardware routers.
Cheers,
Schumi
> >Do you mean "NAT Routers". Like Linksys, etc.?
> >If so... they have limited memory capabilities, so mapping ports will
reach
> >a maximum. Which is something to be concerned about if you play more than
1
> >game on different ports, or the game uses a broad-spectrum port range.
> >The only alternative left with many of them is to assign your Gamebox as
the
> >DMZ... which basically forwards all ports not listed in the Port Mapping
> >table to your gamebox... which in turn means that your NAT security
(which
> >is of little consolation) is null & void.
> >But we may be talking about different things.
> Hey Jason. Glad we're on this subject. I just bought a D-Link DI-704(combo
> switch,router,NAT firewall)to network two home computers. I have yet to
get the
day
> figure it out, it seems highly configurable. Your suggesting it won't have
> enough flexability? Whats the way to go without buying additional IP
address?
> --
> Don Scurlock
> Vancouver,B.C.
> GPLRank -15.27
> MonsterRank 91.34
> Come see how you rank, at the GPLRank site
> http://www.racesimcentral.net/