On 3 July 2018 at 10:44, Brian E. Lavender <br...@brie.com> 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 packages by following: http://docs.openvswitch.org/en/latest/intro/install/debian/ Tangentially, Which version of OVS are you installing? Do you have OVS systemd files in your machine? (e.g /lib/systemd/system/ovsdb-server.service). (OVS repo does not provide any. We just provide /etc/init.d/openvswitc-switch script). > > brian > > On Tue, Jul 03, 2018 at 10:39:03AM -0700, Guru Shetty wrote: > > On 1 July 2018 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 > > > > 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 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 that I have to > > bring > > > the link up on the device. > > > > > > ip link set dev eno1 up > > > ovs-vsctl add-br br0 > > > ovs-vsctl add-port br0 eno1 > > > dhclient br0 > > > > > > This is what I put in /etc/network/interfaces . It's what I thought > > > worked before and seems pretty straight forward, but after boot, I > > get > > > no switch. :( Do I have 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 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. > > > > > > > > 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 > > > > > > > > I check the system and when I look at the output of "ip address", > > it > > > > shows DOWN for interface "eno1". If I do the following from the > > command > > > > line, the bridge comes up and I get an IP address. The "#" > > indicates ran > > > > as root. > > > > > > > > # ip link set dev eno1 up > > > > # ovs-vsctl add-br br0 > > > > # ovs-vsctl add-port br0 eno1 > > > > # dhclient br0 > > > > > > > > Is there something I am missing in my interfaces file on Debian? > > > > > > > > brian > > > > -- > > > > Brian Lavender > > > > [2]http://www.brie.com/brian/ > > > > > > > > "There are two ways of constructing a software design. One way is > > to > > > > make it so simple that there are obviously no deficiencies. And > the > > other > > > > way is to make it so complicated that there are no obvious > > deficiencies." > > > > > > > > Professor C. A. R. Hoare > > > > The 1980 Turing award lecture > > > > _______________________________________________ > > > > discuss mailing list > > > > [3]disc...@openvswitch.org > > > > [4]https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > > > > > > -- > > > Brian Lavender > > > [5]http://www.brie.com/brian/ > > > > > > "There are two ways of constructing a software design. One way is to > > > make it so simple that there are obviously no deficiencies. And the > > other > > > way is to make it so complicated that there are no obvious > > deficiencies." > > > > > > Professor C. A. R. Hoare > > > The 1980 Turing award lecture > > > _______________________________________________ > > > discuss mailing list > > > [6]disc...@openvswitch.org > > > [7]https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > > -- > > Brian Lavender > > [8]http://www.brie.com/brian/ > > "There are two ways of constructing a software design. One way is to > > make it so simple that there are obviously no deficiencies. And the > > other > > way is to make it so complicated that there are no obvious > > deficiencies." > > Professor C. A. R. Hoare > > The 1980 Turing award lecture > > > > _______________________________________________ > > discuss mailing list > > [9]disc...@openvswitch.org > > [10]https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > > > > References > > > > 1. mailto:br...@brie.com > > 2. http://www.brie.com/brian/ > > 3. mailto:disc...@openvswitch.org > > 4. https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > > 5. http://www.brie.com/brian/ > > 6. mailto:disc...@openvswitch.org > > 7. https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > > 8. http://www.brie.com/brian/ > > 9. mailto:disc...@openvswitch.org > > 10. https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > > -- > Brian Lavender > http://www.brie.com/brian/ > > "There are two ways of constructing a software design. One way is to > make it so simple that there are obviously no deficiencies. And the other > way is to make it so complicated that there are no obvious deficiencies." > > Professor C. A. R. Hoare > The 1980 Turing award lecture > > _______________________________________________ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > >
_______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
