[pve-devel] can't add fwpr2004p0 to bridge vmbr0: Unknown error 524
Alexandre DERUMIER
aderumier at odiso.com
Mon Jun 16 09:50:01 CEST 2014
>>Do i need a special kernel feature?
I don't think.
It's just create a veth pair, then plug them in bridge.
I check my logs, I don't have theses
"netpoll: (null): fwpr2004p0 doesn't support polling, aborting "
do you use a custom kernel ?
----- Mail original -----
De: "Stefan Priebe - Profihost AG" <s.priebe at profihost.ag>
À: pve-devel at pve.proxmox.com
Envoyé: Lundi 16 Juin 2014 09:37:14
Objet: [pve-devel] can't add fwpr2004p0 to bridge vmbr0: Unknown error 524
Hello,
ok since i found the 3rd checkbox. It tries to enable the firewall.
But it fails.
PVE Output:
can't add fwpr2004p0 to bridge vmbr0: Unknown error 524
can't add interface 'iface' to bridge 'vmbr0'
/var/lib/qemu-server/pve-bridge: could not launch network script
Kernel Output:
[1705113.081540] IPv6: ADDRCONF(NETDEV_UP): fwln2004i0: link is not ready
[1705113.086468] IPv6: ADDRCONF(NETDEV_CHANGE): fwln2004i0: link becomes
ready
[1705113.088107] device fwln2004i0 entered promiscuous mode
[1705113.088154] fwbr2004i0: port 1(fwln2004i0) entered forwarding state
[1705113.088158] fwbr2004i0: port 1(fwln2004i0) entered forwarding state
[1705113.089771] device fwpr2004p0 entered promiscuous mode
[1705113.089787] netpoll: (null): fwpr2004p0 doesn't support polling,
aborting
[1705113.091350] device fwpr2004p0 left promiscuous mode
[1705113.091354] device fwpr2004p0 entered promiscuous mode
[1705113.091362] netpoll: (null): fwpr2004p0 doesn't support polling,
aborting
[1705113.093038] device fwpr2004p0 left promiscuous mode
Do i need a special kernel feature?
Stefan
_______________________________________________
pve-devel mailing list
pve-devel at pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
More information about the pve-devel
mailing list