We introduced the recipe to connect to the Akamai Multicast Backbone in https://community.akamai.com/docs/DOC-8118
In this document, we describe how one can build a lab setup to connect to our backbone and receive the test Multicast stream.
Testing and Debugging
Multicast Receiver Directly Attached to AMT Gateway
We built a simple topology to connect to and verify the Akamai Multicast backbone in the lab. We setup a Ubuntu 16.04 KVM host (Ubuntu cloudimage http://cloud-images.ubuntu.com/releases/) with two guest images, one is the qcow2 version of the Cisco CSR1000v version 3.16.4bS (the qcow2 image is named csr1000v-universalk9.03.16.04b.S.155-3.S4b-ext.qcow2) and a Ubuntu 16.04 guest as the Multicast receiver.
In addition to the AMT configuration specified in the previous section, the CSR1000V is configured to have 192.168.122.2 on GigabitEthernet1 and 10.100.200.1 on GigabitEthernet2.
Lab Config Instructions
First, one needs to setup another network, for example, isolated1 (please see the content of the xml file below), using a new virtual bridge interface virbr1.
Second, one needs to set up the newly available interfaces with the designed network config on both the CSR1000v and the Ubuntu KVM guest.
For Ubuntu KVM guest:
Third, one also needs to add static routes on the KVM host so the subnet 10.100.200/24 and 10.100.201/24 are reachable from the KVM host. I have experienced failures in establishing the tunnel because these static routes were not properly configured. I spent a lot of wasted time thinking that the iptables configuration was incomplete instead.
Lastly, both the 10.100.200/24 and 10.100.201/24 networks need to be NAT'ed via the virbr0 interface (that has the 192.168.122.1 IP) to the outside. libvirt sets up the NAT for the 192.168.122 network automatically, but one has to manually set up the iptables rules for the 10.100.200/24 and 10.100.201/24 networks. We need additional rules modeled after the 192.168.122 subnet.
In the nat table: