Does the thought of running Wireshark make you nervous? Wireshark’s got a reputation for being more than a bit challenging. With a little practice, though, you can get so much value out of the program. The first step is to capture, so here’s our step-by-step guide!
Do you dread the letters “MS/TP”? If you’ve ever had to capture MS/TP traffic, you probably do. It’s a complicated process, and can mean a lot of trial and error. You can’t ignore MS/TP traffic and hope for the best, though. Eventually you have to roll up your sleeves, pull out your USB, and dig in.
Is your IT department super security-conscious? Maybe they’ve asked you to start filtering and scrubbing all your packet captures (pcaps), and you don’t know where to begin?
MS/TP networks are complex to set up, and it's even more challenging to know if they are running efficiently. This is why Visual BACnet has three diagnostic checks for MS/TP traffic.
We often have people ask us how to create a packet capture, or pcap file, to use in Visual BACnet. While any pcap should give you some insight into your network, there are some best practices that vary depending on what you are trying to discover.
Global Who-Is requests are important to ensure all of the devices on your system are accounted for. However, if they occur too often they can clog the system with all of the I-Am replies. It is important to know if they are being sent out too frequently.
Having unique device IDs in BACnet systems is extremely important. Yet, due to fix-value defaults, changes in systems, or incorrect programming, having duplicate device IDs can be common. Unfortunately, finding the root of these duplicate device IDs is very difficult, and nearly impossible in Wireshark.
© 2024 Optigo Networks Inc | Privacy | Contact Us | 
