Unable to connect private resource using alias via Pangolin Client

[3gmgithub]

Describe the Bug

When using DNS alias I cannot connect/ping remote resource.
When I use the remote IP it works just fine.
Is there something that can be done to fix the remote alias?

Environment

• OS Type & Version: Linux Mint 22.3
• Pangolin Version: 1.15.4
• Gerbil Version: 1.30
• Traefik Version: 3.6
• Newt Version: 1.9.1
• Olm Version: (if applicable) Pangolin client 0.3.3

To Reproduce

ping REMOTERESOURCE.lan

-Nothing happens and eventually fails

Expected Behavior

ping works...

[Tanki90]

same problem :-(

[kreativekrise]

The documentation says:

Aliases do not currently support ICMP ping requests. If you attempt to ping an alias, it will not respond, even if the underlying Resource is reachable. This is because the Pangolin client does not intercept ICMP packets for alias resolution.

Source: https://docs.pangolin.net/manage/resources/private/alias#icmp-ping

[miloschwartz]

@kreativekrise is correct and aliases not supporting icmp ping is currently a small quirk.

More importantly, are you able to access the resource with the alias regardless of the ping status?

[3gmgithub]

When using the local IP of the remote device I can connect no problem.

[Tanki90]

it works. i'm am idiot... need to add the port after the alias.
is there a way in private resources to select the port in the destination like in open resources?
192.168.x.x:port was not acceepted.

[3gmgithub]

I ran ssh root@alias -p 22 and it does not work.

[LaurenceJJones]

it works. i'm am idiot... need to add the port after the alias. is there a way in private resources to select the port in the destination like in open resources? 192.168.x.x:port was not acceepted.

No, as the private resources are just an alias DNS lookup for convenience it doesnt act as a proxy to know if you go to "host.internal" you want to speak to a specific port.

[LaurenceJJones]

I ran ssh root@alias -p 22 and it does not work.

Okay, can you provide these details:

• You are connected to sites via pangolin status (you should see your sites and relay information)
• Check your resolver is set to olm itself cat /etc/resolv.conf (should be nameserver 100.X)

[3gmgithub]

I am using Linux mint, and that uses systemd-resolved...
So I added a file like this:

/etc/systemd/resolved.conf.d/my-dns.conf

[Resolve]
DNS=100.96.128.1
Domains=~myalias

This seems to at least help, but does not solve the problem.
I will try adding directly to /etc/resolv.conf to see if this helps.

[3gmgithub]

No luck still having issues... Any suggestions?

[3gmgithub]

Here are some photos of the problem...

[LaurenceJJones]

So from the images, it seems the background process that handles DNS requests is being rejected. Do you have any filtering or firewall rules that could block requests to port 53 if its not localhost?

[3gmgithub]

No I did not setup anything like that. This would have to be default for Linux Mint 22.3

Are there any ideas on what to check on the backend? I will test on Windows to see if I have the same problems.

[github-actions]

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.