[pve-devel] PROBLEM: Kernel-Update 2.6.32-31 to 2.6.32-37 and difference in parameters?!

Alexandre DERUMIER aderumier at odiso.com
Thu May 7 13:49:13 CEST 2015


Hi,


>>/etc/modprobe.d/local.conf
>>
>>their was this inside:
>>
>>options ipv6 disabled=0
>>
>>#rm local.conf
>>otherwise with kernel 2.6.32-37 IPv6 cant start and then pve-firewall
>>cant start!

This local.conf is not coming from proxmox.
So, somebody have writen it manually.


(But I think we should add a check in pve-firewall if ipv6 is enabled or not )



>>/etc/syszctl.conf: 
>>
>>now this must been disabled - and before enabled?: 
>># net.ipv6.conf.all.forwarding=1 
>># net.ipv6.conf.all.proxy_ndp=1 

Note sure about this change, maybe it has been change in redhat kernel



----- Mail original -----
De: "Detlef Bracker" <bracker at 1awww.com>
À: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Jeudi 7 Mai 2015 13:36:33
Objet: [pve-devel] PROBLEM: Kernel-Update 2.6.32-31 to 2.6.32-37 and difference in parameters?!

Dear, 

I have found a problem with settings, this was 3 years ok and after 
kernel-update to 2.6.32-37 we get problems with them! 
Can somebody tell us more about why and why this create a crash? And why 
traffic goes behind the kernel update via the 
bridged interfaces with MAC? 

So a big discrepance! 

# Until the 2015-09-26 - until the big crash: 
#https://github.com/outime/ipv6-dhclient-script/issues/1 

/etc/modprobe.d/local.conf 

their was this inside: 

options ipv6 disabled=0 

#rm local.conf 
otherwise with kernel 2.6.32-37 IPv6 cant start and then pve-firewall 
cant start! 

---- other settings unclear: 

/etc/syszctl.conf: 

now this must been disabled - and before enabled?: 
# net.ipv6.conf.all.forwarding=1 
# net.ipv6.conf.all.proxy_ndp=1 




_______________________________________________ 
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