Routers Firewalls QOS VLANS

415eric
Posts: 416
Member Since:
2009-10-29

This has probably been hit more then a few times but I didn't have much luck searching for it.

I would like some input on firewalls people use. In general I need a device that will handle VLANS, QOS and traffic shaping, capable of allowing or denying access to ports based on the incoming PCs public IP, and possibly an Aux or OPT for failover. There might be other stuff but I can't think of it off the top of my head.

I have used a Sonicwall TZ170, TZ100, and TZ200. My big issue with them is they don't handle the SIP NATing very well . The system would work great for a day but then suddenly fail. I tried with the three different models and had the same results. I have seen some users have success and I even followed a walk through or two but no success. I have seen a lot of users having the issue same I had with no resolution.

I have used the Linksys WRT54GL with the DD-WRT firmware. These work great for small offices they have basically all the features you need. They don't seem to allow access to ports based off of incoming public IPs but all other aspects work. They are limited in their throughput and connections which could quickly be an issue for an office over 8-10 people. If you are setting up a SOHO network with just a couple users and a couple phones this is by far the best and cheapest route to go. A new device can be purchased for around $60 and the firmware is Open Source.

I have used the Cisco 881,861. These will do everything I need and more the only real issue I have currently is configuring QOS. I am by no means a Cisco expert so delving through the CLI and trying to make it work is no fun. There is the Cisco Configuration Professional software which provides a GUI and it works in most cases. I still have an issue setting up the QOS and I also noticed that the changes you make in the GUI don't always take affect which forces you to do it via CLI. These devices are rock solid and work great in most cases. I have quite a few deployed and currently haven't had any issues with QOS but I would love to avoid having issues. The big drawback for most people might be the price $500-$900 depending on the features you want.

I have used a Netgear Prosafe FVS338. I can't say I really had any complaints but I also did not test it for a long time. I was able to make a trixbox work behind it so that is a plus. I did not mess with VLANS or QOS so I am not sure if it can handle those things.

I could always build my own but I would rather just purchase a device from a company that specializes in making firewalls. Using something custom can turn into a big headache in situation like if I left town and a firewall died and I was the only tech that knew how to build/maintain the device.

--


SkykingOH
Posts: 9677
Member Since:
2007-12-17
I think you summed it up.

I think you summed it up. You get what you pay for.

The only real alternative is the Juniper SSG series. The great thing is you have the SSG20 on the low end at $400.00 that runs the same code as the 30k enterprise box.

I am a huge fan of Juniper.

--

Scott

aka "Skyking"



415eric
Posts: 416
Member Since:
2009-10-29
SSG20

Thank Scott your input is always appreciated.

Is the SSG20 mainly a CLI based config? Have you configured QOS on one? Have you configured a Cisco, how different are the CLI commands?

--


SkykingOH
Posts: 9677
Member Since:
2007-12-17
Quote: Is the SSG20 mainly a
Quote:
Is the SSG20 mainly a CLI based config?

It has a CLI and a web based interface.

Quote:
Have you configured QOS on one?

That's a very broad question. ScreenOS supports several QoS strategies. Unless the upstream host respects your QoS mechanism you are only covering 50% of the issue. ScreenOS even supports packet classification within VPN tunnels.

Quote:
Have you configured a Cisco

A Cisco what? I have over 12 years of experience with Cisco IOS and security software. My company is a Cisco Partner and has deployed countless millions of dollars of Cisco solutions.

Quote:
how different are the CLI commands?

Not sure how to answer that, they certainly do not use the same keywords and arguments.

Juniper is policy based while Cisco is access list based, the whole strategy is different.

--

Scott

aka "Skyking"



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.