> Shouldn't effect a thing all the INTERNAL connections you made
> before should remain unnaffected the only thing that changes is
> the connections to the outside world.
> I actually endorse using this thing as long as you don't need the
> power or flexability of the Linux ipchains firewall or IP
> Masqing. You may run into a funny app that needs some special
> port handling which the Linksys may not do very well.
> It is a cheap effecient and low cost way to seperate your
> firewall from your internal servers (which increases your
> secirity somewhat). I am hard pressed to justify the expense and
> power consumtion of a second PC to do this for home use or very
> small office.
I agree with you totally.
Got rid of the old Linux firewall/router box last year for the same
reasons.
Regardless of brand, or location. Hardware stand along
router/switch/with/IP-packing/portforewarding is the BEST way to go. For
added security. Install portsentry on each box.
Home or office. Actually, especially at home, if you don't like constant
nagging noise.
I even put all my computers inside a closet, just run everything through
two monitors , one tiny keyboard and a Wacom digitizing tablet thru a
KVM. Can't stand the noise.
With the hardware standalong router/switch. Just plug all your RJ45
cables in, fire up your browser. And you're done in 10 minutes.
VERY little heat, no annoying fan/hard drive noises, takes very little
space.
All for under $100 to mid $200. for SOHO models. Make MUCH more sense to
spend $50. on an old clunker, $50 for more RAM. $40-50 for 2 NICs,
amight even need a bigger HDD, plus, after all your spendings, and
setting it up. The old clunker might still dies on you anytime. If not,
more heat, and the very annoying fan/hard drive noise... if you have
more than 2 computers going, the noise is unbearable.
Just let them rag writers hype all about it, or they'll soon run out of
things to write.
I'm so tired of reading how to set up a firewall with an old clunker
with Linux.
It's getting too old and tired already. Especially the price of most
hardware are so cheap.
-Alex / blowfish
> The Linksys can act as a DHCP server, handles PPPoE (may require
> a software upgrade) and does NAT quite well. It even incluse
> it's own builtin 4 port hub. A cool deal.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >I've recently been having numerous stability problems with
> dhcpcd, and since
> >the price of the Linksys routers have come down significantly
> since the last
> >time I looked... I'm about ready to give inand pay the $170 for
> one.
> >However, I'd like to make sure that it will not render some of
> my
> >connectivity useless. I still plan to have my Linux box act as
> a file
> >server (downloads weather data automatically, serves it to all
> computers on
> >the network via Samba, FTP, etc), and I'd still like to be able
> to remotely
> >connect to the Linux box. Will this be a problem with the
> router??
> >Currently, I have 2 windows machines and a hybrid (Linux and
> Windows)
> >workstation behind a Debian server/firewall which has IPMASQ
> installed and
> >running. If I were "off network" and tried to connect to any of
> the
> >computers behind the IPMASQed machine (via ssh or telnet, ftp,
> etc) I
> >couldn't do it. With my Debian server behind the router, would
> the same
> >hold true? I called Linksys and talked to a sales rep (not sure
> how much he
> >really knew), but he did say I could setup the Linksys router's
> firewall to
> >allow connection to a computer on the network through a specific
> set port.
> >It is extremely important that I can still connect to the file
> server
> >remotely via ssh and ftp. Is there anyone out there who has
> used the
> >Linksys routers that can tell me if this will work?
> >Thanks much,
> >Mike
by