Mandriva 2010/2011 could connect VPN perfectly, Mageia 3 could connect but couldn't access sites because of bad firewall, Mageia 4 and 5 beta 1 are unable to connect to the VPN-Internet, and the network interface defines as "enp3" besides of "eth0" which was on networking-stable versions. Motherboard is Asus M2AMX. Reproducible: Steps to Reproduce:
Using enp3 as the interface name shouldn't break openvpn. You'll need to give more details for anyone to help with your issue. This may just be a configuration problem on your side though. You could try asking for help in the forum too.
CC: sysadmin-bugs => (none)Component: Release (media or process) => RPM Packages
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Version: 4 => 5
(In reply to David Walser from comment #1) > Using enp3 as the interface name shouldn't break openvpn. You'll need to > give more details for anyone to help with your issue. This may just be a > configuration problem on your side though. You could try asking for help in > the forum too. Closing per lack of information, and no one else reported issues with VPN related to the interface name, to my knowledge. This is probably a configuration issue.
Keywords: (none) => NEEDINFOStatus: NEW => RESOLVEDResolution: (none) => WORKSFORME