On 6/11/2019 3:30 PM, Steinar H. Gunderson wrote:
On Tue, Jun 11, 2019 at 03:00:00PM -0700, Gregory Rose wrote:
I see the source of the confusion here. The vlan1 interface is added to the
OVS bridge and the port type
is internal. Here's a better way to look at this:
Net Device
<Can originate packets> OVS switch
|------------------| |-----------------|
| | | |
| vlan1 |<----------->| ovsbr1 |
| | ^ | |
|------------------| | |-----------------|
|
|
<internal port> <----------------- Think of that as a
virtual Ethernet cable
When you ssh to a destination via the vlan1 interface then the vlan1
interface is generating the packets. If it has a tcp checksum offload
capability then it would use it but that will depend on the master device
it is controlled by. This port is in no way owned by OVS. OVS has simply
added it to the bridge using a virtual port which is by convention called
an 'internal' port. But think of it as the cable connecting your virtual
device 'vlan1' to the OVS bridge 'ovsbr1'.
Does that help explain?
Only if you can tell me what the vlan1 device is. :-) I had assumed this was
a first-class concept within ovs; after all, when you create a bridge you get
one of these.
You don't automatically get any ports on a bridge when created. For
example:
root@ubuntu-1604-base:~# ovs-ctl start
* Starting ovsdb-server
* system ID not configured, please use --system-id
* Configuring Open vSwitch system IDs
* Starting ovs-vswitchd
* Enabling remote OVSDB managers
root@ubuntu-1604-base:~# ovs-vsctl show
6be291a9-6bab-4fff-bda9-7f54335b4884
ovs_version: "2.11.90"
Now I'll create a bridge:
root@ubuntu-1604-base:~# ovs-vsctl add-br br0
root@ubuntu-1604-base:~# ovs-vsctl show
6be291a9-6bab-4fff-bda9-7f54335b4884
Bridge "br0"
Port "br0"
Interface "br0"
type: internal
ovs_version: "2.11.90"
As you can see no ports are automatically created or added to the
bridge. Some configuration script somewhere added
vlan1 to your bridge and the source of that vlan1 interface should be in
/etc/network/interfaces.
Could you provide your /etc/network/interfaces file? Also, the output
of 'ip link show' and 'ip addr show'.
Thanks,
- Greg
It's created with Debian's ifupdown integration (an “OVSIntPort”-type
interface), which seems to do:
ovs_vsctl -- --may-exist add-port "${IF_OVS_BRIDGE}"\
"${IFACE}" ${IF_OVS_OPTIONS} -- set Interface "${IFACE}"\
type=internal ${OVS_EXTRA+-- $OVS_EXTRA}
No, the internal ports are the virtual interfaces between physical/virtual
devices (vlan1) and the OVS bridge (ovsbr1).
So what are the vlan1 devices? Who should I nag to get them to pad their
packets correctly? :-)
/* Steinar */
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
