That’s right, it’s time for another surveillance-free, EFF-approved episode of Healthy Paranoia! Where the passwords are salted and the packets are always encrypted. This episode is hosted by the infamous Mrs. Y, queen of metadata and official privacy advocate for Healthy Paranoia, and recorded in the NSA-proofed SCIF with Grecs, of Novainfosec.com and Shmoocon Firetalks. […]
The post Healthy Paranoia Show 21: Windows Forensics with Andrew Case appeared first on Packet Pushers Podcast and was written by Mrs. Y.
While setting up my OpenDaylight OVSDB and Devstack following the awesome instructions from Kyle Mestery, I thought it would be fun to run the latest OVS from source on my compute nodes...
While setting up my OpenDaylight OVSDB and Devstack following the awesome instructions from Kyle Mestery, I thought it would be fun to run the latest OVS from source on my compute nodes...
To do this, execute the following commands on one of your compute nodes
before running stack.sh
sudo apt-get -y --force-yes install build-essential devscripts
gcc dkms make automake autoconf debhelper libssl-dev
pkg-config python-all python-qt4 python-zopeinterface
python-twisted-conch gdebi-core dh-autoreconf hardening-wrapper
libtool graphviz ipsec-tools module-assistant python-twisted-web
racoon git
git clone git://git.openvswitch.org/openvswitch
cd openvswitch
./boot.sh
dpkg-buildpackage -b -us -uc -nc
cd ..
Once you’ve built the .deb
’s you can copy these to your other compute
nodes using scp
:
scp *.deb ubuntu@devstack-compute2:
Replace ubuntu
with your username and devstack-compute2
with the
name or IP address of your other compute nodes.
Finally we can install the packages as follows:
sudo dpkg -i *.deb
At the time of writing this will build Open vSwitch 2.1.90. You can check the version as follows:
sudo ovs-vsctl --version
Which will give the following output
ovs-vsctl (Open vSwitch) 2.1.90
Compiled Jan 16 2014 15:18:45
Huge thanks to @FlorianOtel for his help with Devstack!
@dave_tucker
There is a lot of news surrounding Net Neutrality, and potential repercussions of decisions made by courts, and some players out there that want to grab as much cash as they can, and claim it is in the best interest of their customers.
Netflix is just an example people love citing because it is bandwidth intensive, yet is not the entire story itself. Take a moment and understand how the Internet is pieced together. The Internet is a mass of interconnections between networks. These interconnections happen basically 1 of 3 ways:
transit: network A pays network B to reach every other network that isn’t A or B. Good networks usually get multiple transits for failover, and/or alternate paths to those other networks. You can buy multiple ports for bonding to increase capacity, etc. Average transit price without a Service Level Agreement (SLA, guaranteed connectivity or you can yell at us a lot and we credit you) is around $1-2/mbit, and with a SLA can hit upwards of $10/mbit. These are current avg. prices when buying 10G at a time of connectivity/capacity right now.
peering (settlement free, or “free”): Network A spends a bunch of money to get into popular Continue reading
Figure 1: Marking large flows |
Figure 2: Large flow marking controller results |
ping -f 10.0.0.238 -s 1400Figure 2 shows the results, the left half of the chart shows traffic when the controller is disabled and the right half shows traffic when the controller is enabled. The blue line trends the largest unmarked flow seen in the network and the gold line shows the largest marked flow. When controller is disabled, none of the traffic is marked. When the controller is enabled, sFlow-RT detects the large flow Continue reading
While setting up my OpenDaylight OVSDB and Devstack following the awesome instructions from Kyle Mestery, I thought it would be fun to run the latest OVS from source on my compute nodes...
Last week I was at a Cisco users group meeting where some sales engineers were giving a presentation on the new Application Centric Infrastructure (ACI) architecture and Nexus 9000 products. It was a very high-level overview, but it was interesting. I had assumed when Cisco made the ACI announcement that it would be based on […]
The post Cisco ACI – Speculation of its Inner Workings appeared first on Packet Pushers Podcast and was written by Eric Flores.
Figure 1: Best of Velocity 2012, The sFlow Standard |
This week Greg and Ethan go back and forth on a bunch of current happenings. Data Networking is full of releases, updates and progress. In 80 minutes we will discuss the topics that look important to us.
The post Show 175 Dying Desktops, Insecure Firewalls, Networking The Internet of Things appeared first on Packet Pushers Podcast and was written by Greg Ferro.
In Part 1 we saw there were three markings that can be potentially applied to a prefix in CEF. They are the Precedence, qos-group and traffic_index. It’s unfortunate these terms were used because we also find that we are marking prefixes in CEF, not packets, so these terms don’t perfectly map to our traditional sense […]
The post CEF Secret Attributes, Part 2 appeared first on Packet Pushers Podcast and was written by Dan Massameno.
Regular readers no doubt have noticed that I haven't posted anything new in the past few months. I've been pretty busy with the holidays, home projects, and adjusting to a new job, and haven't had much time or motivation to devote to writing. Good news though: I have started on a long-overdue refresh of the Packet Life design and code base.
When I originally debuted Packet Life, I ultimately wanted it to serve as major community hub, so I built in features like the wiki and discussion forum. Although Packet Life has grown quite popular over the last few years, these areas of the site have seen little activity. Acknowledging that there are more active and useful sites out there which serve these functions, I've decided to chop off some of the bloat in favor of focusing on the blog and the site's other more popular features.
Here's the fate I've outlined for each function of the site:
Blog: The blog is the heart of the site and will remain mostly unchanged, albeit refreshed and optimized. I'm considering allow guest posts but haven't committed to the idea.
Lab: No, there are no plans to bring the community lab back online Continue reading