Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Fil DiNoto (fdinotogmail.com)
Date: Sun Jun 09 2013 - 08:27:12 CDT
I am seeking advice in regards to OpenBSD and the vic driver on ESXi server.
I currently lease a physical ESXi server. One of the VMs is an OpenBSD 5.0
system which is configured as a router and serves as a gateway for all the
other VMs. This configuration has many advantages for me because it gives
me a single point to firewall with pf as well as the ability to upgrade
hardware with my provider without changing IP assignments because my /29
and /64 are routed.
Recently I have noticed that my speeds are asynchronous. I have tested to
various places using various methods and am getting the same results. I am
getting 500-700Mbps ingress and 10-50Mbps egress. My ESXi server is in a
data center, so I should not be getting asynchronous speeds.
In my experience results like these are normally caused by a duplex
mismatch or one interface configured for auto-negotiation while the other
side is hard set. And here in is my confusion. I can’t find any solid
documentation as to how to configure the media for a virtual switch. So I
assume auto is the way to go.
However, I noticed that on my OpenBSD 5.0 router the output of the ifconfig
vic0 command simply says:
media: Ethernet autoselect
It doesn’t say what speed or duplex it has negotiated to. Does this matter
at all? I noticed that my Enterprise Linux systems the virtual NIC appear
to be hard set to 10,000BaseT Full, auto-negotiation disabled (and not
available) using the ethtool command.
Does anyone have any advice for me? I am paying for a 1000Mbps Internet
port and I am only getting a fraction of that on my egress speeds. I opened
a ticket with my provider and they confirmed my settings and that my
physical switch port is set to auto, as is my physical port on the ESXi