<?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[Can I use traffic Shaping on XENSERVER 6.2 with a VM running pfsense 2.2]]></title><description><![CDATA[<p dir="auto">On the Traffic Shaping web I dont see the interfaces listed.<br />
I also did some research about the issue.<br />
It seems that the xenserver nic driver isn't support some feature required to use shaping.</p>
<p dir="auto">Is there anyone using it?<br />
What tweaks need to be done to activate traffic shaping?</p>
]]></description><link>https://forum.netgate.com/topic/80174/can-i-use-traffic-shaping-on-xenserver-6-2-with-a-vm-running-pfsense-2-2</link><generator>RSS for Node</generator><lastBuildDate>Sun, 14 Jun 2026 13:18:37 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/80174.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 20 Feb 2015 21:43:06 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Can I use traffic Shaping on XENSERVER 6.2 with a VM running pfsense 2.2 on Sat, 21 Feb 2015 21:37:30 GMT]]></title><description><![CDATA[<p dir="auto">But if you use esxi it works without problem :/<br />
Its seems to be so unfair.<br />
I cant get a good xen firewall</p>
]]></description><link>https://forum.netgate.com/post/521820</link><guid isPermaLink="true">https://forum.netgate.com/post/521820</guid><dc:creator><![CDATA[HellMind]]></dc:creator><pubDate>Sat, 21 Feb 2015 21:37:30 GMT</pubDate></item><item><title><![CDATA[Reply to Can I use traffic Shaping on XENSERVER 6.2 with a VM running pfsense 2.2 on Fri, 20 Feb 2015 21:48:49 GMT]]></title><description><![CDATA[<p dir="auto">No.  Unfortunately xn doesn't have altq.  It sucks.</p>
]]></description><link>https://forum.netgate.com/post/521640</link><guid isPermaLink="true">https://forum.netgate.com/post/521640</guid><dc:creator><![CDATA[Derelict]]></dc:creator><pubDate>Fri, 20 Feb 2015 21:48:49 GMT</pubDate></item></channel></rss>