Not long ago I wrote an article on how to configure an IPsec VPN using Mikrotik and Linux devices. For today, I will replace the Linux device with a Cisco. I did test the entire construct in GNS3 integrated with Mikrotik.
A few months ago I described how bandwidth limitations shatter the dreams of spread-out application stacks with elements residing (or being dynamically migrated) between data centers. Today let’s focus on bandwidth’s ugly cousin: latency.
TL&DR Summary: Spreading the server components of an application across multiple locations (multiple data centers or hybrid cloud deployments) can easily result in dismal performance even when there’s plenty of bandwidth available.
Read more ...Bare metal servers changed the world of compute. The same thing is happening in networking: bare metal switches are the foundation for an inevitable shift in data center networking. The movement is called “open networking” but at it’s core, it’s really just about great physical networks with the additional benefits of a rich ecosystem, broad support for automation and monitoring tools, and improved economics.
The big players in bare metal switching – including Accton and Quanta – leverage best-in-class components to deliver high performance switches, and they do it fast. Add an OS (more on that later) and you’ve got a disaggregated model that enables networking that fulfills the vision of the software-defined data center. If SDDC doesn’t matter so much to you, then think of this: bare metal may fulfill your vision of a more affordable, manageable network that gives you the time and funding for more projects that really help your business.
(For comparisons on pricing and shipping speed versus Continue reading
Don’t expect technical topic in this post. Instead I wanted to show how was my situation before and after the CCDE – Cisco Certified Design Expert !. Enjoy BEFORE Orhan Ergun ( At the Right, Handsome one ), Neil Moore (Only 8xCCIE in the world at the left) and Brian McGahan ( INE ) at […]
The post CCDE Before and After ! appeared first on Network Design and Architecture.
I was recently asked if Arista EOS could run on Whitebox network hardware. From a blog post on the Arista website on July 1, 2013 : In fact, a little known secret is that Arista EOS was intended to run on third-party hardware. The Arista vEOS control plane provides the ability to run as a VM […]
The post Could Arista EOS Run On Whitebox Hardware ? appeared first on EtherealMind.
MPLS Traffic Engineer is sometimes promoted as a QoS solution (it seems bandwidth calendaring is a permanent obsession of some networking engineers, and OpenFlow is no more a solution than MPLS-TE was ;), but in reality it’s pretty hard to make the two work together seamlessly (just ask anyone who had to implement auto-bandwidth MPLS-TE in a large network).
Not surprisingly, we addressed the topic during our MPLS Tech Talk.
So far, we’ve looked at the naming system, routing, and policy in our travel through “internet land.” Last time, we took a quick look at some of the various organizations that create the standards that make the internet work. This time I’m going to start looking in more depth at one specific standard body, or […]
The post HTIRW: IETF Organizational Structure appeared first on Packet Pushers Podcast and was written by Russ White.
I’ll admit it – I’ve drunk the “Network Engineers should learn programming” Kool-Aid. In so doing, I’m gearing up for Kirk Byers upcoming “Python for Network Engineers” course by hacking a bit of Python most every evening. Kirk has recently released a Python “wrapper” module for the popular Python SSH module “Paramiko” that simplifies connections […]
The post Parsing Junos XML with Python appeared first on Packet Pushers Podcast and was written by Will Dennis.
I’ve always sort of set goals for myself, but I never really write any of them down. This year, after talking to a friend about it, I decided to write down some actual goals for 2015. What really struck me about the conversation was a single sentence he said. I believe the exact words he used were “Write them down and you’ll be amazed at how motivated you can be”. Since it certainly sounded like he was speaking from experience, here’s my list. Some are more subjective which will make them harder to ‘check off’ than others. Some are related to my work/career, some are personal, and some are just sort of for fun.
Run a marathon – Some of you know I made a serious attempt at this 2 years ago. It started with others offering tips and training schedules, continued with me disregarding the training plan, and ended with me doing it wrong and messing up my knee. So this year, I’m going to make a serious attempt at following a training schedule and try and get this done. I’ll aim for the Twin Cities marathon which happens Continue reading
One problem I’ve noticed with my Pocket list is that my reading list contains quite a few duplicate entires. Sometimes I forget I saved an article and I save it multiple times, or maybe I save it across-sources (like Twitter or Facebook, or just browsing.
It looks like Pocket has some protective capabilities around this. If I endlessly spam the button provided to me by my Pocket chromecast extension, Pocket only saves the one copy and all is good.
However, take the following example. Many of the articles we read and put into our Pocket list use some kind of URL options for tracking purposes:
?utm_source=social&utm_medium=twitter&utm_campaign=1215
If you arrive to an article from different sources, but save both to Pocket, Pocket will treat these as different URLs. This means that if you’re bad about staying caught up with your Pocket list (like I am), it can be very easy to save duplicate articles, making the situation even worse.
Fortunately I have a solution. I wrote this python script to automate the removal of duplicates of entries in your pocket list.
Currently this script works by removing ALL text after a question mark (?) or a hash mark (#) in each Continue reading
A few days ago, my colleague Marek sent an email about a DDoS attack against one of our DNS servers that we'd been blocking with our BPF rules. He noticed that there seemed to be a strange correlation between the TTL field in the IP header and the IPv4 source address.
CC BY 2.0 image by Jeremy Keith
The source address was being spoofed, as usual, and apparently chosen randomly, but something else was going on. He offered a bottle of Scotch to the first person to come up with a satisfactory solution.
Here's what some of the packets looked like:
$ tcpdump -ni eth0 -c 10 "ip[8]=40 and udp and port 53"
1.181.207.7.46337 > x.x.x.x.53: 65098+
1.178.97.141.45569 > x.x.x.x.53: 65101+
1.248.136.142.63489 > x.x.x.x.53: 65031+
1.207.241.195.52993 > x.x.x.x.53: 65072+
$ tcpdump -ni eth0 -c 10 "ip[8]=41 and udp and port 53"
2.10.30.2.2562 > x.x.x.x.53: 65013+
2.4.9.36.1026 > x.x.x.x.53: 65019+
2.98. Continue reading