Search results

Solution from https://forum.proxmox.com/threads/minor-apparmor-problem-with-tor.173419/ and https://pve.proxmox.com/wiki/Roadmap#9.0-known-issues Add "abi <abi/3.0>," to the beginning of "/etc/apparmor/init/network-interface-security/usr.sbin.ntpd", then "systemctl reload-or-restart...

@Stoiko Ivanov Do you have an answer for me, please?

We have before-queue filtering enabled. I guess when a sender sees the "Rejected for policy reasons" response, this might lead to problems. The mail has been forwarded internally, so there should be no reject. There is no "drop" action, is there? Could this be implemented?

Hi, I added an IP address to the whitelist and would like to add a comment to which system or partner this IP belongs to. A "comment" column would be useful, like in the action objects.

Turns out that BCC works, and also the mail is not delivered to the original adress. But the block action has the downside of the sender getting a "Rejected for policy reasons". @Stoiko Ivanov How can this be prevented? Seems like there should be a "drop" action that currently doesn't exist.

I also need to forward mails (already working), and don't want those mails to receive the original recipient. Using a block action really won't prevent the mail from being accepted in the first place so that BCC still works as before?

Ah, of course. I had closed that part and forgotten about it :rolleyes: Thanks!

Hello, I have manually started a backup job and it seems there is no way in the GUI to have a look at the running job. Only after the job is finished, I can see the log in "Task History". Would expect to find it there while it's still running (with a status of "running"). Am I missing...

Ok, thanks for the information. Guess it's not worth the effort =)

That could only be used to get the ID, not to set anything, right? Don't need the IDs as all of the rules currently don't have the checkbox enabled. Is there a way to set the value for all of the rules?

PMG 8.2 introduced a "New option for Match Field What Object, to restrict matching on the top header section". See https://bugzilla.proxmox.com/show_bug.cgi?id=2709 I assume that it would be better (more performant) to only use recursive matching in special cases and to normally enable the...

I got this working some time ago. As I stumbled upon this thread again, I thought a little how-to might help someone someday. Probably not complete (and I didn't translate some comments). Using a separate VM for PMG, HAProxy, and Exchange. 1) Firewall 25 -> PMG Firewall 26 -> PMG Firewall 443...

I was having the same problem and didn't know that actually nothing needed to be decoded as the "test string" feature showed "...did not match the text...". Guess it would help many users if that feature could also decode the string automatically, so I have created a feature request...

No, I didn't. But after switching to "Use USB Vendor/Device ID", the problem didn't show up again, afair.

Auch nach einem Neustart keine weiteren Einträge mehr. Allerdings wüsste ich zu gerne, warum das auf einmal auftrat, denn nach der Einrichtung des SAN, die erst wenige Monate her ist, kam das noch nicht.

Habe die nicht benötigten IPs/Verbindungen nun auf einem Host testweise entfernt und seitdem sind bisher keine weiteren Einträge im Log bzgl "no route to host" aufgetaucht. Neustart des Servers wird die Tage noch getestet, wenn es passt. iscsiadm -m node -T ${IQN} -p 10.1.4.170 -I...

atl-vm04:~# iscsiadm -m node 10.0.1.100:3260,1 iqn.1986-03.com.hp:storage.msa2040.15472745cf 10.0.1.100:3260,1 iqn.1986-03.com.hp:storage.msa2040.15472745cf 10.0.2.120:3260,3 iqn.1986-03.com.hp:storage.msa2040.15472745cf 10.0.2.120:3260,3 iqn.1986-03.com.hp:storage.msa2040.15472745cf...

Wurde bei der Einrichtung vor ein paar Monaten so gemacht: iscsiadm -m discovery -t sendtargets -p 10.0.3.140 -I iscsi_enp2s0f0 && \ iscsiadm -m discovery -t sendtargets -p 10.1.3.150 -I iscsi_enp2s0f1 D.h. selbst wenn ich das nun manuell lösche und es zunächst funktioniert, wird es immer...

Besten Dank!

Hallo, wir nutzen ein SAN im Zusammenspiel mit Proxmox, welches direkt (ohne Switch) über zwei Kabel am Server angeschlossen ist. Alles funktioniert soweit, aber mir sind störende Einträge im Log aufgefallen, die ich gerne unterbinden würde. Der Server hat zwei Interfaces für iSCSI. Je eines...