On Wed, Jun 15, 2011 at 01:47:34PM -0700, Peter Phaal wrote:
> How about this for the second diagram?
[...]
> In case formatting doesn't come through clearly, the diagram includes
> a bracket on the right to indicate that the ofproto-dpif, dpif,
> dpif-provider and datapath together form an impleme
On Wed, Jun 15, 2011 at 1:15 PM, Ben Pfaff wrote:
> On Tue, Jun 14, 2011 at 08:03:38AM -0700, Peter Phaal wrote:
>> The porting guide shows an "ofproto provider" block in the first diagram,
>> which I take to be the ofproto plugin? This block is dropped in the second
>> diagram.
>
> The block la
On Tue, Jun 14, 2011 at 08:03:38AM -0700, Peter Phaal wrote:
> The porting guide shows an "ofproto provider" block in the first diagram,
> which I take to be the ofproto plugin? This block is dropped in the second
> diagram.
The block labeled ofproto-dpif in the second diagram is an example of
On Mon, Jun 13, 2011 at 11:51:36PM -0700, Justin Pettit wrote:
> (By the way, one thing that may have added to the confusion is that
> the "ofproto-sflow.[ch]" files should really be named
> "dpif-sflow.[ch]". This is a vestige of the reorganizing that
> happened in the process of getting this har
Works perfectly! Thank you!
Dieter
On 15.06.2011 08:52, Justin Pettit wrote:
Something like this should do the trick:
ovs-vsctl set bridge br0 other-config:hwaddr=00:11:22:33:44:55
Obviously, replacing "br0" with the name of your bridge and using the
appropriate MAC address.
--Justi
