Hello, i have my AllStar node setup and working however i cannot connect to some echolink nodes. not sure where to look for the issue.
Not leaving much info to go on. I’m sure there are some I can not connect to as well.
Don’t assume the problem is on your end.
sorry it way too long to get back, life . anyhow there is 1 particular node i have access to( its not mine) that i want to connect to , every time i try to connect to it , it says connection failed. i have the ports forwarded, and have verified that both nodes can connect to other nodes. , node number 2 can connect to me, but i cannot connect to it. it is on a totally different network. in a totally different house, in a different town. any ideas?
Why assume the issue is on your side ?
Port forwarding will only effect inbound connections. Not your complaint yet.
I might suggest you test with some other nodes (several)
It also might help if you say specifically what node numbers you are speaking about.
Can't look at what I can't see. You have blinders on me.
The echolink connection from my KQ4SBP-L TO KB4JDE.. i dont remember mine but the other is 158400. Anyhow. Its the same for these allstar nodes as well. 62033 (mine) to 55072 (the other call mentioned) ot says connection failed.
Can you explain better what you're really trying to do and what Echolink has to with it? You cannot have a non-proxied Echolink (e.g. a PC application) on the same network as an ASL node that you're also trying to configure with Echolink. You can have one or the other - but not both.
So are you trying to connect with an Echolink client (presumably KQ4SBP-L) to a remote Echolink system (KB4JDE)? If so, that has literally nothing to do with AllStarLink at all and is 100% echolink network.
Are you adding the 3 in front of the EL node number for connection purposes to EL connections through ASL ?
Is there any EL node you have been able to connect to ?
yes i am padding the node number with a 3. and yeah i can connect to most other echolinks. checked my ports again, and there fine.
The issue may not be on your end.
Maybe your target does not have port forwarding set-up or some other error.
Port issues are inbound issues. Not outbound.
So, this is outbound for you but inbound for your target.
And it can also be a networking/dns issue. For target or you.
Perhaps capture the text while ASL running in the foreground during the connection attempt and that may reveal the issue.
The echolink servers you have selected may be in error in echolink.conf.
You just have not presented anything to put some definition on it. And that would help.
To many possibilities as is.