Issues with UdpSend

Posted by ArchangelEvo on Mon 18 May 2015 08:55 AM — 5 posts, 19,073 views.

#0
I created a UdpListener in .NET that has a graphical health bar, status windows, clock, etc. The listener seems to work fine, and I can receive packets with it if I send them from Packet Sender.

As soon as I try to send the same packet using UdpSend, it returns with code 0, but the listener never receives them. I have tried suspending my firewall, granting full access, granting access to specific ports, running as admin, changing ports, changing packet text, using aliases, using plugins, using the immediate window, restarting, reinstalling MC. Nothing works.

Any insight into this problem would be greatly appreciated.

The test I am using most often is :
Note(UdpSend ("127.0.0.1", 11000, "128 hp"))

This is on a Win 7 64-bit system
Running ZoneAlarm
MUSHclient ver. 4.94
Using LUA
#1
I realize now that I started this in the wrong sub-forum, but I can't seem to move it.

Regardless, I tried sniffing the localhost with RawCap. I can see the packets coming from Packet Sender. I can't see any UDP at all from MUSHClient, and it still returns with code 0.

Am I missing something obvious here?
Australia Forum Administrator #2
I tested just then with the example plugin on this page:

http://www.gammon.com.au/forum/bbshowpost.php?id=8716

When installing I initially got this message:



I clicked "unblock". Then using the test script, it worked:


/UdpSend ("127.0.0.1", 4112, "Hi there")  --> Got UDP packet: Hi there


Can you try that please?
#3
Unfortunately, I'm not using Windows Firewall.

I monkeyed around with suspending my firewall and turning the Windows one back on, to no avail. I didn't receive any messages about blocking, and it still didn't work.

Finally, I just turned ZoneAlarm off entirely, and suddenly, I could see the packets. MUSHclient is a trusted program in ZA, so it shouldn't have problems, but for some reason, apparently it still does, and just suspending the firewall did not stop them. I had to turn it off completely. I haven't found a work-around yet that doesn't involve leaving my computer exposed or finding a new firewall, but if I do, I'll post my findings here.

Thanks for the input, Nick! You do a phenomenal job supporting your users.
Australia Forum Administrator #4
There must be some rule you can put into ZoneAlarm. Bear in mind it's a UDP packet, not a TCP one.