tazzman
join:2009-03-27
Garnavillo, IA
| Actiontec Modem M1000
I’m running an IPPBX. The challenge at hand is a Remote location. An actiontec Modem with a Linksys WRT54G is behind it. I have complete remote access to each device. e.g. the Modem, Router & VOIP Phone. The issue at hand is I’ve created a DNNS account that I entered into the Router & it pulls & registers with the actiontec not the public IP address. Why is the Actiontec assigning 192.168.0.2 to the router?
Also on port forwards. Am I better off to go with the GRE setting? |
|
Doctor Olds
I Need A Remedy For What's Ailing Me.
Premium,VIP
join:2001-04-19
1970 442 W30
clubs:
| The Actiontec is a Router and getting the Public IP on its WAN and everything on its LAN gets a Private IP (the Linksys in other words has a Private IP on its WAN) and if you setup DynDNS in the Linksys it is sending what you told it to, the WAN IP of the Linksys which is Private IP Space from the Actiontec LAN port.
--
What’s the point of owning a supercar if you can’t scare yourself stupid from time to time? |
|
tazzman
join:2009-03-27
Garnavillo, IA | reply to tazzman
Thanks for the reply.
Sure it is I see. Any thoughts on how I need to make these 2 devices work so that I can achieve DNNS? Also how about GRE on Port Forward? |
|
Doctor Olds
I Need A Remedy For What's Ailing Me.
Premium,VIP
join:2001-04-19
1970 442 W30
clubs:
| reply to tazzman
Does the Actiontech have DynDNS support? Remove the settings for DynDNS in the Linksys and enter them into the Actiontech instead since it has the Public IP.
Now if the Actiontech doesn't have DynDNS support, then you would want to place the Actiontech into Bridge Mode and have the Linksys handle the Public IP along with the DynDNS duties.
HTH
--
What’s the point of owning a supercar if you can’t scare yourself stupid from time to time? |
|
