- Apr 01, 2012
-
-
abat authored
Removing prints not through logger (https://github.com/floodlight/floodlight/pull/69)
-
Srinivasan Ramasubramanian authored
Fix a bug for checking BDDP packet if the packet is not unicast for it to continue down the processing chain.
-
Srinivasan Ramasubramanian authored
If the incoming node port is blocked, allow only unicast and BDDP packets to continue down the processing chain.
-
Srinivasan Ramasubramanian authored
-
Rob Adams authored
-
- Mar 31, 2012
-
-
abat authored
Add a method to TopologyService (https://github.com/floodlight/floodlight/pull/67)
-
abat authored
DeviceManager REST API take two (https://github.com/floodlight/floodlight/pull/68)
-
Kanzhe Jiang authored
-
Srinivasan Ramasubramanian authored
When the device manager gets cleaned up (or when during topologyChanged), it should consider the time difference between switching from broadcast to non-broadcast attachment points (as they might be previously on two different switches).
-
Alex Reimers authored
-
Alex Reimers authored
-
Alex Reimers authored
Added a DeviceManager REST API. You can use this to see what devices the controller has learned along with their IPs and attachment points. Conflicts: src/main/java/net/floodlightcontroller/devicemanager/internal/DeviceManagerImpl.java
-
Rob Adams authored
Some cleanup and bug fix in topology
-
Kanzhe Jiang authored
-
- Mar 30, 2012
-
-
abat authored
Only remove flows on move when the cookie is from forwarding (https://github.com/floodlight/floodlight/pull/65)
-
Rob Adams authored
-
abat authored
fix eclipse environment (https://github.com/floodlight/floodlight/pull/64)
-
- Mar 29, 2012
-
-
Rob Adams authored
-
Kanzhe Jiang authored
-
Srinivasan Ramasubramanian authored
Device manager should implement ITopologyListener to clear out attachment points when topology changes.
-
Srinivasan Ramasubramanian authored
(1) Device manager will drop packets (as the first step) if the topology indicates the packet-in port is not allowed for incoming transmissions. (2) Remove a log message from LinkDiscoveryManager. (3) Topology provides a service called isAllowed() that indicates if the port is enabled for incoming and outgoing traffic. (4) Tests are modified accordingly.
-
- Mar 28, 2012
-
-
abat authored
cleanup device, device ap, and device network address. (https://github.com/floodlight/floodlight/pull/63)
-
Srinivasan Ramasubramanian authored
-
Kanzhe Jiang authored
-
Kanzhe Jiang authored
-
Kanzhe Jiang authored
Conflicts: src/main/java/net/floodlightcontroller/devicemanager/internal/DeviceManagerImpl.java
-
Srinivasan Ramasubramanian authored
-
Alex Reimers authored
-
- Mar 27, 2012
-
-
abat authored
device manager attachment points on broadcast domains (https://github.com/floodlight/floodlight/pull/62)
-
Rob Adams authored
Change device manager to not allow attachment point flapping (there was a bug in the implementation before). Also, remove some crappy info log from ForwardingBase.
-
Kanzhe Jiang authored
-
- Mar 26, 2012
-
-
abat authored
Added a DeviceManager REST API. (https://github.com/floodlight/floodlight/pull/61)
-
Alex Reimers authored
Added a DeviceManager REST API. You can use this to see what devices the controller has learned along with their IPs and attachment points.
-
Kanzhe Jiang authored
-
- Mar 24, 2012
-
-
Kanzhe Jiang authored
-
abat authored
Small fixes & tweaks. (https://github.com/floodlight/floodlight/pull/59)
-
Gregor Maier authored
-
abat authored
Attachment point move suppresion when moving from non-broadcast domain port to broadcast domain port wasn't working. Fixed. (https://github.com/floodlight/floodlight/pull/58)
-
- Mar 23, 2012
-
-
Gregor Maier authored
We really don't use any feature of the class Short anyways. toString was limited to 255 ports. Fixed
-
Gregor Maier authored
-