Re: [ovs-discuss] GTP decapsulation
If you are moving between interfaces between hosts, and then subsequently between interfaces on the SAME host you might also need to make use of OVS patch ports as well. HTH On Apr 16, 2021 at 6:33 AM, Ash Ash wrote: Hi I have some gtp pcap files which I want to decapsulate. Is that possible with ovs? I am trying to send those packets using tcpreplay to ovs, decap them, and send to another interface. I tried experimenting based on this https://docs.openvswitch.org/en/latest/howto/tunneling/?highlight=gre#connecting-vms-using-tunnels tutorial but I had no success. ___ 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
Re: [ovs-discuss] GTP decapsulation
You might find a solution using (or in) the Orabuntu-LXC github code. The latest release v6.13.25.3 offers the option to connect hosts (vm or physical) using [geneve|vxlan|gre] tunnels. If you don't need/want to do a full Orabuntu-LXC install, you can just grep for firewall-cmd and geneve in the uekulele subdirectory of the distro to see the ovs-vsctl and firewall-cmd commands we use. https://github.com/gstanden/orabuntu-lxc/archive/refs/tags/6.13.25.3-beta.zip Also don't forget MTU may need to be set to something like 1420 on one end of the tunnel. HTH Gilbert On Apr 16, 2021 at 6:33 AM, Ash Ash wrote: Hi I have some gtp pcap files which I want to decapsulate. Is that possible with ovs? I am trying to send those packets using tcpreplay to ovs, decap them, and send to another interface. I tried experimenting based on this https://docs.openvswitch.org/en/latest/howto/tunneling/?highlight=gre#connecting-vms-using-tunnels tutorial but I had no success. ___ 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
[ovs-discuss] OVS 2.11.1 RPM build from source fails on Oracle Linux 7.8 and 7.9
Hi, OVS 2.11.1 RPM builds and install fine on Oracle Linux 7.6, but on Oracle Linux 7.8 and 7.9 the RPM build fails with the following errors: In file included from lib/netlink-conntrack.c:27:0: /usr/include/linux/netfilter/nf_conntrack_sctp.h:25:2: error: unknown type name 'u8' u8 last_dir; ^ /usr/include/linux/netfilter/nf_conntrack_sctp.h:26:2: error: unknown type name 'u8' u8 flags; ^ make[2]: *** [lib/netlink-conntrack.lo] Error 1 make[2]: Leaving directory `/opt/olxc/home/ubuntu/Downloads/orabuntu-lxc-master/uekulele/openvswitch/rpmbuild/BUILD/openvswitch-2.11.1' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/opt/olxc/home/ubuntu/Downloads/orabuntu-lxc-master/uekulele/openvswitch/rpmbuild/BUILD/openvswitch-2.11.1' make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.s2PkRp (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.s2PkRp (%build) I've looked at these URLs below, but do not know how to make use of them to get the RPM build working on Oracle Linux 7.8 and 7.9 (I have not tested Oracle Linux 7.7 yet). https://bugzilla.redhat.com/show_bug.cgi?id=1890095 and https://github.com/openvswitch/ovs/commit/8c7130da98c55bdf13eae62b5250434f8dfd366b Is there a way I can get OVS 2.11.1 RPM to build successfully on Oracle LInux 7.8 and 7.9 and what is causing the problem? Thanks, Gilbert Standen Contributor Orabuntu-LXC ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Build OpenvSwitch on Oracle Linux 8
FYI This is what is working after several rounds of testing various methods so far. Some notes:(1) I've tried rolling my own python-six using py2pack (search google on keywords "py2pack james adam creating rpms" ) but it doesn't work because even though I can build the RPM, it won't install the resulting RPM because there are several "conflicting files" errors during the installed of the roll-your-own RPM that conflict with files in the python3-six that comes with the Oracle8 distro by default; and, the python3-six cannot be uninstalled because the new dnf capability in Oracle8 depends on that python3-six that comes with the distro so the OS blocks uninstall of python3-six. I haven't considered whether dnf could be uninstalled but won't go there because an Orabuntu-LXC design principle is we are a pure overlay we don't reconfigure anything unless absolutely unavoidable. However, as indicated in the recipe, the python-six noarch from the CentOS7 repo installs fine with no issues and moreover the openvswitch build likes it.(2) When I try to have the build depend entirely on python3-six (and skip the install of the CentOS7 python-six noarch rpm) and just update the spec file to use "python3-six" throughout I get errors in the OpenvSwitch build. I get errors that "files 'ovs-test' and 'ovs-l3ping' are missing and cannot be deleted." (3) The python py36env virtual python environment also is needed; without it I get errors in the build.(4) When I try to use python2 variants (set in the python alternatives step) I get errors in the build.Here is the code that is working on Oracle8 elif [ $Release -ge 7 ] then echo '' echo "==" echo "Build OpenvSwitch RPMs... " echo "==" echo '' cd /opt/olxc/"$DistDir"/uekulele/openvswitch/rpmbuild/SOURCES tar -zxvf openvswitch-"$OvsVersion".tar.gz cp -p openvswitch-"$OvsVersion"/rhel/*.spec /opt/olxc/"$DistDir"/uekulele/openvswitch/. cd /opt/olxc/"$DistDir"/uekulele/openvswitch if [ $Release -eq 8 ] thenwget https://rpmfind.net/linux/centos/7.7.1908/os/x86_64/Packages/python-six-1.9.0-2.el7.noarch.rpmsudo yum -y localinstall python-six-1.9.0-2.el7.noarch.rpmsudo yum -y install python3-sphinxsudo yum -y install python3-sixsudo yum -y install selinux-policy-devel unbound-devel sudo alternatives --set python /usr/bin/python3 python3 -m venv py36env source py36env/bin/activate python3 -m pip install --upgrade pip python3 -m pip install six python3 -m pip install sphinxsed -i 's/BuildRequires: python-six/BuildRequires: python3-six/g' openvswitch.specsed -i 's/BuildRequires: python-sphinx/BuildRequires: python3-sphinx/g' openvswitch.specsleep 5 fi sed -i 's/python >= 2.7/python27/g' openvswitch.spec rpmbuild --define "_topdir /opt/olxc/"$DistDir"/uekulele/openvswitch/rpmbuild" -ba openvswitch.spec echo '' echo "==" echo "Done: Build OpenvSwitch RPMs " echo "=="On Thu, Oct 3, 2019 at 10:50 AM Ben Pfaff <b...@ovn.org> wrote:If you come up with something that you ulimately find satisfactory, then it would be helpful to post a summary of how to build RPMs for OVS on Oracle Linux. Or, if you're willing, you could contribute a spec file for it to the project. On Wed, Oct 02, 2019 at 10:09:11PM +, Gilbert Standen wrote: > Also need "sudo yum -y install python27" which I had left out ... and that should be everything finally for this build of openvswitch 2.11.1 on Oracle Linux 8 > > if [ $Release -eq 8 ] > then > sudo yum -y install python27 <--this is also needed > sudo yum -y install python3-sphinx > sudo yum -y install python3-six > sudo yum -y install selinux-policy-devel unbound-devel <--this is also needed > sudo alternatives --set python /usr/bin/python3 > python3 -m venv py36env > source py36env/bin/activate > python3 -m pip install --upgrade pip > python3 -m pip install six > python3 -m pip install sphinx > sed -i 's/python-six/python3-six/g' openvswitch.spec > sed -i 's/python-sphinx/python3-sphinx/g' openvswitch.spec >
Re: [ovs-discuss] Guidance Needed for OpenVSwith VLAN
Hi Sam, You may want to download my Orabuntu-LXC project from github and inspect the scripts (they are in bash and are very accessible therefore) because Orabuntu-LXC uses VLANs. Basically Orabuntu-LXC uses patch ports on the OpenvSwitches together with VLANs to push traffic selectively from any switch over the single GRE tunnel on just one pair of switches. You should be able to reverse engineer and understand how it works by looking at the crt_ovs_sw1.sh and crt_ovs_sx1.sh scripts, and if you have any questions just respond back to me I will try to help. Thanks G On Thu, Oct 3, 2019 at 2:09 PM Ben Pfaff wrote: > Probably this is not the best place to get that advice. > > I'd suggest using Faucet, it makes this kind of configuration very easy. > There's a Faucet tutorial in recent versions of the OVS repo. (I doubt > it will work with something as old as OVS 2.3.) > > On Thu, Oct 03, 2019 at 07:05:07PM +, SAMRAT PRAVIN PATEL wrote: > > Ok then any thoughts then how do I mention the VLAN rules in the > Controller for RYU or FloodLight ? > > > > > > From: Ben Pfaff > > Sent: Thursday, October 3, 2019 1:03:34 PM > > To: SAMRAT PRAVIN PATEL > > Cc: OpenV Switch Discussion > > Subject: Re: [ovs-discuss] Guidance Needed for OpenVSwith VLAN > > > > No. > > > > If you are using a controller, VLAN configuration is only in the > > controller. > > > > On Thu, Oct 03, 2019 at 06:59:40PM +, SAMRAT PRAVIN PATEL wrote: > > > Hi so you mean I will have to set the VLAN tags in the OVSwitch and > define the tags in the RYU controller for the OVSwitch to work ? Hoping for > your guideance / > > > > > > > > > From: Ben Pfaff > > > Sent: Thursday, October 3, 2019 12:57:43 PM > > > To: SAMRAT PRAVIN PATEL > > > Cc: OpenV Switch Discussion > > > Subject: Re: [ovs-discuss] Guidance Needed for OpenVSwith VLAN > > > > > > If you're using a controller, then it overrides anything set with OVS > > > itself and you need to configure them with Ryu instead. > > > > > > On Thu, Oct 03, 2019 at 06:51:11PM +, SAMRAT PRAVIN PATEL wrote: > > > > Hi , > > > > > > > > > > > > I have a ryu controller and I have added ports eth1 to VLAN 100 , > eth2 to VLAN 100 and eth3 to VLAN 200 technicall ping should not work from > eth1 to eth3 vice versa , here I am able to ping all the nodes . I guess > the VLAN rules are not being set. Please guide me . > > > > > > > > > > > > From: Ben Pfaff > > > > Sent: Thursday, October 3, 2019 12:46:48 PM > > > > To: SAMRAT PRAVIN PATEL > > > > Cc: OpenV Switch Discussion > > > > Subject: Re: [ovs-discuss] Guidance Needed for OpenVSwith VLAN > > > > > > > > OVS 2.3 does support VLANs. > > > > > > > > So far, your question is just "This doesn't work. How do I make it > > > > work?" We don't have any idea what you're trying to do. To help, we > > > > need to know. > > > > > > > > On Thu, Oct 03, 2019 at 06:40:25PM +, SAMRAT PRAVIN PATEL wrote: > > > > > Hi , > > > > > > > > > > > > > > > Thanks ben . So OVS 2.3 does not support VLAN ?? You mean ? > > > > > > > > > > > > > > > From: Ben Pfaff > > > > > Sent: Thursday, October 3, 2019 12:36:27 PM > > > > > To: SAMRAT PRAVIN PATEL > > > > > Cc: OpenV Switch Discussion > > > > > Subject: Re: [ovs-discuss] Guidance Needed for OpenVSwith VLAN > > > > > > > > > > What are you trying to do? > > > > > > > > > > OVS 2.3 is very old. > > > > > > > > > > On Thu, Oct 03, 2019 at 06:10:48PM +, SAMRAT PRAVIN PATEL > wrote: > > > > > > hi , > > > > > > > > > > > > this is Sam here. Some how I am not able to run my VLAN . I > shall be thankful to you if someone can guide me > > > > > > > > > > > > > > > > > > spp21001@ovs:~$ sudo ovs-vsctl show > > > > > > 89362c3a-1d64-451b-977d-7b2718a1ba20 > > > > > > Bridge "br0" > > > > > > fail_mode: secure > > > > > > Port "eth1" > > > > > > tag: 100 > > &
Re: [ovs-discuss] Guidance Needed for GRE Tunnel
This is what I use for example: sudo ovs-vsctl add-port sw1 gre201 -- set interface gre201 type=gre options:remote_ip=10.0.139.144 sudo ovs-vsctl add-port sw1 gre201 -- set interface gre201 type=gre options:remote_ip=10.0.139.234 And from "sudo ovs-vsctl show" I set the MTU to 1420 on one end of the tunnel so that ssh sessions can run over the tunnel. I attach LXC containers to the ovs switch sw1 and use the GRE tunnel for ssh between containers on the two hosts. orabuntu@ip-10-0-139-144:/etc/network/openvswitch$ ifconfig sw1 sw1 Link encap:Ethernet HWaddr e6:92:cc:99:93:49 inet addr:10.209.53.201 Bcast:0.0.0.0 Mask:255.255.255.0 inet6 addr: fe80::e492:ccff:fe99:9349/64 Scope:Link UP BROADCAST RUNNING MULTICAST *MTU:1420* Metric:1 RX packets:5445 errors:0 dropped:0 overruns:0 frame:0 TX packets:358 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:356641 (356.6 KB) TX bytes:70319 (70.3 KB) ubuntu@ip-10-0-139-234:~$ ifconfig sw1 sw1 Link encap:Ethernet HWaddr d2:d9:c4:bf:8b:43 inet addr:10.209.53.1 Bcast:0.0.0.0 Mask:255.255.255.0 inet6 addr: fe80::d0d9:c4ff:febf:8b43/64 Scope:Link UP BROADCAST RUNNING MULTICAST *MTU:1500* Metric:1 RX packets:273222 errors:0 dropped:0 overruns:0 frame:0 TX packets:230878 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:15256132 (15.2 MB) TX bytes:16409194 (16.4 MB) HTH On Wed, Oct 2, 2019 at 2:22 PM SAMRAT PRAVIN PATEL wrote: > Hi , > > > I am trying to connect two openvswitch on GENI. So for GRE tunnel we need > to add the remote IP of the physical interfaces of the openvswitch ? Please > guide me . Hoping for your response. > > > *sudo **ovs-vsctl add-port br0 gre0 *-- set interface gre0 type=gre > options:remote_ip=10.10.1.3 ( These are the ip address of the host pcs) > > > *sudo **ovs-vsctl add-port br0 gre0 -- set interface gre0 type=gre > options:remote_ip=**10.10.1.* > > *4 ( These remote are the ip address of the host pcs) * > > > > Regards > > Samrat Pravin Patel > ___ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > -- Gilbert Standen Creator Orabuntu-LXC 914-261-4594 gilb...@orabuntu-lxc.com ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Build OpenvSwitch on Oracle Linux 8
Thanks Ben. I will keep hacking away at it. The protocols and design principles of Orabuntu-LXC require all installed software to be packaged - rpm or deb - so I will have to keep working on a solution to get the rpm package to build successfully. BTW that was a typo earlier - we had been using ovs 2.5.4 not 2.0.5 - sorry - 2.0.5 is the LXC version we were using for this testing Sent from my BlackBerry 10 smartphone. Original Message From: Ben Pfaff Sent: Tuesday, October 1, 2019 7:00 PM To: Gilbert Standen Cc: ovs-discuss@openvswitch.org Subject: Re: [ovs-discuss] Build OpenvSwitch on Oracle Linux 8 OK. It seems likely, then, that the Fedora RPM spec files are not suitable for Oracle Linux. If so, then you can install OVS without the RPM packaging, or create some new spec files for Oracle Linux. On Tue, Oct 01, 2019 at 11:55:20PM +, Gilbert Standen wrote: > I've tried all that - that was of course the first thing I tried. > > I've tried everything I can think of: > > [ubuntu@oracle8 ~]$ sudo yum install python-six python-sphinx > [sudo] password for ubuntu: > Last metadata expiration check: 0:27:33 ago on Tue 01 Oct 2019 06:20:33 PM > CDT. > No match for argument: python-six > No match for argument: python-sphinx > Error: Unable to find a match > [ubuntu@oracle8 ~]$ > > and the above is with all repos enabled AND epel installed and enabled: > > [ubuntu@oracle8 yum.repos.d]$ sudo yum install python-six python-sphinx > Extra Packages for Enterprise Linux 8 - Playground - x86_64 463 kB/s | 2.6 MB > 00:05 > Extra Packages for Enterprise Linux 8 - Playground - x86_64 - Debug 589 kB/s > | 1.6 MB 00:02 > Extra Packages for Enterprise Linux 8 - Playground - x86_64 - Source 130 kB/s > | 374 kB 00:02 > Extra Packages for Enterprise Linux 8 - x86_64 35 kB/s | 18 kB 00:00 > Extra Packages for Enterprise Linux 8 - x86_64 - Debug 295 kB/s | 656 kB 00:02 > Extra Packages for Enterprise Linux 8 - x86_64 - Source 239 kB/s | 390 kB > 00:01 > No match for argument: python-six > No match for argument: python-sphinx > Error: Unable to find a match > [ubuntu@oracle8 yum.repos.d]$ > > [ubuntu@oracle8 yum.repos.d]$ sudo yum install python-six python-sphinx > Oracle Linux 8 Addons (x86_64) 2.6 kB/s | 3.2 kB 00:01 > Oracle Linux 8 Application Stream (x86_64) 29 kB/s | 2.9 kB 00:00 > Oracle Linux 8 BaseOS Latest (x86_64) 18 kB/s | 2.7 kB 00:00 > Oracle Linux 8 CodeReady Builder (x86_64) - Unsupported 27 kB/s | 2.7 kB 00:00 > Oracle Linux 8 BaseOS GA (x86_64) 26 kB/s | 2.7 kB 00:00 > No match for argument: python-six > No match for argument: python-sphinx > Error: Unable to find a match > [ubuntu@oracle8 yum.repos.d]$ > > I've also tried setting up a python virtual environment within the script - > that doesn't work either: > > sudo alternatives --set python /usr/bin/python3 > python3 -m venv py36env > source py36env/bin/activate > python3 -m pip install six > python3 -m pip install --upgrade pip > python3 -m pip install six > python3 -m pip install sphinx > > all those commands work, but openvswitch build doesn't see sphinx or six - do > I need to set some switch on the build command ? > > error: Failed build dependencies: > python-six is needed by openvswitch-2.11.1-1.x86_64 > python-sphinx is needed by openvswitch-2.11.1-1.x86_64 > > > > From: Ben Pfaff > Sent: Tuesday, October 1, 2019 6:40 PM > To: Gilbert Standen > Cc: ovs-discuss@openvswitch.org > Subject: Re: [ovs-discuss] Build OpenvSwitch on Oracle Linux 8 > > You're using two different packaging systems here. The RPM spec file > requires the RPMs it mentions to be installed (for Python 2), but you > used pip to install them (for Python 3). > > My guess is that "yum install python-six python-sphinx > selinux-policy-devel unbound-devel" or its Oracle equivalent will fix > the problem. > > On Tue, Oct 01, 2019 at 11:17:18PM +, Gilbert Standen wrote: > > For example: > > > > [ubuntu@oracle8 anylinux]$ python3 -m pip install six > > Requirement already satisfied: six in /usr/local/lib/python3.6/site-packages > > [ubuntu@oracle8 anylinux]$ python3 -m pip install sphinx > > Requirement already satisfied: sphinx in > > /usr/local/lib64/python3.6/site-packages > > Requirement already satisfied: requests>=2.5.0 in > > /usr/lib/python3.6/site-packages (from sphinx) > > Requirement already satisfied: babel!=2.0,>=1.3 in > > /usr/local/lib64/python3.6/site-packages (from sphinx) > > Requirement already satisfied: sphinxcontrib-serializinghtml in > > /usr/local/lib/python3.6/site-packages (from sphinx) > > Requirement already satisfied: sphinxcontrib-jsmath in > > /usr/lo
Re: [ovs-discuss] Docker & Open vSwitch question.
I guess by "patch" you mean "patch ports" . I think you will need to bring VLANs into the solution to accomplish what you are describing. My Orabuntu-LXC software ( https://github.com/gstanden/orabuntu-lxc ) uses a scheme of this type. HTH Gilbert On Sat, Nov 3, 2018, 9:15 AM Kevin Swagger wrote: > > > I am trying to have two separate networks each with an OVS bridge. I have > a few docker containers connected to each bridge. I used a command like > "ovs-docker add-port ovs-br1 eth1 container1 " to connect the docker > containers to the bridges. I tried creating my own docker network that all > the containers used and when I removed the patch connection between the two > bridges the containers could still communicate. When I created two separate > docker networks the containers could not communicate to the other network > of containers. Is there a way I can accomplish my goal? > > > > I want the two Open vSwitch bridges to be able to communicate by a patch. > I want the docker containers to only communicate over the patch and if I > remove the patch I want the containers to not be able to communicate. > > > > Thank you > > > ___ > 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
Re: [ovs-discuss] Bonded interface on ovs bridge configuration
Hi, this is some code I used quite awhile back to create bonded switch
ports in case this helps...
ovs-vsctl add-bond sw4 bond0 sw4p2 sw4p1 trunks=10,322
ovs-vsctl add-bond sw3 bond1 sw3p2 sw3p1 trunks=10,322
ovs-vsctl set interface sw3p1 type=patch options:peer=sw4p1
ovs-vsctl set interface sw4p1 type=patch options:peer=sw3p1
ovs-vsctl set interface sw3p2 type=patch options:peer=sw4p2
ovs-vsctl set interface sw4p2 type=patch options:peer=sw3p2
On Wed, Jun 13, 2018 at 9:34 AM, Chris Boley wrote:
> Hi, depending on your switch: for example a C!$C0 3560 or 3750 will often
> can only use slow LACP negotiation and not fast negotiation. I’m not sure
> if this might make any difference to your scenario.
>
> On Tue, Jun 12, 2018 at 8:13 AM Tejali Bhujbal
> wrote:
>
>> Hi Guys ,
>> I am trying to configure bonded interface on ovs bridge but somehow
>> bonding doesn't up.
>> can you see any mistake in my configuration?
>>
>>
>> auto lo
>> iface lo inet loopback
>> dns-nameservers 129.241.0.200
>> dns-search dev.iaas.ntnu.no mass
>>
>> # Bond enp7s0f0 and enp7s0f1 together
>> allow-vmbr0 bond0
>> iface bond0 inet static
>> ovs_bridge vmbr0
>> ovs_type OVSBond
>> ovs_bonds enp7s0f0 enp7s0f1
>> address 10.212.28.11/22
>> # Force the MTU of the physical interfaces to be jumbo-frame capable.
>> # This doesn't mean that any OVSIntPorts must be jumbo-capable.
>> # We cannot, however set up definitions for eth0 and eth1 directly due
>> # to what appear to be bugs in the initialization process.
>> pre-up ( ifconfig enp7s0f0 mtu 9000 && ifconfig enp7s0f1 mtu 9000 )
>> ovs_options bond_mode=balance-slb lacp=active
>> other_config:lacp-time=fast
>> mtu 9000
>>
>> # Bridge for our bond and vlan virtual interfaces (our VMs will
>> # also attach to this bridge)
>> auto vmbr0
>> allow-ovs vmbr0
>> iface vmbr0 inet manual
>> ovs_type OVSBridge
>> # NOTE: we MUST mention bond0, vlan50, and vlan55 even though each
>> # of them lists ovs_bridge vmbr0! Not sure why it needs this
>> # kind of cross-referencing but it won't work without it!
>> ovs_ports bond0 vlan1529 vlan1530
>> mtu 9000
>>
>> # Proxmox cluster communication vlan
>> allow-vmbr0 vlan1529
>> iface vlan1529 inet static
>> ovs_type OVSIntPort
>> ovs_bridge vmbr0
>> ovs_options tag=1529
>> ovs_extra set interface ${IFACE} external-ids:iface-id=$(hostname
>> -s)-${IFACE}-vif
>> address 10.212.36.11
>> netmask 255.255.252.0
>> gateway 10.212.36.1
>> mtu 1500
>>
>> # Ceph cluster communication vlan (jumbo frames)
>> allow-vmbr0 vlan1530
>> iface vlan1530 inet static
>> ovs_type OVSIntPort
>> ovs_bridge vmbr0
>> ovs_options tag=1530
>> ovs_extra set interface ${IFACE} external-ids:iface-id=$(hostname
>> -s)-${IFACE}-vif
>> address 10.212.40.11
>> netmask 255.255.252.0
>> mtu 9000
>>
>> auto eno1
>> iface eno1 inet static
>> address 10.212.48.11/22
>> mtu 1500
>>
>> auto eno2
>> iface eno2 inet manual
>> mtu 1500
>>
>> auto eno3
>> iface eno3 inet manual
>> mtu 1500
>>
>> auto eno4
>> iface eno4 inet manual
>> mtu 1500
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Kind regards
>>
>> Tejali Sonawane-Bhujbal
>> Department Engineer - NTNU IT
>> Byggteknisk, s-226, Gløshaugen
>> Contact- +47-96708171
>> ___
>> 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
>
>
--
Gilbert Standen
Creator Orabuntu-LXC
914-261-4594
gilb...@orabuntu-lxc.com
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Openvswitch and LXC integration on Ubuntu 18.04
In addition to what Paul has mentioned, here is example of what I use (switch as a systemd service): /etc/systemd/system/sw1.service -rw-r--r-- 1 root root 268 Mar 10 13:45 sw1.service [Unit] Description=sw1 Service Wants=network-online.target After=network-online.target [Service] Type=oneshot User=root RemainAfterExit=yes ExecStart=/etc/network/openvswitch/crt_ovs_sw1.sh ExecStop=/usr/bin/ovs-vsctl del-br sw1 [Install] WantedBy=multi-user.target Then ExecStart and ExecStop can be customized as you want with a command or script reference. I use my own custom script (e.g. crt_ovs_sw1.sh), but as Paul mentioned, you can use the scripts provided as well. On Mon, May 14, 2018 at 5:55 AM, <den...@exemail.com.au> wrote: > Paul > > Thanks for that command. I tried it and found that my br-int was not up . > > After "sudo ip link set br-int up" and "sudo ip addr add 192.168.1.1/24 > dev br-int" it worked and I could ping as expected. > > For Ubuntu 18.04 I have added the following to /etc/network/interfaces > > allow-ovs br-int > iface br-int inet static > address 192.168.1.1 > netmask 255.255.255.0 > ovs_type OVSBridge > > But on reboot br-int is not coming up correctly after reboot. > > 5: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group > default qlen 1000 > link/ether c6:8e:e2:7b:0f:4f brd ff:ff:ff:ff:ff:ff > > Is this the correct way to define a Openvswitch bridge with IP on Ubuntu? > > > Thanks > > Densha > > It looks> Before you rebuild, I suggest you ping at the interval of 0.01, > then, take > > "ovs-ofctl dump-flows br-int" and save it to a file. The relevant columns > > are table and n_packets. Wait a couple of seconds, then take the dump > > again. Compare and find the entries that increment at the rate of your > > ping. > > > > If you don't see the hits in the tables - check iptables, kmod, etc. > > > > If you ser them, use trace to figure out why your traffic is being > > dropped. > > > > Regards, > > Paul > > > > > > Get Outlook for iOS<https://aka.ms/o0ukef> > > ____ > > From: ovs-discuss-boun...@openvswitch.org > > <ovs-discuss-boun...@openvswitch.org> on behalf of den...@exemail.com.au > > <den...@exemail.com.au> > > Sent: Saturday, May 12, 2018 11:45:57 PM > > To: Orabuntu-LXC > > Cc: ovs-discuss@openvswitch.org > > Subject: Re: [ovs-discuss] Openvswitch and LXC integration on Ubuntu > 18.04 > > > > Thanks. I tried that and still unable to ping from the LXC container to > > the IP address set on the bridge. > > > > I will rebuild everything from scratch and retry. > > > >> Check sysctl settings. Check/set these on the LXC host machine in the > >> /etc/sysctl.conf (or in a new file in the /etc/sysctl.d directory, e.g > >> you > >> could call it /etc/sysctl.d/60-lxc.conf) : > >> > >> net.ipv4.conf.default.rp_filter=0 > >> net.ipv4.conf.all.rp_filter=0 > >> net.ipv4.ip_forward=1 > >> > >> Reference: > >> https://thenewstack.io/solving-a-common-beginners- > problem-when-pinging-from-an-openstack-instance/ > >> > >> > >> > >> On Sat, May 12, 2018 at 7:09 AM, <den...@exemail.com.au> wrote: > >> > >>> Thanks for the response and links. I will watch the OvS Con videos. > >>> > >>> I have now successfully started the container, but unable to ping out > >>> or > >>> into the container. > >>> > >>> I have modified my /var/lib/vm1/conf to be > >>> > >>> # Network configuration > >>> lxc.net.0.type = veth > >>> lxc.net.0.link = br-int <- Name of my internal container bridge > >>> lxc.net.0.flags = up > >>> lxc.net.0.name=eth0 > >>> lxc.net.0.hwaddr = 00:16:3e:d2:23:a8 .<- This was in the conf when > >>> created. > >>> > >>> > >>> When I start the container - I can see the port be added to the bridge > >>> on > >>> the host system > >>> > >>> # sudo lxc-start -n vm1 > >>> # sudo ovs-vsctl show > >>> c3d9247e-68f1-4ae1-be0e-4bb86fd2c541 > >>> Bridge br-dmz > >>> Port br-dmz > >>> Interface br-dmz > >>> type: internal > >>> Bridge br-int > >>> Port "veth4U4B0B" <- New port added when >
Re: [ovs-discuss] Openvswitch and LXC integration on Ubuntu 18.04
Check sysctl settings. Check/set these on the LXC host machine in the /etc/sysctl.conf (or in a new file in the /etc/sysctl.d directory, e.g you could call it /etc/sysctl.d/60-lxc.conf) : net.ipv4.conf.default.rp_filter=0 net.ipv4.conf.all.rp_filter=0 net.ipv4.ip_forward=1 Reference: https://thenewstack.io/solving-a-common-beginners-problem-when-pinging-from-an-openstack-instance/ On Sat, May 12, 2018 at 7:09 AM, <den...@exemail.com.au> wrote: > Thanks for the response and links. I will watch the OvS Con videos. > > I have now successfully started the container, but unable to ping out or > into the container. > > I have modified my /var/lib/vm1/conf to be > > # Network configuration > lxc.net.0.type = veth > lxc.net.0.link = br-int <- Name of my internal container bridge > lxc.net.0.flags = up > lxc.net.0.name=eth0 > lxc.net.0.hwaddr = 00:16:3e:d2:23:a8 .<- This was in the conf when > created. > > > When I start the container - I can see the port be added to the bridge on > the host system > > # sudo lxc-start -n vm1 > # sudo ovs-vsctl show > c3d9247e-68f1-4ae1-be0e-4bb86fd2c541 > Bridge br-dmz > Port br-dmz > Interface br-dmz > type: internal > Bridge br-int > Port "veth4U4B0B" <- New port added when > container starts > Interface "veth4U4B0B" > Port br-int > Interface br-int > type: internal > Port "enp2s0" > Interface "enp2s0" > ovs_version: "2.9.0" > > The bridge br-int has self IP 192.168.10.1/24 - that I added using (after > reboot) > > # sudo ip addr del 192.168.0.1/24 dev br-int > > 5: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group > default qlen 1000 > link/ether 00:01:80:82:f8:59 brd ff:ff:ff:ff:ff:ff > inet 192.168.10.1/24 scope global br-int >valid_lft forever preferred_lft forever > > and the new port > > 8: veth4U4B0B@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc > noqueue master ovs-system state UP group default qlen 1000 > link/ether fe:b8:87:1b:1e:5e brd ff:ff:ff:ff:ff:ff link-netnsid 0 > inet6 fe80::fcb8:87ff:fe1b:1e5e/64 scope link >valid_lft forever preferred_lft forever > > Inside the container I set the IP of eth0 device using > > ubuntu@vm1:~$ sudo ip addr add 192.168.10.2/24 dev eth0 > > ubuntu@vm1:~$ ip a > 7: eth0@if8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue > state UP group default qlen 1000 > link/ether 00:16:3e:d2:23:a8 brd ff:ff:ff:ff:ff:ff link-netnsid 0 > inet 192.168.10.2/24 scope global eth0 >valid_lft forever preferred_lft forever > inet6 fe80::216:3eff:fed2:23a8/64 scope link >valid_lft forever preferred_lft forever > > However I still cannot ping the self IP of the bridge. > > Is there anything obvious that I have configured wrong? > > Thanks > > Densha > > > > These materials might help: > > > > 1. Presentation on running LXC on OpenvSwitch at OvS Con: > > > > https://www.youtube.com/watch?v=MXewSiDvQl4=221s (presentation I gave > at > > OvS Con). > > > > I discuss in the preso that for LXC 2.1+, you now have the option to > > configure OpenvSwitch for LXC in two different ways. You can configure > it > > using, as you mentioned, the scripts (and this was the way we had to do > it > > in LXC 1.0.x and 2.0.x. This method has advantage that VLAN's can also > > be > > configured pretty easily in these scripts too. > > > > lxc.net.0.script.up > > lxc.net.0.script.down > > > > Or, starting from 2.1.x you can also configure it directly in the LXC > > config using for example these parameters: > > > > lxc.net.0.type = veth > > lxc.net.0.link = ovsbr0 > > lxc.net.0.flags = up > > lxc.net.0.name = eth0 > > > > which is also discussed here: > > https://discuss.linuxcontainers.org/t/lxc-2-1-has-been-released/487 > > > > 2. Also, my Orabuntu-LXC software projects is specifically designed for > > deploying an entire LXC VLAN-tagged infrastructure on OpenvSwitch with > > just > > a single command: > > > > https://github.com/gstanden/orabuntu-lxc > > > > See if these references above help you set it up, and if not, let me > know. > > > > HTH, Gilbert > > > > > > > > On Sat, May 12, 2018 at 2:32 AM, <den...@exemail.com.au> wrote: > > > >> > >> I am attempting to use LXC containers with OpenVswitch on Ubuntu 18.0
Re: [ovs-discuss] Openvswitch and LXC integration on Ubuntu 18.04
These materials might help:
1. Presentation on running LXC on OpenvSwitch at OvS Con:
https://www.youtube.com/watch?v=MXewSiDvQl4=221s (presentation I gave at
OvS Con).
I discuss in the preso that for LXC 2.1+, you now have the option to
configure OpenvSwitch for LXC in two different ways. You can configure it
using, as you mentioned, the scripts (and this was the way we had to do it
in LXC 1.0.x and 2.0.x. This method has advantage that VLAN's can also be
configured pretty easily in these scripts too.
lxc.net.0.script.up
lxc.net.0.script.down
Or, starting from 2.1.x you can also configure it directly in the LXC
config using for example these parameters:
lxc.net.0.type = veth
lxc.net.0.link = ovsbr0
lxc.net.0.flags = up
lxc.net.0.name = eth0
which is also discussed here:
https://discuss.linuxcontainers.org/t/lxc-2-1-has-been-released/487
2. Also, my Orabuntu-LXC software projects is specifically designed for
deploying an entire LXC VLAN-tagged infrastructure on OpenvSwitch with just
a single command:
https://github.com/gstanden/orabuntu-lxc
See if these references above help you set it up, and if not, let me know.
HTH, Gilbert
On Sat, May 12, 2018 at 2:32 AM, <den...@exemail.com.au> wrote:
>
> I am attempting to use LXC containers with OpenVswitch on Ubuntu 18.04 LTS
> server. However, I am unable to work out the syntax for the container
> settings. The container is failing to start due to unable to create the
> network.
>
> I did a vanilla install onto a media play with two NIC cards - enp1s0 and
> enp2s0.
>
> I installed, created, tested and then destroyed a container using lxc to
> confirm that lxc was functioning correctly on the server.
>
> #sudo apt-get install lxc lxc-templates wget bridge-utils
> #sudo lxc-checkconfig
> #sudo lxc-create -n vm1 -t ubuntu
> #sudo lxc-start -n vm1
> #sudo lxc-console -n vm1
> #sudo lxc-stop -n vm1
> #sudo lxc-destroy -n vm1
>
> I then removed lxc bridge - lxcbr0 by setting USE_LXC_BRIDGE to false in
> /etc/default/lxc-net and removed lxcbr0 device and rebooted.
>
> # sudo ip link set lxcbr0 down
> # sudo brctl delbr lxcbr0
>
> I then installed openvswitch and created two bridges br-dmz (dmz
> containers - 172.18.0.0/24) and br-int (internal containers -
> 192.168.0.0/24). I have added physical NIC port enp2s0 to br-int as I
> have a local WAP installed on that interface.
>
> #sudo apt-get install openvswitch-switch
> #sudo ovs-vsctl add-br br-dmz
> #sudo ovs-vsctl add-br br-int
> #sudo ovs-vsctl add-port br-int enp2s0
>
> #sudo ip addr add 172.18.0.1/24 dev br-dmz
> #sudo ip addr add 192.168.10.1/24 dev br-int
>
> #sudo ovs-vsctl show
> c3d9247e-68f1-4ae1-be0e-4bb86fd2c541
> Bridge br-dmz
> Port br-dmz
> Interface br-dmz
> type: internal
> Bridge br-int
> Port br-int
> Interface br-int
> type: internal
> Port "enp2s0"
> Interface "enp2s0"
> ovs_version: "2.9.0"
>
> #ip a
>
> 5: br-dmz: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
> default qlen 1000
> link/ether 7e:86:2a:79:24:4e brd ff:ff:ff:ff:ff:ff
> inet 172.18.0.1/24 scope global br-dmz
>valid_lft forever preferred_lft forever
> 6: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
> default qlen 1000
> link/ether 00:01:80:82:f8:59 brd ff:ff:ff:ff:ff:ff
> inet 192.168.10.1/24 scope global br-int
>valid_lft forever preferred_lft forever
>
>
> I created a LXC container VM1 and I would like to attach to br-int
>
> sudo lxc-create -n vm1 -t ubuntu
>
> Edit VMs config vi /var/lib/lxc/vm1/config
>
> lxc.net.0.link = br-int<- from lxcbr0
> lxc.net.0.script.up=/etc/lxc/ifup <- added
> lxc.net.0.script.down=/etc/lxc/ifdown <- added
>
> Created scripts to ifup / ifdown interface
>
> vi /etc/lxc/ifup
> #!/bin/bash
> BRIDGE=br-int
> ovs-vsctl --may-exist add-br $BRIDGE
> ovs-vsctl --if-exists del-port $BRIDGE $5
> ovs-vsctl --may-exist add-port $BRIDGE $5
>
> vi /etc/lxc/ifdown
> #!/bin/bash
> ovsBr=br-int
> ovs-vsctl --if-exists del-port ${ovsBr} $5
>
> chmod +x /etc/lxc/if*
>
> When I try to start the container using openvswitch I get the following
> error.
>
> sudo lxc-start -n vm1 --logfile log.txt
>
> lxc-start vm1 20180512072653.582 ERRORlxc_conf - conf.c:run_buffer:347
> - Script exited with status 1
> lxc-start vm1 20180512072653.610 ERRORlxc_network -
> network.c:lxc_create_network_priv:2436 - Failed to create network device
> lxc-start vm1 20180512072653.610 ERRORlxc_start -
> start.c:lxc_spawn:1545 - Failed to create the network
>
Re: [ovs-discuss] SSH over GRE tunnel, MTU 1500 devices in VMs on same physical host
So just to update this in case it helps anyone. The reason MTU 1500 was working in this setup is because the traffic wasn't going over the GRE tunnel which as Sherlock Holmes might have said "once you have eliminated the impossible, whatever remains must be the truth" which is to say it's impossible for packets of MTU 1500 to traverse a GRE tunnel, unencapsulated, no? so then it followed that the traffic wasn't using the tunnel. So I just took away the tunnel entirely and found that all the LXC containers on all the VM's on this host indeed could talk to each other ssh, etc. just fine at MTU 1500 with no GRE tunnel needed. This setup is VirtualBox VM's which are on the same OpenvSwitch network as the LXC containers, with everything on the same physical host. It was quite simple to prove to myself simply by taking away the GRE tunnel and observing that containers in different VM's on the same phyiscal host could still talk with each other just fine. I'm not a networking person originally I've just added on iptables, switches, routers as needed to support my Orabuntu-LXC work, so I must confess I still don't quite understand why the containers on the VM's on same physical host can talk at MTU 1500 without a GRE tunnel while the LXC containers in VM's or physical hosts on different physical hosts required a GRE tunnel and of course MTU 1420, but I'm looking into it. I'm sure it'll be a d'oh! revelation! On Fri, Dec 1, 2017 at 1:44 PM, Gregory Rose <gvrose8...@gmail.com> wrote: > > On 11/29/2017 12:12 PM, Orabuntu-LXC wrote: > > Hi, > > I have what is probably a dumb question so it should be an easy one for > gurus. > > I built two VM's on VirtualBox using my Orabuntu-LXC software. The VM > VNIC's are ports on OvS sw1 on each VM. The VM's are on the same physical > host. I have LXC containers on the sw1 switch also. What has surprised me > with this setup is that I can ssh between containers that are on different > VMs and all the network devices, the VNIC's and the OvS switches, and the > physical interface on the host, are all set to MTU 1500. Not anywhere in > this setup is MTU 1420 used. My understanding was, and what I have found > in all previous cases, was that I had to use MTU 1420 for ssh over a GRE > tunnel to allow for encapsulation, so my question is I am wondering how can > ssh be working over this GRE tunnel when all the MTU of all devices is set > to 1500? > > > ssh will use smaller packets for most terminal oriented applications. > Perhaps you're not exchanging traffic with larger packet sizes. > > Try iperf or something like that which will use maximum size MTUs > > - Greg > > > TIA > > -- > Gilbert Standen > Creator Orabuntu-LXC > 914-261-4594 <(914)%20261-4594> > gilb...@orabuntu-lxc.com > > > > ___ > discuss mailing > listdiscuss@openvswitch.orghttps://mail.openvswitch.org/mailman/listinfo/ovs-discuss > > > -- Gilbert Standen Creator Orabuntu-LXC 914-261-4594 gilb...@orabuntu-lxc.com ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] connecting two physical ovs to extend ports
Could you please paste in output of "ovs-vsctl show" for the switches involved? -- Gilbert Standen Creator Orabuntu-LXC 914-261-4594 gilb...@orabuntu-lxc.com ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] SSH over GRE tunnel, MTU 1500 devices in VMs on same physical host
Hi, I have what is probably a dumb question so it should be an easy one for gurus. I built two VM's on VirtualBox using my Orabuntu-LXC software. The VM VNIC's are ports on OvS sw1 on each VM. The VM's are on the same physical host. I have LXC containers on the sw1 switch also. What has surprised me with this setup is that I can ssh between containers that are on different VMs and all the network devices, the VNIC's and the OvS switches, and the physical interface on the host, are all set to MTU 1500. Not anywhere in this setup is MTU 1420 used. My understanding was, and what I have found in all previous cases, was that I had to use MTU 1420 for ssh over a GRE tunnel to allow for encapsulation, so my question is I am wondering how can ssh be working over this GRE tunnel when all the MTU of all devices is set to 1500? TIA -- Gilbert Standen Creator Orabuntu-LXC 914-261-4594 gilb...@orabuntu-lxc.com ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] connect: Network is unreachable (container-->VM-->Phys Host)
5]: zone urdomain2.com/IN: loaded serial 1610212002 Nov 23 23:43:09 olive named[185]: zone 20.172.in-addr.arpa/IN: loaded serial 1 Nov 23 23:43:09 olive named[185]: zone 127.in-addr.arpa/IN: loaded serial 1 Nov 23 23:43:09 olive named[185]: zone 21.172.in-addr.arpa/IN: loaded serial 1 Nov 23 23:43:09 olive named[185]: zone 168.192.in-addr.arpa/IN: loaded serial 1 Nov 23 23:43:09 olive named[185]: zone 24.172.in-addr.arpa/IN: loaded serial 1 Nov 23 23:43:09 olive named[185]: all zones loaded Nov 23 23:43:09 olive named[185]: running ubuntu@olive:~$ exit logout Connection to olive closed. [ubuntu@ol74a-server ~]$ nslookup ol74a-server Server:10.207.29.2 Address:10.207.29.2#53 Name:ol74a-server.urdomain1.com Address: 10.207.39.12 [ubuntu@ol74a-server ~]$ note 3: In summary, a container "olive" provides containerized DNS/DHCP services, and the VM can successfully use those DNS/DHCP services. note 4: Now I start LXC container "oel73c11" on OvS sx1 but I have no connectivity to the 10.207.29.x network. I get [root@oel73c11 /]# ping 10.207.29.2 connect: Network is unreachable When I trace packets with dhcpdump on the physical host I get nothing if only eth0 on sx1 is started in the oel73c11 container, but if set eth0 in oel73c11 container to start on the default lxcbr0 (which can reach 10.207.29.2 olive) now I get a DHCPNAK message as shown below. ubuntu@athens:~$ sudo dhcpdump -i sx1 TIME: 2017-11-23 18:02:19.534 IP: 0.0.0.0 (0:16:3e:99:78:8) > 255.255.255.255 (ff:ff:ff:ff:ff:ff) OP: 1 (BOOTPREQUEST) HTYPE: 1 (Ethernet) HLEN: 6 HOPS: 0 XID: 41de231b SECS: 0 FLAGS: 0 CIADDR: 0.0.0.0 YIADDR: 0.0.0.0 SIADDR: 0.0.0.0 GIADDR: 0.0.0.0 CHADDR: 00:16:3e:99:78:08:00:00:00:00:00:00:00:00:00:00 SNAME: . FNAME: . OPTION: 53 ( 1) DHCP message type 3 (DHCPREQUEST) OPTION: 50 ( 4) Request IP address10.42.147.244 OPTION: 12 ( 8) Host name oel73c11 OPTION: 55 ( 13) Parameter Request List 1 (Subnet mask) 28 (Broadcast address) 2 (Time offset) 121 (Classless Static Route) 15 (Domainname) 6 (DNS server) 12 (Host name) 40 (NIS domain) 41 (NIS servers) 42 (NTP servers) 26 (Interface MTU) 119 (Domain Search) 3 (Routers) --- TIME: 2017-11-23 18:02:19.534 IP: 10.207.29.2 (0:16:3e:ce:de:26) > 255.255.255.255 (ff:ff:ff:ff:ff:ff) OP: 2 (BOOTPREPLY) HTYPE: 1 (Ethernet) HLEN: 6 HOPS: 0 XID: 41de231b SECS: 0 FLAGS: 7f80 CIADDR: 0.0.0.0 YIADDR: 0.0.0.0 SIADDR: 0.0.0.0 GIADDR: 0.0.0.0 CHADDR: 00:16:3e:99:78:08:00:00:00:00:00:00:00:00:00:00 SNAME: . FNAME: . OPTION: 53 ( 1) DHCP message type 6 (DHCPNAK) OPTION: 54 ( 4) Server identifier 10.207.29.2 OPTION: 56 ( 31) Message requested address not available --- TIME: 2017-11-23 18:02:19.534 IP: 0.0.0.0 (0:16:3e:99:78:8) > 255.255.255.255 (ff:ff:ff:ff:ff:ff) OP: 1 (BOOTPREQUEST) HTYPE: 1 (Ethernet) HLEN: 6 HOPS: 0 XID: 3e62b47c SECS: 0 FLAGS: 0 CIADDR: 0.0.0.0 YIADDR: 0.0.0.0 SIADDR: 0.0.0.0 GIADDR: 0.0.0.0 CHADDR: 00:16:3e:99:78:08:00:00:00:00:00:00:00:00:00:00 SNAME: . FNAME: . OPTION: 53 ( 1) DHCP message type 1 (DHCPDISCOVER) OPTION: 12 ( 8) Host name oel73c11 OPTION: 55 ( 13) Parameter Request List 1 (Subnet mask) 28 (Broadcast address) 2 (Time offset) 121 (Classless Static Route) 15 (Domainname) 6 (DNS server) 12 (Host name) 40 (NIS domain) 41 (NIS servers) 42 (NTP servers) 26 (Interface MTU) 119 (Domain Search) 3 (Routers) --- Are there any additional settings needed to get DHCP to work from an LXC container going through a VM to the physical host where the DNS/DHCP is running? container--> sx1 on VM --> sx1 on Phys Host --> olivex port on sx1 --> olive Thanks, -- Gilbert Standen Creator Orabuntu-LXC 914-261-4594 gilb...@orabuntu-lxc.com ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
