![]() Now I put all the blame on the Virtual Manager/settings. Thus, I assume my application works fine and all the ubuntu OS configurations are correct. I installed the ISO image on the other machine (Virtual box instead of HP Windows Server) and it works as it should. Could the problem be in the network settings? Or the application itself - need to find the bug in the script I did not write. 3) The promiscuous mode allows NIC to pass only traffic that belongs to the host machine. 2) The promiscuous mode allows NIC to pass all the traffic that exists on the Internet. So, I would assume that the packets are correct. This problem has been solved What is promiscuous mode in Wireshark 1) The promiscuous mode allows NIC to pass all the traffic that it receives to the CPU. It looks like when the application is subscribed to only 8 multicast groups, it works fine, however, if subscribed to more than 8, it receives only 2 (if they end on. ![]() The check sums for on the IP and UDP levels are correct. Thus, changing the Ethernet interface configuration to promiscuous mode allows the application to receive all the messages without running the Wireshark.īut what is the problem with the other packets that are not normally received? I tried to cross-verify the hex-dump of the "good" and "bad" messages and they don't seem to be different. ![]() I found several other similar questions like this one, where it explains that because Wireshark is running in promiscuous mode, it allows all packets to get through (through what?), and this explains why my application starts "seeing" them too. However, when Wireshark is capturing, the application starts receiving all messages. The problem is that my application only receives 2 out of 100 groups. ![]() Both are on a HP server run by Hyper-V manager. I am generating UDP packets on a 100 multicast groups on one VM Ubuntu 16.04 machine and subscribe to those groups on the other VM Ubuntu 16.04 machine.
0 Comments
Leave a Reply. |