In my last post on the subject of BGPSEC, I explained the basic operation of the modifications to BGP itself. In this post, I’ll begin looking at some of the properties — both good and bad — of these extensions to BGP. To being, we’ll look at the simple network illustrated here, and see what […]
The post BGPSEC: Protections Offered appeared first on Packet Pushers Podcast and was written by Russ White.
I promise engineers who renew their subscription 4-6 new webinars a year. It’s time to see whether I kept that promise in 2014.
TL&DR summary: it was a great year, but I still missed a few things.
Read more ...
Ah, finally -my camera as arrived. I ordered my Seek Thermal Camera from Amazon for iPhone back in October 2014, and due to some issues between Apple and Seek over the Hardware Certification, the shipments had been delayed. Post by Seek Thermal. Since it is here I can now show you the unboxing of the […]
The post Seek Thermal iOS appeared first on Fryguy's Blog.
Review schemes are useful for identifying good consumer products and applications. But that doesn’t mean that everything needs to prompt me to leave a review. Cisco has started prompting for reviews for IOS versions, but I’m not convinced it makes sense for network operating systems. Perhaps it will do one day when disaggregated hardware/software is the norm for network devices.
I love the 1Password password manager. It’s a well-polished app, and has been great value. Part of making my life better means not annoying me with frequent prompts for review:
1Password never prompts you for a review. We value your workflow too much to interrupt it. If you feel generous and have a couple of minutes, please leave a review. It means the world to us.
I like the Pocket app too. It prompts me to leave a review every single time it gets updated, which annoys the hell out of me. But hey, it’s free, so maybe I shouldn’t complain too much.
Pocket and 1Password are examples of consumer applications in a competitive market. The barrier to switching is relatively low, and they live and die on reviews. In a crowded market, customers rely on reviews, and the Continue reading
After installing the Mininet software-defined network simulator on a virtual machine, you may want to build the documentation. Documentation is available on the Mininet web site but, if you installed a beta version of a new development release or installed an old version, you may want to use the documentation specific for the version you are using.
Mininet documentation is built into the source code and can be generated using the doxypy program. This post details the simple steps required to install doxypy and other required software, and to build and view the documentation.
Start the Mininet virtual machine and log into it via SSH. See my previous post about setting up the Mininet SDN Network Simulator virtual machine.
On the Mininet VM, run the following command to install doxypy, and supporting software packages:
$ sudo apt-get install doxypy doxygen doxygen-latex help2man
This could take a while because it downloads over one Gigabyte of data, such as fonts.
On the Mininet VM, run the following command to build the documentation
$ cd ~/mininet
$ make doc
This builds a PDF version of the documentation named refman.pdf in the folder: ~/mininet/doc/latex/.
At this point we’ve deployed three hosts in our first and second CoreOS posts. Now we can do some of the really cool stuff fleet is capable of doing on CoreOS! Again – I’ll apologize that we’re getting ahead of ourselves here but I really want to give you a demo of what CoreOS can do with fleet before we spend a few posts diving into the details of how it does this. So let’s dive right back in where we left off…
We should have 3 CoreOS hosts that are clustered. Let’s verify that by SSHing into one of CoreOS hosts…
Looks good, the cluster can see all three of our hosts. Let’s start work on deploying our first service using fleet.
Fleet works off of unit files. This is a systemd construct and one that we’ll cover in greater detail in the upcoming systemd post. For now, let’s look at what a fleet unit file might look like…
Note: These config files are out on my github account – https://github.com/jonlangemak/coreos/
Systemd works off of units and targets. Suffice to say for now, the fleet service file describes a service Continue reading
Please Join us in congratulating the following iPexpert clients who have passed their CCIE lab!
Have you passed your CCIE lab exam using any iPexpert or Proctor Labs self-study products, or attended our CCIE Bootcamp? If so, we’d like to add you to our CCIE Wall of Fame!