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”
So, do you run the same WIFI SSID and wireless security on both with WIFI radios active on both devices? I don't think we have the full picture of what has been done in his situation. Not yet at any rate.
In your case your clients on the T-Mobile segment talk to one another and to the internet but unless the backend segment is advertised to the other side the clients would not be aware of it. A client from the internet could never reach into that back end segment as the T-Mobile router has no advertisement of the backend segment from your router. You would need static routing or a dynamic routing protocol on both routers so they could share routing information. I could see clients going out but nothing from the outside could initiate a conversation with one of those clients as it could not be found from the internet.
Contenido relacionado
- Hace 2 años
- Hace 8 meses
- Hace 7 meses
- Hace 2 años