Description of problem: VPNC -- No connection possible to AVM Fritzbox 7590 and 7490 as VPN server Version-Release number of selected component (if applicable): 0.5.3-14 How reproducible: Always Steps to Reproduce: - Setup vpn account in AVM Fritzbox router (tested with 7490 and 7590) - Create vpnc config files, one per router - try to establish connection to the router / vpnc server: [root@MGA7VB vpnc]# pwd /etc/vpnc [root@MGA7VB vpnc]# id uid=0(root) gid=0(root) Gruppen=0(root) [root@MGA7VB vpnc]# rpm -qa | grep vpnc vpnc-0.5.3-14.mga7 [root@MGA7VB vpnc]# # 7490: [root@MGA7VB vpnc]# vpnc vpn1.conf vpnc: response was invalid [2]: (ISAKMP_N_INVALID_PAYLOAD_TYPE)(1) [root@MGA7VB vpnc]# # 7590: [root@MGA7VB vpnc]# vpnc vpn2.conf vpnc: response was invalid [2]: (ISAKMP_N_INVALID_PAYLOAD_TYPE)(1) [root@MGA7VB vpnc]# Remark: As already recommended regarding MGA5, it would be best to integrate the patches from Suse to get it working. This version completely refuses to do what it should. Thanks for fixing!
Source RPM: ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/7/SRPMS/core/release/vpnc-0.5.3-14.mga7.src.rpm => vpnc-0.5.3-14.mga7.src.rpm
(In reply to Markus Robert Keßler from comment #0) > > Remark: As already recommended regarding MGA5, it would be best to integrate > the patches from Suse to get it working. > This version completely refuses to do what it should. > I'm afraid no one here really has time to love that package. It doesn't have a registered maintainer and was only touched 4 times since it was imported in 2011. CC'ing guilomvitch, who touched it twice. However, assigning to all packagers collectively. Markus, if you do have some spare time, then please consider becoming a Mageia packager, so that you could maintain this package yourself. https://wiki.mageia.org/en/Becoming_a_Mageia_Packager If you don't have that much time, but do know which exact Suse patches are needed, then please give a link to them. Thanks :-)
CC: (none) => guillomovitch, marja11Assignee: bugsquad => pkg-bugs
Hi, fully agree with you -- no need to "love" the package :-) It is sufficient to just get it and slightly adapt it to MGA's naming and path convention. You get the most recent version here: http://download.opensuse.org/source/tumbleweed/repo/oss/src/vpnc-0.5.3r550-2.4.src.rpm Thanks!
Created attachment 11260 [details] Source rpm containing spec file and all necessary files I have just imported Suse's working version and have adapted it to Mageia standard. In contrary to the errors listed on top, now this version connects correctly to CISCO vpnc server AND to two different internet routers from AVM: [52 root@MGA7VB /etc/vpnc]# vpnc 7490_vpnc VPNC started in background (pid: 5256)... [53 root@MGA7VB /etc/vpnc]# vpnc-disconnect Terminating vpnc daemon (pid: 5256) [54 root@MGA7VB /etc/vpnc]# vpnc 7590_vpnc VPNC started in background (pid: 5464)... [55 root@MGA7VB /etc/vpnc]# vpnc-disconnect Terminating vpnc daemon (pid: 5464) If someone wants to pick it up and put it into svn, feel free to do so. Please also build for MGA6 and cauldron. For spec file see src rpm attached.
Need further assistance? B.t.w., I have to correct myself: If you live in or visit countries where everything is censored (China, BRDDR, Korea, ...) you *WILL* love vpn connections!
How can we proceed? Should we make a build for Cauldron and test if all the other reported bugs like dropped connections and "vpnc does not connect any more" etc. are gone then, too?
As Marja says in comment #1, this package is unmaintained, meaning there is no one in charge of such decision here. As you may have noticed now from the lack of answers, you seem to be only the only one interested in this issue. I'm afraid that unless you volunteer to handle it yourself, and you're most than welcome, no one will.
Hi, from Marja I heared, that packagers are only allowed to checkin ONE change per commit. Hence, to replace the whole buggy package with a new one, is nearly impossible. New source tarball, new patches, the spec also new from scratch. That's more than one modification, of course. Formerly, in MGA5, there was an attempt from my side to act as a packager, but I had to hear I had "changed too much". So, I just created the package and put it on my webserver, for own use and for others. Well, is there a trick to switch to an imported package from a "foreign" distro at all? -- If so, I've nothing against taking care of this (and maybe other packages).
(In reply to Markus Robert Keßler from comment #7) > Hi, from Marja I heared, that packagers are only allowed to checkin ONE > change per commit. Hence, to replace the whole buggy package with a new one, > is nearly impossible. New source tarball, new patches, the spec also new > from scratch. That's more than one modification, of course. You misunderstood : this only meant we wanted you to split the changes. > > Formerly, in MGA5, there was an attempt from my side to act as a packager, > but I had to hear I had "changed too much". So, I just created the package > and put it on my webserver, for own use and for others. Yes, this can happen when someone comes from outside. But we you are maintainer of a package, you do what you want as long as it follows our policies. > > Well, is there a trick to switch to an imported package from a "foreign" > distro at all? -- If so, I've nothing against taking care of this (and > maybe other packages). Just start the "becoming a packager" cursus, I would be happy to mentor you.
CC: (none) => lists.jjorge
Hi, I've installed cauldron and repeated the build process on that platform successfully. The package now contains the most recent upstream tarball, plus Suse's patch. Meaning, the package can now connect to Fritzboxes also, not only to Cisco3000, and, dropped connections are re-established without interrruptions. (The latter is non-trivial. Debian / Raspbian, for instance, still does not support this. You have to reconnect manually there).
Hi, I want to emphasise that Fritzboxes are very common in Germany and it would be a great idea to have a fully working vpnc version in Mageia 8. I've tested vpnc in Mageia 8 beta 1 and it is still not working with the above mentioned hardware. The solution for me was to use the package from Markus. Even in this situation while working on the upcoming Mageia I write requesting to you integrating the completely working vpnc. Best regards and thanks a lot in advance, Jens
CC: (none) => tom.schmidt-hempel
@ Florian Wanting to CC all our German packagers, the only one I can think of now, is you. Do you mind CC'ing other German packagers (unless you want to fix vpnc yourself)? Thanks, Marja
CC: (none) => doktor5000
I'll try to take a look. According to some related forum posts, seems we need at least rev. 469 (0.5.3 is rev. 371 so quite a lot in between). Necessary changes for connection to FritzBox VPN seem to be described here: https://www.ip-phone-forum.de/threads/androiden-erobern-die-fritzbox-ipsec-vpn-zur-fritzbox.222417/
Assignee: pkg-bugs => doktor5000Status: NEW => ASSIGNED
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Hi bug reporter and hi assignee and others involved, Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly. This report is being closed as OLD because it was filed against Mageia 7, for which support ended on June 30th 2021. Thanks, Marja
Resolution: (none) => OLDStatus: ASSIGNED => RESOLVED