OVS can't really influence whether a VM sends a reply.
On Tue, Oct 18, 2016 at 12:02:16PM -0700, Tom Gajewski wrote:
> More strangeness: when pinging from within VM behind port 13 I observe
> even the reply coming back into VM yet ping reports no reply 100%
> loss. This is with dl_dst:so:me:ma:cc
More strangeness: when pinging from within VM behind port 13 I observe
even the reply coming back into VM yet ping reports no reply 100%
loss. This is with dl_dst:so:me:ma:cc flow. Why would that flow cause
that, how is that even possible if I'm seeing ICMP replies inside VM?
Again, all works fine
That's the requirement, that's why I started this topic. I've
demonstrated that port 13 works perfectly fine with no-flood as long
as the mac-table of openvswitch is populated with its MAC, I still
don't understand why we can't adding a static entry here, seems silly.
But I've pretty much accomplis
On Tue, Oct 18, 2016 at 10:51:33AM -0700, Tom Gajewski wrote:
> Yes of course I've opened up the switch again after flushing ;]
> Basically I have:
>
> cookie=0x0, duration=61132.153s, table=0, n_packets=112313104,
> n_bytes=18199375313, idle_age=0, priority=0 actions=NORMAL
> cookie=0x0, durati
Yes of course I've opened up the switch again after flushing ;]
Basically I have:
cookie=0x0, duration=61132.153s, table=0, n_packets=112313104,
n_bytes=18199375313, idle_age=0, priority=0 actions=NORMAL
cookie=0x0, duration=61107.945s, table=0, n_packets=7122,
n_bytes=467057, idle_age=1576, dl_
> On Oct 18, 2016, at 2:38 AM, Tom Gajewski wrote:
>
> Ben, you had asked about my flow table. I've tried this with a
> completely clear table and not -- same behavior. There has to be some
> logic I'm missing here. Back story is that I'm trying to compensate
> for the inability to populate loca
Ben, you had asked about my flow table. I've tried this with a
completely clear table and not -- same behavior. There has to be some
logic I'm missing here. Back story is that I'm trying to compensate
for the inability to populate local mac-table with this flow as I want
to run ports in 'no-flood'
There has to be something inherently wrong with that flow since once I
enter it, the machine behind port 13 cannot get out anywhere -- and no
traffic can reach it, even once there is an actual entry in the
mac-table. So I'm effectively breaking all traffic to port 13 and MAC
so:me:ma:cc. Can someon
I would generally expect that to work.
Maybe you should show us more of your flow table.
On Mon, Oct 17, 2016 at 10:14:16AM -0700, Tom Gajewski wrote:
> My bad, that was obviously suppose to include the MAC in question. So
> one more time, in an attempt to set a static MAC table entry:
>
> Table
My bad, that was obviously suppose to include the MAC in question. So
one more time, in an attempt to set a static MAC table entry:
Table entry:
13 744 so:me:ma:cc
Flow:
ovs-ofctl add-flow mybridge dl_dst=so:me:ma:cc,actions=output:13
I guess what I'm asking is, what should a static flow th
On Mon, Oct 17, 2016 at 02:45:06AM -0700, Tom Gajewski wrote:
> Hi all,
>
> It is my understanding that one cannot modify the cam (well I guess in
> openvswitch land the mac table ;] ) directly. As I'm trying to set up
> static entries. Do I need to use flows to accomplish this, is there no
> othe
Hi all,
It is my understanding that one cannot modify the cam (well I guess in
openvswitch land the mac table ;] ) directly. As I'm trying to set up
static entries. Do I need to use flows to accomplish this, is there no
other way to just modify this table??
As for flows, I did try to add some cop
12 matches
Mail list logo
