Vopono cannot intialize due to IP address conflict when sharing internet connection over ethernet

[SocietasCooperationis]

Vopono uses the 10.0.0.0/8 IP address range. This IP address range is also used when sharing a computers internet connection via ethernet to another device. As a result, vopono cannot launch processes in network namespaces after a device connects via ethernet. Existing processes run in vopono namespaces still work properly after ethernet is plugged in.

I don't know how to investigate more deeply but I imagine adding a setting to change the IP address range used would be a temporary solution. Given that both services seem to work independent of each other so long as vopono applications are started up first, it may also be possible to make both work in 10.0.0.0/8 range and I would prefer this, though I understand that may be difficult.

[jamesmcm]

Could you add more details? If it fails to assign the IP address it should keep trying shifting to 10.1.x.x, etc. IIRC

Like what is the actual error log?

[SocietasCooperationis]

After some more investigating it appears I am mistaken. I'm connected to the internet over WiFi and sharing my internet connection over Ethernet. After plugging in the cable Vopono defaults to trying to use my Ethernet connection to reach the internet which obviously doesn't work. Specifying the correct network interface with the -i argument solves the problem.

However, doing this isn't very portable between machines (different interface names). Is there a way to make Vopono prefer WiFi over Ethernet? Or even better, be able to detect when an interface is sharing its connection with other devices and not use those interfaces?

[jamesmcm]

Hmm one way might be to support an interface prefix.

Do you know if NetworkManager or ip etc. let you know when the connection is shared like that? I can't test it myself easily.