On Fri, May 23, 2014 at 05:14:35PM -0400, Lars Kellogg-Stedman wrote:
> This patch adds support for RHEL-derived systems (RHEL/CentOS/Fedora)
> for setting the persistent MAC address of an OVS bridge via the MACADDR
> setting in the interface configuration file.
>
> Without this change, when an ad
This patch adds support for RHEL-derived systems (RHEL/CentOS/Fedora)
for setting the persistent MAC address of an OVS bridge via the MACADDR
setting in the interface configuration file.
Without this change, when an administrator provides MACADDR in the
interface configuration file that address wi
On Fri, May 23, 2014 at 05:22:18PM -0400, Lars Kellogg-Stedman wrote:
> This patch adds support for setting the persistent MAC address (on
> RHEL-derived systems) of an OVS bridge via the MACADDR setting in the
> interface configuration file.
>
> Without this change, when an administrator provides
On Fri, May 23, 2014 at 05:23:40PM -0400, Lars Kellogg-Stedman wrote:
> On Fri, May 23, 2014 at 01:15:47PM -0700, Ben Pfaff wrote:
> > How is OVS supposed to tell that you modified it and that the value
> > you gave it should stick?
>
> I am assuming that OVS receives some sort of notification via
On Fri, May 23, 2014 at 01:15:47PM -0700, Ben Pfaff wrote:
> How is OVS supposed to tell that you modified it and that the value
> you gave it should stick?
I am assuming that OVS receives some sort of notification via the
kernel when the MAC address is updated via 'ip link'. Am I wrong?
This is
This patch adds support for setting the persistent MAC address (on
RHEL-derived systems) of an OVS bridge via the MACADDR setting in the
interface configuration file.
Without this change, when an administrator provides MACADDR in the
interface configuration file that address will be set in ifup-et
On Fri, May 23, 2014 at 02:54:45PM -0400, Lars Kellogg-Stedman wrote:
> On Fri, May 23, 2014 at 11:30:46AM -0700, Ben Pfaff wrote:
> > > ip link set br-ex addr $MACADDR
> >
> > Yeah, generally the MAC address of the bridge is derived from the MAC
> > addresses of the ports on the bridge.
>
>
On 05/23/2014 10:46 PM, Filipe Antonio wrote:
> Hi,
>
> Thank you for the reply.
> When you ask "Did you set OpenFlow version compatibility level for the
> bridge?", is about the line *ovs-vsctl set bridge br0
> protocols=OpenFlow10,OpenFlow11,OpenFlow12,OpenFlow1**3*, I run that command
> befo
On Fri, May 23, 2014 at 11:30:46AM -0700, Ben Pfaff wrote:
> > ip link set br-ex addr $MACADDR
>
> Yeah, generally the MAC address of the bridge is derived from the MAC
> addresses of the ports on the bridge.
Well, that I expect.
What is surprising is that setting it explicitly with the "ip"
Hi,
Thank you for the reply.
When you ask "Did you set OpenFlow version compatibility level for the
bridge?", is about the line*ovs-vsctl set bridge br0
protocols=OpenFlow10,OpenFlow11,OpenFlow12,OpenFlow1**3*, I run that command before
connect the openvswitch to the controller.
Regards,
Fili
On Fri, May 23, 2014 at 02:25:44PM -0400, Lars Kellogg-Stedman wrote:
> > What is causing the MAC address to change? How can I get it to stick?
>
> The answer here appears to be "don't set OVS bridge MAC addresses
> using your normal system tools". While this fails as described...
>
> ip li
> What is causing the MAC address to change? How can I get it to stick?
The answer here appears to be "don't set OVS bridge MAC addresses
using your normal system tools". While this fails as described...
ip link set br-ex addr $MACADDR
This seems to stick:
ovs-vsctl set bridge br-ex o
On 05/22/2014 03:39 PM, Filipe Antonio wrote:
> Hi,
>
> I connect a openvswitch (ovs_version: "2.1.90") to a Opendaylight
> Controller. The Controller recognize the switch, but the switch doesn´t
> accept flows from Controller. It seems the connection is temporarely lost.
>
> The output of ovs-v
On Thu, May 22, 2014 at 5:02 PM, Madhu Challa wrote:
> I am looking at adding support for On-demand flow counters and figured one
> of the benefits of doing this is reduced lock contention in
> ovs_flow_stats_update.
>
> If my understanding is correct, this involves processing flags
> OFPFF13_NO_P
On Fri, May 23, 2014 at 5:15 AM, Anand Nande wrote:
> Hi,
>
> was wondering if OVS supports reflective relay when used along with
> macvtap/vepa-mode ?
You could do it by writing flows.
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch
Hi,
was wondering if OVS supports reflective relay when used along with
macvtap/vepa-mode ?
--Anand
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
Quoting Ben Pfaff :
On Thu, May 22, 2014 at 02:04:07PM +0300, Zoi VASILIOU wrote:
I am trying to compile ovs-dpctl for arm architecture.
However the following error is showing:
Compile with this command:
arm-eabi-gcc -c -I. -I../include/
-I/home/zoi/android-ndk-r5b/platforms/android-8/arch-a
Hi Jesse,
I need to play around with ovs source code, please give me some pointers or
share some doc regarding same.
I want to know when I compile the ovs source code, exe will be generated in
which folder? I want to attach the gdb with ovs exe, please suggest me so that
I will kick start it.
On Fri, May 23, 2014 at 04:17:42PM +0500, Asadullah Hussain wrote:
> Hello, Is it possible to run multiple vswitchd instances on the same system?
>
> I know that multiple openvswitch instances can be connected to a single
> vswitchd process but I want to run two openvswitch`s each having its own
On Fri, May 23, 2014 at 12:46:20PM +0300, Zoi VASILIOU wrote:
>
> Quoting Ben Pfaff :
>
> >On Thu, May 22, 2014 at 02:04:07PM +0300, Zoi VASILIOU wrote:
> >>I am trying to compile ovs-dpctl for arm architecture.
> >>However the following error is showing:
> >>
> >>Compile with this command:
> >>
On Fri, May 23, 2014 at 11:36:17AM +0200, Dani Camps wrote:
> We are trying to have ofproto.c calling a function defined in another
> kernel module. For that we do EXPORT_SYMBOL() in the other module, and
> include the corresponding header file in ofproto.c.
This doesn't make any sense. You can't
Hello, Is it possible to run multiple vswitchd instances on the same system?
I know that multiple openvswitch instances can be connected to a single
vswitchd process but I want to run two openvswitch`s each having its own
vswitchd instance.
I have a modified vswitchd process which I want to run
Dear all,
We are trying to have ofproto.c calling a function defined in another
kernel module. For that we do EXPORT_SYMBOL() in the other module, and
include the corresponding header file in ofproto.c.
The problem we have is that we get compilation errors in ofproto.c because
it can not locate t
I knew DHCP request from VM is not sent out of the host but I don't know
how to identify the root cause. as shown in my earliest log I can just find
the packet is output to the vxlan port
cookie=0x0, duration=2294.917s, table=0, n_packets=9, n_bytes=1434,
send_flow_rem in_port=2,dl_src=fa:16:3e:d
24 matches
Mail list logo
