I am stucked within a weired problem. I have two little programs (written in C, using Win API), the one sends a multicast package, the other one receives it. Well, I tried it between two notebooks, the one running win7, the other win8, and it works as expected while running a P2P connection between them (=without switch, just the patch cable plugged into both hosts).
But when I try to connect a switch between both hosts it does not work. I also tested a hub, but that dows not work either. I tested it over wifi, but it still does not work.
The Multicast Packet works just over P2P. And THAT seems to be weired.
Firewall is off, also any other security software. Ping works in any configuration as expected.
Any tip would be highly appreciated :-)
Dirk
I've found the problem for myself - the notebook I tried to send the packets has virtualbox installed. After Disabling the virtualbox service the connection worked successfully. I still don't know exactly the reason, but this workaround helped for me.
Related
I was using WSL to run ROS commands, and at a point i had to enable system to respond to broadcast icmp requests (for a multi master kind of a setup) i.e. on linux i had to make sure
cat /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
returns 0. but WSL does not contain such a file, so i was thinking of enabling it on windows. All the sources i have gone through suggest me to add a rule to firewall but my system is not responding to broadcast ping even when my system's firewall is turned off(domain, private and public have been turned off same with my buddy who is no the same network). i am using an android phone's mobile hotspot to check this.
it would be great if someone could help me on this.
thanks in advance.
I asked something similar
I don't know how to do it purely on WSL. But on windows you have to start the "TCPSVCS.EXE" process. located on System32
I just tried to connect to internet using my home WiFi network and didn't manage. I use Ubuntu 18.04.
I am able to connect using hotspot or any other network, but not this one from home. Also it works fine with Windows. I tried with the Ethernet cable as well and didn't work.
I mention I have Atheros QCA9565 .
I tried:
ping 8.8.8.8 and this was successful.
Then:
ping google.com and got this error message: name or service unknown.
Therefore I added:
nameserver 8.8.8.8 in /etc/resolv.conf file and made this persistent after noticing it is reinitialised at reboot: https://www.tecmint.com/set-permanent-dns-nameservers-in-ubuntu-debian/
Sometimes I can do ping google.com but the time is badly increasing, so it's super slow.
And when I can't connect at all, ping google.com has the same error message.
I mention that I tried to turn off DNS automatic from IPv4 tab from WiFi network settings and the connection persisted for 10 seconds or so: https://www.configserverfirewall.com/ubuntu-linux/ubuntu-set-dns-server/
Might it be a hardware problem or what should I try next?
Although it may not be the issue, I recently had problems with the built-in Wifi on my computer's motherboard. I could access some sites at a good speed while others were unreachable. I tried several things I found online but nothing helped. I spent 30 USD on Amazon for a generic AC1200 PCIe Adapter and all the problems/issues have been resolved. Apparently, something was off with the card that was originally part of the computer.
I was told this should not have made some websites not load but the new card has none of the issues at all.
I am trying to run netsh commands to activate a tunnelbroker tunnel in Windows 10. The first command works fine. When I attempt the second command (netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel localaddress=xxxxxxx remoteaddress= 216.66.22.2) I get the error "There is no driver selected for the device information set or element."
I cannot find an answer for this, even from tunnelbroker. Does anyone have a suggestion? This is driving me up a wall.
It's not an Insider issue. Microsoft decided to step down on IPv6 transition technologies as of Redstone 4 (1803). Unfortuntely, instead of just deactivating it, they stopped providing the tunnel driver at all (nettun.inf, tunnel.sys). It's unclear at this point whether Microsoft intents to fix this or not.
Found the answer: Don't use Windows 10 insider builds for IPv6. It seems they broke IPv6 with some of the more recent builds. I started out from scratch with the current version (Fall Creators, I believe), and the commands ran without issue.
I have installed andlinux Beta 2 on my WinXP. Everything works fine until last night, I don't recall that I ever changed anything on network configuration or andlinux setup, the network stop working inside andlinux. With that said, I mean open a KDE console, I do "ping yahoo.com", I see DNS is resolved correctly, however, no response at all.
My andlinux is startup as a WinXP service. Open windows task manager I can see following services are up and running:colinux-daemon.exe colinux-net-daemon.exe colinux-slirp-net-daemon.exe
On andlinux side, there are two network interface eth0 and eth1. eth1 is configured to communicate with local WinXP. I configured it to use samba to access windows directories, no problem. From WinXP side, I can use ssh to login into andlinux box via eth1 IP address.
eth0 is configured as slirp, no port forwarding. eth0 has IP=10.0.2.15, default gateway is 10.0.2.2, netmask=255.255.255.0; These are configured in /etc/network/interfaces. DNS is 10.0.2.3, which as I just mentioned resolve yahoo.com correctly.
On the windows side, internet works fine. I disabled firewall on all network interface. I rebooted my laptop, no luck. I searched over inet, seem no one has this problem. People say network is done if they kill the colinux-slirp-net-daemon. What frustrated me is that this whole thing worked well, but for no reason it's broken all the sudden. Anyone has experience on this issue, please help, appreciate!
I thought I had the same problem, but then found my andLinux system's network connectivity was actually working fine, and that several things made it difficult to tell what was going on.
Test I did to validate connectivity: wget www.yahoo.com
Behavior I observed that made troubleshooting difficult:
Pings from andLinux - not all hosts will respond to pings from the andLinux OS (ie Ubuntu, not the Host Windows OS). According to my packet captures the pings appear as UDP pings instead of ICMP pings once they leave the host OS's adapter. The major IPs/hosts (like yahoo, google, 4.2.2.2 etc.) on the internet I usually ping to test connectivity currently don't respond to these type of pings.
Traceroutes from andLinux - even when successful, these never show more than 2 hops when done from the andLinux OS. If successful, both hops show 10.0.2.2. If unsuccessful, the second hop just times out. Not sure why, I'm sure there is an explanation.
Packet captures - at the host OS level, the capture (eg wireshark) must be done on the physical interface the traffic is going over. I was initially capturing on the TAP-Win32 Adapter but this only showed X Window traffic.
Installed apt sources URLs no longer valid - Ubuntu 9.04 is long out of support by now, so the URLs in the apt sources.list file didn't exist anymore. This is what got me thrown off in the first place, because I didn't troubleshoot this specifically and just tried to test my internet connectivity first, then got confused by the ping and traceroute behavior seen above. Changed http://us.archive.ubuntu.com/ubuntu to http://old-releases.ubuntu.com/ubuntu/ in sources.list and was good to go.
Proper disclosure: I posted this question on the Adobe forums too. Since I didn't get any answer - I am posting it here. Sorry if it disturbs.
We are working with FMS 4 server for a while for a 2 directions video application, and it works great with RTMP.
We now want to use its rtmfp abilities after we used Cirrus for testing in the last few days and it also worked well.
Locally - everything is working fine, but when we try the application on a remote server - we have some problems.
Each side get the NetStatusEvent code "NetConnection.Connect.Success" and "NetStream.Publish.Start" when publish starts.
However, when we are trying to play the stream, nothing happens for a minute and than we get " NetStream.Connect.Closed" after about a minute.
(Locally, we are getting "NetStream.Play.Start" and "NetStream.Play.Reset").
I did open ports 1024-65535 UDP on the server and since we are able to connect Cirrus, I believe the clients are fine.
I also changed the Adaptor.xml HostPort element to
:19350-65535 where xxx.xxx.xxx.xxx is the same public IP of our FMS Server as the one used by the client.
Again, it is working beautifully both locally and with Cirrus. RTMP also works well with the remote server.
What am I missing?
I'm sorry, I can't really help but tell you that I had a very similar problem but the other way around.
When I tried to connect two devices via Cirrus over our WLAN, I got the same error as you. When testing with one device in WLAN and the other in another Network it worked. Then I tested them both in the same WLAN (but in a WLAN other than ours) and it also worked. My collegue then updated some firmware (on the router? I'm not sure...) and deleted some VOIP data. Then it worked here, too.
I think maybe there is some problem at the remote server. UDP has to be allowed... but I'm sure you know that.
Sorry again for not really helping - but maybe this is at least a bit encouraging.
Do you know this sample: http://labs.adobe.com/technologies/cirrus/samples/ ?
I always tested with that so I knew it wasn't some problem with my code.