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

Retry connection automatically #260

Closed
plektra opened this issue Nov 1, 2023 · 1 comment
Closed

Retry connection automatically #260

plektra opened this issue Nov 1, 2023 · 1 comment

Comments

@plektra
Copy link

plektra commented Nov 1, 2023

Goal:
I am trying to run signalk-server in a Docker container with normal brigded networking in order to preserve isolation. In order to use NMEA2000 via native socketcan, the can interface(s) need to be routed via virtual vxcan kernel module and can-gw (see https://www.lagerdata.com/articles/forwarding-can-bus-traffic-to-a-docker-container-using-vxcan-on-raspberry-pi). Can interfaces are basically network interfaces which aren't published to containers running in bridge networking mode.

Problem:
Virtual CAN interface needs to be moved to the network namespace of the running container, which means that the container must be running before the can interface can be made available within the container runtime. Currently, signalk-server only loads the connections when starting the server, so there's currently no easy way to reinitialize connections once the can interface has been brought up.

Suggestion:
Introduce automatic (perhaps configurable) retry for establishing can connections.

@sbender9
Copy link
Member

I think this is fixed. Please re-open if not...

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