<?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[How to test pfSense after previous problems]]></title><description><![CDATA[<p dir="auto">Hello,</p>
<p dir="auto">I've been running pfSense (latest stable release) on an HP DL380 G5, the HP box was bringing us huge problems due to the NICs (broadcoms) were having troubles with pfSense.</p>
<p dir="auto">So I thought like:<br />
VMWare ESXi emulates Intel e1000 NICs, so in theory I would be able to run pfSense just fine under ESXi</p>
<p dir="auto">But now i'm looking for a way to test if it runs just fine, there are the problems we've had before.</p>
<ul>
<li>
<p dir="auto">HIGH Ping</p>
</li>
<li>
<p dir="auto">Bandwith not getting higher then 2Mbit (even when only a single device was connected to pfSense, connecting the same, single device to the modem gave us 120Mbit)</p>
</li>
<li>
<p dir="auto">DNS Names not resolving with nameserver due to high ping.</p>
</li>
</ul>
<p dir="auto">Now i'd expect these problems to be solved with ESXi as I stated before, but can I rely on this theory? And how can I put it to the test, without having to put all 400 devices behind the pfSense firewall? (Those devices need 24/7 working internet access)</p>
<p dir="auto">Thanks :)<br />
aTastyAim</p>
]]></description><link>https://forum.netgate.com/topic/52151/how-to-test-pfsense-after-previous-problems</link><generator>RSS for Node</generator><lastBuildDate>Sat, 13 Jun 2026 08:52:09 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/52151.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 20 Jan 2013 20:50:22 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to How to test pfSense after previous problems on Mon, 21 Jan 2013 13:42:35 GMT]]></title><description><![CDATA[<p dir="auto">I may have remebered incorrectly about the errors, I can't now find a example of it. However:<br />
http://forum.pfsense.org/index.php/topic,35895.0.html</p>
<p dir="auto">Steve</p>
]]></description><link>https://forum.netgate.com/post/373875</link><guid isPermaLink="true">https://forum.netgate.com/post/373875</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Mon, 21 Jan 2013 13:42:35 GMT</pubDate></item><item><title><![CDATA[Reply to How to test pfSense after previous problems on Mon, 21 Jan 2013 12:51:30 GMT]]></title><description><![CDATA[<p dir="auto">Well I could recall many errors thrown into the log. Couldn't recall what it was about.</p>
]]></description><link>https://forum.netgate.com/post/373859</link><guid isPermaLink="true">https://forum.netgate.com/post/373859</guid><dc:creator><![CDATA[aTastyAim]]></dc:creator><pubDate>Mon, 21 Jan 2013 12:51:30 GMT</pubDate></item><item><title><![CDATA[Reply to How to test pfSense after previous problems on Mon, 21 Jan 2013 12:34:57 GMT]]></title><description><![CDATA[<p dir="auto">Exactly. The Broadcom NICs are handled by ESXi so the issue is mute. Theoretically!  :)<br />
If it was that problem I would have expected you to see many many errors in the logs.</p>
<p dir="auto">Steve</p>
]]></description><link>https://forum.netgate.com/post/373856</link><guid isPermaLink="true">https://forum.netgate.com/post/373856</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Mon, 21 Jan 2013 12:34:57 GMT</pubDate></item><item><title><![CDATA[Reply to How to test pfSense after previous problems on Mon, 21 Jan 2013 12:26:29 GMT]]></title><description><![CDATA[<p dir="auto">That's exactly what happened.<br />
So, if I get this straight, it shouldn't happen when I run pfSense virtualized with ESXi (because ESXi emulates Intel PRO/1000 NICs)?</p>
]]></description><link>https://forum.netgate.com/post/373854</link><guid isPermaLink="true">https://forum.netgate.com/post/373854</guid><dc:creator><![CDATA[aTastyAim]]></dc:creator><pubDate>Mon, 21 Jan 2013 12:26:29 GMT</pubDate></item><item><title><![CDATA[Reply to How to test pfSense after previous problems on Mon, 21 Jan 2013 12:22:04 GMT]]></title><description><![CDATA[<p dir="auto">Ah well that's more difficult to test if you have to wait 2 days for it to show up.  ;)<br />
That does sound similar to the problem that is addressed by the tweaks in the wiki. The system eventually runs out of mbufs due to a driver issue and the NICs start throwing errors. However usually when that happens the logs are full of errors and the traffic stops almost entirely.</p>
<p dir="auto">Steve</p>
]]></description><link>https://forum.netgate.com/post/373852</link><guid isPermaLink="true">https://forum.netgate.com/post/373852</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Mon, 21 Jan 2013 12:22:04 GMT</pubDate></item><item><title><![CDATA[Reply to How to test pfSense after previous problems on Mon, 21 Jan 2013 12:14:12 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/stephenw10">@<bdi>stephenw10</bdi></a>:</p>
<blockquote>
<p dir="auto">Hmm, well since they are Broadcom NICs did you try the advise here:<br />
http://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards#Broadcom_bce.284.29_Cards</p>
<p dir="auto">I would expect it work fine under ESXi though. It should be easy to test that you're not restricted to 2Mbps on a 120Mbps connection.</p>
<p dir="auto">Steve</p>
</blockquote>
<p dir="auto">Yes, I tried that, for me it didn't make the diffrence. And well, the issue is, when running unvirtualised on the broadcom NICs it ran fine for a few days, from then i'd only go downhill.</p>
]]></description><link>https://forum.netgate.com/post/373851</link><guid isPermaLink="true">https://forum.netgate.com/post/373851</guid><dc:creator><![CDATA[aTastyAim]]></dc:creator><pubDate>Mon, 21 Jan 2013 12:14:12 GMT</pubDate></item><item><title><![CDATA[Reply to How to test pfSense after previous problems on Mon, 21 Jan 2013 12:05:06 GMT]]></title><description><![CDATA[<p dir="auto">Hmm, well since they are Broadcom NICs did you try the advise here:<br />
http://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards#Broadcom_bce.284.29_Cards</p>
<p dir="auto">I would expect it work fine under ESXi though. It should be easy to test that you're not restricted to 2Mbps on a 120Mbps connection.</p>
<p dir="auto">Steve</p>
]]></description><link>https://forum.netgate.com/post/373845</link><guid isPermaLink="true">https://forum.netgate.com/post/373845</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Mon, 21 Jan 2013 12:05:06 GMT</pubDate></item><item><title><![CDATA[Reply to How to test pfSense after previous problems on Sun, 20 Jan 2013 22:27:56 GMT]]></title><description><![CDATA[<p dir="auto">I already swapped cables, no result, and set the interface to 100Mbit on both ends, which also, gave me no result.</p>
]]></description><link>https://forum.netgate.com/post/373780</link><guid isPermaLink="true">https://forum.netgate.com/post/373780</guid><dc:creator><![CDATA[aTastyAim]]></dc:creator><pubDate>Sun, 20 Jan 2013 22:27:56 GMT</pubDate></item><item><title><![CDATA[Reply to How to test pfSense after previous problems on Sun, 20 Jan 2013 22:26:16 GMT]]></title><description><![CDATA[<p dir="auto">Those problems sound like an interface duplex mismatch or bad cable (or both  ;)).<br />
You should check for errors on the interface. That is usually caused by a negotiation problem between the two ends of the link which can a result of one end not set to auto-negatioate speed/duplex or a bad cable.</p>
<p dir="auto">Steve</p>
]]></description><link>https://forum.netgate.com/post/373779</link><guid isPermaLink="true">https://forum.netgate.com/post/373779</guid><dc:creator><![CDATA[stephenw10]]></dc:creator><pubDate>Sun, 20 Jan 2013 22:26:16 GMT</pubDate></item></channel></rss>