Hi Yod,
I've been doing some tests on MTG-SC025 to try to find a root cause. As far as I can tell, there are no problems with the configuration, the software, or the network. I understand that Dennis found in his testing some problems, but that they seem to have been fixed after resting the interceptctl process.
My testing only tested the proxy process and the connection to the outside world, but not using the same IP address ranges as your test machine. I see that you have several policies that change the behaviour of the cache depending on the client subnet. When you do your next round of testing, can you please make sure that you've disabled any custom policies that would affect your client's connection?
Also, if you run into problems during your next test, can you please include the output from iptables -L -n -b? Restarting iptables will flush the local iptables configuration, so it's possible that the problem was caused by incorrect or incomplete iptables configuration.
Hi Yod,I've been doing some tests on MTG-SC025 to try to find a root cause. As far as I can tell, there are no problems with the configuration, the software, or the network. I understand that Dennis found in his testing some problems, but that they seem to have been fixed after resting the interceptctl process.My testing only tested the proxy process and the connection to the outside world, but not using the same IP address ranges as your test machine. I see that you have several policies that change the behaviour of the cache depending on the client subnet. When you do your next round of testing, can you please make sure that you've disabled any custom policies that would affect your client's connection?Also, if you run into problems during your next test, can you please include the output from iptables -L -n -b? Restarting iptables will flush the local iptables configuration, so it's possible that the problem was caused by incorrect or incomplete iptables configuration.
การแปล กรุณารอสักครู่..
