In Unix, all is a file, did you try to look inside the /proc/net
directory to find your local IP ?
Then, [text] can be used to load a specific file.
++
Jack
Le 17/12/2017 à 14:59, Roman Haefeli a écrit :
> On Son, 2017-12-17 at 10:48 +, Andy Farnell wrote:
>
>> If the server is brokering t
On Son, 2017-12-17 at 01:41 +0100, Roman Haefeli wrote:
>
> If there's no easy way, I might turn that into a feature request for
> iemnet's [udpclient] and [tcpclient] to print the src IP address and
> src port on the status outlet. Does that make sense?
Here it is:
https://git.iem.at/pd/iemnet/is
On Son, 2017-12-17 at 10:48 +, Andy Farnell wrote:
> 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
> addresses.
>
> But I guess you wa
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
addresses.
But I guess you want to use the server to do peer discovery
and then havin
Le 17/12/2017 à 01:41, Roman Haefeli a écrit :
>
> On Sam, 2017-12-16 at 21:26 +0100, Jack wrote:
>> Your router has a public and local IP. So, i guess your local machine
>> has only a local IP. Then, your local machine need to pass through
>> your
>> router to access remote server. Your router ha
Hi Roman,
I'm not sure but may be these two croos-platform apps will help sending and
analyzing received packets:
https://packetsender.com/
https://www.wireshark.org/
Salutti,
Lucarda.
Mensaje telepatico asistido por maquinas.
On 12/16/2017 9:41 PM, Roman Haefeli wrote:
On Sam, 2017-12-16
On Sam, 2017-12-16 at 21:26 +0100, Jack wrote:
> Your router has a public and local IP. So, i guess your local machine
> has only a local IP. Then, your local machine need to pass through
> your
> router to access remote server. Your router has NAT rules to know
> which
> local machine to route th
Hello Roman,
Your router has a public and local IP. So, i guess your local machine
has only a local IP. Then, your local machine need to pass through your
router to access remote server. Your router has NAT rules to know which
local machine to route the content from the remote server.
I don't real