InformAction Forums

Starting with the June 12 release, I think, ABE stops me from getting to the blog portions of my local web sites unless I turn off the "WAN ∈ LOCAL" flag on ABE.

My web site is at home. Their IP address is my home WAN address. I can get to the top level web site (http://www.somedomain.org) just fine, but when I try to go to http://www.somedomain.org/blog (a wordpress installation), ABE starts getting in the way.

Turning off "WAN ∈ LOCAL" makes it work, but this seems to be the wrong solution. I feel like I'm leaving something out, what do I need to explain to get to the right solution?

Thanks!

Can I see the exact message(s) you get from ABE?
Does downgrading to a pre-Jun 12 version actually help?

Doesn't repeat right now when I turn WAN ∈ LOCAL back on. There was some trouble with my WAN address changing (dynamic DHCP).

ABE wasn't visibly complaining, is there a log?

Log is in the error console, Ctrl+Shift+j.

Good to hear that it's working now . It would be tricky to add an exception since the address is dynamic.

Just a heads up to all out there who are using either DSL/Cable (anything that is dynamically assigned by the ISP), if you happen to be in the middle of something on your machine and it happens to catch the modem/router in a cycle (meaning its renewing the IP or its rebooting, happens all the time) then you will temporarily have packets that have (without getting into too technical of a packet structure discussion) mismatching header/frame/source/dest ip addressees as well as IP CEF or local DNS cache mismatch causing ABE to trigger as a local block. That is NORMAL. Specially on Windows machine where in the absence of a valid IP/WAN connection, it creates and assigns virtual addressing which is indeed YOUR OWN MACHINE, hence, LOCAL.

Normally easiest and QUICKEST fix, wait until the cycle is complete, close your browser and try again and all is well in the world. If not an option, can't see why, then just open the link you were working on in a new tab and that should do it. Or all else fails, force a DNS update inside the browser, toggle the option and that should force a clean up for any cached entries. This information has come from lots of personal and observational experience. Hope it helps.