Musings

I have been buried in stuff to work on lately.  The amazing part of this is that it is all very interesting and things I want to do and learn.  The exhausting part is that there is an overwhelming amount of it.  It is a good problem to have. The list of things goes on and on (and obviously I don’t do all of this stuff by myself, we have an amazing team) but the short list is a pretty tall order.  I need to really learn MPLS and deploy a decent sized MPLS network over the span of a state.…

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

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.  MicroFlow policing…

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. This is not a…