Debug: Connect error: connection timed out.

[janikvonrotz]

Hi

I am working on an Ansible implementation of the project.

• innernet-server
• innernet-client

Basically this project sets up the server, cidrs, peers and invitation.
Eveythings seems fine, but I just fail to connect with the client.

First I tested ports:

On my client:

(venvmaster) ➜  ~ ncat 49.12.42.20 51820
hi

On my server:

root@atlas:~# ncat -l -p 51820
hi

Everything looks good.

This is the generated inviation file:

[interface]
network-name = "mintsystem"
address = "10.42.5.3/16"
private-key = "6LZ9YACiYL9nooX8u21CQdTcZMN1Osstft2Rux5GxGs="

[server]
public-key = "5Z3CNm68o0N5NOZV6Nry1FfDOOvmJ0VPqrKlPFuWlGg="
external-endpoint = "49.12.42.20:51820"
internal-endpoint = "10.42.0.1:51820"

I start the innernet-server:

root@atlas:~# innernet-server serve mintsystem

And try to install on mhy client, but if ails.

sudo inn install /var/tmp/127.0.0.1.yml
✔ Interface name · mintsystem
[*] bringing up the interface.
[*] Generating new keypair.
[*] Registering keypair with server (at 10.42.0.1:51820).
[E] failed to start the interface: http://10.42.0.1:51820/v1/user/redeem: Connection Failed: Connect error: connection timed out.
[*] bringing down the interface.
[E] Failed to redeem invite. Now's a good time to make sure the server is started and accessible!

[E] http://10.42.0.1:51820/v1/user/redeem: Connection Failed: Connect error: connection timed out

How can I debug the connection time out? Did my client reach server?

[janikvonrotz]

@amarao I tried to reproduce the issue #141

• watch interface watch $(ip link show)
• uncomment everything in gai.conf vi /etc/gai.conf
• redeem the invitation inn install /var/tmp/127.0.0.1.yml (don't mind the filename, its generated by Ansible)
• dump the interface sudo tcpdump -i mintsystem -v

I still got the connection failed issue:

[E] failed to start the interface: http://10.42.0.1:51820/v1/user/redeem: Connection Failed: Connect error: connection timed out.
[*] bringing down the interface.
[E] Failed to redeem invite. Now's a good time to make sure the server is started and accessible!

[E] http://10.42.0.1:51820/v1/user/redeem: Connection Failed: Connect error: connection timed out

And this dump:

➜  ~ sudo tcpdump -i mintsystem -v
tcpdump: listening on mintsystem, link-type RAW (Raw IP), capture size 262144 bytes
09:19:53.514733 IP (tos 0x0, ttl 64, id 24197, offset 0, flags [DF], proto TCP (6), length 60)
    10.42.5.3.57704 > 10.42.0.1.51820: Flags [S], cksum 0x1986 (incorrect -> 0x3f6e), seq 2650750376, win 64860, options [mss 1380,sackOK,TS val 220224912 ecr 0,nop,wscale 7], length 0
09:19:57.610721 IP (tos 0x0, ttl 64, id 24198, offset 0, flags [DF], proto TCP (6), length 60)
    10.42.5.3.57704 > 10.42.0.1.51820: Flags [S], cksum 0x1986 (incorrect -> 0x2f6e), seq 2650750376, win 64860, options [mss 1380,sackOK,TS val 220229008 ecr 0,nop,wscale 7], length 0
09:20:05.802724 IP (tos 0x0, ttl 64, id 24199, offset 0, flags [DF], proto TCP (6), length 60)
    10.42.5.3.57704 > 10.42.0.1.51820: Flags [S], cksum 0x1986 (incorrect -> 0x0f6e), seq 2650750376, win 64860, options [mss 1380,sackOK,TS val 220237200 ecr 0,nop,wscale 7], length 0
tcpdump: pcap_loop: The interface disappeared
3 packets captured
3 packets received by filter
0 packets dropped by kernel

At this point I am not sure what to make of it. I am also not sure if this is related to your issue at all.

➜  ~ ifconfig  mintsystem
mintsystem: flags=81<UP,POINTOPOINT,RUNNING>  mtu 1420
        inet 10.42.5.3  netmask 255.255.0.0  destination 10.42.5.3
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 32  bytes 4736 (4.7 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Any idea what to check?

root@pop-os:/home/janikvonrotz# sudo wg show
interface: mintsystem
  public key: B1N1ZnIcGyZKmiFoX6oxyOvbXODWDY8VpCrw+6A2M3M=
  private key: (hidden)
  listening port: 54448

peer: 5Z3CNm68o0N5NOZV6Nry1FFDOOvmJ0VPqrKlPFuWlGg=
  endpoint: 49.12.42.20:51820
  allowed ips: 10.42.0.1/32
  transfer: 0 B received, 5.78 KiB sent
  persistent keepalive: every 25 seconds

Currently I am intrigued by the listening port of the interface.

[janikvonrotz]

So as mentioned i tried to automate the process with Ansible and got these issues.

Whenn doing everything manually, I succeed to set up a connection.

[janikvonrotz]

So as mentioned i tried to automate the process with Ansible and got these issues.

Whenn doing everything manually, I succeed to set up a connection.