Skip to content
Snippets Groups Projects
  1. Sep 13, 2016
  2. Aug 19, 2016
  3. Aug 16, 2016
  4. Aug 12, 2016
  5. Aug 08, 2016
  6. Aug 05, 2016
  7. Jul 30, 2016
  8. Jul 24, 2016
  9. Jul 18, 2016
  10. Jul 15, 2016
  11. Jul 14, 2016
  12. Jul 13, 2016
  13. Jul 12, 2016
    • rsharo's avatar
      General code cleanup. · cef10a52
      rsharo authored
      * Eliminated (new) warnings
      * Fixed indentation
      * Removed excess blank lines
      * Improved some varable names
      * Removed (unneeded) commented-out code
      * Fixed up comments
      * Added @Override annotations
      cef10a52
  14. Jul 11, 2016
    • rsharo's avatar
      Unit test cleanup and bugfix. · e17f923a
      rsharo authored
      ForwardingTest.testForwardDeleteFlowsByDescriptorMultiple() passed in Eclipse, but failed when run by "ant test".
      Changed Forwarding.deleteFlowsByDescriptor() to use List<> instead of Set<> to simplify the unit test.
      Tests now pass in every configuration I'm able to run them (eclipse single test, eclipse test class, eclipse all tests, ant all tests).
      
      Also general code and comment cleanup.
      e17f923a
  15. Jul 06, 2016
  16. Jul 04, 2016
  17. Jul 01, 2016
  18. Jun 30, 2016
  19. Jun 29, 2016
    • brobertson3's avatar
      Most of the changes for the Firewall to update the flowtables on switches · ce9f6813
      brobertson3 authored
      Updated Firewall.java so that addRule and deleteRule and enableFirewall announce that a rule is being changed in the firewall. Then the IRoutingDecisionChangedListener shall alert Forwarding to update the flowtable accordingly.  None of this is tested and the TopologyManager needs to be fixed.  I might even want to move the change out of TopologyManager altogether since RoutingDecisionChange doesn't concern it.
      ce9f6813
  20. Jun 21, 2016
  21. Jun 20, 2016
  22. May 31, 2016
  23. May 18, 2016
  24. May 10, 2016
    • Randy Sharo's avatar
      Initial design work on flow-deletes triggered by changes in firewall rules. · f6686b38
      Randy Sharo authored
      TODO:
         * RoutingDecisionsChanged event
            * Define Listener class
            * Add Listener registration/messaging (probably going into IRoutingService)
            * Add code to fire event when firewall rules change.
            * Add code to fire event when firewall enable/disable happens.
            * Add code to handle RoutingDecisionsChanged in Forwarding
         * Unit tests
         * Functional tests
      f6686b38
  25. Apr 29, 2016
  26. Apr 28, 2016
    • Ryan Izard's avatar
      Handle link and port down events in Forwarding. Remove flows ingress and... · 13c6e012
      Ryan Izard authored
      Handle link and port down events in Forwarding. Remove flows ingress and egress a failed port or link to eliminate stale entries. This is done in Forwarding instead of the Link Discovery Manager, since some user modules might not want their flows removed and wish for them to persist until the link comes back up.
      13c6e012
  27. Apr 26, 2016
  28. Apr 06, 2016
  29. Jan 21, 2016
  30. Jan 10, 2016
  31. Dec 04, 2015
  32. Oct 12, 2015
  33. Oct 08, 2015
  34. Oct 07, 2015
    • Ryan Izard's avatar
      Added ability to disable ARP flows in Forwarding. Many hardware switches... · 2e5d773a
      Ryan Izard authored
      Added ability to disable ARP flows in Forwarding. Many hardware switches cannot handle ARP flows. ARP flows on by default; turn off/on via 'flood-arp' in floodlightdefault.properties. Also, finished integrating new topology service/routing into Forwarding. This required a few more null checks to handle cases where packet-ins are received while the controller is starting/still discovering the topology/links.
      2e5d773a
Loading