I have noticed an unexpected behaviour of the Zynthian, regarding the way it is seen by an external computer, for Webconf settings and related operations.
When the two devices are linked through an Ethernet cable, I expect this type of connection to take precedence. Instead, if Wifi Is enabled on the Z, for it to receive updates, it appears that the wireless connection takes priority over cabled Ethernet.
This may generate confusion, if more Zynths surround the computer used to configure them, as in my case, because Webconf seems capable of detecting them all on zynthian.local, keeping as default the last one connected to the configuring computer, unless the full URL of the specifically required Zynthian is typed in the browser’s search bar.
Therefore, I have discovered that, in order to assuredly locate and configure a given Z unit through an Ethernet connection on zynthian.local, I must disable WiFi on the other units. Alternatively, I have to renounce altogether using a LAN cable, thus relying only on WiFi, and addressing each Zynthian with its specific URL (retrieved from the admin menu).
Am I missing something? There is something faulty in my workflow? Or is this behaviour expected to be normal?
I had already considered this, but would it be reflected in the way the local server (Zynthian) has to be typed?
Would a statement like:
new_zynthian_name.local
work as an exclusive connection to a specific Zynth, considering that the webconf access mask only asks for the root user password? (I’m away from home now, and thus without access to my gear).
In any case, this workaround wouldn’t solve the apparent dubious priority between Ethernet or WiFi connections on the same Zynthian.
Ideally, I would expect the connected cable to exclusively transfer data from the external computer to the Z, and the enabled Wi-Fi service to only receive from the outer Internet world.
If you call all your zynthians the same thing, they won’t know who you are talking to.
Give them different names so that you can access them as individuals.
Regarding WiFi and direct connection, they are using different name resolution mechanisms. WiFi is using DNS and the direct connection is using mDNS. The names live in different domains.
