Forum Discussion
Cannot access my Gateway at 192.168.12.1
- Hace 3 años
After a lot of investigation, I uninstalled the VPN and I can now access my gateway 192.168.12.xx
iTinkeralot wrote:
My guess is that he plugged a router into the T-Mobile router, as you speculated, and it served the 192.168.12.1 DNS server up on its ethernet segment as the DNS server. No way clients on the second broadcast domain can ever be routed out and back as the T-Mobile router will never know of the ethernet segment on the other side of the other router. In effect he needs to turn that to bridge mode and disable the DHCP server or just shut the old router down. Unless there is a demand for expansion of the wireless to try to cover more area the best solution is to just go with the T-Mobile router. The second router would have the double NAT solution and well that could cause issues as well.
My TMHI Gateway is the router, it is an integral part of a single “box”
Sorry if you are offended, no intention to do so. Was just trying to offer suggestions and help determine what was going on. The "he" would have been referring to the original author of the conversation, you. Cuándo gpmaz and I bantered back and forth trying to determine what was going on to try to offer suggestions that could help all the "specific details" of your solution were not clear. I supposed to be clear I should have inserted mb300e4m instead of "he". When the address 192.168.68.105 was exposed in the address data there were a few ways that could take place. Another router with a DHCP server o say a VPN which would account for a different IP address than the local network. If the mesh "router" has no DHCP server running that should not cause a problem. Of course with the VPN tunnel up that makes sense to have the client with the IP on the VPN. If not in a split tunnel it would make sense that local resources would be isolated from the VPN tunnel connection.
Contenido relacionado
- Hace 2 años
- Hace 8 meses
- Hace 7 meses
- Hace 2 años