I am not very experienced with networking and as I build out my services on prem I have come to this community for help and support.

I have done a lot of reading about subnets and masking and the like and I semi-understand how it works and what I want to do but I don’t know how to actually do it.

Thanks to this community I have a OPNSense Router that I installed on a desktop computer where I purchased a 2x1gb NIC to install. I’ve learned how to open ports and how to NAT/forward even with reflections for my https local services.

I just can’t figure this out. I drew my network topology and put it here: https://imgur.com/a/XY8V5Sl

My wired network is 192.168.1.0/24 meaning 255.255.255.0. My wireless is Google Nest Wifi which limits me a bit. It is using 192.168.86.0/24. The gateway for both networks is my opnsense router 192.168.1.1.

I want to create a route between 192.168.86.0/24 and 192.168.1.0/24. I believe one way to do it is to use 255.255.0.0 meaning /16 but I don’t know where to make that change and since the Google Wifi uses its own DHCP, i am not sure I can change that properly.

My preference is to leave Google Wifi alone (its a piece a shit, by the way, don’t buy it) and my expectation is that I can create a route in opnsense to ‘bridge’ the two different subnets.

Am i correct? If not, can you help me understand? If i am correct, can you guide me?

  • Kaizar@tezzo.f0rk.pl
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    1 year ago

    This will fuck your plans but you should look at internal ipv6 routing, it’s confusing at first but for situations exactly like this it’s a gamechanger.

    • knaak@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      I disabled IP6 completely… it was completely confusing and looking at the damn thing I couldn’t understand it. I figured that I didn’t need it. I guess I am missing something then.

      • Kaizar@tezzo.f0rk.pl
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        1 year ago

        https://www.youtube.com/watch?v=oItwDXraK1M best quickstart, explains how DHCP and subnets become a thing of the past and how you can basically transfer network hardware between “master” networks without having to touch a host or waste time on routing ports & co. , the main reason ipv6 is so confusing is because the engineers went overkill on the futureproofing after suffering ages of ipv4 being a combination of “temporary” solutions and outdated networking philosophies, it’s a case of “never again”.