I have one more configuration issue I'm trying to resolve with my networking configuration.
Here is the scenerio: I have a 500GB HP MediaVault that currently has an IP address of 192.168.1.50, which I defined as static. Therefore it communicates fine with all my "regular" home w/s on this same subnet. I keep all my audio, pictures, and videos here. However, the problem is the CORE hasn't mapped any CIFS shares to it, presumably because the way the CORE works it wants the HP unit to be on the 192.168.80.x subnet to discover it.
But, if I put it on this side of the LAN, I can't see it anymore from the "regular w/s" on the 192.168.1.x subnet. Acutally, I can't ping or see anything on the 192.168.80.x subnet from them.
So maybe I need some routing entries defined on the CORE so that they will see it, is this correct? If so, is this done by adding routes, and what would the entries have to say?
For example would it be the following?
$ sudo route add -net 192.168.80.0 netmask 255.255.255.0 gw 192.168.80.1 dev eth0 (eth0 being the external interface 192.168.1.100)
If I leave it the way it is now, I possibly could manually configure the network shares. But are there advantages to having the HP unit on the 192.168.80.x subnet besides the discoverabilty factor?
Thanks in advance for any input on this.
-fins
