udpreceive port not opening (binding to port 0) with an ip address

drewmcm's icon

Hi there,
sorry if this has been answered somewhere before, but I've searched and haven't found it yet.
I had a udpsend and udpreceive working a day ago on different networks using a VPN(L2TP) on a mikrotik set up on a cloud/virtual router. It is now not working even though I changed nothing, and when max opens the patch, or opens after being restarted, I get 'binding to port 0' in my max console.

here is how I have the udpreceive set on the receiving computer/network (for e.g.):
[udpreceive 192.1xx.xx.xx9 74xx]

here's how the udpsend is set up(for e.g.):
[udpsend 192.1xx.xx.xx8 74xx]

Bothe share the same ip address in the virtual router except for the last number. The receiver's VPN is on xx8, and the sender is on xx9.

All worked fine 48 hours ago - now when I open up, I get a binding to port 0, and nothing gets sent/received. Vothe computers connected to their respective VPN ip accounts and ip addresses, so I'm at a loss as to why it's stopped working.

Through the network utility it pings between the two ip addresses fine, from either computer/network and ip to the other.

Any help gratefully received

Thanks a lot

drew

yaniki's icon

Use [udpreceive] with just one parameter (port number), eg.

[udpsend 192.1xx.xx.xx8 7485] -> [udpreceive 7485]

drewmcm's icon

Oh my god thank you so much. I am such a numbnut.
When I had made the patch initially it did have the udpreceive with only the port number attached, when I set up the port forwarding I created another udprecieve and included the ip address before the port number, without noticing that I had left the other udpreceive attached! So it all worked fine.

Next day, tidied up the patch a bit, and deleted the first udpreceive with just the port number (no ip address) thinking that wasn't needed... and... aaaarrrrrgggggghhhhhhh!!!! NOT WORKING!!!! Why? Why? Why?

48 hours later a one line reply, all resolved! Thanks so much, obviously I'm not experienced with networking at all.

drew

yaniki's icon

Haha... This is just a kind of mistake that everyone commits from time to time ;-) I've always been fascinated by it: others immediately see errors in my projects that I can not find.