Post
by TonyB » Mon Dec 14, 2009 5:02 pm
The more I look at the AirPort Extreme (router) utility settings, it appears that changes in Ooma Advanced settings did work. This is what I now see, and I didn't do anything since yesterday:
IP Address = 172.27.35.10 (was .123)
Subnet Mask = 255.255.255.0
Router Address = 172.27.35.1
The "Router Address" is that of the Ooma, right? In this set-up, the Ooma is seen as a router... So, I was looking for this router address to change to 172.27.35.10, and it didn't budge, and that's probably why...
Maybe the actual router (AirPort Extreme) address is the one called "IP Address"... Bingo. As a test, in the Ooma settings, I did this:
DHCP Start, End & DMZ = 172.27.35.11
I then did a power cycle of both, and now I get this in the APE utility:
IP Address = 172.27.35.11
Subnet Mask = 255.255.255.0
Router Address = 172.27.35.1
So, "IP Address" is that of the router, not "Router Address", which is the Ooma...
That all said, I'm not certain where this leaves me... I just put those settings within Ooma back to "10", power cycled, and the APE utility is showing the 10 address again for the APE router. I think I need to go back and re-read some posts as this should be working...
The Ooma is the first device in line... It has one rule for port forwarding:
Ports = 85
Type = TCP & UDP
Forwarded To = 172.27.35.10:85
So, it then forwards to the APE router at 172.27.35.10. This device has Port Mapping set-up for TCP and UDP on port 85, and forwards to 10.0.1.6 - the static IP for the DVR, which I can reach locally on the LAN.
The power cycling, as someone said earlier, really is important. If this is indeed possible, I should be mighty close. Thanks.