How do I setup Inter-vlan routing on a Netgear router FVS318N?

[kambizd]

Hi,

This is my very first post in here, so please go easy on me...

PROBLEM:

Anyway, I have several embedded linux systems, All connected to a window 7 system. The Window system has a default IP address of 169.254.0.100 and has a DHCP server running on it, which allocates addresses to the embedded linux blades in the 169.254.0.x subnet.

The linux systems are separated by sets of 3 or 5 CPUs, and we do not want to allow one of these( in each set) to talk to the Window 7 server. But all of the blades need to talk to each other. So, we do have a separate subnet 169.254.1.x for all of the blades. This way, they can all talk to each other, but only the ones that are on the 169.254.0.x can communicate with the Windows7 pc. The single blade which we do not want to communicate with the windows PC will always have the same IP address of 169.254.1.199. So if all of these were connected to the same switch, we could potentially end up with multiple nodes with the IP address of 169.254.1.199 on our network.

MY SETUP (using a Netgear GS724T switch and a Netgear FVS318N router):

So, here is what I have as far as a setup goes:

I have put each of these sets of 3 or 5 CUPs on their own separate VLAN connected to the  Netgear GS724T switch. so I have the following (I am using sets of 3 CPUs here for simplification):

               IP of 169.254.0.1 and 169.254.1.1 << same system but two different IP addresses ( port 3 of the switch)

               IP of 169.254.0.2 and 169.254.1.2 and  << same system but two different IP addresses for (port 4 of the switch)

               IP of 169.254.1.199  << single CPU that we do not want to connect to the WIN7 PC, but want it to talk to the other 2 cpus above. (port 5 of the switch)

all on the same VLAN, say VLAN4

and another set of 3 CPUS on its own VLAN, say VLAN5 (as follow):

              IP of 169.254.0.3 and 169.254.1.3 << same system on two separate subnets (port 8 of the switch)

              IP of 169.254.0.4 and 169.254.1.4 << same system but on two separate subnets (port 9 of the switch)

              IP of 169.254.0.199  << single CPU with hard coded address that we do not want it to connect to the WIn7 PC, but can talk to the above 2 CPUS. (port 10 of the switch)

And I have the WIN7 PC on it's own VLAN, say VLAN1 (or the default VLAN of the switch) on port 2 of the switch. 

This setup does provide the isolation that I am trying to get keeping each of the CPU sets connected together, but keeping them from connecting to the other set of CPUs, BUT, it does not let me connect to my Windows PC, which is on a separate VLAN(VLAN6). So I need to have the traffic on VLAN4 and 5, to get to VLAN6.

I have followed the instructions outlined by Netgear in this article from Netgear support , which sets up a trunk line to a router (Netgear FVS318N) and connects all of the incoming VLANs to the WAN port. But I am not trying to get these out to the WAN port, rather, I need to get the packets from one VLAN to be routed to my VLAN1 of the switch.  (The Trunk line is set-up on port 1 of the switch connected to port 1 of the router. )

QUESTIONS:

Is this possible with what I have? and if so, how can I do it?

I have configured each VLAN with it's own routing IP address on the switch, But the router does not allow me to set-up routes to route packets from one VLAN to another. How is the Inter-vlan routing done with the Netgear equipments, their documention is horrible and is pretty much non-existent when it comes to inter-vlan routing. 

Any suggestions, comments, alternate approaches, pointer to documentations and etc would be appreciated.  

Thanks in advance for any help.

 

 

[+BudMan MVC]

  Quote

blades in the 169.254.0.x subnet.

That is APIPA and not routable.. Why would you pick that??  Just use something in actual rfc1918 space... 10.x.x.x, 192.168.x.x or 172.16-31.x.x

There is no point in reading the rest of your issue, you can not route that address space - pretty much every device that routes will not route them...

But in general you do not have to add routes to a router for its own connected networks, if will know that it has network a.b.c.d connect and a.b.c.e and will pass traffic between them without having to actually create a route.. But again that space is not routable!!!