ага, уже нашёл, но как применить? у меня на CentOS7 получается старые исходники в rpm выкачивает чтоли ?(

похоже что так. как применить - ну, если в лоб, то просто скачать свежий compat и собрать

Не пропускает, брас поднимает сессию через жопу, у меня такое ещё при л2 ловилось, возможно это один и тот же баг

Или фича

Не замечали пока

Hi! I'm trying to play with accel-ppp + ipoe + radius
One debug question.
I'm using Proxmox, and in future I need to run with this kind of virtualization. I don't know is QnQ is working fine, I will need for ipoe.
My asks:
- I'm sending dchp in QinQ vlan, but I'm not reciveing nothin. I have installed 8021q module and loaded, and also creaded manually interface vlan, or listening to trunk interface, and I haven't recived any packet about DHCP. Any idea?  ( i'm using tcpdump)
- Is needed to load 8021q in accel-ppp ipoe ?

Many thanks :)

Hi. Firstly you need to check if your VM receives qinq frames. So.. just run tcpdump -e on eth-interfaces for qinq traffic

You need to run on parent interface inside VM, not on vlan subinterface

For debug purposes you can create qinq interface inside VM, like eth0.2.3 and add this interface to Accel-pp configuration

Hi @GilObradors, which ethertype are you using?

Old cisco switches use 0x9100 ethtype so it might be an issue

You can check ethtype via tcpdump as I mentioned before

802.1ad can use 0x88A8, in this case you need to create not 8021q

Thanks @sergey239 , first check fail.
VM1 -—— VIrtualbridge  vmbr0
         —— Inside ens19
            —- configured ens19.1001  192.168.1.1/24
VM2 -—— VIrtualbridge  vmbr0
         —— Inside ens19
            —- configured ens19.1001  192.168.1.2/24

No pings, no tcpdump.  So we can conclude that for now, QinQ not working in Promxox default Vswith config.

@dimka_88 I'm throwing a DHCP request via ens19, without QinQ  ( but Vswitch internally has vlan69)
this is the output
19:54:49.917400 a6:07:46:ce:4f:82 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from a6:07:46:ce:4f:82 (oui Unknown), length 300

So my ethtype is 0x0800 ?

Generally, the community didn't use VM ?  In my case Proxmox 6.1

I'd recommend you to use pci passthrough if you plan to have a lot of traffic

I don't use bridges or vswitches for high load network hosts

@Korvin7 @TomakSI привет, как там на Proxmox qinq заводить?

@GilObradors try please dump traffic on physical network interface on Proxmox at first, lake in example

tcpdump -n -i eth0 -e -v port 67 or port 68

Can you draw your network map for better understanding? In draw.io