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 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: > [2]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?
I installed the OVS that came with squeeze. Here is the information from
the changelog.
openvswitch (2.6.2~pre+git20161223-3) unstable; urgency=medium
* Avoid installing ovs-vswitchd.conf.db.5 manpage into directory for
language "db". Closes: #850631. Thanks to Michael Stapelberg
<stapelb...@debian.org> for reporting this bug.
-- Ben Pfaff <pfaff...@debian.org> Mon, 09 Jan 2017 14:46:48 -0800
> (e.g /lib/systemd/system/ovsdb-server.service). (OVS repo does not
> provide any. We just provide /etc/init.d/openvswitc-switch script).
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?
>
> 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][3]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][4]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][5]disc...@openvswitch.org
> > > > [4][6]https://mail.openvswitch.org/mailman/listinfo/ovs-
> discuss
> > >
> > > --
> > > Brian Lavender
> > > [5][7]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][8]disc...@openvswitch.org
> > > [7][9]https://mail.openvswitch.org/mailman/listinfo/ovs-
> discuss
> > --
> > Brian Lavender
> > [8][10]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][11]disc...@openvswitch.org
> > [10][12]https://mail.openvswitch.org/mailman/listinfo/ovs-
> discuss
> >
> > References
> >
> > 1. mailto:[13]br...@brie.com
> > 2. [14]http://www.brie.com/brian/
> > 3. mailto:[15]disc...@openvswitch.org
> > 4. [16]https://mail.openvswitch.org/
> mailman/listinfo/ovs-discuss
> > 5. [17]http://www.brie.com/brian/
> > 6. mailto:[18]disc...@openvswitch.org
> > 7. [19]https://mail.openvswitch.org/
> mailman/listinfo/ovs-discuss
> > 8. [20]http://www.brie.com/brian/
> > 9. mailto:[21]disc...@openvswitch.org
> > 10. [22]https://mail.openvswitch.org/
> mailman/listinfo/ovs-discuss
>
> --
> Brian Lavender
> [23]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
> [24]disc...@openvswitch.org
> [25]https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>
> References
>
> 1. mailto:br...@brie.com
> 2. http://docs.openvswitch.org/en/latest/intro/install/debian/
> 3. mailto:br...@brie.com
> 4. http://www.brie.com/brian/
> 5. mailto:disc...@openvswitch.org
> 6. https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
> 7. http://www.brie.com/brian/
> 8. mailto:disc...@openvswitch.org
> 9. https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
> 10. http://www.brie.com/brian/
> 11. mailto:disc...@openvswitch.org
> 12. https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
> 13. mailto:br...@brie.com
> 14. http://www.brie.com/brian/
> 15. mailto:disc...@openvswitch.org
> 16. https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
> 17. http://www.brie.com/brian/
> 18. mailto:disc...@openvswitch.org
> 19. https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
> 20. http://www.brie.com/brian/
> 21. mailto:disc...@openvswitch.org
> 22. https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
> 23. http://www.brie.com/brian/
> 24. mailto:disc...@openvswitch.org
> 25. 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
signature.asc
Description: PGP signature
_______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
