I started working on Juniper equipment around 2002. At my employer, we had an M40 with the serial number 256. We did Layer3 only. I had no idea if the Juniper even did layer2. It certainly wasn’t a layer3 switch like a 6500 like I was used to. It was like a deliciously robust version of any Layer 3 router I’d worked on previously. Over the years Juniper has added a switching line utilizing their FreeBSD based OS, JunOS.

Last year, Networking Field Day was something that I’d heard of but wasn’t really aware of what is really was. I occasionally looked at Twitter and saw the hash tags but did not know much about how it was set up or what it was about. In fact, I actually thought it was supposed to be like the HAM radio field day stuff where you go out and build out an emergency network on the fly.

Tyler Christiansen - Mar 6, 2013 So what happens when the circuit to the one transit provider providing a default IPv6 route drops? Or if instability is otherwise introduced? Nick Buraglio - Mar 6, 2013 That is a known limit. One could have default from >1 provider or not have had to do this in the first place, ideally. In this particular instance, there is only one provider that can truly give default (cogent isn’t a full v6 table regardless of what they say) and the rest are close but not full.

I’ve recently run into a situation where there was no longer enough space in the FIB to handle both the full IPv4 global table and the full IPv6 global table. We prefer to run a default-free network within this particular SP network, but in this case, until a hardware refresh can happen, we’ll need to adjust that. Given what we knew about the size of both tables, it made more sense to take a default IPv6 route from one transit provider and filter the rest.

Nick Buraglio - Mar 4, 2013 Fixed a typo in the ifcfg-br0 section. Networking Field Day 5, participation. - Mar 3, 2013 […] old blog (which became this site). I’m working more on OpenFlow, virtualization stuff like KVM, VirtualBox and VMware and bringing up 100G WAN links. I even had the extremely cool opportunity […] vps - Mar 4, 2013 I really like your blog. You write about very interesting things.

I am a network engineer by profession, but with the proliferation of SDN and OpenFlow, I have had to spend a lot of time re-learning a lot of system admin skills that I’d shelved years ago. Now, I’ve been a virtualization user forever. From VMware (Fusion, ESX), VirtualBox, to Parallels, I’ve used them at least in testing if not in production environments. I’d not really spent any mentionable amount of time with XEN, qEMU or KVM, but some projects I was working on suggested it for the virtualization mechanism, so I figured I’d try to pick it up.

From the help command, here is a reference sheet for the virsh command: virsh [options]... [<command_string>] virsh [options]... <command</command [args...] options: -c | --connect=URI hypervisor connection URI -r | --readonly connect readonly -d | --debug=NUM debug level [0-4] -h | --help this help -q | --quiet quiet mode -t | --timing print timing information -l | --log=FILE output logging to file -v short version -V long version --version[=TYPE] version, TYPE is short or long (default short) -e | --escape set escape sequence for console commands (non interactive mode): Domain Management (help keyword 'domain') attach-device attach device from an XML file attach-disk attach disk device attach-interface attach network interface autostart autostart a domain blkdeviotune Set or query a block device I/O tuning parameters.

Install KVM on CentOS 6.3 - Quick Start to a VM - Mar 5, 2013 […] KVM virsh command reference […]

From the help command, here is a reference sheet for the virsh command:``` virsh [options]… [] virsh [options]… [args…] options: -c | –connect=URI hypervisor connection URI -r | –readonly connect readonly -d | –debug=NUM debug level [0-4] -h | –help this help -q | –quiet quiet mode -t | –timing print timing information -l | –log=FILE output logging to file -v short version -V long version –version[=TYPE] version, TYPE is short or long (default short) -e | –escape set escape sequence for console

Recently SI6 released the IPv6 Toolkit 1.3  This release is on the heels of this IETF draft  on IPv6 host scanning. It was long thought that scanning an IPv6 network was impossible. The address space was too large and reliably ascertaining the hosts from it would be too time consuming to even attempt. However, as Dr. Hans Zarkov says in the 1980 classic cult film of my youth, Flash Gordon, “You can’t beat the human spirit!