What's new
By:

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Recent content by toxaris

  1. toxaris

    Internal routing issue with RT-AC66U

    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.
  2. toxaris

    Internal routing issue with RT-AC66U

    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...
  3. toxaris

    Internal routing issue with RT-AC66U

    @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
  4. toxaris

    Internal routing issue with RT-AC66U

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

    Internal routing issue with RT-AC66U

    @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...
  6. toxaris

    Internal routing issue with RT-AC66U

    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...
See more
Back
Top
✖