I am using Debian and I am just trying to get a simple bridge going and
connect the ethernet to it. It is an Intel NUC and the ethernet shows up
as "eno1". I don't know why it doesn't come up as "eth0".
iface eno1 inet dhcp
auto eno1
But, if I replace that with the following, it doesn't come up.
Turns out OVS got stuck in the systemd cycle. After waiting 5 minutes,
it came up.
brian
On Sun, Jul 01, 2018 at 09:06:48AM -0700, Brian E. Lavender wrote:
> I did a fresh install and tried things from scratch.
>
> I tried again bringing up the switch manually using the com
to add something for the link up?
allow-ovs br0
iface br0 inet dhcp
ovs_type OVSBridge
ovs_ports eno1
allow-br0 eno1
iface eno1 inet manual
ovs_bridge br0
ovs_type OVSPort
Any suggestions?
On Sat, Jun 30, 2018 at 11:08:07PM -0700, Brian E. Lavender wrote:
> I am using Debian an
I connected a wire to my eth0 physical port that has trunked vlans:
vlan1 and vlan2. The vlan1 is an internal network that I want to give
an IP address to in order to access the hypervisor on the machine as
well as connect to VMs in Xen. vlan2 is a vlan for connecting machines
directly visible to
See inline below
On Tue, Jul 03, 2018 at 11:17:31AM -0700, Guru Shetty wrote:
>On 3 July 2018 at 10:44, Brian E. Lavender <[1]br...@brie.com> wrote:
>
> I am using the package that comes with Debian Stretch. Is there an
> Open
> vSwitch Debian repository
It turns out that the file /etc/init.d/openvswitch-switch has one of the
lines you mentioned, but not the other. When I added the one line it
worked.
_SYSTEMCTL_SKIP_REDIRECT=yes # this line was present
SYSTEMCTL_SKIP_REDIRECT=yes # missing this line
I added the second line and it boots now
018 at 22:37, Brian E. Lavender <[1]br...@brie.com> wrote:
>
> Turns out OVS got stuck in the systemd cycle. After waiting 5
> minutes,
> it came up.
>
>You are likely using packages from Canonical and not from this repo?
>
> brian
>
>
