InformAction Forums

Today for the first time ABE failed to detect my WAN IP. I can't figure out why. Is there a way I can force it to check again?

I would also like to add that secure.informaction.com/ipecho is detecting the IP correctly so why isn't ABE able to pick it up?

Sorry for the multiple posts but it was resolved when I restarted my computer, I guess you can lock this

It appears this was not fixed by restarting the computer. The WAN IP detection appears to be rather iffy. It is seems to be randomly losing my IP for no reason. Sometimes it will lose it after 3 hours sometime just 1. Other times it will detect after I restart Firefox once, other times it takes 3 or 4 tries. Sometimes it will work after I restart Windows, other times not. I can't figure this out, is there any way I could get more detail in the ABE error message in order to help troubleshoot what is happening?

You could troubleshoot it by logging all the traffic back and forth the IP detection site.

You could use Fiddler for this. Note that since the traffic is HTTPS, you need to configure Fiddler to MITM attack the line (and install Fiddler's CA):
http://www.fiddler2.com/Fiddler/help/ht ... yption.asp

I guess my final quest would be am I missing any anti-CSRF protection if ABE fails to detect my WAN IP?

Guest wrote:I guess my final quest would be am I missing any anti-CSRF protection if ABE fails to detect my WAN IP?

This one, if your router is vulnerable (NoScript failing at persistently recognize your WAN IP may hint at your router NOT being vulnerable, though).

Giorgio Maone wrote:

Guest wrote:I guess my final quest would be am I missing any anti-CSRF protection if ABE fails to detect my WAN IP?

This one, if your router is vulnerable (NoScript failing at persistently recognize your WAN IP may hint at your router NOT being vulnerable, though).

But to if my router wasn't vulnerable wouldn't ABE never be able to recognize my WAN IP?
Also it appears that if ABE loses my IP if I disconnect and reconnect to my network, then force ABE to check the WAN IP again (by checking and unchecking the WAN IP = LOCAL) it usually picks it up, I'm not sure if that has any significance though. This only seemed to have started occurring in NoScript 2.0.9.8, in which the WAN IP checks were increased to 1hour. It may have been that I just didn't notice before because the WAN IP checks occurred more often.

Guest wrote: But to if my router wasn't vulnerable wouldn't ABE never be able to recognize my WAN IP?

Nope. Recognizing your IP always work, no matter whether your router is vulnerable or not.
Storing it consistently is easier if your router is vulnerable, because it will always answer with its console.

Guest wrote:This only seemed to have started occurring in NoScript 2.0.9.8, in which the WAN IP checks were increased to 1hour. It may have been that I just didn't notice before because the WAN IP checks occurred more often.

This is possible. Does it show a wrong IP or no IP at all?
Is anything shown in your Error Console?
Does ABE recover within one hour?

Guest wrote:This only seemed to have started occurring in NoScript 2.0.9.8, in which the WAN IP checks were increased to 1hour. It may have been that I just didn't notice before because the WAN IP checks occurred more often.

This is possible. Does it show a wrong IP or no IP at all?
Is anything shown in your Error Console?
Does ABE recover within one hour?

It never shows the wrong IP just no IP as in WAN IP(????) and [ABE] WAN IP not detected! in the Error Console. Sometimes it will recover in an hour by itself, most times I have to "help" it by doing what I said before (reconnecting, unchecking and rechecking WAN IP). Also secure.informaction.com/ipecho always displays the correct IP.

One thing that appears to be consistent is that if ABE fails the IP when I open Firefox it becomes incapable of detecting during that session, even after an hour or two. I feel I may have found a cause for that, though. My laptop sleeps when I close the lid, thus disconnecting from the network, if I wake it and start Firefox when Windows is still connecting to the network( which I do sometimes because I am in impatient) ABE will not detect the IP, which makes sense because ABE is unable to connect to the internet.

I've realized something else
As you may know Google recently changed their top navigation bar to like this:
http://3.bp.blogspot.com/-9nHxp1Q8vE4/T ... 2011-2.png
However occasionally the "new" bar doesn't load load and rather it looks this:
http://3.bp.blogspot.com/_ZaGO7GjCqAI/R ... on-bar.png
It appears as though there may be at least some correlation between the ABE not detecting the IP and the Google navigation bar. It appears sometimes when the latter bar is displayed on the Firefox default homepage ABE fails to detect the IP upon starting Firefox. It's likely coincidence but I thought it was something.

I am having this same problem with Abe not detecting my IP (no IP as in WAN IP(???) and [ABE] WAN IP not detected! in the Error Console)...

Don't know if coincidence or not, but all is well with ABE (for now) after flushing DNS cache. I had been getting the error console ABE messages previously mentioned for the last two days this time (has happened before briefly, but seemed to correct itself with no action from me) with *nothing* mentioned in OP's post working to correct it .

OOPS! The last response (Guest) was from me. Forgot to type in my nym...

OP here
Flushing the DNS cache works but it seems I have to every time I leave my computer on sleep mode for more than an hour.
If I exit Firefox leave my computer on sleep for more than an hour when I wake the computer and open Firefox ABE will not detect my IP