I finally figured it out.
FAUCET sets ofp_switch_config.miss_send_len = 0 when the switch connects.
We do this because we don't want any packets coming to the controller, if
there is no matching flow in a table. We program a priority 0, actions=drop
flow in all tables as well, to really hammer the
If you can try to narrow it down further, that's helpful. If you don't
have any luck with that, let me know and I'll see if I can figure
anything out.
On Thu, May 17, 2018 at 05:26:54PM +1200, Josh Bailey wrote:
> I apologize, I dropped the ball. I'll go take another look at this. I had a
> go at
I apologize, I dropped the ball. I'll go take another look at this. I had a
go at reproducing it (with just a single table) and failed - the packet in
is sent.
It's only not sent, when FAUCET has put other flows in other tables and the
problem priority 0 rule is in table 2. I have some work to do
On Tue, Mar 06, 2018 at 11:20:40AM -0800, Ben Pfaff wrote:
> On Tue, Mar 06, 2018 at 06:54:30AM +, Josh Bailey via discuss wrote:
> > Hoping I'm missing something obvious!
> >
> > I have a flow like this:
> >
> > $ grep CONTROLLER sab-dump-flows.log
> > cookie=0x5adc15c0, duration=63.446s, t
On Tue, Mar 06, 2018 at 06:54:30AM +, Josh Bailey via discuss wrote:
> Hoping I'm missing something obvious!
>
> I have a flow like this:
>
> $ grep CONTROLLER sab-dump-flows.log
> cookie=0x5adc15c0, duration=63.446s, table=3, n_packets=60, n_bytes=3436,
> priority=0 actions=CONTROLLER:96
>
Hello,
Hoping I'm missing something obvious!
I have a flow like this:
$ grep CONTROLLER sab-dump-flows.log
cookie=0x5adc15c0, duration=63.446s, table=3, n_packets=60, n_bytes=3436,
priority=0 actions=CONTROLLER:96
I can cause packets to match it, but no packets are output ot the
controller.
f