Configure two subnets with a default gateway for efficient data sharing.
Configure two subnets with a default gateway for efficient data sharing.
Hi, I understand you're setting up a small test network for learning. You have eight devices, two subnets, and two different default gateways. You're thinking about whether to buy one or two routers—maybe a TP-Link AX50 would work. Devices 1 and 2 are on different subnets but need to communicate. If you want them to share data despite the subnet split, you'll likely need to connect them properly. For a local network without internet, port forwarding isn't necessary unless you're accessing external services. It sounds like you're just building a simple lab setup.
To connect various parts of a network, it makes sense to place them across separate subnets. This setup allows for organized traffic flow and simplifies security management by using firewall rules to enable communication between them.
The client aims to accomplish something specific using Ubiquiti devices, as they are familiar with them and confirm their compatibility.
I'm going to sound like a total jerk here, but maybe you should just let the pros handle it. Subnets are built for separation, so you always need a device on both sides that acts as the "gateway" for communication between them (see where this phrase comes from?). In enterprise equipment, this gateway is usually a firewall, while at home it's typically the router (your LAN and WAN also form separate subnets). When choosing a device to manage this, the most affordable Cisco small business router is likely your best option for handling all the requirements. I'm not going to walk you through everything because it's not a straightforward setup. This brings me to the point of curiosity—why are you trying to replicate this at home? It sounds like you're aiming for a very specific industrial configuration.
I’m preparing the test bench for your needs. It won’t involve the entire network setup at the final stage. The goal is to verify devices in their final configuration working together. The PLC functions perfectly on a single network, but I need to confirm compatibility with specific IP addresses. I’m considering using one or two routers and port forwarding to test connectivity. If possible, I’ll look for someone local who can set up an Ubiquity or Cisco switch for this quick 10-minute check.
Naturally, by default all devices on subnet 1 won't communicate with those on subnet 2 unless the IT team has set up the gateway properly. This approach actually supports the goal of testing beyond the final setup.
It relies heavily on the intended layout and purpose. I question the viability of a single TP-Link AX50 since it likely features switched ports, not routing ports (except WAN and the connection to the switching fabric). If you opt for two routers, you’ll also need a third network for linking them, plus a method for them to recognize each other’s networks—like static routes or dynamic protocols. This would change the overall structure unless you clarify the final setup. It’s probably a yes, but it hinges on your goals and network design.
It reminds me of situations where someone assumes the only issue is a minor detail, thinking help will be easy. In reality, each step becomes a hurdle, turning what should be simple into a complex, time-consuming task with many questions. I strongly suggest you reconsider unless there’s a compelling reason.
At this stage, we lack clear network details, so the result could differ vastly from what you expect. Just as with choosing a CPU before building a PC, knowing the components isn’t enough—physical and configuration specifics matter. If you’re planning a future build, testing now would save countless hours later.
I agree, I’d rather avoid that task, but I think they’re trying to confirm that if it fails after installation, it’s due to configuration issues, not device faults. I’d rather not face that, but I guess they doubt their internal team? They want me to demonstrate functionality in one city so I don’t have to travel to another just to verify my work, and it seems the IT person might have missed something in the firewall. I plan to try altering the subnet mask to see if it resolves the problem—I realize it’s more challenging than I anticipated. My initial thought was to use two different subnets on opposite sides of a router, allowing traffic between them, but it definitely doesn’t seem that straightforward.
It's quite straightforward in some aspects, yet the challenge lies in ensuring the device works consistently across similar situations rather than just in isolated tests. Failing to simulate real-world usage can lead to misconfigurations or mistaken faults in subnet routing.