Your message dated Wed, 19 Oct 2005 13:32:33 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#334203: fixed in vpnc 0.3.3+SVN20050909-5
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 16 Oct 2005 10:29:10 +0000
>From [EMAIL PROTECTED] Sun Oct 16 03:29:10 2005
Return-path: <[EMAIL PROTECTED]>
Received: from khan.acc.umu.se [130.239.18.139] (postfix)
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1ER5lO-00019L-00; Sun, 16 Oct 2005 03:29:10 -0700
Received: from localhost (localhost [127.0.0.1])
        by amavisd-new (Postfix) with ESMTP id 6DF68D204
        for <[EMAIL PROTECTED]>; Sun, 16 Oct 2005 12:29:08 +0200 (MEST)
Received: by khan.acc.umu.se (Postfix, from userid 23136)
        id 2E37BD203; Sun, 16 Oct 2005 12:29:06 +0200 (MEST)
Date: Sun, 16 Oct 2005 12:29:06 +0200
From: David Weinehall <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: vpnc 0.3.3 route troubles
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-Editor: Vi Improved <http://www.vim.org/>
X-Accept-Language: Swedish, English
X-GPG-Fingerprint: 7ACE 0FB0 7A74 F994 9B36  E1D1 D14E 8526 DC47 CA16
X-GPG-Key: http://www.acc.umu.se/~tao/files/pub_dc47ca16.gpg.asc
X-Virus-Scanned: by amavisd-new at acc.umu.se
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: vpnc
Version: 0.3.3+SVN20050909-4
Severity: important

With the latest few 0.3.3 svn snapshots of vpnc, the routing information
no longer seems to be set up correctly.  Also, there's an extra warning
about RTNETLINK there wasn't there in the old (0.3.2-snapshot) version.
vpnc 0.3.2+SVN20050326-2 works for me, newer versions doesn't.


vpnc 0.3.2+SVN20050326-2:

smyslov:~# vpnc-connect <config>
Enter password for <censored>
vpnc version 0.3.2
IKE SA selected psk+xauth-3des-sha1
NAT status: this end behind NAT? YES -- remote end behind NAT? no
got address 10.162.253.115
IPSEC SA selected 3des-sha1
VPNC started in background (pid: 9318)...
smyslov:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
<censored>      <censored>      255.255.255.255 UGH   0      0        0 eth0
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
default         *               0.0.0.0         U     0      0        0 tun0


vpnc 0.3.3++SVN20050909-4:

smyslov:~: vpnc-connect <config>
Enter password for <censored>
vpnc version 0.3.3
IKE SA selected psk+xauth-3des-sha1
NAT status: this end behind NAT? YES -- remote end behind NAT? no
got address 10.162.252.184
IPSEC SA selected 3des-sha1
RTNETLINK answers: File exists
VPNC started in background (pid: 9525)...
smyslov:~/deb# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
<censored>      <censored>      255.255.255.255 UGH   0      0        0 eth0
<censored>      *               255.255.255.255 UH    0      0        0 tun0
<censored>      *               255.255.255.255 UH    0      0        0 tun0
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
10.162.252.0    *               255.255.254.0   U     0      0        0 tun0
default         <censored>      0.0.0.0         UG    0      0        0 eth0


disconnected:

smyslov:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
default         128.1.168.192.i 0.0.0.0         UG    0      0        0 eth0


Clearly the new vpnc sets up several extra route entries compared to
the old vpnc.  The old vpnc works, the new one doesn't.

Because of company security policy I've had to censor quite a lot of
details, I hope there's enough left to give you a clue anyway.

Justification for severity: makes the package useless at least with
this particular setup.  I cannot tell whether it's a generic problem
or a specific problem, hence I'm not using Severity: grave.


Regards: David Weinehall
-- 
 /) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window           (\
//  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~   //  Diamond-white roses of fire //
\)  http://www.acc.umu.se/~tao/    (/   Beautiful hoar-frost       (/

---------------------------------------
Received: (at 334203-close) by bugs.debian.org; 19 Oct 2005 20:38:02 +0000
>From [EMAIL PROTECTED] Wed Oct 19 13:38:02 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1ESKbx-0003jz-00; Wed, 19 Oct 2005 13:32:33 -0700
From: Eduard Bloch <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#334203: fixed in vpnc 0.3.3+SVN20050909-5
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 19 Oct 2005 13:32:33 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Source: vpnc
Source-Version: 0.3.3+SVN20050909-5

We believe that the bug you reported is fixed in the latest version of
vpnc, which is due to be installed in the Debian FTP archive:

vpnc_0.3.3+SVN20050909-5.diff.gz
  to pool/main/v/vpnc/vpnc_0.3.3+SVN20050909-5.diff.gz
vpnc_0.3.3+SVN20050909-5.dsc
  to pool/main/v/vpnc/vpnc_0.3.3+SVN20050909-5.dsc
vpnc_0.3.3+SVN20050909-5_i386.deb
  to pool/main/v/vpnc/vpnc_0.3.3+SVN20050909-5_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Eduard Bloch <[EMAIL PROTECTED]> (supplier of updated vpnc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 13 Oct 2005 22:14:39 +0200
Source: vpnc
Binary: vpnc
Architecture: source i386
Version: 0.3.3+SVN20050909-5
Distribution: unstable
Urgency: low
Maintainer: Eduard Bloch <[EMAIL PROTECTED]>
Changed-By: Eduard Bloch <[EMAIL PROTECTED]>
Description: 
 vpnc       - Cisco-compatible VPN client
Closes: 334203 334699
Changes: 
 vpnc (0.3.3+SVN20050909-5) unstable; urgency=low
 .
   * set the default string "No" for DNS_UPDATE (closes: #334699)
   * do not see any additional routes sent by the server when the
     TARGET_NETWORKS is set (closes: #334203)
Files: 
 3703281723ce2d1680699809ab3698a8 610 net extra vpnc_0.3.3+SVN20050909-5.dsc
 05a7777c4c73cecfe03fbf73d14d448d 15833 net extra 
vpnc_0.3.3+SVN20050909-5.diff.gz
 efb86fd1c1a353cd34505fa528e3b928 52226 net extra 
vpnc_0.3.3+SVN20050909-5_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDVpRS4QZIHu3wCMURAto+AJ4gv2trGsLN3T6/UK1N2kYY0kNlZgCdEWpu
WFOgowozRL6tCfA94BVHzLY=
=b9Bh
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to