Re: nm-openvswitch on debian/ubuntu
Yes and since I'm on debian, it is openvswitch-switch. I can create bridge
using ovs-vsctl without a problem.
My db.sock file is in /var/run/openvswitch/
Thanks.
Le mer. 28 juil. 2021 à 16:54, Thomas Haller a écrit :
> On Wed, 2021-07-28 at 15:14 +0200, Sohaib E. wrote:
> > I found this error in the logs : ovsdb: Could not connect: No such
> > file or directory
> >
> > My ovsdb's unix socket is in /var/run/openvswitch. I don't think
> > Network Manager is expecting another path but if it is, where do I
> > change that ?
>
> it's not configurable, it's a compile time constant.
>
> Grep the source for "/db.sock".
>
> But that should be correct already. Did you `systemctl start
> openvswitch.sevice`?
>
> Where is your db.sock file exactly?
>
>
> best,
> Thomas
>
>
> >
> > Thanks.
> >
> >
> > Le mer. 28 juil. 2021 à 12:57, Thomas Haller a
> > écrit :
> > > Hi,
> > >
> > > On Wed, 2021-07-28 at 12:41 +0200, Sohaib E. wrote:
> > > > Thank you for your quick answer.
> > > >
> > > > I have compiled NetworkManager's package myself but I still faced
> > > some
> > > > issues deploying an ovs bridge.
> > > >
> > > > Besides the NetworkManager-ovs.conf (openvswitch-switch.service
> > > instead
> > > > of openvswitch.service), what other settings must be modified for
> > > this
> > > > to work ?
> > >
> > >
> > > I don't think anything else is missing.
> > >
> > > Obviously, you need to create connection profiles, read `man nm-
> > > openvswitch` about that ([1]). And, you'd activate the right
> > > profiles
> > > (`nmcli connection up` and watch current setup with `nmcli device`
> > > and
> > > `nmcli connection`).
> > >
> > > Other than that, nothing comes to mind. As always when debugging
> > > NetworkManager, enable level=TRACE logging and read the log. See
> > > [2]
> > > for hints about logging.
> > >
> > > Maybe the path to ovsdb's unix socket is different on the system?
> > > That
> > > is currently a compile time constant. You should see that in the
> > > logs...
> > >
> > >
> > > [1]
> > >
> https://networkmanager.pages.freedesktop.org/NetworkManager/NetworkManager/nm-openvswitch.html
> > > [2]
> > >
> https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/2d879c1ac5d907fe184898b23693fb8148363645/contrib/fedora/rpm/NetworkManager.conf#L27
> > >
> > >
> > > best,
> > > Thomas
> > >
> > >
> > > >
> > > > Thank you for your time,
> > > > Sohaib
> > > >
> > > > Le mer. 28 juil. 2021 à 10:39, Thomas Haller
> > > > a
> > > > écrit :
> > > > > On Tue, 2021-07-27 at 18:39 +0200, Sohaib E. via
> > > > > networkmanager-
> > > list
> > > > > wrote:
> > > > > > Hello,
> > > > > >
> > > > > > I'm trying to use Network Manager to deploy ovs bridges on
> > > > > > debian/ubuntu.
> > > > > >
> > > > > > I understand that Network Manager itself do not have such a
> > > feature
> > > > > > and needs an additional plugin called nm-openvswitch.
> > > Nevertheless,
> > > > > > this plugin is not available on debian/ubuntu and, therefore,
> > > > > > I
> > > was
> > > > > > wondering if there was any workaround to deploy ovs bridges
> > > using
> > > > > > nmcli on ubuntu/debian or to install nm-openvswitch on
> > > > > ubuntu/debian.
> > > > >
> > > > > nm-openvswitch is part of NetworkManager, but
> > > > >
> > > > > - it can be disabled/enabled at compile time
> > > > >
> > > > > - it is loaded from a shared library (dlopen), so it can be
> > > packaged
> > > > > separately (as done on Fedora, with NetworkManager-openvswitch
> > > > > package). But it doesn't have to be packaged separately, Debian
> > > tends
> > > > > to put all these device plugins in the same "network-manager"
> > > > > package,
> > > > > while Fedora tends to split them (NetworkManager-
> > > > > {wifi,team,wwan,...}).
> > > > >
> > > > >
> > > > > Debian builds with this code disabled. You would either have to
> > > > > convince the debian maintainers to package this, or build
> > > > > NetworkManager yourself. In the latter case, you could just
> > > rebuild
> > > > > the
> > > > > debian package with minor changes to the build settings.
> > > > >
> > > > >
> > > > > best,
> > > > > Thomas
> > > > >
> > >
> > >
>
>
>
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-openvswitch on debian/ubuntu
First, make sure that ovs is installed correctly, e.g. E.g. make sure something like this works ovs-vsctl add-br MyBridge if this is working, you would need the following three commands to create a bridge and should in ovs-vsctl output nmcli conn add type ovs-bridge conn.interface MyBridge nmcli conn add type ovs-port conn.interface MyBridge master MyBridge nmcli conn add type ovs-interface slave-type ovs-port conn.interface MyBridge master nsx-switch0 ipv4.method disabled NM does not create a port & an interface when you create a bridge, and the bridge will not should in the output until app three are created. But you will see connection profiles in the /etc/NetworkManager/systemXXX (forgot full directory name) On Wed, Jul 28, 2021 at 7:54 AM Thomas Haller via networkmanager-list < networkmanager-list@gnome.org> wrote: > On Wed, 2021-07-28 at 15:14 +0200, Sohaib E. wrote: > > I found this error in the logs : ovsdb: Could not connect: No such > > file or directory > > > > My ovsdb's unix socket is in /var/run/openvswitch. I don't think > > Network Manager is expecting another path but if it is, where do I > > change that ? > > it's not configurable, it's a compile time constant. > > Grep the source for "/db.sock". > > But that should be correct already. Did you `systemctl start > openvswitch.sevice`? > > Where is your db.sock file exactly? > > > best, > Thomas > > > > > > Thanks. > > > > > > Le mer. 28 juil. 2021 à 12:57, Thomas Haller a > > écrit : > > > Hi, > > > > > > On Wed, 2021-07-28 at 12:41 +0200, Sohaib E. wrote: > > > > Thank you for your quick answer. > > > > > > > > I have compiled NetworkManager's package myself but I still faced > > > some > > > > issues deploying an ovs bridge. > > > > > > > > Besides the NetworkManager-ovs.conf (openvswitch-switch.service > > > instead > > > > of openvswitch.service), what other settings must be modified for > > > this > > > > to work ? > > > > > > > > > I don't think anything else is missing. > > > > > > Obviously, you need to create connection profiles, read `man nm- > > > openvswitch` about that ([1]). And, you'd activate the right > > > profiles > > > (`nmcli connection up` and watch current setup with `nmcli device` > > > and > > > `nmcli connection`). > > > > > > Other than that, nothing comes to mind. As always when debugging > > > NetworkManager, enable level=TRACE logging and read the log. See > > > [2] > > > for hints about logging. > > > > > > Maybe the path to ovsdb's unix socket is different on the system? > > > That > > > is currently a compile time constant. You should see that in the > > > logs... > > > > > > > > > [1] > > > > https://networkmanager.pages.freedesktop.org/NetworkManager/NetworkManager/nm-openvswitch.html > > > [2] > > > > https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/2d879c1ac5d907fe184898b23693fb8148363645/contrib/fedora/rpm/NetworkManager.conf#L27 > > > > > > > > > best, > > > Thomas > > > > > > > > > > > > > > Thank you for your time, > > > > Sohaib > > > > > > > > Le mer. 28 juil. 2021 à 10:39, Thomas Haller > > > > a > > > > écrit : > > > > > On Tue, 2021-07-27 at 18:39 +0200, Sohaib E. via > > > > > networkmanager- > > > list > > > > > wrote: > > > > > > Hello, > > > > > > > > > > > > I'm trying to use Network Manager to deploy ovs bridges on > > > > > > debian/ubuntu. > > > > > > > > > > > > I understand that Network Manager itself do not have such a > > > feature > > > > > > and needs an additional plugin called nm-openvswitch. > > > Nevertheless, > > > > > > this plugin is not available on debian/ubuntu and, therefore, > > > > > > I > > > was > > > > > > wondering if there was any workaround to deploy ovs bridges > > > using > > > > > > nmcli on ubuntu/debian or to install nm-openvswitch on > > > > > ubuntu/debian. > > > > > > > > > > nm-openvswitch is part of NetworkManager, but > > > > > > > > > > - it can be disabled/enabled at comp
Re: nm-openvswitch on debian/ubuntu
I found this error in the logs : ovsdb: Could not connect: No such file or
directory
My ovsdb's unix socket is in /var/run/openvswitch. I don't think Network
Manager is expecting another path but if it is, where do I change that ?
Thanks.
Le mer. 28 juil. 2021 à 12:57, Thomas Haller a écrit :
> Hi,
>
> On Wed, 2021-07-28 at 12:41 +0200, Sohaib E. wrote:
> > Thank you for your quick answer.
> >
> > I have compiled NetworkManager's package myself but I still faced some
> > issues deploying an ovs bridge.
> >
> > Besides the NetworkManager-ovs.conf (openvswitch-switch.service instead
> > of openvswitch.service), what other settings must be modified for this
> > to work ?
>
>
> I don't think anything else is missing.
>
> Obviously, you need to create connection profiles, read `man nm-
> openvswitch` about that ([1]). And, you'd activate the right profiles
> (`nmcli connection up` and watch current setup with `nmcli device` and
> `nmcli connection`).
>
> Other than that, nothing comes to mind. As always when debugging
> NetworkManager, enable level=TRACE logging and read the log. See [2]
> for hints about logging.
>
> Maybe the path to ovsdb's unix socket is different on the system? That
> is currently a compile time constant. You should see that in the
> logs...
>
>
> [1]
> https://networkmanager.pages.freedesktop.org/NetworkManager/NetworkManager/nm-openvswitch.html
> [2]
> https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/2d879c1ac5d907fe184898b23693fb8148363645/contrib/fedora/rpm/NetworkManager.conf#L27
>
>
> best,
> Thomas
>
>
> >
> > Thank you for your time,
> > Sohaib
> >
> > Le mer. 28 juil. 2021 à 10:39, Thomas Haller a
> > écrit :
> > > On Tue, 2021-07-27 at 18:39 +0200, Sohaib E. via networkmanager-list
> > > wrote:
> > > > Hello,
> > > >
> > > > I'm trying to use Network Manager to deploy ovs bridges on
> > > > debian/ubuntu.
> > > >
> > > > I understand that Network Manager itself do not have such a feature
> > > > and needs an additional plugin called nm-openvswitch. Nevertheless,
> > > > this plugin is not available on debian/ubuntu and, therefore, I was
> > > > wondering if there was any workaround to deploy ovs bridges using
> > > > nmcli on ubuntu/debian or to install nm-openvswitch on
> > > ubuntu/debian.
> > >
> > > nm-openvswitch is part of NetworkManager, but
> > >
> > > - it can be disabled/enabled at compile time
> > >
> > > - it is loaded from a shared library (dlopen), so it can be packaged
> > > separately (as done on Fedora, with NetworkManager-openvswitch
> > > package). But it doesn't have to be packaged separately, Debian tends
> > > to put all these device plugins in the same "network-manager"
> > > package,
> > > while Fedora tends to split them (NetworkManager-
> > > {wifi,team,wwan,...}).
> > >
> > >
> > > Debian builds with this code disabled. You would either have to
> > > convince the debian maintainers to package this, or build
> > > NetworkManager yourself. In the latter case, you could just rebuild
> > > the
> > > debian package with minor changes to the build settings.
> > >
> > >
> > > best,
> > > Thomas
> > >
>
>
>
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-openvswitch on debian/ubuntu
On Wed, 2021-07-28 at 15:14 +0200, Sohaib E. wrote:
> I found this error in the logs : ovsdb: Could not connect: No such
> file or directory
>
> My ovsdb's unix socket is in /var/run/openvswitch. I don't think
> Network Manager is expecting another path but if it is, where do I
> change that ?
it's not configurable, it's a compile time constant.
Grep the source for "/db.sock".
But that should be correct already. Did you `systemctl start
openvswitch.sevice`?
Where is your db.sock file exactly?
best,
Thomas
>
> Thanks.
>
>
> Le mer. 28 juil. 2021 à 12:57, Thomas Haller a
> écrit :
> > Hi,
> >
> > On Wed, 2021-07-28 at 12:41 +0200, Sohaib E. wrote:
> > > Thank you for your quick answer.
> > >
> > > I have compiled NetworkManager's package myself but I still faced
> > some
> > > issues deploying an ovs bridge.
> > >
> > > Besides the NetworkManager-ovs.conf (openvswitch-switch.service
> > instead
> > > of openvswitch.service), what other settings must be modified for
> > this
> > > to work ?
> >
> >
> > I don't think anything else is missing.
> >
> > Obviously, you need to create connection profiles, read `man nm-
> > openvswitch` about that ([1]). And, you'd activate the right
> > profiles
> > (`nmcli connection up` and watch current setup with `nmcli device`
> > and
> > `nmcli connection`).
> >
> > Other than that, nothing comes to mind. As always when debugging
> > NetworkManager, enable level=TRACE logging and read the log. See
> > [2]
> > for hints about logging.
> >
> > Maybe the path to ovsdb's unix socket is different on the system?
> > That
> > is currently a compile time constant. You should see that in the
> > logs...
> >
> >
> > [1]
> > https://networkmanager.pages.freedesktop.org/NetworkManager/NetworkManager/nm-openvswitch.html
> > [2]
> > https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/2d879c1ac5d907fe184898b23693fb8148363645/contrib/fedora/rpm/NetworkManager.conf#L27
> >
> >
> > best,
> > Thomas
> >
> >
> > >
> > > Thank you for your time,
> > > Sohaib
> > >
> > > Le mer. 28 juil. 2021 à 10:39, Thomas Haller
> > > a
> > > écrit :
> > > > On Tue, 2021-07-27 at 18:39 +0200, Sohaib E. via
> > > > networkmanager-
> > list
> > > > wrote:
> > > > > Hello,
> > > > >
> > > > > I'm trying to use Network Manager to deploy ovs bridges on
> > > > > debian/ubuntu.
> > > > >
> > > > > I understand that Network Manager itself do not have such a
> > feature
> > > > > and needs an additional plugin called nm-openvswitch.
> > Nevertheless,
> > > > > this plugin is not available on debian/ubuntu and, therefore,
> > > > > I
> > was
> > > > > wondering if there was any workaround to deploy ovs bridges
> > using
> > > > > nmcli on ubuntu/debian or to install nm-openvswitch on
> > > > ubuntu/debian.
> > > >
> > > > nm-openvswitch is part of NetworkManager, but
> > > >
> > > > - it can be disabled/enabled at compile time
> > > >
> > > > - it is loaded from a shared library (dlopen), so it can be
> > packaged
> > > > separately (as done on Fedora, with NetworkManager-openvswitch
> > > > package). But it doesn't have to be packaged separately, Debian
> > tends
> > > > to put all these device plugins in the same "network-manager"
> > > > package,
> > > > while Fedora tends to split them (NetworkManager-
> > > > {wifi,team,wwan,...}).
> > > >
> > > >
> > > > Debian builds with this code disabled. You would either have to
> > > > convince the debian maintainers to package this, or build
> > > > NetworkManager yourself. In the latter case, you could just
> > rebuild
> > > > the
> > > > debian package with minor changes to the build settings.
> > > >
> > > >
> > > > best,
> > > > Thomas
> > > >
> >
> >
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-openvswitch on debian/ubuntu
Hi,
On Wed, 2021-07-28 at 12:41 +0200, Sohaib E. wrote:
> Thank you for your quick answer.
>
> I have compiled NetworkManager's package myself but I still faced some
> issues deploying an ovs bridge.
>
> Besides the NetworkManager-ovs.conf (openvswitch-switch.service instead
> of openvswitch.service), what other settings must be modified for this
> to work ?
I don't think anything else is missing.
Obviously, you need to create connection profiles, read `man nm-
openvswitch` about that ([1]). And, you'd activate the right profiles
(`nmcli connection up` and watch current setup with `nmcli device` and
`nmcli connection`).
Other than that, nothing comes to mind. As always when debugging
NetworkManager, enable level=TRACE logging and read the log. See [2]
for hints about logging.
Maybe the path to ovsdb's unix socket is different on the system? That
is currently a compile time constant. You should see that in the
logs...
[1]
https://networkmanager.pages.freedesktop.org/NetworkManager/NetworkManager/nm-openvswitch.html
[2]
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/2d879c1ac5d907fe184898b23693fb8148363645/contrib/fedora/rpm/NetworkManager.conf#L27
best,
Thomas
>
> Thank you for your time,
> Sohaib
>
> Le mer. 28 juil. 2021 à 10:39, Thomas Haller a
> écrit :
> > On Tue, 2021-07-27 at 18:39 +0200, Sohaib E. via networkmanager-list
> > wrote:
> > > Hello,
> > >
> > > I'm trying to use Network Manager to deploy ovs bridges on
> > > debian/ubuntu.
> > >
> > > I understand that Network Manager itself do not have such a feature
> > > and needs an additional plugin called nm-openvswitch. Nevertheless,
> > > this plugin is not available on debian/ubuntu and, therefore, I was
> > > wondering if there was any workaround to deploy ovs bridges using
> > > nmcli on ubuntu/debian or to install nm-openvswitch on
> > ubuntu/debian.
> >
> > nm-openvswitch is part of NetworkManager, but
> >
> > - it can be disabled/enabled at compile time
> >
> > - it is loaded from a shared library (dlopen), so it can be packaged
> > separately (as done on Fedora, with NetworkManager-openvswitch
> > package). But it doesn't have to be packaged separately, Debian tends
> > to put all these device plugins in the same "network-manager"
> > package,
> > while Fedora tends to split them (NetworkManager-
> > {wifi,team,wwan,...}).
> >
> >
> > Debian builds with this code disabled. You would either have to
> > convince the debian maintainers to package this, or build
> > NetworkManager yourself. In the latter case, you could just rebuild
> > the
> > debian package with minor changes to the build settings.
> >
> >
> > best,
> > Thomas
> >
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-openvswitch on debian/ubuntu
Thank you for your quick answer.
I have compiled NetworkManager's package myself but I still faced some
issues deploying an ovs bridge.
Besides the NetworkManager-ovs.conf (openvswitch-switch.service instead of
openvswitch.service), what other settings must be modified for this to work
?
Thank you for your time,
Sohaib
Le mer. 28 juil. 2021 à 10:39, Thomas Haller a écrit :
> On Tue, 2021-07-27 at 18:39 +0200, Sohaib E. via networkmanager-list
> wrote:
> > Hello,
> >
> > I'm trying to use Network Manager to deploy ovs bridges on
> > debian/ubuntu.
> >
> > I understand that Network Manager itself do not have such a feature
> > and needs an additional plugin called nm-openvswitch. Nevertheless,
> > this plugin is not available on debian/ubuntu and, therefore, I was
> > wondering if there was any workaround to deploy ovs bridges using
> > nmcli on ubuntu/debian or to install nm-openvswitch on ubuntu/debian.
>
> nm-openvswitch is part of NetworkManager, but
>
> - it can be disabled/enabled at compile time
>
> - it is loaded from a shared library (dlopen), so it can be packaged
> separately (as done on Fedora, with NetworkManager-openvswitch
> package). But it doesn't have to be packaged separately, Debian tends
> to put all these device plugins in the same "network-manager" package,
> while Fedora tends to split them (NetworkManager-{wifi,team,wwan,...}).
>
>
> Debian builds with this code disabled. You would either have to
> convince the debian maintainers to package this, or build
> NetworkManager yourself. In the latter case, you could just rebuild the
> debian package with minor changes to the build settings.
>
>
> best,
> Thomas
>
>
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-openvswitch on debian/ubuntu
On Tue, 2021-07-27 at 18:39 +0200, Sohaib E. via networkmanager-list
wrote:
> Hello,
>
> I'm trying to use Network Manager to deploy ovs bridges on
> debian/ubuntu.
>
> I understand that Network Manager itself do not have such a feature
> and needs an additional plugin called nm-openvswitch. Nevertheless,
> this plugin is not available on debian/ubuntu and, therefore, I was
> wondering if there was any workaround to deploy ovs bridges using
> nmcli on ubuntu/debian or to install nm-openvswitch on ubuntu/debian.
nm-openvswitch is part of NetworkManager, but
- it can be disabled/enabled at compile time
- it is loaded from a shared library (dlopen), so it can be packaged
separately (as done on Fedora, with NetworkManager-openvswitch
package). But it doesn't have to be packaged separately, Debian tends
to put all these device plugins in the same "network-manager" package,
while Fedora tends to split them (NetworkManager-{wifi,team,wwan,...}).
Debian builds with this code disabled. You would either have to
convince the debian maintainers to package this, or build
NetworkManager yourself. In the latter case, you could just rebuild the
debian package with minor changes to the build settings.
best,
Thomas
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
nm-openvswitch on debian/ubuntu
Hello, I'm trying to use Network Manager to deploy ovs bridges on debian/ubuntu. I understand that Network Manager itself do not have such a feature and needs an additional plugin called nm-openvswitch. Nevertheless, this plugin is not available on debian/ubuntu and, therefore, I was wondering if there was any workaround to deploy ovs bridges using nmcli on ubuntu/debian or to install nm-openvswitch on ubuntu/debian. Thanks. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
