could not allocate udp6 stun:stun.l.google.com:19302: on Ubuntu 16.04. about ssh-p2p HOT 7 CLOSED

nmap -p 19302 stun.l.google.com
returns:

Starting Nmap 7.01 ( https://nmap.org ) at 2019-02-20 14:47 EET
Nmap scan report for stun.l.google.com (64.233.161.127)
Host is up (0.046s latency).
Other addresses for stun.l.google.com (not scanned): 2a00:1450:4010:c01::7f
rDNS record for 64.233.161.127: lh-in-f127.1e100.net
PORT      STATE    SERVICE
19302/tcp filtered unknown

Nmap done: 1 IP address (1 host up) scanned in 0.54 seconds

So it is supposed to be reachable.

from ssh-p2p.

These warnings likely indicate that the interfaces don't support IPv6. It should be safe to ignore them. Are you able to connect regardless of these warnings?

from ssh-p2p.

IPv6 is disabled by my Internet provider. I can't connect, that's nothing happens after run ssh -p 2222 127.0.0.1. It stuck and there is no console output.

from ssh-p2p.

Is it possible to use it without IPv6 support?

from ssh-p2p.

Yes, these warnings should be safe to ignore. I'll defer to someone with more ssh-p2p knowledge to help you debug. I'm more familiar with pions/webrtc, the underlying library.

from ssh-p2p.

It works as expected if openssh-server is installed and ssh-p2p server and client run on the same host.
But it still doesn't work for me if run them on different hosts. So I created the issue:
#16

from ssh-p2p.

Hi,
I have the same problem and i can't connect via ssh-p2p .. any solution for that ?
Thanks

from ssh-p2p.