I just tried sent a patch to avoid ipset list chains. Please can you review?
Thanks, I'll test it tomorrow
I was quite easy to implement, so maybe I miss something? What exactly was
the reason
to introduce those list chains?
I think it was related to security groups, which could have a rule
I think it was related to security groups, which could have a rule with ipset
and
ipv6.
(we could have security group, apply both on iptables and ip6tables)
I cannot see that problem. Will also do more tests next week.
___
pve-devel mailing list
Hi,
i know double firewalling normally is not usefull. But we also use the firewall
to protect us againts customers against ip spoofing etc..
one of our customers who has serveral virt servers cant use pfsense.
Ist just enough to enable the firewall and pfsense does not nat anymore. We
have
On Sun, 30 Nov 2014 20:02:33 +
VELARTIS Philipp Dürhammer p.duerham...@velartis.at wrote:
Any ideas how to debug it?
Do you block private networks on the wan settings page?
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael at rasmussen dot cc
Hi,
are you tagging vlan inside the guest vm ? (in pfsense) ?
if yes, does it works with tagging vlan inside a simple linux vm ? (I don't
remember if we have tested this)
- Mail original -
De: VELARTIS Philipp Dürhammer p.duerham...@velartis.at
À: pve-devel@pve.proxmox.com
Hi to PVE team developers
This is a new summary of a major problem between PVE, KVM and Win2008R2 SP1
VM.
Maybe i am doing something wrong, or maybe PVE or KVM need some corrections,
but i have done many test for get that the Win2008R2 SP1 works correctly
without successful, so that i would
3) In parallel to this strange behavior, htop on PVE is showing that the
process that consume a lot of processor is: /usr/bin/kvm, this behavior is
repetitive in all threads of processor that the VM has access.
The kvm process is your vm ;) (each guestvm is a kvm process)
4) In parallel to
also, can you post your vm config file ?
Proxmox use some hyper-v features to help for some case, including high memory.
But currently, 2 features are missing.
in /usr/share/perl5/PVE/QemuServer
if ($ost eq 'win7' || $ost eq 'win8' || $ost eq 'w2k8' ||
$ost eq 'wvista') {
