[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2222
  • Last Modified:

VYATTA Router VM on VMware Workstation 7 VNET and intermittent connectivity issues

Helloooo experts....

Ok so this is my situation...

I am running a LAB VMware Workstation 7 on my laptop with the following config...

(1) Vyatta Virtual router with (3) interfaces
  eth0= 10.10.5.5 - Bridged
  eth1=10.10.4.5 - Bridged
  eth2=10.10.3.5 - Bridged

(2) OpenFiler Virtual SANs with (2) interfaces each.

Filer1:
  eth0= 10.10.5.10/24 - Bridged
  eth1=10.10.4.10/24 - Bridged
  GW=10.10.4.5 eth0

Filer2:
  eth0=10.10.4.11/24 - Bridged
  eth1=10.10.5.11/24 - Bridged
  GW=10.10.4.5 eth0

Local host:

  LAN: 10.10.3.50/24
  GW: 10.10.3.1

Internet router
  LAN: 10.10.3.1/24
  Static routes:
  10.10.4.0 > 10.10.3.5 Metric 1
  10.10.5.0 > 10.10.3.5 Metric 1

Diagram:

 Lab diagram
Now this is my issue... While routing works... I am getting intermittent connectivity to the router and the nodes behind it.

I have tried updating the Vyatta router. I had RIP enabled, which is now disabled but i cant get my head around what the problem is.

At one point i had the filers on a private LAN but i want to be able to serve them out to real machines so that wont work for me.

Not being an expert in VMware Workstation, I am wondering what i could be doing wrong here.
ICMP is intermittently dropping packets from my workstation to the filer and router interfaces.

It is oddly algorithmic actually.

See below:
 Ping from workstation 10.10.3.53 to router 10.10.3.5
Now i don't know if setting all of my hosts to bridge mode is supported so it could be that i am completely screwing the pooch.. But theoretically it seems like it should work.

I have been having a tough time getting help here recently. Not sure if i am in the right place but i figured i would give it a shot.

Any assistance would be greatly appreciated.

Thanks!

P
0
pacman_d
Asked:
pacman_d
  • 4
  • 2
1 Solution
 
pacman_dAuthor Commented:
One more thing...

Interestingly enough.. I can Ping any FQDN from the VYATTA virtual machine without interruption.
So this issue seems to be relegated to requests coming from my workstation to the VMs.

Thanks again.
0
 
bgoeringCommented:
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
0
 
pacman_dAuthor Commented:
Hey BG,

Appreciate you jumping in here. I have configured as you have suggested but this is the thing.

Nodes outside of my laptop cannot hit the Filer nodes.

My original thinking was that if i had everything bridged, that it would be just like a switch and the router would simply manage the connectivity to the nodes.

The filer 10.4.x and 10.5.x interfaces would be in a single broadcast space so i figure, no issue there.
Its really just i want to route in and out of the 10.10.3.5 router interface to the other internal subnets.

I will be using a VM to test the iSCSI and NAS share connectivity and it will be on the 10.10.4.x subnet so no worries there.

But this lab for me is also to test vyatta routing, and one of my goals is to set up routing so that i can manage from other machines. 3.x

I am not as familiar with workstation as I should be It could very well be that i simply do not understand the way the Vswitch and routing work in VMware workstation.

But my thinking was that if i had a (3) interface Virtual router set up with (1) 3.x) bonded to my bridge interface (as you suggested) and interfaces (4.x -5.x) bonded to "host only" , that it would route ok.

The the filer gateways are pointed to the vyatta router on 4.5 eth0 (as to have only (1) gateway for the node not confuse them.

Am i just going about this all wrong? Is it reasonable to have this type of configuration on workstation?

I think i am close, My time has been tight the last couple of days so i will try to respond and act quickly.

What are your thoughts?

Thanks,

P




 
0
 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

 
bgoeringCommented:
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.
0
 
pacman_dAuthor Commented:
Hey BG,

Originally I had OSPF enabled. Then RIP.... Routing was working but the challenge was the odd intermittent drops in ICMP and general connectivity.

I will try again and get back to you.

Thanks,

P
0
 
pacman_dAuthor Commented:
Hey BG,

Ok so I made the changes and routing across all of my internal subnets are good to go.

I was still having a problem with my 4.x and 5.x  subnets routing all the way out past my WAN interface on my internet router but got that figured out.

With these Fios routers you not only need to add the routes back to the indirect subnets, you apparently need to bind to the connection additional IPs for these subnets (in my case 10.10.4 and 5.x respectively for the router FW to allow the return traffic to these next hop subnets.

Your basic analysis was right on point so thanks!

I am all good with full routing and resolution for all of my nodes.

Thanks!

P
0

Featured Post

Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now