SPNA248 March 2021 TM4C1292NCPDT , TM4C1292NCPDT , TM4C1292NCZAD , TM4C1292NCZAD , TM4C1294KCPDT , TM4C1294KCPDT , TM4C1294NCPDT , TM4C1294NCPDT , TM4C1294NCZAD , TM4C1294NCZAD , TM4C1299KCZAD , TM4C1299KCZAD , TM4C1299NCZAD , TM4C1299NCZAD , TM4C129DNCPDT , TM4C129DNCPDT , TM4C129DNCZAD , TM4C129DNCZAD , TM4C129EKCPDT , TM4C129EKCPDT , TM4C129ENCPDT , TM4C129ENCPDT , TM4C129ENCZAD , TM4C129ENCZAD , TM4C129LNCZAD , TM4C129LNCZAD , TM4C129XKCZAD , TM4C129XKCZAD , TM4C129XNCZAD , TM4C129XNCZAD
If you hook up the MCU device and the PC to the Ethernet switch, you will not be able to view the DNS traffic on Wireshark. The reason is that the DNS traffic is between the DNS server and the device. The switch will not route the traffic to the PC running Wireshark. In order to view the DNS traffic, you either have an Ethernet hub which broadcasts all traffic on the network to all ports connected to it or you need to configure the ethernet switch for “Port Mirroring”. An ethernet hub is hard to find these days. It is easy to find a Smart Switch that you can configure for Port Mirroring. Figure 8-1 shows where the EK-TM4C1294XL connecting to the switch Port 2 is mirrored onto Port 1 that is connected to the PC. With the port mirroring, all traffic to/from Port 2 will be snooped by the Wireshark on port 1. Consult your switch or router data sheet on how to configure port mirroring.