Reef Angel Forum

Your port forwarding is broken and has nothing to do with the nat loopback.

The nat loopback refers to connecting to the public wan ip from inside the network. The home/away profiles try to make that easier to manage.

Most likely your issues are with those firewall settings.

So even though it shows my port is open and not blocked my my ISP when I checked it on canyouseeme.org, it still could be a firewall issue?

It could be yes

Ok, thanks. When I get off of work I will look at my firewall settings. How do you post a pic of your router page? I tried yesterday using the snip it tool, but couldn't figure out how to post it.

Ok my routers firewall as an "add rule" for IPv4. It asks for the rule name, protocal, source ip address, destination ip address, source port start, source port end, destination port start, destination port end, subnet mask for both source and destination IP address. I guess I use reef angel for the rule name since that is what I called it when I port forwarded? Protocal should be TCP? Where it asks for all the ports, they should be 2000? I"m just not sure which address I should use for the destination IP address and the source IP address and both subnet mask's.

The destination IP and netmask would be the reef angel wifi address and netmask (most likely 255.255.255.0)

For the source, you'd want it to be a wildcard you could try 0.0.0.0/0.0.0.0 if it forces you to put in a value..

Protocol is TCP port is 2000 so yeah 2000 for all the fields

I tried what you said for the source IP, but it said "invalid source IP address", on both entries. It also have the option for inbound and outbound. I'm assuming it should be inbound, right? Should I leave the subnet mask for source IP address blank like I would for the soure ip address?

Yes try blanks what model is the router? Ill see if i can dig up the documentation..

Its a netgear B90-7550.

Still no luck getting my port forwarding to work. I left the source IP address and the subnet mask for that ip both blank, and still nothing.

If you pm me your external ip address, I can check if I can connect to it or not.
Is the router provided by your ISP? If so, they can set it up for you.
Another user was having issues too and he just called AT&T and they got it working for him.
All you need to make sure is that you have is the correct ip and port of your wifi attachment.
The port is 2000 and the ip is whatever you got from the wifi utility.

Ya I will pm you my external ip address. Yes the router is provided by my isp. I called them awhile ago to help me port forward and they were of little help. They told be to use IP-pass through on my connection configuration tab, which I did, but it made my internet real slow. Also if used what they said all unsolicited traffic would be allowed to bypass the firewall. They said they couldn't even give me support on anything to do with the firewall, cause they were not allowed to. Frustrating to say the least!

I can confirm that your port forwarding is working just fine and your controller is accessible from the internet just fine.
So, it can only be NAT loopback.... Sorry

But I thought that would only matter if I was trying to connect on my public IP address, inside my own network?

Correct. That's what I thought you were trying to do.
Can you explain the problem again, then?

I can't access the android app when I use the away profile and the controller. If I use away with the portal its fine.

Do you have your external ip address and port set correctly in the away profile?
You need to be on 3G and not wifi mode. Are you in 3G mode?

UGGGGG!! I have been trying with wifi this whole time! I wish someone told me earlier, it would have saved a lot of confusion!

I thought it was working at one time..I must have been on 3G when it was.

Oh... that's why
If you are on wifi mode, it is trying to go through the NAT and your router is not letting it loopback.
The biggest problem is the NAT loopback here.
If your router would allow this, none of this confusion would be happening.

Thanks Roberto! Now I will have to go and try this, just to make sure.

I thought I had this finally but now I'm getting another error. This one is 23: XML SAX Parser. Any ideas?

Drs1210 wrote:I thought I had this finally but now I'm getting another error. This one is 23: XML SAX Parser. Any ideas?

that one means that there is an error parsing the xml data from the controller.

if you would, enable logging in the app (at the bottom of the settings page / screen). either append or replace the log file. then run the app. after you get an xml parse error, go back into the settings and select email log file to the developer. that will send me the error that you are receiving and maybe shed more light on the problem.

Sent from my Nexus 7

ok sent

Any news on this yet, Curt? I would like to try to get this resolved because I'm leaving for vacation tomorrow.

Did you try this?

http://forum.reefangel.com/viewtopic.php?p=29662#p29662

According to Roberto...

rimai wrote:Android doesn't crash. It reports SAX parser error.

I downloaded tera term, but I can't get it to do anything. I went to the wifi manual and followed the steps until I got to the step where it says you will see green and blue blinking lights and the following screen. I was not able to see any of that. I typed in $$$ and got nothing. And yes I put the right COM port in.

You can just telnet to your wifi module and run the command but you have to be quick.

Go to a command prompt and type

telnet whateveripaddress 2000

When you get a connected message you can type $$$ and i recommend having that and the command you need in your clipboard so you can just paste it...

So type in thisz: $$$ and this: set c s 1420 at the same time?

Not at same time but i think you can paste them and it will be fine