currently we only check the entry for cgroup v1 to decide if cores
should be rebalanced. extend the check to include cgroup v2 entries.
reported in forum [0]
[0]: https://forum.proxmox.com/threads/hard-set-streams-for-lxc-container.97768/
Signed-off-by: Oguz Bektas
---
PVE/Service/pvestatd.pm
On 14.10.21 08:22, Oguz Bektas wrote:
>> Hmm, I'd maybe avoid the list of exact release, tends to be outdated to fast
>> for some.
>>
>> Maybe we can link to the respective upstream release pages?
> i thought it'd make sense to have a list, but yeah i suppose we can link
> to their release pages.
hi,
On Thu, Oct 14, 2021 at 07:35:23AM +0200, Thomas Lamprecht wrote:
> On 13.10.21 12:59, Oguz Bektas wrote:
> > adds a simple section with a list of officially supported templates
> >
> > Signed-off-by: Oguz Bektas
> > ---
> > pct.adoc | 76 +++-
This is one of the commits in includes/net/ip.h...
I'd say someone should look over this and fix it :)
commit 93fdd47e52f3f869a437319db9da1ea409acc07e
Author: Herbert Xu
Date: Sun Oct 5 12:00:22 2014 +0800
bridge: Save frag_max_size between PRE_ROUTING and POST_ROUTING
As we may
On 13.10.21 12:59, Oguz Bektas wrote:
> adds a simple section with a list of officially supported templates
>
> Signed-off-by: Oguz Bektas
> ---
> pct.adoc | 76 +++-
> 1 file changed, 70 insertions(+), 6 deletions(-)
>
> diff --git a/pct.adoc
Hi,
I did some more digging searching for 'bridge-nf-call-iptables
fragmentation'
Found these forum posts:
https://forum.proxmox.com/threads/net-bridge-bridge-nf-call-iptables-and-friends.64766/
https://forum.proxmox.com/threads/linux-bridge-reassemble-fragmented-packets.96432/
And this patch,
On 13.10.21 17:48, Stefan Reiter wrote:
> Signed-off-by: Stefan Reiter
> ---
>
> Applies on top of the 6.1 rebase.
>
> .../extra/0006-qxl-fix-pre-save-logic.patch | 34 +++
> debian/patches/series | 1 +
> 2 files changed, 35 insertions(+)
> create mo
Signed-off-by: Stefan Reiter
---
Applies on top of the 6.1 rebase.
.../extra/0006-qxl-fix-pre-save-logic.patch | 34 +++
debian/patches/series | 1 +
2 files changed, 35 insertions(+)
create mode 100644 debian/patches/extra/0006-qxl-fix-pre-save-logic
If you Stop pve firewall service and echo 0 >
/proc/sys/net/bridge/bridge-nf-call-iptables (you stop the netfilter hook)
Then it works for me also with taged tap devices and vlan aware bridge. I think
it is a kernel bug.
What I don’t understand why not more people are reporting it...
-Urspr
Hi,
I can confirm that s > 12000 does not work on either
size, tap(untagged, mtu 1500)->vlan-aware bridge(mtu 9000)->bond(mtu
9000), tap(tagged, mtu1500)->vlan-aware bridge(mtu 9000)->bond(mtu 9000)
s > 12000, doesn't work, doesn't work
s > 8000 , works, doesn't work
The traffic(one packet de
And what happens if you use packet size > 9000? this should still
work...(because it gets fragmented)
-Ursprüngliche Nachricht-
Von: pve-devel Im Auftrag von Josef
Johansson
Gesendet: Mittwoch, 13. Oktober 2021 13:37
An: pve-devel@lists.proxmox.com
Betreff: Re: [pve-devel] BUG in vlan a
Med vänliga hälsningar
Josef Johansson
On 10/13/21 15:47, VELARTIS Philipp Dürhammer wrote:
>>> As a datapoint I could ping fine from a MTU 1500 host, over MTU 9000
>>> vlan-aware bridges with firewalls to another MTU 1500.
>>> As you would assume the package is defragmented over MTU 9000 links
>> As a datapoint I could ping fine from a MTU 1500 host, over MTU 9000
>> vlan-aware bridges with firewalls to another MTU 1500.
>> As you would assume the package is defragmented over MTU 9000 links and
>> fragmented again over MTU 1500 devices.
So you did a ping with -s 2000 (or bigger) and
apparently this caused a weird[0] bug... when a container with a snapshot was
cloned, it would take 'parent: foo' from the original container. if you
add a new snapshot 'bar', and then another one 'foo', this causes the
snapshots to become parents of each other (thus not parsed correctly in
the tre
v1->v2:
* remove other snapshot-related properties during clone
* add check when creating new snapshots and abort if new name already a parent
for existing snapshot
pve-container:
Oguz Bektas (1):
api: clone_vm: don't include snapshot properties
src/PVE/API2/LXC.pm | 5 +
1 file changed,
Hi,
AFAIK it's netfilter that is doing defragmenting so that it can firewall.
If you specify
iptables -t raw -I PREROUTING -s 77.244.240.131 -j NOTRACK
iptables -t raw -I PREROUTING -s 37.16.72.52 -j NOTRACK
you should be able to make it ignore your packets.
As a datapoint I could ping fine
adds a simple section with a list of officially supported templates
Signed-off-by: Oguz Bektas
---
pct.adoc | 76 +++-
1 file changed, 70 insertions(+), 6 deletions(-)
diff --git a/pct.adoc b/pct.adoc
index d01e6d7..1415f67 100644
--- a/pct.ad
HI,
Yes i think it has nothing to do with the bonds but with the vlan aware bridge
interface.
I see this with ping -s 1500
On tap interface:
11:19:35.141414 62:47:e0:fe:f9:31 > 54:e0:32:27:6e:50, ethertype IPv4 (0x0800),
length 1514: (tos 0x0, ttl 64, id 3, offset 0, flags [+], proto ICM
Am 12.10.21 um 15:32 schrieb Oguz Bektas:
apparently this caused a weird[0] bug... when a container with a
snapshot 'foo' was cloned, it would take 'parent: foo' from the original
container. when you add a new snapshot 'bar' to the cloned container,
and then another one 'foo', this causes the sna
19 matches
Mail list logo
