<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Netgate embedded firewall - question]]></title><description><![CDATA[<p dir="auto">I am using the netgate m1n1wall firewall 2D3.<br />
Up to how many concurrent calls can this device handle? It doesn't have too much ram (256) MB and I plan on doing traffic shaping with this. I am just worried that this little device won't be able to handle such a heavy load because I do plan on putting 50-80 concurrent calls on the network, and more in the future. Note that I wont be using the sip proxy on the firewall; just a regular asterisk server.</p>
<p dir="auto">Thanks</p>
]]></description><link>https://forum.netgate.com/topic/19115/netgate-embedded-firewall-question</link><generator>RSS for Node</generator><lastBuildDate>Thu, 16 Apr 2026 20:28:47 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/19115.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 07 Nov 2009 03:00:58 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Netgate embedded firewall - question on Sat, 07 Nov 2009 15:35:58 GMT]]></title><description><![CDATA[<p dir="auto">Concurrent connections don't matter so much as total throughput. I'm not sure how much the numbers are reduced once you put traffic shaping on, but when sending in the clear an ALIX box like that can pass through about 80-85Mbit.</p>
<p dir="auto">As far as concurrent connections go, RAM would only matter in terms of state table size, and you can fit ~100,000 states in about 97MBytes of RAM. I'm not sure if traffic shaping adds any more overhead onto that.</p>
]]></description><link>https://forum.netgate.com/post/212665</link><guid isPermaLink="true">https://forum.netgate.com/post/212665</guid><dc:creator><![CDATA[jimp]]></dc:creator><pubDate>Sat, 07 Nov 2009 15:35:58 GMT</pubDate></item></channel></rss>