Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Firewall only searches URLs that start with "HTTP" and ignores all others.Given a firewall configuration using the banned URL of "google.com", the router will act in the following manner: When the user goes to "http://www.google.com", the router wil...
Firmware v4.0.4.02 has a nasty bug in the VPN section. If you switch to "IP by DNS Resolved" (yes, it says "Resolved" instead of "Resolution". Gotta love all the Engrish in the RV042!), it will automatically populate the field with "@yourdomain.com...
The entire "incoming log table" is just full of this! It's all the same! This is on the current firmware 4.0.4.02Sep 20 12:49:35 2011KernelOut of memory: Killed process 5385 (iptables). Sep 20 12:49:39 2011KernelOut of Memory: Kill process 5387 (ip...
Tom. First off, thanks for taking the time to address these issues. We are not trying to harasse or otherwise make your life difficult. We are just looking for answer to things which appear to be unusual to us, and that does not appear to be ha...
Not throwing a tantrum, but you do appear to be evading the question. Is there a technical reason why HTTPS cannot be blocked in the same manner as HTTP? Simple YES or NO will work.If it cannot be done, then say "NO! It cannot be done!". Otherwis...
I'm confused. It still has to perform a session negotiation (handshake) before it goes encrypted. It has to say "Hello" to the server. Block it there. Explain to me why it cannot do this?If I see traffic on port 443 and the destination matches a ...
