Hi Murphy, here is another patch. This one fixes a bug where FeaturesReceived was raised by connection itself but the event did not went through. (see lines 245-246 of of_01.py). Actually, POX should log an error/warning if you try to raise an event which is not published by your class. I do not have a patch for that but it looks to me that the necessary changes are: - in revent/revent.py, raiseEvent function, replace raise RuntimeError with some new special error, call it EventNotFoundError() - in revent/revent.py raiseEventNoError function should not ignore EventNotFoundError but log an error in this case (and proceed silently otherwise)
Peter >From af28225d5dbe25b443dd3f86bb23c7460846ad74 Mon Sep 17 00:00:00 2001 From: Peter Peresini <[email protected]> Date: Wed, 4 Jun 2014 09:44:17 +0200 Subject: [PATCH] Connection is raising FeaturesReceived event but it was not in event mixin. --- pox/openflow/of_01.py | 1 + 1 file changed, 1 insertion(+) diff --git a/pox/openflow/of_01.py b/pox/openflow/of_01.py index e21663a..12a3a36 100644 --- a/pox/openflow/of_01.py +++ b/pox/openflow/of_01.py @@ -691,6 +691,7 @@ class Connection (EventMixin): PortStatsReceived, QueueStatsReceived, FlowRemoved, + FeaturesReceived, ]) # Globally unique identifier for the Connection instance -- 1.8.3.2
