Pioneers is only listeneing on IPv6. It is not working on IPv4. I have tested this on source and binary builds on Ubuntu 16.04 and Arch Linux. Even trunk exhibits the same behavior. This problem doesnt exist on Windows build.
My testing platform is Debian Testing. netstat shows only IPv6 for the listening port, but I can still connect with IPv4 (nc -4 localhost 5556)
It seems that I have IP-forwarding turned on:
cat /proc/sys/net/ipv4/ip_forward shows 1
Apparently I changed the setting on my development machine, I'll have to investigate further.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Even on cloud, I tried on Azure VMs I was not able to make connection from
outside to the service listening on IPv6 port only. Pioneers works fine on
Azure VM when hosted on Windows as it is binding on IPv4. None of the
public cloud providers supports IPv6.
My testing platform is Debian Testing. netstat shows only IPv6 for the
listening port, but I can still connect with IPv4 (nc -4 localhost 5556)
It seems that I have IP-forwarding turned on:
cat /proc/sys/net/ipv4/ip_forward shows 1
Apparently I changed the setting on my development machine, I'll have to
investigate further.
Status: open Group: Created: Mon May 11, 2020 08:14 PM UTC by Kunal Deo Last Updated: Mon May 11, 2020 08:14 PM UTC Owner: Roland Clobus
Pioneers is only listeneing on IPv6. It is not working on IPv4. I have
tested this on source and binary builds on Ubuntu 16.04 and Arch Linux.
Even trunk exhibits the same behavior. This problem doesnt exist on Windows
build.
For what it's worth, I've been testing the server on a local machine (Debian buster), EC2 (AWS Linux based on RHEL), and a Docker container (again based on Debian) and the networking works on all of them. This is using the console server.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I would like to help here, but I'm at a loss.
How can I reproduce your test case? I don't have AWS or Azure accounts.
Can you point me to a specific hostname:port where I could try to reproduce/diagnose the issue?
With kind regards,
Roland Clobus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My testing platform is Debian Testing. netstat shows only IPv6 for the listening port, but I can still connect with IPv4 (nc -4 localhost 5556)
It seems that I have IP-forwarding turned on:
cat /proc/sys/net/ipv4/ip_forward shows 1
Apparently I changed the setting on my development machine, I'll have to investigate further.
Even on cloud, I tried on Azure VMs I was not able to make connection from
outside to the service listening on IPv6 port only. Pioneers works fine on
Azure VM when hosted on Windows as it is binding on IPv4. None of the
public cloud providers supports IPv6.
On Tue, May 12, 2020 at 1:01 PM Roland Clobus rclobus@users.sourceforge.net
wrote:
--
Kunal Deo
Twitter: http://twitter.com/kunaldeo
Related
Bugs: #305
To clarify this further. It seems this issue is only with Azure VMs. Google
Cloud Platform VMs are working fine with only listening on IPv6.
For what it's worth, I've been testing the server on a local machine (Debian buster), EC2 (AWS Linux based on RHEL), and a Docker container (again based on Debian) and the networking works on all of them. This is using the console server.
Hi,
I would like to help here, but I'm at a loss.
How can I reproduce your test case? I don't have AWS or Azure accounts.
Can you point me to a specific hostname:port where I could try to reproduce/diagnose the issue?
With kind regards,
Roland Clobus
I'm adding the 'NEEDINFO' marker. If no additional information is provided, this ticket will be closed during the next round of ticket maintenance.