It looks like vnet0 and vnet2 don't exist, so OVS can't attach them.
--Justin
> On Dec 26, 2013, at 8:43 AM, Echedey Lorenzo wrote:
>
> Hi all,
>
> I've been working with Openvswitch for a while now. I hope this is the right
> place to show the problem I'm having after a reboot. I'm using O
On Thu, Dec 26, 2013 at 6:43 AM, Echedey Lorenzo wrote:
> Hi all,
>
> I've been working with Openvswitch for a while now. I hope this is the right
> place to show the problem I'm having after a reboot. I'm using Openvswitch
> 1.9.3 on SLES 11 SP3 and sometimes it does not work while apparently it
Yes, your understanding is correct.
--Justin
> On Dec 26, 2013, at 9:37 AM, kevin parker wrote:
>
> Hi i am trying to understand this better
>
> from 192.168.3.3
>
> ping 192.168.3.4 -c 10
>
> 10 packets transmitted, 10 received, 0% packet loss, time 9003ms
>
> ovs-dpctl dump-flows
>
>
Hi i am trying to understand this better
from 192.168.3.3
ping 192.168.3.4 -c *10*
*10* packets transmitted, 10 received, 0% packet loss, time 9003ms
ovs-dpctl dump-flows
in_port(3),eth(src=52:b9:12:5f:87:b1,dst=ea:91:10:fc:7a:bf),eth_type(0x0800),ipv4(src=192.168.3.4,dst=192.168.3.3,proto=1,t
Hi all,
I've been working with Openvswitch for a while now. I hope this is the
right place to show the problem I'm having after a reboot. I'm using
Openvswitch 1.9.3 on SLES 11 SP3 and sometimes it does not work while
apparently it is up&running properly.
I see in /var/log/messages that there was