Download speed on Xen max 3Mbit on a 150Mbit connection

Started by markkrueg, February 21, 2016, 05:44:29 PM

Previous topic - Next topic
My tested speed with a hardware router is 150mbit download with 20mbit upload. When running a workstation through OPNsense, I can only get 3Mbit download speed. But I get the full 20Mbit upload.

I am running Oracle VM Server (which is Xen). My VM was installed with OPNsense-16.1-OpenSSL-cdrom-amd64.iso. I have applied the updates as they are released; but no changes. I'm not seeing any high loads or errors. I have dedicated 2 CPUs to the VM (3.9Ghz Xeon) and 2GB RAM.

I would love to figure this one out; as OPNsense looks amazing.

I ended up building a Ubuntu Server 14.04.4 LTS VM temporarily using iptables for firewall/NAT. It is able to achieve the full 150Mbit. I really want to use OPNsense, but 3Mbit download just kills it for me.

Other related threads:
https://forum.opnsense.org/index.php?topic=2149.0

I also tried all the steps in this thread:
https://forum.opnsense.org/index.php?topic=2134.0

Let me know if there is anything else I can do to help troubleshoot this.


Why have you started a new (duplicate) thread when you already have your question in the other thread? I'm sure that someone will answer when they have the time and to echo the reply of weust in that other thread, I don't have any problem with speed running OPNsense if a VM on ESXi.
Regards


Bill

Hallo,

If your opnsense runs as a HVM Xen domU I would recommend to try this https://forum.pfsense.org/index.php?topic=85797.15. This worked for me.

In Short


  • find out the id of your domU
  • execute in the dom0 the command 'ethtool -K vif<your-opnsense-domU-Id>.0 tx off'
This needs to be done  after each reboot of opnsense. at least in my case i had full speed again

Br br

We've had someone in IRC recently who went through this and more trouble during setup and offered to write a full tutorial. I'll try to track him down and send him here. :)

February 22, 2016, 05:28:57 PM #4 Last Edit: February 22, 2016, 05:31:07 PM by markkrueg
Quote from: phoenix on February 21, 2016, 06:02:18 PM
Why have you started a new (duplicate) thread

You are correct; of course. And I apologize for the breech of forum etiquette. In this instance I felt like it might be worthwhile having a thread dedicated specifically to the problem with Xen on 16.1, vs. the other thread which was more general VM. I was considering adding some more info to that thread about my specific issue; but it started to feel off topic. Anyway, I probably made the wrong call. I won't do this in the future.

Quote from: phoenix on February 21, 2016, 06:02:18 PMI don't have any problem with speed running OPNsense if a VM on ESXi

This is a useful data point, however Xen and ESXi are completely different beasts.

Quote from: bringha on February 21, 2016, 11:03:27 PMIf your opnsense runs as a HVM Xen domU I would recommend to try this

Thank you so much for the useful info and link! I am working through it. The workaround may be a bit more complex than I was hoping for though. I might wait until either Xen or OPNsense is fixed vs. the workaround. I like to keep things pretty generic on my VM server to ease maintenance.

Quote from: franco on February 22, 2016, 07:22:02 AM
We've had someone in IRC recently who went through this and more trouble during setup and offered to write a full tutorial. I'll try to track him down and send him here. :)

Thanks much franco! I'm not sure if the IRC channel has a history bot running; if so you can just point me to that link and I can read the transcript.

It was pretty easy to install OPNsense on Oracle VM Server using the ISO. Everything went very smoothly until I hit this issue.

I don't have the exact IRC log, it was a longer discussion that took place over a few days or so, but that TX setting was one of the key pieces.

VM host settings for FreeBSD can be tricky, especially on Xen and KVM at the moment there are these configuration troubles one might run into. As far as I know there is little the guest system can do (other than fixing the checksum issues which seems uncertain for the FreeBSD 10 series at the moment).

I'll keep you posted on the doc progress, I know people are on vacation time at the moment so things seems slower than usual. :)