Check any firewall settings - I've had a lot of issues with macs (especially on 10.5) that are set up conservatively, and the firewall is blocking MaxMSP.

Als - give [mxj net.maxhole] a quick try (probably the help file is all you need - boot it on both computers). If you can't get maxhole communicating then it's probably a network setup issue, rather than a MaxMSP problem.

HTH

A.

shutted down it, all the same.

wireshark gets messages... it means the network is ok :-(

trying to troubleshoot that... without any success :-(

Try in terminal ping 192.168.0.30 . If it's nothing occurs, ports aren't fowarded, see your router config.

no router only a basic LAN with a 24bits mask ip range ping is ok

For both computers ? ping computer A on your computer B and inverse… You are in local network ? Are you in automatic ip config ? Have you indicate the port used to your object udpreceive ? And the ip and the port to your object udpsend ? Ad/

no problem for network connectivity. static ips ip/port on udpsend port on udpreceive => and this one seems to receive ONLY on the loopback

did you try maxhole? If so - you got nothing?

A.

maxhole are multicast I guess. it doesn't fit with my emitter :-(

Which port ? Post your patch, because that should work without any problem

I'm sending basic osc over udp message from one side (I'm sure of this part because I can trace it on the receiver computer with a basic eth sniffer) one more thing, the message captured are basically osc/udp standard.

and the patch on the other side is:

... only that.

one more (so strange) thing: instancing udpreceive 9999 in max seems to correctly open the port (netstat -ap UDP shows that) BUT the bind s for the 0.0.0.0 address. nothing for 127. and for my 192.

change the port maybe… plenty of issues with 9999 apparently…

I tested a lot of ports. when I change the port in the max object, the previous socket seems to be correctly killed (nothing appears in netstat)

all the same.

as I wrote, it is strange. because 0.0.0.0 means, AFAIK, all the network interfaces. so it should include listening on my 192.

I am not sure where in the network stack Wireshark operates but it may be possible that your system has a firewall that is blocking your port. It wouldn't block a packet sent to the loopback address so I would check for a software firewall. What system are you running the server (udpreceive) on?

no firewall for sure. I found the problem! I had a DOUBLE persistent route to 0.0.0.0. probably my juniper network connect VPN ssl client :-( now it is ok. it was the problem :) ...thanks christopher!

that double route gave problem to bind the port correctly (curious) I didn't dig much, because it wasn't the purpose :)