You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
During a hackathon preparation, we wanted to set up Some/IP multicast routing.
Unfortunately, we at first didn't realize that we did not set up a specific routing, hence, the multicast messages went to the wrong network interface. We were looking at eth0, but the default route was wlan0.
We were also unsure whether the container with the Some/IP adapter was able to send/receive multicast packets to/from 239.0.0.1, since it uses veth (which is set up by kanto-cm).
For troubleshooting purposes, it would have been great to have network utilities available on the full quickstart image:
tcpdump
iperf or another tool to verify multicast works (ping 239.0.0.1 and check if there is a reply from someone)
Describe the solution you'd like
Pre-install tcpdump on the quickstart image (sdv-image-full)
More detailed documentation on the network setup, esp different setups and multicast routing for Some/IP
Additional context
It would also be great if sdv-health could verify that multicast networking is supported and the necessary Linux-level system settings are properly set (ip_forward, ip link set eth0 multicast on, ip route add ...)
It should include a test as well, e.g. sending multicast pings (Note that ICMP is different and needs to be enabled AS WELL) and checking for responses.
The text was updated successfully, but these errors were encountered:
Multicast is enabled by default. This can easily be checked with ip link show.
If there is a problem with a specific application, it can be debugged with the available tools; I don't think that adding a generic check to sdv-health will make much sense.
Is your feature request related to a problem? Please describe.
During a hackathon preparation, we wanted to set up Some/IP multicast routing.
Unfortunately, we at first didn't realize that we did not set up a specific routing, hence, the multicast messages went to the wrong network interface. We were looking at eth0, but the default route was wlan0.
We were also unsure whether the container with the Some/IP adapter was able to send/receive multicast packets to/from 239.0.0.1, since it uses veth (which is set up by kanto-cm).
For troubleshooting purposes, it would have been great to have network utilities available on the full quickstart image:
Describe the solution you'd like
Additional context
It would also be great if sdv-health could verify that multicast networking is supported and the necessary Linux-level system settings are properly set (ip_forward, ip link set eth0 multicast on, ip route add ...)
It should include a test as well, e.g. sending multicast pings (Note that ICMP is different and needs to be enabled AS WELL) and checking for responses.
The text was updated successfully, but these errors were encountered: