Skip to content
Snippets Groups Projects

Repository graph

You can move around the graph by using the arrow keys.
Select Git revision
  • gh-pages
  • hot-failover
  • master default protected
  • master-green
  • master-prejava8
  • perf-test
  • release.asplus
  • release.asplus.bvs
  • revert-555-master
  • revert-559-revert-555-master
  • revert-594-master
  • v0.8
  • v0.82
  • v0.85
  • v0.90
  • v0.91
  • v1.0
  • v1.1
  • v1.2
  • wallaby
  • v1.2
  • v0.91
  • v1.1
  • v1.0
  • v0.90
  • v0.85
  • v0.82
  • v0.8
  • asplus-rc5
  • asplus-rc2
30 results
Created with Raphaël 2.2.017Apr16138327Mar262019171615141312109327Feb20165420Jan1230Dec2925232221191817161512121Nov2018141310753131Oct3027261024Sep1615141129Aug27211917161514131211108765431Jul302818Jun21Apr20625Mar754228Feb1Mar30Dec205Nov30Oct17Sep756Aug222Jul1728Jun26252423222120191817141312111076543231May3029282726252423222120191817161514131211109876532130Apr29282726252322211918Update readmeMerge pull request #522 from rizard/masterFinally got around to fixing LearningSwitch.Merge pull request #519 from rizard/masterFixed issue where multipart flow replies would only show the last part/reply and not print the others. Only a REST API issue. This will also fix the Web UI where people reported not seeing all their flows.Merge pull request #521 from puneet2singh/patch-2Update OFVendorStatistics.javaModified slightly to track the specific initial state. If we were slave first, then we won't clear the flow table if we go to master for the first time.Added ability to customize start/role-transition behavior at the request of an individual a while ago. Using floodlightdefault.properties, you can specify if you want the controller to clear the flow tables of switches (1) upon inital handshake and transition to master or (2) upon every transition to master. Or you can not ever clear the tables if you want.Fix Firewall bug with getting in_port from Match vs from PI.Added ability to switch OF roles per DPID or for all switches at once. This includes a REST interface and integration with the handshake and channel handlers in order to keep the switch in the correct state. An IOFConnectionListener also has the ability to listen for messages that are written now instead of read from the wire. This allows modules to write role requests, have the underlying handshake/channel substrate tap in and listen to the request, and automatically update the role of the switch when the response comes back.fix typo in commentMerge pull request #518 from rizard/mastermerge conflict fixManually pulling in commit #517.Fixed OFChannelHandler to always allow echo requests and replies no matter the state in the handshake process. This issue was discovered during an unsuccessful handshake with an HP 5900af, which for whatever reason wants to handshake as follows: ... (1) FL features request, (2) HP echo request, (3) FL echo reply, (4) HP features reply. There are still issues with this switch after the handshake completes, but an echo should be honored in any state.Merge pull request #511 from deepurple/masterAdd DHCPServer module to the list of possible modules to load.Fixed fetching of ingress port to work with OF1.0 and 1.2+. This is the final commit for the DHCP server. Will add some unit tests in a later and near-future commit as practice/exercise for me =)Initial DHCP server code commit. This was a test of how easy is is to port v0.91- code to v1.0. I have not tested this module yet. TODO: Write unit tests for the dhcpserver module.Fix comment typo. Make shallow compare like my comment intended it to be...Reapplied the LinkDiscoveryManager's patch from earlier (issue #471). Updated Ethernet.java to use EthType instead of short for EthTypes. In conjunction, bitmasked the LSBs of the ethertype as it is casted from short to int. This preserves the MSB (sign) as a data bit --> unsigned integer.Correct the spelling errorForwarding's doDropFlow() changed to not base Match on OFPacketIn, which it shouldn't in the first place. We need to first deserialize the packet and use its header attributes. TODO: How much is too much to match on? Sometimes we want a very specific match by default. Other times, we don't. The former creates a larger flow table, while the latter might inadvertently match packets that we don't intend to. Perhaps this should be a user-configurable option? Such as net.floodlightcontroller.Forwarding.matchLayer=L2, L3, or L4?Undo LinkDiscoveryManager 'bug' fix from a while back. We'll test to see if it's what's causing some issues with invalid ethertypes. Also, includes a patch for OFChannelHandler that will accept the smallest of the OpenFlow versions during the initial handshake.Merge pull request #500 from Pengfei-Lu/masterupdate copyright informationadd copyright information and remove useless filesMerge pull request #504 from rizard/v1.0update properties file to add the new ACL applicationadd new ACL application and test codeUpdated Restlet from 2.2M3 to 2.3.1. Included with the update is full SSL support for the REST API, either all-access+encryption or restricted-access+encryption (truststore verified clients only). Additional options have been added to floodlightdefault.properties in order to turn HTTPS on/off. HTTPS ccan be used in conjunction with vanilla HTTP as well -- each must reside on a different TCP port though. Also, this time, I remembered to update and test the build.xml file to remove the old and include the new Restlet jars.Merge pull request #503 from rizard/v1.0Oops. Update build.xml with new Netty 3.10.0 jar file name.Merge pull request #502 from rizard/v1.0Tidied up some import warnings and unused variables from recently-pulled Firewall REST API changes.Merge branch 'master' of http://github.com/floodlight/floodlight into v1.0Merge pull request #485 from electricjay/masterBug fix WRT closed issue #471. ethertype range check for valid LLC lengths expanded to include 17-1535 inclusive and <17 as invalid.Merge pull request #501 from rizard/v1.0