I have the following network configuration set up at a remote location that I can't access right now (4 hour drive):
- PC connected directly to my default gateway. IP address is 192.168.0.3.
- Hub connected via TPLink wifi through a nest router. IP address of HUB is reserved and set to 192,168.86.103.
I would like to log into the hub from the computer which I connect to using TeamViewer. Right now it fails to connect to the hub. Is there a way to configure my router such that I can make this connection?
This hub only controls yard lighting right now, so I don't care at all about any security concerns.
If I understand your question - the answer is yes. You can do a couple of things. One is to multihome the PC. By assigning it multiple IP addresses on the same NIC, you can effectively bridge the 2 subnets. Recall from your IP days that 192.168.x is by definition non-routable.
A different and more complex solution is to NAT the 2 subnets, but I'd really stay away from that as setting up a router between the 2 subnets can be wicked difficult.
Another solution is to change the netmasks. By making the subnet of 192.168.0-86 as the network, you could make all devices with the proper netmask appear as being on the same network. All of this is at your peril as I don't have the details of your network design and other devices could be negatively affected!
Finally, I'll add you can solve with hardware as well. - a 2nd NIC (network card) in the PC. You could bridge the two networks in this manner as well putting the PC on both networks simultaneous and let the ARP/routing of the net stack take over.
Hey thanks for the input. There is currently no physical connection between the Nest network and the computer, and the computer (which I built) has no wifi card in it right now (didn't need one when I built it). So, the solution would need to go through the router for now. Since I currently don't have access to the computer what I ended up doing was just picking a random port on the Nest router to use to forward to the hub. Nest routers have remote admin through Google home, so this is fairly straightforward. For example: 192.168.0.2:1001 --> 192.168.86.103:80
Now I can just type in 192:168.0.2:1001 into a browser on the computer and it takes me to the home screen of the hub where I can configure and monitor my lighting program.
1 Like
And that would work too! Since your port forwarding an internal net - it's not a security issue so... a 4th way! You do bring up yet another - a wifi dongle. of course that means you'd have to finger the unit... I saw a wifi dongle for 6 bux recently at a box store... I almost bought a couple just because! but I hate wifi... so I didn't 
