New setup - will this setup work
-
That Cisco box should have some logging or traffic history you can get from it. Determining the peak throughput in Mbps or PPS would be very helpful here.
However, as I say, at 100Mbps I would not anticipate any issue.
Steve
-
I'll have a look, but this is more of a consumer grade device, but it's marketed to businesses.
At any rate, I'll move forward with the pfSense build as is.
Thanks again to both you and pfBasic for your help.
-
for VoIP, I would strongly recommend you read the linked thread in its entirety, then ask whatever questions you may have either here or in the traffic shaping forum. - playing with fq_codel in 2.4
In short, VoIP traffic suffers badly from high latency as I'm sure you know.
pfSense just implemented (as a result on upstream FreeBSD developments) fq_codel.
Why do you care? Because fq_codel is very easy to implement over your entire network, it does not require much tuning (usually none at all) and it will do an exceptional job of giving traffic such as VoIP very low latency connections even when your WAN is maxed out.
It's currently a CLI-only implementation, but very easy to do (done in <5 minutes). -
Hi belt9,
I'm sorry for the delayed response. I read through that thread, and played a little with traffic shaping on my pfSense box at home (still running 2.3.4 on that one, so I messed around with the GUI traffic shaping).
It seems to be going pretty well. There weren't really any issues to begin with, so I can't say the connection is better in anything I've observed in my normal daily activities.
I did check out a speed test over at dslreports.com which shows a "bufferbloat" indicator. While I can't personally tell a difference in our every day internet activities, the bufferebloat is way less when the traffic shaping is enabled.
I did some reading and I kind of understand what it is and how it works, what it tells me is happening on the network end. I still have a lot of reading to do though.
This box is built and almost fully configured to replace the existing router. While the higher ups are deciding on a cut over date, I am learning all I can about traffic shaping so we can hit the ground running with the best configuration I can implement.
-
if this is the hardware you already own then yes it will do the job.
if you are considering purchasing this hardware to do the job your described then don't.
it's way overkill and terribly inefficient, not to mention will cost you too much money.
Build a system based around a J3355B - it's $55 for the SoC (motherboard + CPU), has a slot for your dual NIC card - however, if the switches you have support VLAN's and you're comfortable using them then you can meet your needs with a single NIC. Up to you.
It is also totally fanless - paired with a cheap SSD & picoPSU you will have a system with no moving parts for very cheap = low power usage, no sound & high reliability.https://www.newegg.com/Product/Product.aspx?Item=N82E16813157726
http://www.ebay.com/itm/2GB-DDR3-PC3-10600-Laptop-RAM-2x1GB/282612191170?hash=item41ccffcfc2%3Ag%3A-x0AAOSw5FNZkzVf
https://www.amazon.com/Kingspec-KSD-SA25-7-Channel-Internal-Solid/dp/B00JYB99O4/ref=sr_1_2?s=pc&ie=UTF8&qid=1503099361&sr=1-2&refinements=p_n_feature_three_browse-bin%3A14027456011%2Cp_n_feature_keywords_four_browse-bin%3A6158693011
http://www.mini-box.com/picoPSU-80-60W-power-kit
http://www.ebay.com/itm/IBM-I340-T2-Dual-Port-Ethernet-Network-Server-Adapter-Card-Low-Profile-49Y4232-/172564219960?epid=1505484004&hash=item282da10838:g:WrAAAOSwhSVZhHfv
That's a very low power system that is pfSense 2.5 compatible and will easily exceed your needs.
$135 + case if you don't already have one.
Correction, you already have a HDD so $111 + case.Great built info; however, what's enclosure recommendation and cost? I might recommend to a friend who would ask such a question…the cheapest I have seen so far is for macro ATX tower for $34/eBay...maybe too big though.
-
Depends on what you're needing as far as size.
https://www.newegg.com/Product/Product.aspx?Item=N82E16811147123
This microATX tower is pretty small. 13.78 inches tall (top to bottom), 6.89 inches wide (left to right), and 13.86 inches deep (front to back). This is as if you were looking at the front of the case.
-
Depends on what you're needing as far as size.
https://www.newegg.com/Product/Product.aspx?Item=N82E16811147123
This microATX tower is pretty small. 13.78 inches tall (top to bottom), 6.89 inches wide (left to right), and 13.86 inches deep (front to back). This is as if you were looking at the front of the case.
Cool…awesome, that's the one I was looking at on eBay for $34...thanks for the link.
-
No problem buddy. As pfBasic mentioned, the parts he listed can be run silent, I took that to mean fanless. This case comes with fans, but you likely won't need them unless it will be sitting in a hot closet or something.
You would also be good to go with the pico power supply he listed as well, the drawback is, there's a gaping hole in the back of the case, which was meant for a bigger power supply unit.
For a little bit more money, you can get one of these: http://www.mini-box.com/M350-universal-mini-itx-enclosure
This will fit the system board listed, and can be bundled with the pico power supply. It has a spot on the back where the external part of the power supply plugs into the unit. Nice and clean looking, and it's even smaller than the one you were looking at.
-
No problem buddy. As pfBasic mentioned, the parts he listed can be run silent, I took that to mean fanless. This case comes with fans, but you likely won't need them unless it will be sitting in a hot closet or something.
You would also be good to go with the pico power supply he listed as well, the drawback is, there's a gaping hole in the back of the case, which was meant for a bigger power supply unit.
For a little bit more money, you can get one of these: http://www.mini-box.com/M350-universal-mini-itx-enclosure
This will fit the system board listed, and can be bundled with the pico power supply. It has a spot on the back where the external part of the power supply plugs into the unit. Nice and clean looking, and it's even smaller than the one you were looking at.
Thanks…I had looked at that one too from pfBasic's link on the power supply.
-
I read through that a couple of times, and my understanding is that, while it does not prioritize VoIP traffic, fq_codel manages the queue more efficiently, so that the small VoIP packets are worked into available spaces, which means they're not waiting in the queue for other 'stuff' to finish.
That's way over simplified, but is it an accurate way to describe it?
for VoIP, I would strongly recommend you read the linked thread in its entirety, then ask whatever questions you may have either here or in the traffic shaping forum. - playing with fq_codel in 2.4
In short, VoIP traffic suffers badly from high latency as I'm sure you know.
pfSense just implemented (as a result on upstream FreeBSD developments) fq_codel.
Why do you care? Because fq_codel is very easy to implement over your entire network, it does not require much tuning (usually none at all) and it will do an exceptional job of giving traffic such as VoIP very low latency connections even when your WAN is maxed out.
It's currently a CLI-only implementation, but very easy to do (done in <5 minutes).
