Internal routing issue with RT-AC66U

[toxaris]

Hello.

I have quite complex network at home.
And I have a strange routing behavior.

I have done a map of my network for you to look at.

This picture here (OneDrive)

This works for example:
-Infra01 can reach all clients in the network.
-Client1 can reach all clients in the network.
-RT-AC66U can reach all clients in the network.
-All client have internet access.

This does not work:
Client2, Client3, Infra02, Infra03 only reach clients on the 192.168.1.0 and 192.168.2.0-network but cant reach any clients on 192.168.0.0-network except RT-AC66U (192.168.0.1).

In other words, there is some strange issue when clients on ether 192.168.1.0 or 192.168.2.0-networks try's to reach anything on 192.168.0.0 network except the gateway RT-AC66U (192.168.0.1).

If I do a tracert from Client1 (192.168.0.2) to Client2 (192.168.2.2) it ends up with three hops. Working as expected.
1: RT-AC66U (192.168.0.1)
2: Infra01 (192.168.0.82)
3: Client2 (192.168.2.2)

But if I do a tracert the other way around, Client2 (192.168.2.2) to Client1 (192.168.0.2), I get this.
1: Infra01 (192.168.2.1)
2: Timeout
3: Timeout
...

What is wrong here?

 

[phibertron]

my guess is that the routing table one Infra01
It shows 192.168.2 as being on Nic2
But in your diagram you show 192.168.2 as being on Nic3

 

[L&LD]

Very impressed with your network map, which program did you use to create that?

As for the question; does setting up Static Routes on the RT-N66U solve these issues for you?

Go to LAN and click the Route tab to setup Static Routes.

 

[toxaris]

@phibertron, it might be confusing. But the Hyper-V host have 3 NICs. But the NIC 1,2 and 3 isnt the same number as its Internal Hyper-V Switch.
Hyper-V Host Configuration.
NIC 1: 192.168.0.10/24 (Management NIC)
NIC 2: 192.168.0.82/24 (Bound to Hyper-V External switch "External 1")
NIC 3: 192.168.2.1/24 (Bound to Hyper-V External Switch "External 2")

And by the way, dont get confused but the naming convention on the Hyper-V switches.
In Hyper-V there is three types of virtual switches, External, Internal and Private. That's why they are named like this.

Internal = Both the virtual machines and the host is connected to this virtual switch bound to the same NIC. Some sort of bridge so to say .
External = Bound to its own physical NIC only.
Private = A virtual switch that isn't bound to any physical NIC and cant talk to the host.

@L&LD, I made the map by hand in OneNote actually
There is two static routes on RT-AC66U:
Network NetMask Gateway Metric Interface
192.168.1.0 255.255.255.0 192.168.0.82 5 LAN
192.168.2.0 255.255.255.0 192.168.0.82 10 LAN

If I for example remove those routes, then clients on 192.168.0.0 cant ping clients on 192.168.1.0 or 192.168.2.0 networks. So I believe these are correct.

 

[L&LD]

OneNote, cool!

Sorry, I got mixed up and thought you were running the N66U. RT-AC66U it is.

If you add a static route to 192.168.0.2, does it work?

 

[toxaris]

OneNote, cool!

Sorry, I got mixed up and thought you were running the N66U. RT-AC66U it is.

If you add a static route to 192.168.0.2, does it work?

Hmm, interesting thought. I'll try that just to se what happens.

 

[toxaris]

@L&LD, actually, if I put in this route on RT-AC66U Client2 (192.168.2.2) can reach Client1 (192.168.0.2).
Network Networkmask Gateway Metric Interface
192.168.0.2 255.255.255.0 192.168.0.1 2 LAN

 

[L&LD]

@L&LD, actually, if I put in this route on RT-AC66U Client2 (192.168.2.2) can reach Client1 (192.168.0.2).
Network Networkmask Gateway Metric Interface
192.168.0.2 255.255.255.0 192.168.0.1 2 LAN

So, this solves it for you?

If I'm not mistaken, Static Routes are one way by default, if you need access both ways then you need a rule for each.

 

[toxaris]

Well not realy, cos now I can only reach 192.168.0.2 from clients on 192.168.1.0 and 192.168.2.0 networks.

So thats more of a workaround to reach on client.

One interesting thing is that now with this configuration the traffic doesn't hop on RT-AC66U.
If I do a tracert from Client2 (192.168.2.2) to Client1 (192.168.0.2) thers only two hops.
1: Infra01 (192.168.2.1)
2: Client1 (192.168.0.2)

Should there be three hops?
Like This.
1: Infra01 (192.168.2.1)
2: RT-AC66U (192.168.0.1)
3: Client1 (192.168.0.2)

 

[L&LD]

I think that's the switches doing their jobs.

But now that I look at it closer, can you put a Static Route on the Hyper V Host?

 

[toxaris]

Yes, Infra01 is a Windows 2012 R2 server that acts as the router.
I have installed RRAS and enabled IPv4 routing. That is basically what I have done so far.