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 with
>
>
> So, if I build OVS from source, am I going to have the same problem? It
> seems that everything in Squeeze is systemd? I guess I could try and
> see. Will the init.d script work?
>
>
You said it is OVS 2.6.2. First thing to do is to simply modify your
/etc/init.d/openvswitch-switch to include
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?
> Or, should I bu
On 3 July 2018 at 10:44, Brian E. Lavender wrote:
> I am using the package that comes with Debian Stretch. Is there an Open
> vSwitch Debian repository?
>
> Or, should I build the package from source using the latest source? I
> take it already has the debian/rules ?
>
Yes. You can build debian
I am using the package that comes with Debian Stretch. Is there an Open
vSwitch Debian repository?
Or, should I build the package from source using the latest source? I
take it already has the debian/rules ?
brian
On Tue, Jul 03, 2018 at 10:39:03AM -0700, Guru Shetty wrote:
>On 1 July 2018
On 1 July 2018 at 22:37, Brian E. Lavender 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
>
> On Sun, Jul 01, 2018 at 09:06:48AM -0700, Brian E. Lavender wrote:
> > I
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 command line and
> for so
I did a fresh install and tried things from scratch.
I tried again bringing up the switch manually using the command line and
for some reason, when I attempt to do the same with
/etc/network/interfaces, it doesn't work. The only thing that seems
different from when I did this before is the fact th
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.
