Sudo ip netns exec netns_leah ip link set dev veth_ns_leah up Sudo ip link set dev veth_ns_leah netns netns_leah Sudo ip link set dev veth_leah master bridge_home Sudo ip link add dev veth_leah type veth peer name veth_ns_leah Sudo ip netns exec netns_leah ip link set dev lo up Sudo ip netns exec netns_dustin ip address add 10.0.0.11/24 dev veth_ns_dustinĮcho "nameserver 8.8.8.8" | sudo tee -a /etc/netns/netns_leah/nf Sudo ip netns exec netns_dustin ip link set dev veth_ns_dustin up Sudo ip link set dev veth_ns_dustin netns netns_dustin ![]() Sudo ip link set dev veth_dustin master bridge_home Sudo ip link add dev veth_dustin type veth peer name veth_ns_dustin Sudo ip netns exec netns_dustin ip link set dev lo up Sudo ip address add 10.0.0.1/24 dev bridge_homeĮcho "nameserver 8.8.8.8" | sudo tee -a /etc/netns/netns_dustin/nf ![]() Sudo ip link add dev bridge_home type bridge How do Kubernetes and Docker create IP Addresses?! If a refresher is needed on any of the following, please take a look at We’re going to quickly set up an environment as we did in the previous post. We’ll be manually creating network namespaces with python HTTP servers running, which will be treated as our “pods.” Recall that Kubernetes creates a network namespace for each pod. Like the first two articles, we won’t use Docker or Kubernetes in this post.
0 Comments
Leave a Reply. |