I am trying to send UDP packets from Linux machine (Ubuntu 18.04 ) to a windows 10 machine. But the packets are not received at the Windows machine. I have already send UDP packets from Windows 10 to Linux machine and was successful. I have wireshark installed on both machines to debug. Pings are working from Linux to Windows as well.
The udp packets from Linux machine seems to be send as per Wireshark. However the wireshark on windows machine shows nothing regarding UDP packets from Linux machine. I have added inbound rules for the port on Windows machine, but still the issue persists. I have tried using different port numbers as well. Kindly let me know if there is anything missing from my end
The problem was due to active Symantec End Point Protection. So created an exception rule for the respective Sender IP address and everything works fine
Related
I'm having no joy in getting a replayed UDP Multicast packet to be "seen" by a client program on a different machine.
Details:
I have two machines on my local (wired) network connected through one unmanaged switch. One machine (running tcpreplay) is running Ubuntu 20.04, the other machine is running Windows 10.
On the Windows machine I have a Python program I wrote which listens for UDP multicast packets on port 5110 (this is dictated by the source of the UDP stream which is a commercial program). When I run the commercial program, my Python code correctly consumes the incoming packets and all seems to be working fine. I have a lot of work yet to do on the contents of those packets after they are received, but that isn't important for this issue.
So, moving forward, I decided it would be great to be able to work on the Python code without having the commercial program always running in the background hogging up resources. I figured if I could catch a snippet of UDP broadcasts from that program, I should be able to replay at leisure without having to run that resource hog.
So, on the Windows machine, I captured a UDP multicast packet stream using Wireshark and saved to a pcap file which I then copied to the Ubuntu machine.
I then attempted to replay that pcap file (on the Ubuntu machine) as follows:
$sudo tcpreplay -i enp5s0 single.pcap
To my disappointment, my Python program (on the Windows machine) did not receive the incoming packets.
Back on the Windows machine, I fired up Wireshark again and captured the "replayed" packet coming from the Ubuntu machine - so it appears the packet did make it out of my Ubuntu machine and into my Windows one. The contents of both the source packet (sent by tcpreplay) and the received packet (grabbed by Wireshark) appear identical - including the source and destination MAC addresses and the checksums. A diff on the byte contents of each packet yields no differences.
However, my Python program still stoically sits there waiting at:
data, address = sock.recvfrom(1024)
Here on stackoverflow, I did find this thread which seems to be an identical problem, however none of the solutions presented within helped (including changing the rp_filter parameter). I also saw mention of a Windows program, "Colasoft PacketPlayer", which I tried - running on the same machine as my Python client. This appears to have the same apparent results (i.e. no joy). I did not initially try that route as I was concerned with generating the packet on the same machine which is listening for it. (As an aside, I did also capture the replayed packet from Colasoft PacketPlayer and it too appears identical to the source packet).
At this point I'm out of ideas and am reaching out to the community for possible next steps?
I'm publishing my data through MQTT in a Windows 10 Virtual Machine via specific IP, hosted by Ubuntu 18.04 and I'm trying to save this data on my host OS. I created a bridge between the host and the guest OS so my guest can be seen by the router (My host receives Ping from my guest and the guest is at the same subnet mask as my host).
I can see the data in the MQTT-Lens in my host machine at the same IP by subscribing to the topic. I wrote a script to save the data. The script is working just fine if I manually publish some data. But it's not subscribing to the same network while I'm publishing data from my guest OS.
Does anyone have any idea? How can I make sure I'm addressing the same broker in my host and guest OS?
Trying to ping from target to Test PC ( windows having Virtual Linux Machine)
Ping works smoothly when:
1. VM ubuntu is not turned off
or
2. Wireshark is not capturing LAN where actual connect is made
This is applicable for IP4 and IP6 ping.
Here VM is configured for Bridged network (same LAN configured in VM)
If I disable LAN ( bridged n/w), then ping works from target
Wireshark if capture lets say WLAN, then ping works from target
I had a suspect on the gateway, subnet but the same setup work in absence of VM + Wireshark
Above things shows if same NIC is used by additional utilities e.g. Wireshark or VM, there are certain communication problem causing ARP or NDP to fail.
I have heard of such congestion failure.
Now I wish to know is this specific behavior of PC, PC configuration (e.g. regedit) or something wrong from the target.
Target is a linux based system.
Error mesaage:
icmp_seq=1 Destination unreachable: Address unreachable
Try to play with 'promiscous mode' on network card at machine where wireshark is running.
The broadcast stops working 5 seconds after the start. All ports are open. Why can this error still occur?
If you run Ant Media Server on Ubuntu virtual machine on Windows host and run browser (as WebRTC peer) on host (Windows) side, then you can encounter with such a problem.
As a solution, you can start browser on virtual machine side. Or better run AMS on a real machine or VPS.
I installed a Ubuntu 14.10 virtual machine on Windows 8.1 using Vmware.
Ubuntu has access to Internet in the NAT mode. But I can't establish a pptp connection to a remote server from Ubuntu. Is this supported?
change to bridged (instead of NAT)
I use VMware with a Macbook. I have found that I can use bridged mode with a hard wired connection. Then the virtual machine reports its own unique MAC address and receives its own IP address. After that PPTP works. No luck with WiFi. It must be adapter dependent, though; since I cannot imagine how it would otherwise be different. It is annoying not to be able to use WiFi for the VPN.