Installing KVM, Libvirt and Open vSwitch on Fedora

In my NetOps to DevOps Training Plan I mentioned installing KVM, Libvirt and Open vSwitch. I did this a few weeks ago and documented it to produce this tutorial. My motivation was to replace my VMware environment at home with something Open Source. I am also a strong believer in "eat your own dog food" and as a lot of the work I am doing in the Open Source community centers around these 3 technologies, I should get used to using them every day...

Prerequsites

Before we get started, I'll assume that you already have a Fedora Minimal Installation that you are ready to work on...

Installing the packages

sudo yum install -y @standard @virtualization openvswitch

That was easy wasn't it!

@standard installs some useful utilities and @virtualization installs libvirt + KVM

I'm sure you can guess what openvswitch does.

Configuration

Now here comes the fun part!

Configure the services

# Disable NetworkManager
sudo systemctl stop NetworkManager.service
sudo systemctl disable NetworkManager.service

# Enable "Proper" Networking
sudo systemctl enable network.service
sudo systemctl start network.service

# Enable the Open vSwitch service
sudo systemctl enable openvswitch.service
sudo systemctl start openvswitch.service

Setting up Networking with Open vSwitch

Our Continue reading

Setting Up Overlays on Open vSwitch

Packet Capture in Diverse / Tunneled Networks?

Packet Capture in Diverse / Tunneled Networks?

Installing KVM, Libvirt and Open vSwitch on Fedora

In my NetOps to DevOps Training Plan I mentioned installing KVM, Libvirt and Open vSwitch. I did this a few weeks ago and documented it to produce this tutorial. My motivation was to replace my VMware environment at home with something Open Source. I am also a strong believer in "eat your own dog food" and as a lot of the work I am doing in the Open Source community centers around these 3 technologies, I should get used to using them every day...

Networking is a Service, and you are the Service Provider

The status quo approach to Networking is the biggest barrier to realizing the full potential of Virtualization and the private, public, or hybrid cloud. We must re-think how Networking Services are delivered, in a way that comports with automation, decoupling, pooling, and abstractions. I would argue, the solution is a more software-centric approach – Network Virtualization. But more importantly, we must re-think how we view Networking as a career skill set and the value we bring to an organization.

This was the message of two keynote talks I recently gave at the Sydney & Melbourne VMUG user conferences. The title of the talk was Three reasons why Networking is a pain in the IaaS, and how to fix it. I will share the slides and a brief summary of that talk in a subsequent post. But before I do that, please indulge me in a heart-to-heart chat from one long time Networking professional (me) to another (you):

I emphasize the word services because if you really think about it, that is what Networking really is – Networking is a Service. It always has been, and will always continue to be a service – a service that will always be needed. Continue reading

Networking is a Service, and you are the Service Provider

The status quo approach to Networking is the biggest barrier to realizing the full potential of Virtualization and the private, public, or hybrid cloud. We must re-think how Networking Services are delivered, in a way that comports with automation, decoupling, pooling, and abstractions. I would argue, the solution is a more software-centric approach – Network Virtualization. But more importantly, we must re-think how we view Networking as a career skill set and the value we bring to an organization.

This was the message of two keynote talks I recently gave at the Sydney & Melbourne VMUG user conferences. The title of the talk was Three reasons why Networking is a pain in the IaaS, and how to fix it. I will share the slides and a brief summary of that talk in a subsequent post. But before I do that, please indulge me in a heart-to-heart chat from one long time Networking professional (me) to another (you):

I emphasize the word services because if you really think about it, that is what Networking really is – Networking is a Service. It always has been, and will always continue to be a service – a service that will always be needed. Continue reading

Networking is a Service, and you are the Service Provider

The status quo approach to Networking is the biggest barrier to realizing the full potential of Virtualization and the private, public, or hybrid cloud. We must re-think how Networking Services are delivered, in a way that comports with automation, decoupling, pooling, and abstractions. I would argue, the solution is a more software-centric approach – Network Virtualization. But more importantly, we must re-think how we view Networking as a career skill set and the value we bring to an organization.

This was the message of two keynote talks I recently gave at the Sydney & Melbourne VMUG user conferences. The title of the talk was Three reasons why Networking is a pain in the IaaS, and how to fix it. I will share the slides and a brief summary of that talk in a subsequent post. But before I do that, please indulge me in a heart-to-heart chat from one long time Networking professional (me) to another (you):

I emphasize the word services because if you really think about it, that is what Networking really is – Networking is a Service. It always has been, and will always continue to be a service – a service that will always be needed. Continue reading

Networking is a Service, and you are the Service Provider

Wi-Fi Tools

Weighing AWS VPN Options

 Option 1

Build the VPNs off the Internet routers themselves. Route AWS traffic in to the corporate network through the firewall. In an ideal world, you’d probably dedicate some routers for this purpose, but I’ve never had anyone do that. We’re talking about a LAN-to-LAN VPN, here; one doesn’t commonly deploy totally dedicated infrastructure for each new Continue reading

HP Comware-based Switches – Configuring filters for BPDU (bpdu-filtering)

The Spanning-tree protocol sends messages every two second in order to keep the LAN stability, protecting the topology from physical loops (blocking the logical loop) and providing high availability in case of any switch fail.

For that matter, the Switches exchange messages called BDPUs which are utterly important for the correct functioning of the network described as above.

There are scenarios when is necessary to deactivate the protocol within a specific interface, utilizing other protocols and features of high availability such as RRPP, Smart-Link, Monitor-Link, etc or when also the Switch needs to transport the information in tunnel form (transparent), for example, QinQ.

In client-sharing environments, it is not recommended that the network alteration be advised for all  Swtiches that do not belong to that particular network and have the same Switch in common, for example, Service Provider and Data Center.

The main question in this scenario of BPDU filtering is to certify that the network does not have any sort of loop that can cause a disaster for the Network Engineer’s project.

Certifying those questions, the HP Comware based Switches carry the following commands, that may help  finding a solution:

Interface gigabitethernet 1/0/1
stp disable
! Deactivating  STP only on  Continue reading

ONS2014 SDN Idol finalist demonstrations

ONS2014 Announces Finalists for SDN Idol 2014 provides some sFlow related trivia relating to the finalists. 

Slovak Air Force MiG-29 with 2008 Digital Camoflage, 1/48

For best article visual quality, open Slovak Air Force MiG-29 with 2008 Digital Camoflage, 1/48 directly at NetworkGeekStuff.

I am failing to find words to describe this very beautiful 1/48 scale model, but this one is simply very special for me. First reason is that as a Slovak national, it was very enjoyable to be able to build this majestic plane. Second reason is that I was able to finally incorporate proper pre-shading technique along with manually painted (with painfully detailed masking) of the digital camouflage pattern this plane uses. The painting of this one actually took me two weeks of work every evening (yes, I have full time job, so that is the best I can have). Because this plane is so special for me , I will also make this article a little bit different as well. So this time it will not be only a simple few picture gallery, but I will actually go a little bit over the construction right after that.

MiG-29AS in Slovak Air Force
(super quick history)

Slovak Air Force MiG29 – plane number #0921

The Mikoyan MiG-29 (Russian: Микоян МиГ-29; NATO reporting name: “Fulcrum“) is a fourth-generation jet fighter Continue reading

Network Flavors in OpenDaylight

OpenStack uses the concept of flavors to define compute/storage configurations that vary in terms of resource consumption. When we start to consume the network as a resource pool, we need a similar concept. This post explains how this is achieved in the context of the Flavors application in the OpenDaylight project

Network Flavors in OpenDaylight

OpenStack uses the concept of flavors to define compute/storage configurations that vary in terms of resource consumption. When we start to consume the network as a resource pool, we need a similar concept. This post explains how this is achieved in the context of the Flavors application in the OpenDaylight project

Fallacies of Distributed Computing

If you haven't read the Fallacies of Distributed Computing you should. Specifically points 2 and 3.

2) Latency is Zero 3) Bandwidth is Infinite

The truth is that not all networks are created equally. We may have some pools of 2:1, 4:1, 8:1 oversubscribed fabric. We may links between data centers at varying bandwidths and costs to the business.

In a cloud network, we can increase our ROI by charging out portions of the network based on their actual cost to the business, but to do this we need to model the network appropriately. Applications also need to consume networking in an abstract way, and the concept of using Flavors as this abstraction is an interesting prospect.

Problem Statement

The problem is that todays cloud networking solutions (OpenDaylight included) are based on "Overlay Networks". The Overlay Network solution only assumes L3 reachability between tunnel endpoints Continue reading

Network Flavors in OpenDaylight

OpenStack uses the concept of flavors to define compute/storage configurations that vary in terms of resource consumption. When we start to consume the network as a resource pool, we need a similar concept. This post explains how this is achieved in the context of the Flavors application in the OpenDaylight project

Changing Your MAC Address Using Macchanger

Macchanger is a free utility used to change the MAC address of the network adapter. Macchanger can randomly assign a MAC address or assign a specific MAC address of your choosing.

Usage

There are several instances changing the MAC address is necessary, but I use the utility while pentesting a wireless network with MAC filtering enabled and have to assign an approved MAC address to the wireless adapter.

Install

The Macchanger utility is included with Kali Linux, but to install the application, update it, or verify your using the most up to date version run the following command. In the screen shot that follows the install command confirms that the newest version is already installed.

#apt-get install macchanger

Help

Help with Macchanger can be accessed by running the following two commands.

#macchanger --help

#man macchanger

Assign a Random MAC Address

I’m using an Alfa USB wireless adapter and I will run the following commands to verify the adapters interface and the permanent MAC address.

#ifconfig

#ifconfig wlan1

Macchanger can also be used to verify the manufacture burned in MAC address by running the following command.

#macchanger--show wlan1

Change the MAC address using one of the following commands.

#macchanger -r  Continue reading

3Com / H3C / HP Comware based Switches – Edged-port + BPDU Protection

Today we’ll comment on the two features that work as a complement to the Spanning-Tree. The edged-port command gathers many benefits to the STP, for example, the timeout prevention concerning the DHCP process. As for the bpdu-protection, it prevents loop in the “edged” configured ports within the network via HUBs, “Switches HUB”, etc.

Edged-port

The edged-port feature allows the interface to skip the Listening and Learning states of the Spanning-Tree Protocol, setting the ports into the Forwarding state immediately.  The STP’s configuration edged-port enable, forces the interface to ignore the convergence states of the STP, including the notification of topology change messages (TCN messages).

The command must be applied to the access ports connected to servers, workstations, printers, etc.

Configuration

[Switch]interface gigabitethernet 1/0/1
[Switch-GigabitEthernet1/0/1]stp edged-port enable
[Switch-GigabitEthernet1/0/1]quit
[Switch]interface gigabitethernet 1/0/2
[Switch-GigabitEthernet1/0/2]stp edged-port enable
[Switch-GigabitEthernet1/0/2]quit

PS: When a port is configured as a edged-port receives a BPDU, the interface will return to participate on the STP like any other interface.
PS:An Edged-port send BPDUs normally. The edged-port feature is also known as Portfast.

 BPDU Protection

The utilization of the edged-port feature is restricted to ports connected to the final equipment such as servers and workstations. Continue reading

Network Management Challenges of 2014

Network Management Challenges of 2014

No matter how much virtualization or abstraction or automation we place into the network, it still has to run on a physical infrastructure somewhere. And you still need to understand how the underlying network is performing, which route the traffic is taking, how much bandwidth each application needs and during what time periods, etc. 

So no matter how much the venerable router is under assault and in danger of becoming a commodity, we know that you will never be able to abstract all physical devices – or humans for that matter – from the network. But we will all need to adapt. 

This is the perspective we’re taking in this blog. Welcome to the first post of the Packet Design blog, where we will delve into all things network management, route analytics, SDN, IT and beyond. We’ll be covering issues for everyone affected by network management concerns. 

That’s a broader audience than you’d think at first glance. It of course includes the planners, architects and engineers who design, set up and maintain the network, the NOC staff who oversee it, the managers responsible Continue reading