RT-AC68U: Merlin : URL Filter block internal website

[sfruksi]

Router: RT-AC68U
Firmware: 3.0.0.4.374.39

Issue:
I'm trying to block a number of domains using the URL Filter in my AC68U, and it does so successfully. However my external facing website, becomes unavailable if the URL Filter is enabled. To clarify it becomes unavailable internally, externally it is fine. I can access internally via the internal IP address when URL Filtering is enabled.

None of the URL Filter keywords match any part of my website. I removed all website address filters, but left the URL Filter active, and the internal website will still does not resolve.

Any suggestions? Thanks

 

[thelonelycoder]

You are using both, the URL- and the Keyword Filter?
It should not matter unless it interferes the way how your internal Website is resolved.
Do you mean the routers Webinterface or an actual Webserver within your network?
If it is the latter how do you resolve the domain locally?

 

[sfruksi]

Keyword filtering is disabled. For url filtering I am thing like ".cn" and ".sx". This exact setup worked on my DIR-655 router that I just replaced.

The routers web interface is fine. What does not resolve is an external facing website unrelated to the router, but on the same subnet.

The local webserver is resolved through our local DNS, rerouting it to the external IP address.

After more testing, when a site is blocked by the filter, the site instantly comes back as "webpage is not available". When the filter is active our internal website does not get that error, it just keeps trying to connect until it fails.

 

[thelonelycoder]

Are you filtering the exact wording ".cn" and not "cn" without the dot I presume?

 

[sfruksi]

I am filtering with the ".".

See above image.

 

[sfruksi]

But again, if I clean that whole list and leave it blank, but keep the filtering enabled, I can still not get my website via its domain name/external ip address.

I can ping via the IP address with filtering enabled and disabled.

 

[thelonelycoder]

After more testing, when a site is blocked by the filter, the site instantly comes back as "webpage is not available". When the filter is active our internal website does not get that error, it just keeps trying to connect until it fails.

With your filters enabled, try asdfasdf.cn in your browser...
Same behaviour as your internal resolving. Maybe your internal dns bounces off the router when filtering is on.

 

[thelonelycoder]

Just noticed. If you do a traceroute to an unknown domain but with a blocked tld such as asdfasdf.cn the following happens:
on my Linux boxes (traceroute) it returnes its own IP
while my Windows box (tracert) correctly says it cannot be resolved.
My router is not shown in the trace.
There may be a bug in the filter mechanism. Merlin?