-
December 11th, 2018, 21:29 #11
- Join Date
- Dec 2018
- Posts
- 8
ATT: Screenshot (73).png
NET: Screenshot (72).png
ATT(When connected to it): Screenshot (72).png
-
December 11th, 2018, 21:29 #12
you can only port forward to a device/address on the same ip range.
you need to look at the WAN interface or Status page in the 10.0.0.1 and get the WAN address which will start with 192.168.1.something
on the 192.168.1.254 router port forward to that 192.168.1.something address
Just like on the 10.0.0.1 device you port forward to your PC which starts with 10.0.0.something
-
December 11th, 2018, 21:29 #13
- Join Date
- Dec 2018
- Posts
- 8
ATT: Screenshot (73).png
NET: Screenshot (72).png
ATT(When connected to it): Screenshot (71).png
-
December 11th, 2018, 21:36 #14
-
December 11th, 2018, 21:58 #15
- Join Date
- Dec 2018
- Posts
- 8
I don't think I'm putting the WAN address in the right config. As I keep getting error messages.
-
December 11th, 2018, 22:01 #16
Archangel
- Join Date
- Apr 2008
- Location
- Virginia Beach
- Posts
- 3,096
Another option is to put your first router in bridge mode to remove the first port forwarding. That is what I personally do at home. When on the road like I am 75% of the time I use PureVPN, which is awesome but another expense.
-
December 11th, 2018, 22:06 #17
- Join Date
- Dec 2018
- Posts
- 8
I can not put my first router into bridge mode apparently.
-
December 11th, 2018, 22:08 #18
send me a PM if you would like me to have a look at it with you
-
December 11th, 2018, 22:35 #19
I just replied to your PM.
I do have to dash soon.
Let me know.
-
December 11th, 2018, 22:58 #20
This was mostly the LAN not being set to Private in Network and Sharing Centre
there may have been a router/port-forward issue but we re did them all to be safe
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks