Forum Discussion

derek765's avatar
derek765
Dialled in
2 days ago

subnets

Setup

  • 1Gb connection
  • Hub5 in router mode 192.168.0.1 (needs to be router mode because of pod)
    • DHCP 192.168.0.2 reserved for tplink router using its mac address
  • Black pod
  • Cat 6 cable to TPLink AX50 WAN port
  • AX50 in router mode (needs to be router mode as I need functionality that is lost in AP mode)
    • AX50 Internet (WAN):
      • IP: 192.168.0.2 
      • Default gateway: 192.168.0.1
      • subnet mask: 255.255.255.0
    • AX50 LAN:
      • IP: 192.168.1.1
      • subnet mask: 255.255.255.0
    • Static link added:
      • Network destination: 192.168.0.0
      • Subnet mask: 255.255.255.0
      • Default gateway: 192.168.0.1
      • Interface: LAN


Everything works fine except I can't connect from a device on 192.168.1 to a device on 192.168.0
(I have a samba server I'd like to be able to access from both 192.168.0 and 192.168.1 - dont care which subnet its connected to if this makes things easier)

I also tried a route to 192.168.0.11 255.255.255.255 - no changes.

Have I got a config wrong/how do I resolve ? Or is this something the Hub is blocking ? Are there any workarounds. 
I guess I could probably access with cloudflare tunnelling but this seems overkill unless its the only way

TIA !

5 Replies

  • carl_pearce's avatar
    carl_pearce
    Superstar
    2 days ago

    You won't have access to devices between routers when using the WAN port.

    • Tudor's avatar
      Tudor
      Very Insightful Person
      2 days ago

      "You won't have access to devices between routers when using the WAN port."
      This is correct. You are thinking that the VM hub is a ‘real’ router, but it’s not, just a cut down device to VM specs.

  • legacy1's avatar
    legacy1
    Alessandro Volta
    2 days ago

    Add another NIC to the samba server and connect it to the TPLink AX50 LAN

  • Client62's avatar
    Client62
    Alessandro Volta
    2 days ago

    The black Pod may be free, but is totally inflexible and has already caused you to create a configuration that is very suboptimal.   Double NAT only has downsides.

    Perhaps retire the black Pod and use Hub 5 in Modem mode + the AX50 as the router,
    add an Wi-Fi AP if more wireless coverage is needed or a retail Wi-Fi repeater that can be configured to the IP range of your preference.

  • legacy1's avatar
    legacy1
    Alessandro Volta
    2 days ago

    samba to show devices uses broadcast or multicast which does not cross subnets but you can do it direct to IP so if 192.168.1.3 wants to connect to 192.168.0.100 by \\192.168.0.100 it can but if you want to connect to 192.168.1.3 from 192.168.0.100 that a whole new story beccuase it will not be \\192.168.1.3 but the routers TPLink AX50 WAN like 192.168.1.2 which brings another problem because you have to NAT port forward and then if you have another drvice on 192.168.0.50 that want to connect to say 192.168.1.40 you can't because you used the same port to NAT to 192.168.1.3

    now if the hub did Static routes and must be done on the hub for 192.168.1.0/24 gateway 192.168.0.2 then it be fine if the TPLink AX50 then accepts and does routeing without SNAT like IP 192.168.0.100 to 192.168.1.3 or 192.168.1.3 to 192.168.0.100 then it be a Asymmetrical Route unless the router in this case TPLink AX50 does Overwrite Direct Route when it routes to gateway 192.168.0.1.