Traffic to own public key address not routed

[nagy]

It should be possible to find a route to the own public address (not routing via IP, but direct public key addressing). This can be useful in e.g. yggmail where you want to send an email to your own address.

---

Old description ( likely just an issue on my side ) :

Currently, when I try to ping my own yggdrasil address, I get no response. Can we allow that the traffic to the own address is being routed?

This would allow for the convenience of having a unified machine configuration across a multitude of machines. Meaning, that I could have the same ssh config or the same /etc/hosts file for a set of different machines and all hostnames are still reachable.

[xandaaah]

Do you have a firewall on? It may be interfering, as it works on my machine.

[nagy]

I was investigating that before and explicitly turned off the firewall and it did not help. Therefore I figured it must yggdrasil. Let me check if I can reproduce this on another machine.

[nagy]

You were right. On another machine it works. I still cannot explain why my ping is not responding locally even with an empty firewall table, but that is another issue. Thank you for your help.

[NikitaPuzyryov]

I'd suggest reopening. I suspect own routing works when using IPs, because route gets shortcircuited inside the kernel (no clue why I'd doesn't work in your case though). But when using routing by key—packets indeed are not routed properly inside yggdrasil. It is every evident when trying to send yggmail to self.

I remember reporting it on Matrix, but never got around filing an issue 😅

[nagy]

I have adapted the initial comment to reflect this.