Unusual port forwarding issue Question about configuring ports in a network setup
Unusual port forwarding issue Question about configuring ports in a network setup
Hi there, I'm not a developer, but I've taken on leading the IoT product development. The setup involves a unique network configuration where I'll place a router behind the customer's existing one to support my device. For remote access, port forwarding is essential. If I include these ports in my own router, will it continue to forward them through the customer's router? Or do I need to configure the same ports on theirs as well? Any guidance would be greatly appreciated!
This setup is really confusing and a bit frustrating. The modem handles signal conversion between different types of connections, but there are restrictions in the chipset. If your ISP offers higher speeds and the modem supports them, you can stick with the same device. Routers act as gateways, directing traffic to the ISP, managing NAT, DHCP, and other features for more advanced setups. They don’t have any issues with port forwarding, though some ISPs might restrict it unless they use CGNAT. If you bypassed a router and connected directly to a modem, you’d get just one public IP address, leaving your device exposed online—unless the consumer router adds basic security like a firewall. ISPs usually don’t care about port forwarding unless they’re implementing CGNAT, which would make forwarding pointless due to multiple layers of NAT.
Your router will redirect its network segment and that’s the end. The customer must enable specific ports on their router to direct traffic to your router for direct internet access to the IoT device. Based on the configuration, a tunnel could route data from the IoT device through your router, then to another server, bypassing port forwarding entirely—though this approach is complex and raises security concerns.
The only option that stands out beyond using a VPN is UPnP, which is why IoT gadgets aren’t ideal. They become vulnerable and can be added to DDoS attacks, making security a major concern. Home routers are generally straightforward enough for someone to identify port forwarding settings. A bigger challenge lies in the fact that not every internet service provider supports port forwarding or charges extra for it. There are also individuals unfamiliar with networking who opt for Double NAT, creating a tough situation if your IoT device needs port access. I don’t think you need a router for this setup—it would trap the IoT device behind Double NAT and make port forwarding difficult.
Setting up port forwarding across several routers tends to be more complicated. Without understanding the settings your clients use, it’s difficult to ensure they receive the correct public or private IP address from their provider.