I would change the setup where instead of bridging all connections to your physical NIC, only bridge the 10.10.3.5 interface on Vyatta. Use host-only networking for the other two network. You should already have a host-only network on vmnet1, use that for your 10.10.4.x network. Use Manage Virtual Networks to create another host-only network on vmnet2 and use that for the 10.10.10.5 network.One question - what are you using the Openfiler to serve? If a VMware software (or dependent hardware) adapter is to be the consumer of your storage be aware that iSCSI storage (and I think NFS storage) has to reside on the same IP subnet as the VMkernel port configured to access it - not sure about other systems. In that case your storage won't work on a routed network.
You might want to check your iSCSI client and make sure it will work over a routed network.Good Luck. Hey BG,Appreciate you jumping in here. For other nodes to access your internal host-only networks, you will have to have routes configured somewhere so that they can find them.
One way to do that is if you are using RIP, OSPF, or some other routing protocol on you network - you can enable the routing protocol to vyatta and let it advertise the new 10.10.4.0/24 and 10.10.5.0/24 networks so that other machines can find them through the 10.10.3.5 gateway. You could also use static routes to accomplish that purpose - if your internal corporate LAN only has a couple of routers that may be easier.The trick is to have the routing in place so other machines can find your filers, and make sure you have a default gateway set on the vyatta so that if you clients are further away than your 10.10.3.0/24 network, the filers can find their way back to them. If your clients are on the 10.10.3.0/24 network, then instead of modifying your router configuration you can simply add some static routes on the client to find the filers.