curl http://localhost:8080/wm/firewall/module/enable/json `````` curl http://localhost:8080/wm/firewall/module/status/json Add allow rule: curl -X POST -d '{"[00:00:00:12:f2:91:58:00](http://128.174.43.242:8080/switch/00:00:00:12:f2:91:58:00)": "00:00:00:00:00:00:00:01"}' http://localhost:8080/wm/firewall/rules/json http://docs.projectfloodlight.org/display/floodlightcontroller/Firewall+%28Dev%29

curl http://localhost:8080/wm/firewall/module/enable/json `````` curl http://localhost:8080/wm/firewall/module/status/json Add allow rule: curl -X POST -d '{"[00:00:00:12:f2:91:58:00](http://128.174.43.242:8080/switch/00:00:00:12:f2:91:58:00)": "00:00:00:00:00:00:00:01"}' http://localhost:8080/wm/firewall/rules/json `````` http://docs.projectfloodlight.org/display/floodlightcontroller/Firewall+%28Dev%29

http://ethancbanks.com/2014/03/15/my-home-lab-esxi-5-5-server-build-and-the-logic-behind-it-all/

Some people have a need to push hardware to it’s limits. Generally, I end up being one of those people. I must admit, I enjoy seeing how far things can be pushed, especially when it yields new and or interesting gains or knowledge. One of the things that I needed to do was to rate limit a large set of addresses, but to allow unfettered access to other resources. It’s possible there may be a better way to do this, but all of my other attempts to do this failed.

The Border Gateway Protocol (BGPv4) is the foundation of the modern internet. Without it we would still be in the information dark ages and interconnectivity as we know it would not exist. One would assume, quite incorrectly I might add, that this foundational protocol is robust, secure and optimally configured to shepherd us through the daily use of this critical resource. While BGP has the capability of being all of those things, in practice it’s really not done that way.

Are you indexing your flow data? You should be. My new favorite flow collector isn’t even a flow collector. It’s two of the three parts of an ELK stack.

Much less noise. That was my initial thought when this box was first powered. The 4500 sounds like a jet engine. I was particularly excited about the Juniper EX4550 because it addressed a number of things that were less than ideal about the EX4500. Soem of the differences ciuyld be argued as either oa pro or con depending on deployment scanerio, but for what we’re looking for, the 4550 is far better.