Cipe configuration error

[Roger Young]

Hello. I get the following error when trying
to configure cipe:

bash-3.1# ./configure
loading cache ./config.cache
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking for texinfo... no
checking for tex... tex
checking for makeinfo... makeinfo
checking for gmake... gmake
checking for kernel source tree... /usr/src/linux-2.6.18
checking for kernel version...
configure: error: Unsupported kernel version

Does this mean cipe is not compatible with this kernel
version, or is something else wrong??

Thankyou for your help,

Roger Young.

This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.


--
Message sent by the cipe-l@... mailing list.
Unsubscribe: mail majordomo@..., "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>

[Karl Kleinpaste]

Roger Young <r.young@...> writes:
> configure: error: Unsupported kernel version
> Does this mean cipe is not compatible with this kernel
> version, or is something else wrong??

I will be somewhat surprised if there is any further support for
moving CIPE into newer kernel revisions.  CIPE was very good and very
much needed for a time, but its time is past.  I suggest you examine
OpenVPN instead.

I use it quite a bit, and my first two configurations of it were to
replace previously existing CIPE links.  After a good bit of
consideration of the man page, it was possible to replace my old CIPE
links in about an hour of OpenVPN config hacking.

--
Message sent by the cipe-l@... mailing list.
Unsubscribe: mail majordomo@..., "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>

[Stephan von Krawczynski]

On Wed, 03 Jan 2007 06:53:43 -0500
Karl Kleinpaste <karl@...> wrote:

> Roger Young <r.young@...> writes:
> > configure: error: Unsupported kernel version
> > Does this mean cipe is not compatible with this kernel
> > version, or is something else wrong??
>
> I will be somewhat surprised if there is any further support for
> moving CIPE into newer kernel revisions.  CIPE was very good and very
> much needed for a time, but its time is past.  I suggest you examine
> OpenVPN instead.
>
> I use it quite a bit, and my first two configurations of it were to
> replace previously existing CIPE links.  After a good bit of
> consideration of the man page, it was possible to replace my old CIPE
> links in about an hour of OpenVPN config hacking.

Please Karl, stop that. If you like OpenVPN more please go and read/write
their mailing-list.

Roger:
what does "uname -r" say?

Regards,
Stephan

--
Message sent by the cipe-l@... mailing list.
Unsubscribe: mail majordomo@..., "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>

[Les Mikesell]

On Wed, 2007-01-03 at 17:15 +0100, Stephan von Krawczynski wrote:

> > Roger Young <r.young@...> writes:
> > > configure: error: Unsupported kernel version
> > > Does this mean cipe is not compatible with this kernel
> > > version, or is something else wrong??
> >
> > I will be somewhat surprised if there is any further support for
> > moving CIPE into newer kernel revisions.  CIPE was very good and very
> > much needed for a time, but its time is past.  I suggest you examine
> > OpenVPN instead.
> >
> > I use it quite a bit, and my first two configurations of it were to
> > replace previously existing CIPE links.  After a good bit of
> > consideration of the man page, it was possible to replace my old CIPE
> > links in about an hour of OpenVPN config hacking.
>
> Please Karl, stop that. If you like OpenVPN more please go and read/write
> their mailing-list.

Oddly enough, questions about 'unsupported kernel versions' don't
come up much on the openvpn list...  I don't think this is about
liking CIPE or not.

---
  Les Mikesell
   les@...



--
Message sent by the cipe-l@... mailing list.
Unsubscribe: mail majordomo@..., "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>

[Joachim Otahal]

Stephan von Krawczynski wrote:
> Please Karl, stop that. If you like OpenVPN more please go and read/write
> their mailing-list.
>  
Gibs auf, cipe is tot seit Mitte 2002. Gemäß deiner Homepage sollte man
auch besser die Finger von cipe lassen, hat Security Probelme by design,
es sollte nicht mehr genutzt werden. Grüße nach Bayern aus Württemberg!
(ab jetzt auf englisch:)

The Problem with cipe is that the developer themself gave up the project
since cipe has no real reason to continue, OpenVPN is more simple in
config, uses existing kernel modules (tun/tap modules), and the link is
more reliable. On top of that OpenVPN does not have "by design"
weaknesses like the cipe protocol has. OpenVPN uses some parts of
cipe-win for its Windows driver code stuff.
Check http://openvpn.net/static.html the config is sooo simple, I just
suggest to add the line 'cipher AES-256-CBC'. Server and client side
linux/windows mix is no problem, even mac osx clients exist.

You are free to continue developing cipe to work with the latest 2.4 and
2.6 kernels if you want to, cipe is somewhat dead since last code update
was January 2002 (see http://sites.inka.de/bigred/devel/cipe.html and  
http://sourceforge.net/project/showfiles.php?group_id=66201 ).

The most common OpenVPN start problems are: forgotten tun/tap kernel
modules in kernel (no prob in debian and other newer distros, just
modprobe tun) and missing /dev/net/tun device. For the latter mkdir
/dev/net and mknod /dev/net/tun c 10 200 should be sufficient (needed
for the six years old RedHat Linux 7.1 as example).

IMHO Olaf Titz should give some big notes on the cipe homepage and the
sourceforge-dl page that cipe will not be continued by him, since this
mailing list ONLY wakes up due to allways the same reason, cipe in newer
kernels/distros.

kind regards,

Joachim Otahal

> Roger:
> what does "uname -r" say?
>
> Regards,
> Stephan
>
> --
> Message sent by the cipe-l@... mailing list.
> Unsubscribe: mail majordomo@..., "unsubscribe cipe-l" in body
> Other commands available with "help" in body to the same address.
> CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>
>
>
>  

--
Message sent by the cipe-l@... mailing list.
Unsubscribe: mail majordomo@..., "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>

[Roger Young]

Thankyou for your replies and this discussion.
Relevant to this, I have also been in contact with
Hans Steegers who is the developer of cipex.
He has kindly supplied me with a patched version
of cipe (and cipex) which installs cleanly under 2.6.18.
So I no longer have a problem.
He has also indicated that he has patches for
2.6.19. The patched files are

cipex-1.6.0-0.70 (2.6.18)
cipe-1.60-StE-3  (2.6.18)
cipex-1.6.0-0.71 (2.6.19)
cipe-1.6.0.-StE-4 (2.6.19)

Regards,
Roger.

....................................................................................

On Thu, 04 Jan 2007 02:00:46 +0100
Joachim Otahal <jou@...> wrote:

> Stephan von Krawczynski wrote:
> > Please Karl, stop that. If you like OpenVPN more please go and read/write
> > their mailing-list.
> >  
> auch besser die Finger von cipe lassen, hat Security Probelme by design,
> (ab jetzt auf englisch:)
>
> The Problem with cipe is that the developer themself gave up the project
> since cipe has no real reason to continue, OpenVPN is more simple in
> config, uses existing kernel modules (tun/tap modules), and the link is
> more reliable. On top of that OpenVPN does not have "by design"
> weaknesses like the cipe protocol has. OpenVPN uses some parts of
> cipe-win for its Windows driver code stuff.
> Check http://openvpn.net/static.html the config is sooo simple, I just
> suggest to add the line 'cipher AES-256-CBC'. Server and client side
> linux/windows mix is no problem, even mac osx clients exist.
>
> You are free to continue developing cipe to work with the latest 2.4 and
> 2.6 kernels if you want to, cipe is somewhat dead since last code update
> was January 2002 (see http://sites.inka.de/bigred/devel/cipe.html and  
> http://sourceforge.net/project/showfiles.php?group_id=66201 ).
>
> The most common OpenVPN start problems are: forgotten tun/tap kernel
> modules in kernel (no prob in debian and other newer distros, just
> modprobe tun) and missing /dev/net/tun device. For the latter mkdir
> /dev/net and mknod /dev/net/tun c 10 200 should be sufficient (needed
> for the six years old RedHat Linux 7.1 as example).
>
> IMHO Olaf Titz should give some big notes on the cipe homepage and the
> sourceforge-dl page that cipe will not be continued by him, since this
> mailing list ONLY wakes up due to allways the same reason, cipe in newer
> kernels/distros.
>
> kind regards,
>
> Joachim Otahal
>
> > Roger:
> > what does "uname -r" say?
> >
> > Regards,
> > Stephan
> >
> > --
> > Message sent by the cipe-l@... mailing list.
> > Unsubscribe: mail majordomo@..., "unsubscribe cipe-l" in body
> > Other commands available with "help" in body to the same address.
> > CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>
> >
> >
> >  
>
>
> --
> Message sent by the cipe-l@... mailing list.
> Unsubscribe: mail majordomo@..., "unsubscribe cipe-l" in body
> Other commands available with "help" in body to the same address.
> CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>
>
> This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
>

--
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Dr. Roger Young
Industrial Research Ltd             Telephone: [phone]
Applied Mathematics                 Fax:       [phone]        
P O Box 31-310, Lower Hutt    Internet:  R.Young@...
New Zealand.                      
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.


--
Message sent by the cipe-l@... mailing list.
Unsubscribe: mail majordomo@..., "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>

[Stephan von Krawczynski]

On Wed, 03 Jan 2007 11:11:06 -0600
Les Mikesell <les@...> wrote:

> On Wed, 2007-01-03 at 17:15 +0100, Stephan von Krawczynski wrote:
> > > Roger Young <r.young@...> writes:
> > > > configure: error: Unsupported kernel version
> > > > Does this mean cipe is not compatible with this kernel
> > > > version, or is something else wrong??
> > >
> > > I will be somewhat surprised if there is any further support for
> > > moving CIPE into newer kernel revisions.  CIPE was very good and very
> > > much needed for a time, but its time is past.  I suggest you examine
> > > OpenVPN instead.
> > >
> > > I use it quite a bit, and my first two configurations of it were to
> > > replace previously existing CIPE links.  After a good bit of
> > > consideration of the man page, it was possible to replace my old CIPE
> > > links in about an hour of OpenVPN config hacking.
> >
> > Please Karl, stop that. If you like OpenVPN more please go and read/write
> > their mailing-list.
>
> Oddly enough, questions about 'unsupported kernel versions' don't
> come up much on the openvpn list...  I don't think this is about
> liking CIPE or not.

What did his answer have to do with the question besides the fact of teaching
how superior OpenVPN is in his eyes? He didn't give a damn about the
question ... what did his answer have to do with cipe? Exactly zero.

--
Regards,
Stephan

--
Message sent by the cipe-l@... mailing list.
Unsubscribe: mail majordomo@..., "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>

[Eric M. Hopper]

On Thu, 2007-01-04 at 04:28 +0100, Stephan von Krawczynski wrote:
> What did his answer have to do with the question besides the fact of
> teaching how superior OpenVPN is in his eyes? He didn't give a damn
> about the question ... what did his answer have to do with cipe?
> Exactly zero.

I think the question of whether or not CIPE is still a useful project
given that OpenVPN exists and has such broad cross-platform support is a
question that is very relevant to CIPE.

I too feel that CIPE has reached the end of its usefulness and that
perhaps something else should be chosen by people who want the
functionality it offered.  There are other choices that are clearly
better in almost every respect.

Have fun (if at all possible),
--
The best we can hope for concerning the people at large is that they
be properly armed.  -- Alexander Hamilton
-- Eric Hopper (hopper@...  http://www.omnifarious.org/~hopper) --

[Karl Kleinpaste]

skraw@... wrote:
>> What did his answer have to do with the question besides the fact of
>> teaching how superior OpenVPN is in his eyes? He didn't give a damn about
>> the question ... what did his answer have to do with cipe? Exactly zero.

hopper@... writes:
> I think the question of whether or not CIPE is still a useful project
> given that OpenVPN exists and has such broad cross-platform support is a
> question that is very relevant to CIPE.
> I too feel that CIPE has reached the end of its usefulness

CIPE is old.  It's a plain fact.  And what my answer had to do with
CIPE was the simple fact of that age, and the implications of using a
tool of such advanced years.

When it came into existence, it was needed and very much welcome.  But
there is no longer anything CIPE can do that other systems, notably
but not exclusively OpenVPN, cannot do better and with less pain,
especially in the area of maintaining compatibility with every new
point-release of the kernel, CIPE being all alone in that need.

The only reasons I can conceive for deploying it freshly now are:
[a] Ignorance.  We all start out ignorant; ignorance is not
    blameworthy in itself.  But it is a correctable condition.
[b] New obligations (e.g. business partners) with it already in use.
[c] Foolishness.
Stated differently:
[a] You aren't aware that you have a choice.
[b] You genuinely don't have a choice.
[c] You make a poor choice.

I made contributions to CIPE in its earlier years; I believe I started
using it when it was in the 0.4 stage, but I no longer remember for
sure, it's been over a decade.  And I spent a fair amount of time on
this list (my archives show ~150 messages I've sent to cipe-l), rarely
asking questions of my own and usually helping others configure it and
get a handle on how to route through a tunnel.  But I'm bright enough
to know when it is time to move on.

--
Message sent by the cipe-l@... mailing list.
Unsubscribe: mail majordomo@..., "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>