From 4e60b8e32ca61cfcb6ef999dfbfa9496b48f2b35 Mon Sep 17 00:00:00 2001 From: Erik Stidham Date: Wed, 22 Nov 2017 09:52:30 -0600 Subject: [PATCH] Add FAQ about cali interface MAC - Added to master, v3.0, and v2.6. --- master/usage/troubleshooting/faq.md | 8 ++++++++ v2.6/usage/troubleshooting/faq.md | 8 ++++++++ v3.0/usage/troubleshooting/faq.md | 8 ++++++++ 3 files changed, 24 insertions(+) diff --git a/master/usage/troubleshooting/faq.md b/master/usage/troubleshooting/faq.md index a8c18edda33..80942419d4b 100644 --- a/master/usage/troubleshooting/faq.md +++ b/master/usage/troubleshooting/faq.md @@ -49,6 +49,14 @@ interface. This makes the host behave like a gateway, responding to ARPs for 169.254.1.1 without having to actually allocate the IP address to the interface. +## Why do all cali\* interfaces have the MAC address ee:ee:ee:ee:ee:ee? + +In some setups the kernel is unable to generate a persistent MAC address and so +{{site.prodname}} assigns a MAC address itself. Since {{site.prodname}} uses +point-to-point routed interfaces, traffic does not reach the data link layer +so the MAC Address is never used and can therefore be the same for all the +cali\* interfaces. + ## Can I prevent my Kubernetes pods from initiating outgoing connections? Yes! The Kubernetes [`NetworkPolicy`](https://kubernetes.io/docs/concepts/services-networking/network-policies/) diff --git a/v2.6/usage/troubleshooting/faq.md b/v2.6/usage/troubleshooting/faq.md index 8ae869c497b..2d4e5cfca90 100644 --- a/v2.6/usage/troubleshooting/faq.md +++ b/v2.6/usage/troubleshooting/faq.md @@ -50,6 +50,14 @@ interface. This makes the host behave like a gateway, responding to ARPs for 169.254.1.1 without having to actually allocate the IP address to the interface. +## Why do all cali\* interfaces have the MAC address ee:ee:ee:ee:ee:ee? + +In some setups the kernel is unable to generate a persistent MAC address and so +{{site.prodname}} assigns a MAC address itself. Since {{site.prodname}} uses +point-to-point routed interfaces, traffic does not reach the data link layer +so the MAC Address is never used and can therefore be the same for all the +cali\* interfaces. + ## Can I prevent my Kubernetes pods from initiating outgoing connections? Yes! The Kubernetes [NetworkPolicy](https://kubernetes.io/docs/concepts/services-networking/network-policies/) diff --git a/v3.0/usage/troubleshooting/faq.md b/v3.0/usage/troubleshooting/faq.md index 7595f0d648d..6689a0feea2 100644 --- a/v3.0/usage/troubleshooting/faq.md +++ b/v3.0/usage/troubleshooting/faq.md @@ -49,6 +49,14 @@ interface. This makes the host behave like a gateway, responding to ARPs for 169.254.1.1 without having to actually allocate the IP address to the interface. +## Why do all cali\* interfaces have the MAC address ee:ee:ee:ee:ee:ee? + +In some setups the kernel is unable to generate a persistent MAC address and so +{{site.prodname}} assigns a MAC address itself. Since {{site.prodname}} uses +point-to-point routed interfaces, traffic does not reach the data link layer +so the MAC Address is never used and can therefore be the same for all the +cali\* interfaces. + ## Can I prevent my Kubernetes pods from initiating outgoing connections? Yes! The Kubernetes [`NetworkPolicy`](https://kubernetes.io/docs/concepts/services-networking/network-policies/)