Eric,
many thx that you really tried with setting a password.
This was/is the main problem Kenneth and I reported.
You tried to help with posting of some screenshots ( not even actual? ) and many basic explanations, but you did show your real configuration very late in this thread. This (little) information showed the problem!
Thus our conversation sometimes seemed to be not really consistent.
Could you post a bug at bugzilla, please? You got this error earlier and you have more insight in the pitfalls of the proxy configuration.
Eric,
That was meant to be a Hooray!
Thanks greatly. Now Iāve moved on to
wondering why the IPS log file is always blank - possible
that my area is not part of any scan or attack surface.
Thanks, you have done much work and canāt express the relief of
having not to worry or wonder why that was.
Hope that it is beneficial to other users. Perhaps should petition the
manager of the site to allow editing the post to make it easy to comprehend.
Had hoped the fire hydrant looking like a Dalmatian and titled tah-rah-boom-b-a
was A-List. Loved your Mustang - drove a three speed convertible in 1966 San Diego.
Macho 351 Windsor motor.
New Topic added. and have received an idea to
test an eicar web page; firewall blocked access to
that page but no reason was given in the Log file
since eicar is not part of the rule-set. Hmm?
Meanwhile checked a few DNS Protocol and that
caused 100s of log results - regretfully way
too many.
regarding our conversation about the Cache Management
could you please reconfirm adding the cacheās IP to the
White List (that IP 192.168.2.2 is the BLUE Wireless).
Doesnāt adding that to the Whitelist defeat the Firewall?
Iāve removed that IP from the white list thinking to
add it back when it is necessary to examine the cache.
If your referring to the Unrestricted IP box in the Web Proxy settings, that is for a single IP . x.x.x.x/32ā¦ The box above it is for the Full Network /24. Those Group boxes are a subset of the Cache Manager, not Browser Traffic. They should have named it something like āAllow access to Cache Managerā to prevent confusion.
#2.
It is so it can process the traffic flowing through it, if I am hearing what your saying. I would try to remove the IP, recycle services, test, and if it works correctly, leave the entry out. If not, put it back and recycle services, test and see if it again works.
When you say whitelist, I am assuming you mean the URL filter settings. When I remove my Interface IP x.x.x.1 for Green from the URL Whitelist box, this happens and it wonāt load.
If Bernhard is still monitoring maybe he can confirm or set me straight if I am wrong. I would have thought the GUI would take into consideration its other parts, but this is just a front-end GUI to several linux networking tools. The fact that I can literally cause the cache manager menu to not work by removing my interface IP from my whitelist is strange. On the flip side of the coinā¦ you may be right. I am confused myself at this point.
Eric,
yes I am monitoring this thread. But I can not follow your considerations about whitelists, blacklists, ā¦
The topc is āCache Manager Menu For Proxy Not Loadingā. And we found, that there is a problem, if you set a password.
This is the solution, I think.
REGARDING THE CACHE MANAGER.
THE CACHE MANAGER IS NOW (FOR THE MOMENT AT LEAST) WORKING.
THERE IS NO PASSWORD
THERE IS NO IP ENTERED INTO THE WEB PROXY
THERE IS NO IP ENTERED INTO THE URL FILTER
YET THE CACHE MANAGER WORKS
THE ONLY CHANGE WAS TO HAVE DISABLED THE INTERNAL PROXIES
ACCESS TO GREEN . ACCESS FROM BLUE
PICTURE OF CHANGE
