Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Considering both of neither of these are routers your question is misleading at best and confusing at worst. Words do have meaning and we should use them correctly to ensure our request are understood. Even in today's marketplace where there is considerable overlap in function even a layman should understand that even though firewalls can route they are not routers. The converse also applies. Precision is your friend.
To answer the question as posed we use Cisco routers. If there is need we then deploy firewalls from: Checkpoint, Cisco, Fortinet, Juniper, or Palo Alto according to customer needs or preference.
You knew exactly what he meant...
Considering both of neither of these are routers your question is misleading at best and confusing at worst. Words do have meaning and we should use them correctly to ensure our request are understood. Even in today's marketplace where there is considerable overlap in function even a layman should understand that even though firewalls can route they are not routers. The converse also applies. Precision is your friend.
To answer the question as posed we use Cisco routers. If there is need we then deploy firewalls from: Checkpoint, Cisco, Fortinet, Juniper, or Palo Alto according to customer needs or preference.
Zyxel
1 PA-500 with threat-prevention, bright cloud url filtering, and premium support came $6,120.
There is a severe lack of proper terminology going on in this thread. Ether that or none of you know what a router is. You guys are all listing off firewalls not routers. Yes they have some router like features but they are not routers.
We use a pair of Cisco 3800 series routers here at work.
The only major complaint I have is VPN traffic shaping. You can't traffic shape on a vpn interface unless you shape the whole pipe. Have you ever run into this issue? How did you handle it?
I haven't had to deal with that (yet). We have dedicated circuits for our VPNs with fail over to our other lines via Quagga. VOIP is the primary use, but a lot of AD/minor filesharing/etc flows over the line and we've never had a complaint about VOIP, even when under moderate load.
Does it not work to assign an interface to the VPN and shape on it?
Unfortunately, it does not :-(. My current solution is splitting data into one vpn link, and VOIP into another link, and then shaping each pipe accordingly. I struggled long and hard with this and Ermal (the developer of the traffic shaper) stated you just can't shape stuff going into, in, or coming out of a VPN. For all other prioritization, I just use QOS on the switch. Cisco's do allow for QOS on VPN tunnels but they are also hugely expensive with mandatory support contracts to stay up-to-date. So the trade-off's I make with pfSense are well worth it for all the small/medium business stuff I do.
BTW Just tried out the edge router lite. It's a pretty sweet little device. I can see myself using this for small installs. Only complaint thus far is QOS is 100% cli configured. So it's a little time consuming to setup.