Gateway mDNS discovery timeout on localhost prevents connection to CDA

[ayeshachittivelu]

I am attempting to connect the Classic Diagnostic Adapter (CDA) to the SOVD Gateway (sovd-server) in a local development environment (Ubuntu/Linux). While both components are running successfully on the loopback interface (127.0.0.1), the Gateway is unable to discover the CDA via mDNS, leading to a timeout and preventing the CDA components from appearing in the Gateway's aggregated list.

Steps to Reproduce:

1. Start the ECU Simulator bound to 127.0.0.1:13400.
   

2. Start the CDA with --tester-address 127.0.0.1.
   

3. Verified that http://127.0.0.1:20002/vehicle/v15/components returns the ECU list correctly.
   

4. Start the SOVD Gateway in gateway mode: cargo run --bin sovd-server -- 127.0.0.1 8000 telematics --sovd-mode gateway
   

5. Request components from the Gateway: curl http://127.0.0.1:8000/v1/components
   

Expected Behavior: The Gateway should discover the CDA instance (via mDNS or static configuration) and include flxc1000 / flxcng1000 in the aggregated items list.

Actual Behavior: The Gateway logs an mDNS timeout error: ERROR [sovd_server::server_config] mDNS browse timed out or no matching service found. Manual overrides via environment variables (e.g., SOVD_REMOTE_COMPONENTS) appear to be ignored if the component is defined in sovd_server_apps.conf.

Environment:

OS: Ubuntu 24.04 (or your version)
OpenSOVD Version: 0.1.0 (as seen in logs)
Networking: Localhost/Loopback

Additional Context: Even when providing a static URL in sovd_server_apps.conf, the server persists in trying to resolve the instance via mDNS. This makes local development difficult when mDNS reflection is not configured or supported on the loopback interface.