Protocol decoding The best packet sniffer should be able to monitor all protocols, such as what AthTek NetWalk can do. That will greatly help administrators to fast analyze the network connections as well as packet details.
It is very important for a packet sniffer to clearly list traffic status with elegant charts and diagrams. Vns3 -> azure network with destination IP 10.1.2.Packet Sniffer Overview Dash board of packet sniffer The following image shows the dash board of our packet sniffer. So, from the network sniffer output, I would assume that the packages are traveling like this: VM2 -> vns3
POSTROUTING\_CUST -o eth0 -j MASQUERADE-ONCEįORWARD\_CUST -o eth0 -m conntrack -ctstate NEW,ESTABLISHED,RELATED -j ACCEPT FORWARD\_CUST -i eth0 -m conntrack -ctstate RELATED,ESTABLISHED -j ACCEPT Trying to open in a browser in VM2 gives me a timeout.įirewall Rules of the vns3: POSTROUTING\_CUST -o eth0 -s 10.0.0.0/8 -j SNAT -to 172.20.153.119 I don't have the on-prem under control, so: I cannot change there anything.Ĭommunication between a VM1 in "hub" and "on-prem" works fine (browser shows page on ).Communication between a VM2 in "spoke" and "hub" works fine (browser shows page on, which is the UI of the VNS3 gateway).
I have a hub/spoke in Azure with on-prem connected via Azure Network Gateway and Site-2-Site tunnel: I am a little bit lost - maybe there is something in Azure that I do miss.
0 kommentar(er)
