Originally Posted by bdbcat
Something a bit odd on Mac, alright.
I find that TCP output works if you set the connection address to
0.0.0.0 (which is the same as "AnyAddress" in netspeak).
For some reason the Mac network stack will not bind (i.e. open) a server if the port is set to the physical port of the server itself. But linux
seems to be able to do this.
This makes a little bit of sense; in OCPN, if the TCP connection is set as output, then O acts as a server. So he should be listening for connecitons from "anything on the specified port, e.g.10110", so to speak.
Any networking gurus are welcome to chime in with insight here. My understanding of TCP/IP is vague, especially when it doesn't work...
Anyway, please try this (0.0.0.0) and report back. If it works, I will make some adjustments to the OCPN TCP network code.
You were absolutely right to suspect this was the issue!!!
For test, I connected to Frisco AIS
on one inet connection. Then, I changed the broadcast TCP server to 0.0.0.0 and set it for repeat. This was the result (all as expected)
Then, I had my second mac (mountain lion w/3.2.2) connect to the snow leopard
mac running 3.2.2 and this was the result....SUCCESS!!!
Wooo hooo! Even if this is a bug, Im very happy it all works. Great tip to use 0.0.0.0 as the IP of the TCP server!!!