I know that even with me forwarding everything through the firewall the MyCloud will not connect with any of my wireless devices. (different nets)
I am also aware that setting a static IP can be problematic for the MyCloud device as well
My networking knowledge/skills are my weakest point which is why I’m asking for assistance.
Can I edit the /etc/network/interfaces file to set not only a static ip (hopefully skipping the difficulty that people have had by bypassing the UI) and set an alias interface with an ip on my wireless networks range
I do have 1 additional gigabit port available on my firewall so I could put the mycloud on that and do something in the firewall there as another solution
(dont have my actual /etc/network/interfaces so best guess)
If you want to do sub-interface, you would get into vlan tagging which is a totally different monster. Probably doable if the switches support it, but without network skills too hard.
1- Static problematic on mycloud? Where did you get that from? That is probably the best thing you can do, assign a static IP to a NAS on ANY environment.
2- Beside forwarding everything thru the firewall, if clients and NAS are in different networks, you need routes/routing. In a few words, 192.168.1.0 needs to know how to get to whatever network the NAS is at. At the same time, the network for the NAS has to know how to get back to the client. You provided the network ranges in used, however, not how is all connected and who are the default gateways for each.
But start with pinging across each network. If those fails, you might need to add routes and/or FW rules.
And finally, you will not be able to access the dashboard outside the NAS network, shares yes.
I’ve done vlan tagging - but my switches don’t support it (thought about that) - I may create the bridge in the firewall and use the two ports that do home network and wireless together and use a common dhcp set (probably best answer)
I remember reading on the forum at one point about the mycloud being touchy with static ip addresses (I’ve just used a reservation on the UTM to handle that) - I agree about servers being static ips
I have the routing setup in the firewall (in an attempt to get it working its routing all<->all) - I can ping all devices from any of the 3 networks and but none of my wireless devices can access the mycloud shares (might be a windows thing)
Probalby right about joining the wireless and hardlined networks together
The class c address are my home devices while the class a address set is for my Xen homelab (beefy HP 380G6) - It needs to be kept isolated so I can run the windows server as a ADDC plus the various services there of - very careful of the ports that route to my other networks as well as outside
If you can ping (also try ping both directions to check for fw rules, ping = icmp protocol), then routing is fine and devices can see each other. It would be just a matter of FW TCP rules, either the FW device and/or software firewall/IPtables on servers/PCs/etc.