On Wed, Oct 30, 2013 at 2:46 AM, ashish yadav wrote:
> Hi,
>
> I have not tested Vlan with Openvswitch_mod.ko (provide by kmod-openvswitch
> rpm (1.4.6 OVS)), so can't comment.
>
> I think Openvswitch_mod.ko (OVS distribution 1.4.6) contain code related
> with vlan ( datapath/vlan.c & vlan.h).
> B
Hi,
I have not tested Vlan with Openvswitch_mod.ko (provide by kmod-openvswitch
rpm (1.4.6 OVS)), so can't comment.
I think Openvswitch_mod.ko (OVS distribution 1.4.6) contain code related
with vlan ( datapath/vlan.c & vlan.h).
But same is not true with Openvswitch.ko (upstream kernel module), no
Hi Ashish/Jesse,
I have one Query here:
Environment: CentOS6.3/6.4 Kernel 2.6.32-358.18.1
Using Openvswitch_mod.ko (provide by kmod-openvswitch rpm (1.4.6 OVS)) ,
Vlan work fine with OVS.
But when using Openvswitch.ko (provide by upstream kernel
2.6.32-358.18.1), Vlan not work with OVS.
Hi Jesse,
Thanks for info .
With Regards
Ashish
On Tue, Oct 29, 2013 at 2:36 AM, Jesse Gross wrote:
> On Fri, Oct 25, 2013 at 7:48 PM, ashish yadav
> wrote:
> > Hi Jesse,
> >
> > I think 2.6.32-358.18.1 Kernel version is latest with RHEL/Centos.
> > So it has almost all patches from ups
On Fri, Oct 25, 2013 at 7:48 PM, ashish yadav wrote:
> Hi Jesse,
>
> I think 2.6.32-358.18.1 Kernel version is latest with RHEL/Centos.
> So it has almost all patches from upstream...
It doesn't have anywhere near all of the patches from the most recent
version of Linux.
> If anyone has really t
Hi Jesse/Ben,
Any Pointer here
Regards
Ashish
On Sat, Oct 26, 2013 at 8:18 AM, ashish yadav wrote:
> Hi Jesse,
>
> I think 2.6.32-358.18.1 Kernel version is latest with RHEL/Centos.
> So it has almost all patches from upstream...
>
> If anyone has really try Vlan with upstream OVS kernel
See the mac table first . Do you find an entry for .198 there ? I think you
won't until you add eth0 to port.
> On 25-Oct-2013, at 12:08 pm, ashish yadav wrote:
>
> Hi,
>
> I am using CentOS 6.3 (2.6.32-358.181.1 Kernel) & OVS 1.4.6 on two host
> Machine.
> I used upstream OVS kernel module
Hi Jesse,
I think 2.6.32-358.18.1 Kernel version is latest with RHEL/Centos.
So it has almost all patches from upstream...
If anyone has really try Vlan with upstream OVS kernel module
(openvswitch.ko) ?
If Vlan not works then its really serious problem with upstream OVS in
Linux Kernel.
Thanks
On Fri, Oct 25, 2013 at 9:43 AM, ashish yadav wrote:
> Hi Jesse,
>
> With Kernel Version 2.6.32-358.18.1, CentOS6.3/6.4 has upstream OVS kernel
> module.
Old kernels have known problems with vlans, so you might have to use
the vlan splinters feature as a work around.
_
Hi Jesse,
With Kernel Version 2.6.32-358.18.1, CentOS6.3/6.4 has upstream OVS kernel
module.
Please the attach logs of my previous mail.
Also see the attach lsmod log for host in this mail (you can see
openvswitch module in it).
Thanks & Regards
Ashish
On Fri, Oct 25, 2013 at 10:04 PM, Je
On Thu, Oct 24, 2013 at 11:38 PM, ashish yadav wrote:
> Hi,
>
> I am using CentOS 6.3 (2.6.32-358.181.1 Kernel) & OVS 1.4.6 on two host
> Machine.
> I used upstream OVS kernel module (openvswitch.ko) rather than
> openvswitch_mod.ko module provided by kmod-openvswitch rpm.
If I recall correctly,
Hi,
Please find the attach logs (Environment & Results) for both Machine.
Thanks & Regards
Ashish
On Fri, Oct 25, 2013 at 12:08 PM, ashish yadav wrote:
> Hi,
>
> I am using CentOS 6.3 (2.6.32-358.181.1 Kernel) & OVS 1.4.6 on two host
> Machine.
> I used upstream OVS kernel module (openvs
Hi,
I am using CentOS 6.3 (2.6.32-358.181.1 Kernel) & OVS 1.4.6 on two host
Machine.
I used upstream OVS kernel module (openvswitch.ko) rather than
openvswitch_mod.ko module provided by kmod-openvswitch rpm.
Both Server have Same Configuration.
Host1:
a. ovs-vsctl show :
aaf010
On Thu, Jan 24, 2013 at 07:21:22PM +0100, Julius Bachnick wrote:
> I just set up three OVS (s1, s2, s3) with two interfaces (eth1+eth2) each
> and set their VLANS during runtime using
>
>
> ovs-vsctl set port tag= for access and
>
> self.cmd('ovs-vsctl set port trunks= for trunk.
>
> My Setup
Hey all,
I just set up three OVS (s1, s2, s3) with two interfaces (eth1+eth2) each
and set their VLANS during runtime using
ovs-vsctl set port tag= for access and
self.cmd('ovs-vsctl set port trunks= for trunk.
My Setup is as
S1 (eth1) (eth1) S2 (eth2) --- (eth1) S3
but when I ping f
15 matches
Mail list logo