Also having problems with tcpdump
Like the previous post I also have a question about LFS258, Lab 3.4. - Deploy a Simple Application. I am using AWS and my kubeadm version is 1.20.
As per the lab sessions I have 2 nodes:
$ kubectl get nodes NAME STATUS ROLES AGE VERSION ip-172-31-17-67 Ready control-plane,master 9d v1.20.5 ip-172-31-27-81 Ready <none> 9d v1.20.5
and I have successfully deployed nginx to the worker node and exposed the service on port 80,
as per instructions 14-15.
$ kubectl get nodes NAME STATUS ROLES AGE VERSION ip-172-31-17-67 Ready control-plane,master 9d v1.20.5 ip-172-31-27-81 Ready <none> 9d v1.20.5 $ kubectl get deployments,pods NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/nginx 1/1 1 1 4d22h NAME READY STATUS RESTARTS AGE pod/nginx-7848d4b86f-pkw86 1/1 Running 0 55m $ kubectl get ep nginx NAME ENDPOINTS AGE nginx 192.168.14.138:80 55m
Now from the worker node I can get the sample nginx page served up,
so from the machine at 172.31.27.81 I can do:
$ curl 192.168.14.138:80 <!DOCTYPE html> <html> <head> ...
But when I try
tcpdump I don't see any traffic on the worker node (i even eventually tried issuing it from the control plane node, that is the machine with TCP/IP address of 172.31.17.67)
$ sudo tcpdump -i tunl0 tcpdump: tunl0: That device is not up
tcpdump -v without a specific tunnel...
$ sudo tcpdump -v tcpdump: listening on vxlan.calico, link-type EN10MB (Ethernet), capture size 262144 bytes ^C 0 packets captured 0 packets received by filter 0 packets dropped by kernel
but it did not capture any traffic even though I issued several
curl 192.168.14.138:80 commands in another session on the same
I also did note that when I issued
curl 192.168.14.138:80 on the control plane, I got no HTTP response.
What should I check and what am I doing wrong?