Hi everyone, I’m reporting this issue too.
I installed the latest version 1.5.3 Plus, after purchasing an activation code, but I’m in bridge mode and can’t use the peripherals on my network, while simultaneously accessing a folder on the ZimaOS hard drive. Pinging with Terminal works with all active IPs except the Zima IP. Is there a way to browse a shared folder in ZimaOS with a ZVM in bridge mode? In NAT mode, shared folders are detected by browsing the network with any file manager, but there’s no way to access the rest of the network behind the NAT.
In bridge mode, the ZVM can connect to other devices on the network, but it cannot connect to the ZimaOS host machine.
In NAT mode, the ZVM can connect to the host, but it cannot connect to other devices on the network.
Hello everyone…
For now, without having to configure the network with its Zima logic, I solved the problem this way…
Having a NAS on the 192.168.1.(NAS) network, the same as ZimaOS, I installed WebDAV on ZimaOS, using a port of my choice, such as 5555. I declared the ZimaOS share folder in WebDAV.
Then I created a reverse proxy rule on the NAS, calling the NAS IP on port 5555 → ZimaOS IP port 5555.
At this point, by opening any file explorer, for example in Ubuntu, I can call up the shared folder using the syntax:
WebDav Reverse Proxy NAS → ZimaOS
dav://admin@192.168.1.(NAS):5555
Obviously, it asks for a password and connects to the internal ZimaOS folder.
A bit complicated, but for now, it’s the easiest solution, without affecting the configuration. ZimaOS default
Bye bye…
Hi, same problem here. With NAT works but with bridge looks like the bridge is blocking connection from VM to Host but somehow can reach the whole subnet…. Looks like a bug to me since there is nothing that can be configured in the VM NIC settings.
Same bug here: [BUG] ZVM: network adaptor problems (no route from VM to host machine) · Issue #336 · IceWhaleTech/ZimaOS · GitHub
I need to use my reverse proxy (NPM docker) to access to my HomeAssistant home automation software (“HAOS” version) working on a ZVM.
By default, the HAOS ZVM and the Docker container NPM can’t communicate.
I currently use the two Ethernet port on a Ethenet Switch workaround :
This is generelly working, but some time, after a reboot, I need to change the ZVM ethernet port to Eth0 and some time returning to Eth1 to make this working.
In addition, each Ethenet port change in the ZVM configuration also generate a new random MAC address of the ZVM NIC and need to reconfigure my DHCP or to change the destination IP in the reverse proxy config.
So, this solution isn’t really stable and so not acceptable
We really need that de ZimaOS routing rules make possible to ZVM to communiocate with ZimaOS (ie : SMB sharing) and Docker containers seemlessly !
@777-Spider @zima-jerry The ZVM function is a very important function in Zima OS, and it need to work fine. I am sure that fixing this issue don’t need a big work.
We love Zima OS, but We need your help ont this issue 
1 Like