I have found out it was not the issue with release, it is hardware specific
problem and I am investigating it more.
Thanks for your response.
On Thu, Sep 5, 2013 at 11:03 PM, Justin Pettit wrote:
> Sorry, I haven't put it up on the site yet. I'll do it in the next couple
> of hours.
>
> --Just
Sorry, I haven't put it up on the site yet. I'll do it in the next couple of
hours.
--Justin
On Sep 5, 2013, at 9:54 AM, Ben Pfaff wrote:
> We just released 1.10.2, can you try that?
>
> On Thu, Sep 05, 2013 at 09:52:36PM +0500, Junaid Rao wrote:
>> I am using OVS version 1.10.0.
>>
>>
>>
We just released 1.10.2, can you try that?
On Thu, Sep 05, 2013 at 09:52:36PM +0500, Junaid Rao wrote:
> I am using OVS version 1.10.0.
>
>
> On Thu, Sep 5, 2013 at 9:12 PM, Ben Pfaff wrote:
>
> > On Thu, Sep 05, 2013 at 08:23:22PM +0500, Junaid Rao wrote:
> > > I am running OVS in userspace m
I am using OVS version 1.10.0.
On Thu, Sep 5, 2013 at 9:12 PM, Ben Pfaff wrote:
> On Thu, Sep 05, 2013 at 08:23:22PM +0500, Junaid Rao wrote:
> > I am running OVS in userspace mode and I am using the following script to
> > start it:*
>
> I don't think you mentioned what OVS version you are usi
On Thu, Sep 05, 2013 at 08:23:22PM +0500, Junaid Rao wrote:
> I am running OVS in userspace mode and I am using the following script to
> start it:*
I don't think you mentioned what OVS version you are using. What
version is it?
___
dev mailing list
dev
Hello,*
*
I am running OVS in userspace mode and I am using the following script to
start it:*
*
ovsdb-tool create /usr/etc/openvswitch/conf.db vswitchd/vswitch.ovsschema
ovsdb-server /usr/etc/openvswitch/conf.db
--remote=punix:/usr/var/run/openvswitch/db.sock \
--remote=db:
