#11
|
|||||
|
|||||
np, let us know if you run into other troubles.
|
#12
|
|||||
|
|||||
that link you posted (which I had been on before but failed with) does say the private IP field should match the IP address from step 1.
I had tried 10.0.1.6 already but must have done something else wrong. that is the address i'm currently using in my browser to access the controller from inside my network. Last edited by lastlight; 01-06-2014 at 11:06 PM. |
#13
|
|||||
|
|||||
the goal is to be able to login from your public IP address (with the correct port#).
which means your public IP need to be linked with your APEX private IP somehow, thats the general map you are looking at, the configuration is confusing sometimes, but once you put in the right value you are all set. Check your APEX display unit, it will tell you what the private IP address is, I'm not sure if the one Apple displayed was a correct one? |
#14
|
|||||
|
|||||
the values in the apple screens are just the defaults that appear when you go to add a new rule.
http://10.0.1.6/ is what I'm using in my browser to access the controller. |
#15
|
|||||
|
|||||
Ok, then 10.0.1.6 will be your private IP
Sent from my SGH-I337M using Tapatalk |
#16
|
||||
|
||||
If your telus device is a router then you need port forwarding on your telus router. If that is the case then you are double routing with the apple router wich makes things more complicated and in some instances you may not be able to get everything working as not all services will allow double NATing and PATing.
Easiest way might be to plug the apex into the telus router, get it working there. It should still work internally as your apple router will have a route to the subnet of the telus LAN. Or you could look at changing the apple router settings so it isn't routing if you are comfortable with that.
__________________
72g bowfront, t5. 29g JBJ nano cube, ATI 26HD. Livestock: clown fish, chromis, coral beauty. Corals: Toadstool, maze brain, candy cane, mushrooms (purple & green hairy), button polyps, green zoas, GSP. |
#17
|
|||||
|
|||||
i have been messing around with port forwarding directly on the Telus Actiontec V1000H for hours and after digging around the web it sounds like Telus blocks all inbound ports. Not sure if that is the right lingo but I give up for now
|
#18
|
||||
|
||||
Telus does not block all inbound ports. For starters that would prevent all internet services from working. They do block common ports such as 80. I have a VPN running through my v1000h using port forwarding so I can say for sure that port forwarding does work.
But your situation is a lot more complicated with the apple router as well. With the apex behind the apple router the v1000h forwarding needs to point to the WAN address on the apple and the apple forwarding needs to point to the apex. You need to use a port other than 80. I really don't know if it will ever work in that configuration though as it will be routing, NATing, and PATing twice and a lot of services won't work like that.
__________________
72g bowfront, t5. 29g JBJ nano cube, ATI 26HD. Livestock: clown fish, chromis, coral beauty. Corals: Toadstool, maze brain, candy cane, mushrooms (purple & green hairy), button polyps, green zoas, GSP. |
#19
|
|||||
|
|||||
I think you're right. Although I don't understand networking very well I'm sure that the use of two routers is making this much more difficult. I'm going to remove the Apple device tonight and give that a shot. I've heard port 8080 is good... any others? thanks again everyone for the help.
|
#20
|
|||||
|
|||||
I use port 85 on my Shaw, but anything should be good.
|