ARDOP TNC initialization failed: dial tcp [ :: 1]:8515: connect: connection refused

[Shane Engelman]

Hey there. This is my first time posting in the Group, so forgive me if I miss protocol. I've been through the existing questions and did not see a resolution.

On both MacOS and Linux, I encounter the same issue when trying to make a connection. On selection in either the web UI or command line interface, I experience the same failure, as shown in the included screenshot and described in the Subject.

I was able to connect using a Raspberry Pi and https://github.com/CarpeNoctem/pat-on-a-pi. I do not see an appreciable difference between the configurations between my other setups and the Pi. I will be happy to provide redacted configuration files on request. Has anyone else experienced this?

[Martin Hebnes Pedersen]

Hi Shane,

This is message you get when your operating system refuses to set up a connection. It's typically because the ARDOP TNC isn't running or is listening on a different TCP address/port.

I'd start by checking the ARDOPc log output, and verify that it is running.

Also, it looks like localhost resolves to a IPv6 address. I'm not sure, but it might be that ARDOPc only listens for IPv4 connections. A work around could be to replace "localhost" with "127.0.0.1" in your Pat config's ardop section.

Please keep us posted!

-- 

73 de LA5NTA / Martin

--
You received this message because you are subscribed to the Google Groups "pat-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pat-users+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/4bceee28-c92c-4ac2-9369-7718404101fcn%40googlegroups.com.

[Gmail]

Hello Martin

I have also problems with Ardopc.

The problems are only a little bit different as those of Shane.

I am using build-a-pi in combination with a IC7100.

Starting ardopc is no problem. I get a handshake with the reply that I have a connection. But then there is no further reply. The calling is going on and I am answer ing but there is no connection anymore. There is every time no ack and then it stops after a while. 

What could be the problem.

73 Ron

PD7RON

Op 8 okt. 2022 om 08:46 heeft Martin Hebnes Pedersen <martin.h...@gmail.com> het volgende geschreven:



To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/CAAUuLGmutb%2B6yAbHtEVMvchsqHh4gHOiRMSOPH%3DTrGDby8y63g%40mail.gmail.com.

[Martin Hebnes Pedersen]

Thanks John,

As I understand it, a properly configured hybrid IPv4+IPv6 system should be able to handle this with the RFC 6555 Fast Fallback mechanism implemented in Go's TCP dialer. It should also handle the most common misconfigurations.

I'm guessing the name resolution resolves localhost ONLY to the IPv6 address on his system. But this is way outside my area of expertise.

Anyway, the quick fix should be to address ARDOP using 127.0.0.1 instead of localhost in the Pat config. If that's not helping, I would guess that ARDOP either isn't running on the system or configured to listen to another port/address.

I hope you are able to get things working soon :)

-- 

73 de LA5NTA / Martin

lør. 8. okt. 2022, 09:10 skrev John Wiseman <john.w...@ntlworld.com>:

Yes, ARDOPC only listens on IPV4, so that is likely to be the problem.

73,
John

To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/CAAUuLGmutb%2B6yAbHtEVMvchsqHh4gHOiRMSOPH%3DTrGDby8y63g%40mail.gmail.com.

[Martin Hebnes Pedersen]

Hi Ron,

Your problem seems unrelated to the one discussed in this thread. Please start another thread for your issue so we don't get off topic.

PS: It would be useful if you could include some more information. Log output from both Pat and ARDOP will be useful in helping to identify the cause of your problem. Please include this when you start the new thread.

-- 

73 de LA5NTA / Martin

[Shane Engelman]

Thank you for the replies. I took the information under consideration and with quite a bit of troubleshooting on my part, was able to get this working on a newly-annointed ThinkPad with Ubuntu. I have a lot of notes for the instructions in the wiki. I will write a blog post of my exact steps and follow up.