• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Just ordered DSL....get a router or use a PC?

Woodie

Platinum Member
I've just ordered DSL from SBC/SNET, should be here by 10/1. 😀

Anyway, I'm trying to decide how to connect to my network, and searching the FAQ and the forum came up with useful info, but didn't really address my question.

Should I purchase some sort of router (NetGear seems a solid performer) or take an older PC, and make it a *nix based firewall?

Things to weigh:
I'm cheap, and don't want to spend much.
I can get a P166 or 200 virtually free.
Current home network has 3 pcs, including a DNS/DHCP/WINS server (yes, I have Windows) all on a token-ring network. The server has t/r and ethernet nics.
I'm very security-aware, and somewhat paranoid, so I MUST have a firewall between me and the internet, not on any of my current machines.

For architecture, I'm thinking I'll just drop in the DEVICE (router/firewall) between the DSL modem and the server (ethernet nic). That way I don't have to resetup any of my existing network, just turn on routing on the server, and set a new default gateway (via DHCP)for the clients.

I know I'm adding some latency by using the server as a router, but I don't game online, and that makes the least amount of work for me.

Running a software firewall on the server is unacceptable from a security perspective (it is a Windows server).

So, do I buy a NetGear or do I drop 2 nics into a P166 machine?
 
At this point in time when Entry Level Cable/DSL Routers cost $50 or less, I would suggest to use one even if a person does not have a Network. It worth the price for the Hardware (NAT) Firewall, and DHCP server.

In case of PPPOE DSL it is even more important. The combo PPPOE software and software NAT arrangement is a source of trouble.

In new installation you log on to the Router, in the PPPOE menu you type username and password. As long as you don't switch off the DSL Modem, and the Router you are connected "forever" (the computer can be switched off). The Router?s PPPOE capacity is independent from the Computer, and it keeps the connection alive.

Working through the Router should yield faster smoother (5%-%10) Internet connection.

If it is not PPPOE, it is your call.
 
When we switched from a dedicated pc internet server to a router, our performance improved dramatically. But, we weren't using Linux, and I know some people here are quite high on it. Quite apart from any performance or technical issues though, it was nice just to be able to replace this big bulky pc with a nice little tiny router. So, if space is an issue and everything else is more or less a tossup, go with the router.
 
a router will be quick and eazy.

a nix box as your router/firewall will be much more fun and rewarding.....IMHO

of course you will need a switch or hub for the nix box.
 
Ive got SBC/SNET DSL (Naugatuck, CT), the router made things much better connection wise, no buggy software to install for connections.
 
Thanks for the input folks. Although I'd like to play with a linux/BSD based firewall, it is bigger and would take more power, so I'm leaning towards the router solution. BTW, yes it is PPoE.

Now, any suggestions for router/firewall? I don't need DHCP or DNS, just the firewall (more than just NAT) and PPOE. For future needs, I'll need at least a five port (1 server, 4 clients, and the uplink). I know that doesn't appear to leave room for expansion, but keep in mind that I already have a t/r network, that's working just fine.
 
If you need a more elaborate Firewall you can not count on the Entry Level staff, you have to look at the more expensive Routers, most of them go for over $250.

On the other end you can get 8 ports Entry level Router, and supplement the protection with good Software Firewall on each machine.

Look over the Routers specs here it will give a perspective.

Practicallynetworked.com - Router's List.
 
Woodie,
I was able to get a 'discontinued' 3Com Home Ethernet Gateway router for $50. 3Com still honored its warranty and gave me good support setting it up.
It has a 4port user including a parallel printer port. Input is RJ45 from the DSL modem. 10/100 based.
 
Most of the cheaper Dsl routers come NAT enabled for connection sharing. This actually facilitates the need for DHCP, as Nat needs to 1 Keep track of the computers on your internal network, and 2 Make sure That they have to pass through the NAT server in order to controll that access. Usually on newer dsl routers, They will also serve as a DHCP server automatically as this is how NAT works. Usually it will assign IP adresses in the range of 192.168.0.1 -192.168.255.254. This IP address range is reserved for internal networks and will not be recognized on the internet. But you seem to under stand that already. Network Address Translation will not work without an Address to translate. If you already have a working network without a DHCP server installed, Then just enable them as clients and all should work fine. If you have a Win2k server, then you already have all the NAT you need already. I am sending this through my Netgear RP114 I bought at Compusa for $75.00 and it actually came with two NICS also. I reccommend it.
 
Check the Hot Deals forum for a firewall/router/switch, it's the easy way out. I use a SMC Barricade which also acts as a print server for the network. All of the low priced models have pretty much identical features except for that.

Using a DSL router> firewall/switch> network topology is actually easier to set up, there's no need for an addl. nic in the server. Treat your server as if it were just another computer, let the firewall serve as security. This is easily the most common method for home networks. You can also uplink addl switches/hubs into the firewall device to accomodate more clients.
 
Back
Top