Re: Checking refusal of a network connection

On 2019-06-03 14:54:29 +0200, Markus Elfring wrote: > > How would this conversion take place? Localhost is 127.0.0.1. > > Localhost6 is ::1. They are different > > My configuration file “/etc/hosts” provides the following information > as usual. > > “… > ::1 localhost ipv6-localhost

Re: Checking refusal of a network connection

> How would this conversion take place? Localhost is 127.0.0.1. > Localhost6 is ::1. They are different My configuration file “/etc/hosts” provides the following information as usual. “… ::1 localhost ipv6-localhost ipv6-loopback …” > and you cannot route between the two. I got o

Re: Checking refusal of a network connection

On 01Jun2019 12:57, Dennis Lee Bieber wrote: On Sat, 1 Jun 2019 15:33:43 +0200, Markus Elfring declaimed the following: I don't know "strace" (I'd likely be running WireShark to capture all traffic for investigation). Sure, but that means you need to winnow it from any other traffic.

Re: Checking refusal of a network connection

On 2019-06-01 20:44:29 +0200, Markus Elfring wrote: > > Which specific information in that man page contradicts what I wrote? > > We can agree that the mentioned IP addresses are distinct. > But the corresponding functionality should be equivalent. > > > > If you think of > > > > | IPv4 connecti

Re: Checking refusal of a network connection

> It looks like the service isn't listening at the time the so.connect is > called. * I get an other impression from the programs “/usr/bin/netstat” and “/usr/bin/ss”. * The data transmission seems to work also for my small script “socket-send_test_data1.tcl” (even when the identification “:

Re: Checking refusal of a network connection

> Which specific information in that man page contradicts what I wrote? We can agree that the mentioned IP addresses are distinct. But the corresponding functionality should be equivalent. > If you think of > > | IPv4 connections can be handled with the v6 API by using the > | v4-mapped-on-v6 ad

Re: Checking refusal of a network connection

On 2019-06-01 20:22:39 +0200, Markus Elfring wrote: > >> I would expect that the IPv4 address from such a connection attempt > >> would be automatically converted to a IPv6 loopback address. > > > > You haven't said which OS you are using, but as far as I know this > > expectation will be frustrate

Re: Checking refusal of a network connection

>> I would expect that the IPv4 address from such a connection attempt >> would be automatically converted to a IPv6 loopback address. > > You haven't said which OS you are using, but as far as I know this > expectation will be frustrated at least on Linux: There ::1 and > 127.0.0.1 are distinct ad

Re: Checking refusal of a network connection

On 06/01/2019 11:15 AM, Markus Elfring wrote: >>> connect(3, {sa_family=AF_INET, sin_port=htons(37351), >>> sin_addr=inet_addr("127.0.0.1")}, 16) = -1 ECONNREFUSED (Connection refused) >> >> Without seeing the code, I'd be suspicious of that difference. > > I would expect that the IPv4 addre

Re: Checking refusal of a network connection

On 2019-06-01 19:15:28 +0200, Markus Elfring wrote: > >> connect(3, {sa_family=AF_INET, sin_port=htons(37351), > >> sin_addr=inet_addr("127.0.0.1")}, 16) = -1 ECONNREFUSED (Connection > >> refused) > > Without seeing the code, I'd be suspicious of that difference. > > I would expect that the

Re: Checking refusal of a network connection

>> connect(3, {sa_family=AF_INET, sin_port=htons(37351), >> sin_addr=inet_addr("127.0.0.1")}, 16) = -1 ECONNREFUSED (Connection refused) > > Without seeing the code, I'd be suspicious of that difference. I would expect that the IPv4 address from such a connection attempt would be automatica

Re: Checking refusal of a network connection

> Also, it can be very useful to strace the client process, eg: Do you find the following background information more helpful for the desired clarification of unexpected software behaviour? elfring@Sonne:~/Projekte/Python> LANG=C strace -e trace=network /usr/bin/python3 socket-send_json_data.py

Re: Checking refusal of a network connection

On 31May2019 17:35, Markus Elfring wrote: I can start a service as desired. elfring@Sonne:~/Projekte/Bau/C++/test-statistic-server1/local> ./test-statistic-server2 & /usr/bin/ss -t -l -p -H|grep test [1] 8961 waiting for connections server_id: localhost server_port: 35529 LISTEN 0

Re: Checking refusal of a network connection

> Well, providing minimal code samples that produce the problem would be > a start. I prefer an other approach to clarify relevant software configuration differences. > Otherwise we are just guessing... I can offer other data before. > Maybe you have a firewall problem. I hope

Checking refusal of a network connection

Hello, I can start a service as desired. elfring@Sonne:~/Projekte/Bau/C++/test-statistic-server1/local> ./test-statistic-server2 & /usr/bin/ss -t -l -p -H|grep test [1] 8961 waiting for connections server_id: localhost server_port: 35529 LISTEN 0 123 [::1]:35529