" Windows Defender by default does not limit any outbound connections. " > This depends on the security policies and the version of the windows; windows blocks every new program for outbound without even the pop up asking if user wants to allow.
" The inbound allow is needed since OrBit needs to "listen" for the car to find it, which is an incoming connection hence blocked by default with the Defender firewall (or any firewall for that matter)"
Tanks for the info, I did not know that car actually opens the first session towards Orbit / VIDA using specific destination UDP port "13400" that Orbit listens to.
I checked the VIDA too, it listens to UDP 13400 and TCP 24200 + ( ANY TCP PORT from source 13400 tcp ) ports and creates the firewall rules during installation!
I guess, that's why Orbit worked for me from the beginning!
" The inbound allow is needed since OrBit needs to "listen" for the car to find it, which is an incoming connection hence blocked by default with the Defender firewall (or any firewall for that matter)"
Tanks for the info, I did not know that car actually opens the first session towards Orbit / VIDA using specific destination UDP port "13400" that Orbit listens to.
I checked the VIDA too, it listens to UDP 13400 and TCP 24200 + ( ANY TCP PORT from source 13400 tcp ) ports and creates the firewall rules during installation!
I guess, that's why Orbit worked for me from the beginning!