Hi,
So here is the setup I've with Openvswitch 1.1.0 release running with brcompat
module. It is all running on a single physical machine.
Xen VM (a - 10.19.128.34) --- vif 1.0 -- (pibr102 - bridge) -- vif 2.0 --- Xen
VM (b - 10.19.128.36)
[root@vm-container-0-1 ~]# ovs-dpctl show pibr10
On Wed, Jun 08, 2011 at 11:28:00AM +0100, nauman.lagh...@bt.com wrote:
> Also added a couple of flows for attaching to the queue
>
>
>
> [root@vm-container-0-1 ~]# ovs-ofctl add-flow pibr102 'priority=65535,
> idle_timeout=5, dl_type=0x800, in_port=ANY, nw_src=ANY,
> nw_dst=10.19.128.34, a
Hi,
Just wanted to bring this up to archive the issue for consideration
later and as a cautionary note to those dealing with ARP using
OpenFlow. The specific issue pertains to clarity and consistency of
the OpenFlow specs.
In OpenFlow (up till v1.1), we allow IP addresses in ARP to be match
usin
Hello,
Am trying to understand the details about what/when messages are exchanged
between AP's and controller that creates the smooth hand off. Specifically,
how SNMP contributed in improving the hand off in OpenRoads?
I'll Appreciate it, if you could guide me to a paper/wiki-page that explain
Hi Landy,
As explained (probably deep in the details), some configuration and event
are triggered using SNMP.
For example, for a switch to know of a client in OpenFlow, we have to look
at packet-in from the client. This can take a while, esp. for clients that
does not perform DHCP upon associati
