[PD] IP address of local machine

Andy Farnell padawan12 at obiwannabe.co.uk
Sun Dec 17 11:48:24 CET 2017

Hi Roman, 

If the server is brokering the traffic then you never need to know 
the private network addresses as NAT will map them to public port
numbers and the router will map the returned packets back to local

But I guess you want to use the server to do peer discovery
and then having the two clients communicate directly.

Aren't there some more genral network utility objects in Pd?

In my wishes we would have:
[tcpdump] and [hping], one to dump traffic, maybe in hex to 
avoid Pd's fussiness about control characters, and one to 
craft any and all packets according to a template sent in 
a prior message.

And to get really serious about Pd as a network utility
how about [sock], an object to be set up as a raw socket?


On Sun, Dec 17, 2017 at 01:41:38AM +0100, Roman Haefeli wrote:

> in my patch. However, if both clients are in the same local network,
> they can't establish a connection because they try to connect to the
> public IP address of their own router. So, in order to overcome this
> limitation, my idea was to check if my router's public IP address is
> the same as the one of my peer. If they are, it means both clients are
> part of the same local network. In that case, they would use the public
> server to exchange each other's local IP addresses.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: Digital signature
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20171217/07f360d1/attachment.sig>

More information about the Pd-list mailing list