Search results

Thanks for your advice Chris! NFLOG works as LOG - just counts a packages. It looks like this is because CT is unprivileged in my case. Do you have any idea? Is it possible to avoid this issue and keep CT unprivileged? Regards!

Hi there! Absolutely correct - iptables logging doesn't work in CT. Doesn't matter INPUT, OUTPUT or FORWARD. Sure rule counts logged packets but nothing in log (messages, kern, syslog etc). Even if set up dedicated log file you will get nothing there. Any other rules work well (DROP, ACCEPT...

Hi there! Thanks for your advice! I have tried this before my first post but with no success.

Thanks again, Stefan! Unfortunately nothing helped me. Even downgrade to lxc-pve 3.1.0-61 (the same error as well). So if you have interest in this issue I could provide some additional information about system and config. Or just wait until further updates :) Regards!

Thanks a lot for your response, Stefan! Yes, I have restarted container after changes. But not host machine (just have restarted AppArmor service on host machine). And I have Debian on host and in containers as well. So, this problem appears just after last update Debian and Proxmox packages...

Hi there! Thanks a lot for your advice and I wonder does it really work for your system? Because it doesn't work for me: Manual start of tor binary gives success. conf: Does anybody know any other solution?

Hi there! Also you can do this via terminal: Stop pct (ex.: vmid is 100): pct stop 100 Make backup Make temp dir (ex.: /tmp/100): mkdir /tmp/100 Mount container mount -o loop /path/to/vm-100-disk... /tmp/100 Run follow commands: find /tmp/100 -type f | while read S; do U="$(ls -ln "${S}" |...