Archive for the ‘networking’ Category
I wrote a few days ago about my first failed attempt to do this. After some perseverance, and with some lessons learned along the way I’m pleased to say that I now have it working. Given that VXLAN (at least in the Linux kernel implementation) needs multicast I’m still not sure that this is a […]
Filed under: Docker, networking | 3 Comments
Tags: 14.04, bridge, Docker, iproute2, multicast, network, open vswitch, tunnel, Ubuntu, vxlan
This seemed like a good idea, as VXLAN has been in the Linux kernel since 3.7. TL;DR – this doesn’t work as I’d hoped. The two major issues being: VXLAN needs a multicast enabled network, which rules out most public clouds. Instability – I’ve managed to provoke multiple kernel panics on stock Ubuntu 14.04. Background […]
Filed under: Docker, networking | 2 Comments
Tags: bridge, Docker, fail, gre, iproute2, multicast, network, open vswitch, tunnel, Ubuntu, vxlan
Beware the default network
I was helping a colleague troubleshoot a deployment issue recently. He’d set up a virtual private cloud (VPC) in Amazon with a public subnet and a bunch of private subnets: 10.0.0.0/16 – VPC (the default) 10.0.0.0/24 – Public subnet 10.0.0.1/24 – Private subnet 1 10.0.0.2/24 – Private subnet 2 10.0.0.3/24 – Private subnet 3 Everything was behaving […]
Filed under: cloud, CohesiveFT, Docker, networking | 1 Comment
Tags: aws, CIDR, conflict, defaults, Docker, howto, LXC, lxcbr0, networks, peering, routing, troubleshooting, VNS3, VPC
Chris Swan's Weblog 