Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote connections not working as intended #238

Open
Crook3dTeeth opened this issue Oct 21, 2023 · 1 comment
Open

Remote connections not working as intended #238

Crook3dTeeth opened this issue Oct 21, 2023 · 1 comment

Comments

@Crook3dTeeth
Copy link

With the latest version of beamngpy I can't remotely connect to a beamngpy instance on another computer. Using beamngpy version 1.26.1 works perfectly fine but 1.27 gets a WinError 10060. I've tried disabling firewalls and all that and I've used wireshark to see that the packets are making it to the host machine but nothing is being returned or showing up in the console log. I am also having latency issues when connecting remotely and locally with getting camera data which I can fix with is_using_shared_memory being set to true but this crashes when trying to use it remotely which is what I intend on doing.

@aivora-beamng
Copy link
Contributor

Hi,
for security reasons, BeamNGpy since 1.27 launches BeamNG to listen on the local network interface only by default, you can set it up to listen on all network interfaces by:

beamng = BeamNGpy('localhost', 64256)
beamng.open(listen_ip='*')

or you can set a binding IP address (see the docs) to listen on a network interface of your choice.

Shared memory cannot work with a remote host, but the user experience should be better than just crashing. We'll investigate it and put more meaningful error messages for this case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants