Nabble - CIPE

cipe with new kernel version

2008-01-10T11:20:59Z

Hello all,

can i get a littlle help here using cipe? Are there any new patches to use
cipe with newer kernel releases? I want to use the 2.6.23.12 release and get
errors while compiling.

cipe/device.c:172: error: `CRYPTO_TFM_MODE_CBC' undeclared (first use in this
function)

and some more all in device.c.

Thanks in advance
Regards

Dirk
--

--
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>

Compile CIPE in module then ship to another machine with 2.4.32 kernel

2007-05-25T00:13:44Z

I am terribly sorry to trouble you with my problem. I have an IPcop box
running and it has CIPE for inter-office connection, the box was installed
years ago in IPcop version 1.4.6, the cipcb.o is in the kernel module and
loaded from the rc.local file.

Until recently, I would need to upgrade the IPcop to the latest version,
currently 1.4.15 (kernel 2.4.34, I copied the cipcb.o to the new machine,
when I do a modprobe cipcb it complained about the wrong kernel.

I have another FC5 machine, downloaded the cipe 1.6 trying to compile one
then copy the cipcb to the IPcop 1.4.15, but I find that the kernel of the
FC5 is 2.6.xx.

I am wondering, is there a way of compile a matched cipcb.o copy to the
IPcop machine, as the IPcop does not have the sources and the gcc compiler.

I could not find the original inventor who put the cipcb.o in the machine,
in the /lib/modules/2.4.29/kernel/misc directory.

Many thanks in advance.

--
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>

Centos-4.4 kernel and REGPARAM option

2007-02-14T05:03:25Z

Hello!

Compiling cipe with --enable-regparam builds a module that will panic as soon as you run ciped.

How can I fix this issue without recompiling the kernel without the REGPARAM option?

Regards,

Andrei

Re: Cipe configuration error

2007-01-04T17:19:47Z

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>

Re: Up-to-date versions of CIPE/CIPEX.

2007-01-04T15:33:43Z

Hans Steegers writes:
> I am amazed so many undertakers are still
> lurking this list.
> Many of them were very active in the Gutmann
> security discussion (2003).
> None of them contributed anything to the
> development of CIPE.

Hmmm ... I've kept quiet this go around so far,
but I'd qualify as an "undertaker" who still lurks
here and who did contribute a little ... I wrote
and made available by ftp patches that got a few
cipe people through the kernel api changes around
kernel versions 2.6.10 to 2.6.14. (Somebody even
downloaded my 2.6.14 patch this morning.)

I stopped developing patches because A) my last
cipe user canceled his account, and B) people like
Hans were doing a better job anyway.

I am curious, though, what the rationale is for
carrying on with cipe or cipe-derived development
or use. As someone with a lot of experience with
both cipe and OpenVPN, the only advantage I can
think of for cipe is that it was there when we
needed it.

That was monumental at the time, and cipe deserves
a shining place of honor in the history of Linux -
and, for that matter, in the history of computing,
but the operative word is "history".

I wrote my first computer program in 1964 (!), and
in the many years since then I've had to learn to
recognize when it was time to let treasured things
go. A few years ago I was actively promoting cipe
and selling cipe-based tunnels. Today, I would no
more recommend using cipe than I would using
029's.

(For the youngsters out there, IBM 029's were the
typewriter-like machines that punched the holes in
IBM cards.)

Perhaps Hans can give a good reason for continuing
cipe, but so far I haven't seen one. As an
elderly geek who has been replaced by younger
blood, I can assert there is no loss of honor in
being replaced. Those who replaced me will
achieve more not because they are inherently
better but because they have better stuff to build
upon. So it is with OpenVPN. It builds upon a
base that simply wasn't there when cipe was in its
glory. By utilizing what is available now,
OpenVPN can and does achieve things cipe cannot.

So I would say it is time to "let go" of cipe and
to remember it as it was when it was the only act
in town. Trying to keep it going when there is no
good reason to do so risks having it remembered
not as something grand but as something that
couldn't keep up. It deserves having its place of
honor in history preserved.

--
Dick St.Peters, stpeters@...
Gatekeeper, NetHeaven, Saratoga Springs, NY

--
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>

Re: Up-to-date versions of CIPE/CIPEX.

2007-01-04T12:30:22Z

Hans Steegers wrote:
> For those who still are using CIPE(X), I
> still maintain a site at:
> http://www.hsx.dds.nl/software/cipexpatch/cipexpatch.html
> with links to up-to-date versions of CIPE/CIPEX.
>
Woot!
It is still alive, thank you!
Now I can keep some hardware-dieing cipe boxes on newer hardware by just
updating the kernel to the latest 2.4 version and keep the distro the
way it is. Saves time and hassle.

Joachim Otahal

--
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>

Re: Up-to-date versions of CIPE/CIPEX.

2007-01-04T06:20:22Z

Hans Steegers wrote:

> Hi all,
> I am amazed so many undertakers are still
> lurking this list.
> Many of them were very active in the Gutmann
> security discussion (2003).
> None of them contributed anything to the
> development of CIPE.
>
> For those who still are using CIPE(X), I
> still maintain a site at:
> http://www.hsx.dds.nl/software/cipexpatch/cipexpatch.html
> with links to up-to-date versions of CIPE/CIPEX.

I still have a few boxes running Linux 2.4 kernels with CIPE
still working happily, but have been changing to openvpn when
updating because it provides equivalent functionality without
having to patch anything - and I have both running on a hub
machine so they are interchangeable at the end points. Perhaps
you are in the best position to comment on whether there is
anything specific about CIPE that makes it worth having to
patch the kernel on every update when there is a packaged openvpn
available or included for most distributions.

--
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>

Up-to-date versions of CIPE/CIPEX.

2007-01-04T05:28:33Z

Hi all,
I am amazed so many undertakers are still
lurking this list.
Many of them were very active in the Gutmann
security discussion (2003).
None of them contributed anything to the
development of CIPE.

For those who still are using CIPE(X), I
still maintain a site at:
http://www.hsx.dds.nl/software/cipexpatch/cipexpatch.html
with links to up-to-date versions of CIPE/CIPEX.

__________________________________________________
Hans Steegers

--
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>

Re: Cipe configuration error

2007-01-03T23:28:20Z

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) --

signature.asc (192 bytes) Download Attachment

Re: Cipe configuration error

2007-01-03T19:28:11Z

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>

Re: Cipe configuration error

2007-01-03T18:58:46Z

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: 64-4-5690-247
Applied Mathematics Fax: 64-4-5690-003
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>

Re: Cipe configuration error

2007-01-03T17:00:46Z

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>

Re: Cipe configuration error

2007-01-03T09:11:06Z

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>

Re: Cipe configuration error

2007-01-03T08:15:28Z

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>

Re: Cipe configuration error

2007-01-03T03:53:43Z

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>

Cipe configuration error

2007-01-02T21:35:46Z

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>

CIPE-WIN32 ON WINDOWS XP SP2

2006-11-06T07:36:35Z

Hello

i'm kamrul fr malaysia. i'm computer vendor for my government. i already setup cipe vpn using linux slackware n it's perfect running. my government already using this around 5 year without problem. now they can link around 180 site using cipe between slackware server n slackware server.

now i got new problem, anybody know how to configure cipe on windows xp sp2. i already tired to try the solution fr this site until now i can't get the connection. anybody expert to help me pls.

ref site : http://article.gmane.org/gmane.comp.encryption.cipe/2228

Re: Peer IP number log

2006-08-15T10:07:13Z

This is one of the most annoying things.

I hacked this in once a long time ago, and lost the hack. (Along with my other
foreground hacks to facilitate use in inittab, which I re-created). You can
pick this up in syslog with the 'New Peer' entry. The syslog entry is
generated by the *kernel module*, not the ciped-cb process, the latter calls
the cipe up script. There was something difficult about this, and frankly I
don't remember what I did. If I get bored one day I may look at it again,
but I want to figure out openVPN, which I may replace CIPE with. There are a
number of things about CIPE I like though, in particular the way I've got it
foregrounded and using inittab. It makes it trivial to bring a tunnel up and
down.

--KS

On Tuesday 15 August 2006 02:37 am, you wrote:
> Hi all,
>
> Is there any way to get the peer's carrier IP number in the ip-up script,
> say for log purposes? The $5 variable in that script contains the cipe
> device IP number, but it would be nice to log the carrier IP number of the
> connecting machine as well.
>
> --Mahdavian

--
Keith Smith keith@...
655 W Fremont Dr
Tempe AZ 85282 it's hot

attachment0 (196 bytes) Download Attachment

Peer IP number log

2006-08-15T03:37:35Z

Hi all,

Is there any way to get the peer's carrier IP number in the ip-up script, say for log purposes? The $5 variable in that script contains the cipe device IP number, but it would be nice to log the carrier IP number of the connecting machine as well.

--Mahdavian

Kernel Panic ...

2006-07-20T20:52:43Z

I've noted an issue with CIPE recently that required some other ethx
interface to be up and running before you load the cipcb *module*. Not
doing this causes a kernel panic. Why is beyond me, and I haven't
investigated that much to be honest. Caused me no end of grief for
quite a long time.

Now I just make sure my eth modules are loaded and the interface is up
and allow cipcb to autoload later.

Let me know if this helps. I'm currently typing this on a connection
using my patch!

--KS

Konstantin Kubatkin wrote:

>> I got on 2.6.17.6/Slack 10.2
>>
>> Source/patches at http://www.ksmith.com top of page, or these links:
>>
>> http://www.ksmith.com/cipe/cipe-1.6.0-3.tar.bz2
>>
>> http://www.ksmith.com/cipe/cipe-1.6.0-1.6.0-3.diff
>>
>> YMMV, use at your own risk.
>>
>> Header file problems is all...
>
> I got on 2.6.17.6, Debian/testing
>
> I apply the given patch and I receive a following mistake ( in attach )
>
> ------------------------------------------------------------------------
>
> Jul 20 15:04:36 ip54 kernel: cipc: CIPE driver vers 1.6.0 (c) Olaf Titz 1996-2003, 100 channels, debug=1
> Jul 20 15:04:36 ip54 kernel: cipc: cipe_alloc_dev 0
> Jul 20 15:04:51 ip54 kernel: cipc0: alloc
> Jul 20 15:04:51 ip54 kernel: cipc0: setpar
> Jul 20 15:04:51 ip54 kernel: crypto_alloc_tfm `blowfish-internal'
> Jul 20 15:04:51 ip54 kernel: cipc0: setpar 0.0.0.0:0 2500 150000 0200 0
> Jul 20 15:04:51 ip54 kernel: cipc0: setkey
> Jul 20 15:04:51 ip54 kernel: BUG: unable to handle kernel paging request at virtual address f5b17a8b
> Jul 20 15:04:51 ip54 kernel: printing eip:
> Jul 20 15:04:51 ip54 kernel: c01fc4a8
> Jul 20 15:04:51 ip54 kernel: *pde = 00000000
> Jul 20 15:04:51 ip54 kernel: Oops: 0000 [#1]
> Jul 20 15:04:51 ip54 kernel: Modules linked in: cipc crc32 parport_pc parport via686a hwmon serio_raw i2c_isa i2c_viapro 3c59x mii ide_cd cdrom i2c_core
> Jul 20 15:04:51 ip54 kernel: CPU: 0
> Jul 20 15:04:51 ip54 kernel: EIP: 0060:[<c01fc4a8>] Not tainted VLI
> Jul 20 15:04:51 ip54 kernel: EFLAGS: 00010286 (2.6.17 #2)
> Jul 20 15:04:51 ip54 kernel: EIP is at __dev_get_by_name+0x5b/0x8c
> Jul 20 15:04:51 ip54 kernel: eax: ffffffff ebx: de167f40 ecx: 0000000f edx: decd51a4
> Jul 20 15:04:51 ip54 kernel: esi: decd51a5 edi: de167f41 ebp: f5b17a8b esp: de167ef8
> Jul 20 15:04:51 ip54 kernel: ds: 007b es: 007b ss: 0068
> Jul 20 15:04:51 ip54 kernel: Process ciped-c (pid: 2724, threadinfo=de166000 task=dfe61a50)
> Jul 20 15:04:51 ip54 kernel: Stack: de167f40 00000001 000089f3 00000000 c01fd890 de167f40 c01fe432 bfbf3ec4
> Jul 20 15:04:51 ip54 kernel: c012f9fa de167f68 de2a543c df13b3c0 df13b404 dfb480ec 00000000 00000002
> Jul 20 15:04:51 ip54 kernel: c0286e48 00000000 63706963 bfbf0030 0804cd32 00000063 bfbf3fa4 0000000a
> Jul 20 15:04:51 ip54 kernel: Call Trace:
> Jul 20 15:04:51 ip54 kernel: <c01fd890> dev_load+0x8/0x26 <c01fe432> dev_ioctl+0x35b/0x3a2
> Jul 20 15:04:51 ip54 kernel: <c012f9fa> filemap_nopage+0x166/0x2c0 <c01f55a7> sock_ioctl+0x0/0x1a2
> Jul 20 15:04:51 ip54 kernel: <c0150a52> do_ioctl+0x16/0x48 <c0150c86> vfs_ioctl+0x202/0x219
> Jul 20 15:04:51 ip54 kernel: <c0150cc9> sys_ioctl+0x2c/0x43 <c010249f> syscall_call+0x7/0xb
> Jul 20 15:04:51 ip54 kernel: Code: 04 8d 04 07 01 d0 6b f8 0b 4e 41 83 fe ff 75 e5 89 f8 25 ff 00 00 00 8b 2c 85 e0 9c 2f c0 eb 03 8b 6d 00 85 ed 75 04 31 d2 eb 2a <8b> 45 00 8d 44 20 00 8d 55 f0 b9 10 00 00 00 89 df 89 d6 49 78
> Jul 20 15:04:51 ip54 kernel: EIP: [<c01fc4a8>] __dev_get_by_name+0x5b/0x8c SS:ESP 0068:de167ef8
> Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
> Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c01f7348> lock_sock+0x84/0x8b
> Jul 20 15:04:51 ip54 kernel: <c0135ee5> free_pgd_range+0x127/0x14a <c01f53ff> sock_fasync+0x54/0xf7
> Jul 20 15:04:51 ip54 kernel: <c01f619f> sock_close+0x1e/0x2a <c01442d3> __fput+0x87/0x116
> Jul 20 15:04:51 ip54 kernel: <c0141fb8> filp_close+0x4e/0x54 <c010fe3e> put_files_struct+0x63/0xa5
> Jul 20 15:04:51 ip54 kernel: <c0110c7f> do_exit+0x190/0x624 <c010f270> printk+0x14/0x18
> Jul 20 15:04:51 ip54 kernel: <c0102f25> die+0x1fd/0x205 <c010a9fb> do_page_fault+0x0/0x52b
> Jul 20 15:04:51 ip54 kernel: <c010ae44> do_page_fault+0x449/0x52b <c010a9fb> do_page_fault+0x0/0x52b
> Jul 20 15:04:51 ip54 kernel: <c01026c7> error_code+0x4f/0x54 <c01fc4a8> __dev_get_by_name+0x5b/0x8c
> Jul 20 15:04:51 ip54 kernel: <c01fd890> dev_load+0x8/0x26 <c01fe432> dev_ioctl+0x35b/0x3a2
> Jul 20 15:04:51 ip54 kernel: <c012f9fa> filemap_nopage+0x166/0x2c0 <c01f55a7> sock_ioctl+0x0/0x1a2
> Jul 20 15:04:51 ip54 kernel: <c0150a52> do_ioctl+0x16/0x48 <c0150c86> vfs_ioctl+0x202/0x219
> Jul 20 15:04:51 ip54 kernel: <c0150cc9> sys_ioctl+0x2c/0x43 <c010249f> syscall_call+0x7/0xb
> Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
> Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c01f5497> sock_fasync+0xec/0xf7
> Jul 20 15:04:51 ip54 kernel: <c01f619f> sock_close+0x1e/0x2a <c01442d3> __fput+0x87/0x116
> Jul 20 15:04:51 ip54 kernel: <c0141fb8> filp_close+0x4e/0x54 <c010fe3e> put_files_struct+0x63/0xa5
> Jul 20 15:04:51 ip54 kernel: <c0110c7f> do_exit+0x190/0x624 <c010f270> printk+0x14/0x18
> Jul 20 15:04:51 ip54 kernel: <c0102f25> die+0x1fd/0x205 <c010a9fb> do_page_fault+0x0/0x52b
> Jul 20 15:04:51 ip54 kernel: <c010ae44> do_page_fault+0x449/0x52b <c010a9fb> do_page_fault+0x0/0x52b
> Jul 20 15:04:51 ip54 kernel: <c01026c7> error_code+0x4f/0x54 <c01fc4a8> __dev_get_by_name+0x5b/0x8c
> Jul 20 15:04:51 ip54 kernel: <c01fd890> dev_load+0x8/0x26 <c01fe432> dev_ioctl+0x35b/0x3a2
> Jul 20 15:04:51 ip54 kernel: <c012f9fa> filemap_nopage+0x166/0x2c0 <c01f55a7> sock_ioctl+0x0/0x1a2
> Jul 20 15:04:51 ip54 kernel: <c0150a52> do_ioctl+0x16/0x48 <c0150c86> vfs_ioctl+0x202/0x219
> Jul 20 15:04:51 ip54 kernel: <c0150cc9> sys_ioctl+0x2c/0x43 <c010249f> syscall_call+0x7/0xb
> Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
> Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c0240f25> unix_release_sock+0x3c/0x179
> Jul 20 15:04:51 ip54 kernel: <c01f5fa9> sock_release+0x11/0x63 <c01f61a7> sock_close+0x26/0x2a
> Jul 20 15:04:51 ip54 kernel: <c01442d3> __fput+0x87/0x116 <c0141fb8> filp_close+0x4e/0x54
> Jul 20 15:04:51 ip54 kernel: <c010fe3e> put_files_struct+0x63/0xa5 <c0110c7f> do_exit+0x190/0x624
> Jul 20 15:04:51 ip54 kernel: <c010f270> printk+0x14/0x18 <c0102f25> die+0x1fd/0x205
> Jul 20 15:04:51 ip54 kernel: <c010a9fb> do_page_fault+0x0/0x52b <c010ae44> do_page_fault+0x449/0x52b
> Jul 20 15:04:51 ip54 kernel: <c010a9fb> do_page_fault+0x0/0x52b <c01026c7> error_code+0x4f/0x54
> Jul 20 15:04:51 ip54 kernel: <c01fc4a8> __dev_get_by_name+0x5b/0x8c <c01fd890> dev_load+0x8/0x26
> Jul 20 15:04:51 ip54 kernel: <c01fe432> dev_ioctl+0x35b/0x3a2 <c012f9fa> filemap_nopage+0x166/0x2c0
> Jul 20 15:04:51 ip54 kernel: <c01f55a7> sock_ioctl+0x0/0x1a2 <c0150a52> do_ioctl+0x16/0x48
> Jul 20 15:04:51 ip54 kernel: <c0150c86> vfs_ioctl+0x202/0x219 <c0150cc9> sys_ioctl+0x2c/0x43
> Jul 20 15:04:51 ip54 kernel: <c010249f> syscall_call+0x7/0xb
> Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
> Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c01f7348> lock_sock+0x84/0x8b
> Jul 20 15:04:51 ip54 kernel: <c01f53ff> sock_fasync+0x54/0xf7 <c01f619f> sock_close+0x1e/0x2a
> Jul 20 15:04:51 ip54 kernel: <c01442d3> __fput+0x87/0x116 <c0141fb8> filp_close+0x4e/0x54
> Jul 20 15:04:51 ip54 kernel: <c010fe3e> put_files_struct+0x63/0xa5 <c0110c7f> do_exit+0x190/0x624
> Jul 20 15:04:51 ip54 kernel: <c010f270> printk+0x14/0x18 <c0102f25> die+0x1fd/0x205
> Jul 20 15:04:51 ip54 kernel: <c010a9fb> do_page_fault+0x0/0x52b <c010ae44> do_page_fault+0x449/0x52b
> Jul 20 15:04:51 ip54 kernel: <c010a9fb> do_page_fault+0x0/0x52b <c01026c7> error_code+0x4f/0x54
> Jul 20 15:04:51 ip54 kernel: <c01fc4a8> __dev_get_by_name+0x5b/0x8c <c01fd890> dev_load+0x8/0x26
> Jul 20 15:04:51 ip54 kernel: <c01fe432> dev_ioctl+0x35b/0x3a2 <c012f9fa> filemap_nopage+0x166/0x2c0
> Jul 20 15:04:51 ip54 kernel: <c01f55a7> sock_ioctl+0x0/0x1a2 <c0150a52> do_ioctl+0x16/0x48
> Jul 20 15:04:51 ip54 kernel: <c0150c86> vfs_ioctl+0x202/0x219 <c0150cc9> sys_ioctl+0x2c/0x43
> Jul 20 15:04:51 ip54 kernel: <c010249f> syscall_call+0x7/0xb
> Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
> Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c01f5497> sock_fasync+0xec/0xf7
> Jul 20 15:04:51 ip54 kernel: <c01f619f> sock_close+0x1e/0x2a <c01442d3> __fput+0x87/0x116
> Jul 20 15:04:51 ip54 kernel: <c0141fb8> filp_close+0x4e/0x54 <c010fe3e> put_files_struct+0x63/0xa5
> Jul 20 15:04:51 ip54 kernel: <c0110c7f> do_exit+0x190/0x624 <c010f270> printk+0x14/0x18
> Jul 20 15:04:51 ip54 kernel: <c0102f25> die+0x1fd/0x205 <c010a9fb> do_page_fault+0x0/0x52b
> Jul 20 15:04:51 ip54 kernel: <c010ae44> do_page_fault+0x449/0x52b <c010a9fb> do_page_fault+0x0/0x52b
> Jul 20 15:04:51 ip54 kernel: <c01026c7> error_code+0x4f/0x54 <c01fc4a8> __dev_get_by_name+0x5b/0x8c
> Jul 20 15:04:51 ip54 kernel: <c01fd890> dev_load+0x8/0x26 <c01fe432> dev_ioctl+0x35b/0x3a2
> Jul 20 15:04:51 ip54 kernel: <c012f9fa> filemap_nopage+0x166/0x2c0 <c01f55a7> sock_ioctl+0x0/0x1a2
> Jul 20 15:04:51 ip54 kernel: <c0150a52> do_ioctl+0x16/0x48 <c0150c86> vfs_ioctl+0x202/0x219
> Jul 20 15:04:51 ip54 kernel: <c0150cc9> sys_ioctl+0x2c/0x43 <c010249f> syscall_call+0x7/0xb
> Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
> Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c01f7348> lock_sock+0x84/0x8b
> Jul 20 15:04:51 ip54 kernel: <c010303a> dump_stack+0x13/0x15 <c022a201> udp_destroy_sock+0x8/0x1a
> Jul 20 15:04:51 ip54 kernel: <c01f7738> sk_common_release+0x11/0x89 <c0230168> inet_release+0x43/0x48
> Jul 20 15:04:51 ip54 kernel: <c01f5fa9> sock_release+0x11/0x63 <c01f61a7> sock_close+0x26/0x2a
> Jul 20 15:04:51 ip54 kernel: <c01442d3> __fput+0x87/0x116 <c0141fb8> filp_close+0x4e/0x54
> Jul 20 15:04:51 ip54 kernel: <c010fe3e> put_files_struct+0x63/0xa5 <c0110c7f> do_exit+0x190/0x624
> Jul 20 15:04:51 ip54 kernel: <c010f270> printk+0x14/0x18 <c0102f25> die+0x1fd/0x205
> Jul 20 15:04:51 ip54 kernel: <c010a9fb> do_page_fault+0x0/0x52b <c010ae44> do_page_fault+0x449/0x52b
> Jul 20 15:04:51 ip54 kernel: <c010a9fb> do_page_fault+0x0/0x52b <c01026c7> error_code+0x4f/0x54
> Jul 20 15:04:51 ip54 kernel: <c01fc4a8> __dev_get_by_name+0x5b/0x8c <c01fd890> dev_load+0x8/0x26
> Jul 20 15:04:51 ip54 kernel: <c01fe432> dev_ioctl+0x35b/0x3a2 <c012f9fa> filemap_nopage+0x166/0x2c0
> Jul 20 15:04:51 ip54 kernel: <c01f55a7> sock_ioctl+0x0/0x1a2 <c0150a52> do_ioctl+0x16/0x48
> Jul 20 15:04:51 ip54 kernel: <c0150c86> vfs_ioctl+0x202/0x219 <c0150cc9> sys_ioctl+0x2c/0x43
> Jul 20 15:04:51 ip54 kernel: <c010249f> syscall_call+0x7/0xb
> Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
> Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c022a20f> udp_destroy_sock+0x16/0x1a
> Jul 20 15:04:51 ip54 kernel: <c01f7738> sk_common_release+0x11/0x89 <c0230168> inet_release+0x43/0x48
> Jul 20 15:04:51 ip54 kernel: <c01f5fa9> sock_release+0x11/0x63 <c01f61a7> sock_close+0x26/0x2a
> Jul 20 15:04:51 ip54 kernel: <c01442d3> __fput+0x87/0x116 <c0141fb8> filp_close+0x4e/0x54
> Jul 20 15:04:51 ip54 kernel: <c010fe3e> put_files_struct+0x63/0xa5 <c0110c7f> do_exit+0x190/0x624
> Jul 20 15:04:51 ip54 kernel: <c010f270> printk+0x14/0x18 <c0102f25> die+0x1fd/0x205
> Jul 20 15:04:51 ip54 kernel: <c010a9fb> do_page_fault+0x0/0x52b <c010ae44> do_page_fault+0x449/0x52b
> Jul 20 15:04:51 ip54 kernel: <c010a9fb> do_page_fault+0x0/0x52b <c01026c7> error_code+0x4f/0x54
> Jul 20 15:04:51 ip54 kernel: <c01fc4a8> __dev_get_by_name+0x5b/0x8c <c01fd890> dev_load+0x8/0x26
> Jul 20 15:04:51 ip54 kernel: <c01fe432> dev_ioctl+0x35b/0x3a2 <c012f9fa> filemap_nopage+0x166/0x2c0
> Jul 20 15:04:51 ip54 kernel: <c01f55a7> sock_ioctl+0x0/0x1a2 <c0150a52> do_ioctl+0x16/0x48
> Jul 20 15:04:51 ip54 kernel: <c0150c86> vfs_ioctl+0x202/0x219 <c0150cc9> sys_ioctl+0x2c/0x43
> Jul 20 15:04:51 ip54 kernel: <c010249f> syscall_call+0x7/0xb
> Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
> Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c01f7740> sk_common_release+0x19/0x89
> Jul 20 15:04:51 ip54 kernel: <c0230168> inet_release+0x43/0x48 <c01f5fa9> sock_release+0x11/0x63
> Jul 20 15:04:51 ip54 kernel: <c01f61a7> sock_close+0x26/0x2a <c01442d3> __fput+0x87/0x116
> Jul 20 15:04:51 ip54 kernel: <c0141fb8> filp_close+0x4e/0x54 <c010fe3e> put_files_struct+0x63/0xa5
> Jul 20 15:04:51 ip54 kernel: <c0110c7f> do_exit+0x190/0x624 <c010f270> printk+0x14/0x18
> Jul 20 15:04:51 ip54 kernel: <c0102f25> die+0x1fd/0x205 <c010a9fb> do_page_fault+0x0/0x52b
> Jul 20 15:04:51 ip54 kernel: <c010ae44> do_page_fault+0x449/0x52b <c010a9fb> do_page_fault+0x0/0x52b
> Jul 20 15:04:51 ip54 kernel: <c01026c7> error_code+0x4f/0x54 <c01fc4a8> __dev_get_by_name+0x5b/0x8c
> Jul 20 15:04:51 ip54 kernel: <c01fd890> dev_load+0x8/0x26 <c01fe432> dev_ioctl+0x35b/0x3a2
> Jul 20 15:04:51 ip54 kernel: <c012f9fa> filemap_nopage+0x166/0x2c0 <c01f55a7> sock_ioctl+0x0/0x1a2
> Jul 20 15:04:51 ip54 kernel: <c0150a52> do_ioctl+0x16/0x48 <c0150c86> vfs_ioctl+0x202/0x219
> Jul 20 15:04:51 ip54 kernel: <c0150cc9> sys_ioctl+0x2c/0x43 <c010249f> syscall_call+0x7/0xb
> Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
> Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c01f776c> sk_common_release+0x45/0x89
> Jul 20 15:04:51 ip54 kernel: <c0230168> inet_release+0x43/0x48 <c01f5fa9> sock_release+0x11/0x63
> Jul 20 15:04:51 ip54 kernel: <c01f61a7> sock_close+0x26/0x2a <c01442d3> __fput+0x87/0x116
> Jul 20 15:04:51 ip54 kernel: <c0141fb8> filp_close+0x4e/0x54 <c010fe3e> put_files_struct+0x63/0xa5
> Jul 20 15:04:51 ip54 kernel: <c0110c7f> do_exit+0x190/0x624 <c010f270> printk+0x14/0x18
> Jul 20 15:04:51 ip54 kernel: <c0102f25> die+0x1fd/0x205 <c010a9fb> do_page_fault+0x0/0x52b
> Jul 20 15:04:51 ip54 kernel: <c010ae44> do_page_fault+0x449/0x52b <c010a9fb> do_page_fault+0x0/0x52b
> Jul 20 15:04:51 ip54 kernel: <c01026c7> error_code+0x4f/0x54 <c01fc4a8> __dev_get_by_name+0x5b/0x8c
> Jul 20 15:04:51 ip54 kernel: <c01fd890> dev_load+0x8/0x26 <c01fe432> dev_ioctl+0x35b/0x3a2
> Jul 20 15:04:51 ip54 kernel: <c012f9fa> filemap_nopage+0x166/0x2c0 <c01f55a7> sock_ioctl+0x0/0x1a2
> Jul 20 15:04:51 ip54 kernel: <c0150a52> do_ioctl+0x16/0x48 <c0150c86> vfs_ioctl+0x202/0x219
> Jul 20 15:04:51 ip54 kernel: <c0150cc9> sys_ioctl+0x2c/0x43 <c010249f> syscall_call+0x7/0xb
>

Re: cipe-1.6.0 kernel 2.6.17.5 kubuntu 6.0.6

2006-07-20T06:14:36Z

> I got on 2.6.17.6/Slack 10.2

>
> Source/patches at http://www.ksmith.com top of page, or these links:
>
> http://www.ksmith.com/cipe/cipe-1.6.0-3.tar.bz2
>
> http://www.ksmith.com/cipe/cipe-1.6.0-1.6.0-3.diff
>
> YMMV, use at your own risk.
>
> Header file problems is all...

I got on 2.6.17.6, Debian/testing

I apply the given patch and I receive a following mistake ( in attach )

--
Konstantin Kubatkin [KUB-RIPE] [KUB-UANIC]
Kherson, TriLogiC Group
Fido: 2:468/13@FidoNet

Jul 20 15:04:36 ip54 kernel: cipc: CIPE driver vers 1.6.0 (c) Olaf Titz 1996-2003, 100 channels, debug=1
Jul 20 15:04:36 ip54 kernel: cipc: cipe_alloc_dev 0
Jul 20 15:04:51 ip54 kernel: cipc0: alloc
Jul 20 15:04:51 ip54 kernel: cipc0: setpar
Jul 20 15:04:51 ip54 kernel: crypto_alloc_tfm `blowfish-internal'
Jul 20 15:04:51 ip54 kernel: cipc0: setpar 0.0.0.0:0 2500 150000 0200 0
Jul 20 15:04:51 ip54 kernel: cipc0: setkey
Jul 20 15:04:51 ip54 kernel: BUG: unable to handle kernel paging request at virtual address f5b17a8b
Jul 20 15:04:51 ip54 kernel: printing eip:
Jul 20 15:04:51 ip54 kernel: c01fc4a8
Jul 20 15:04:51 ip54 kernel: *pde = 00000000
Jul 20 15:04:51 ip54 kernel: Oops: 0000 [#1]
Jul 20 15:04:51 ip54 kernel: Modules linked in: cipc crc32 parport_pc parport via686a hwmon serio_raw i2c_isa i2c_viapro 3c59x mii ide_cd cdrom i2c_core
Jul 20 15:04:51 ip54 kernel: CPU: 0
Jul 20 15:04:51 ip54 kernel: EIP: 0060:[<c01fc4a8>] Not tainted VLI
Jul 20 15:04:51 ip54 kernel: EFLAGS: 00010286 (2.6.17 #2)
Jul 20 15:04:51 ip54 kernel: EIP is at __dev_get_by_name+0x5b/0x8c
Jul 20 15:04:51 ip54 kernel: eax: ffffffff ebx: de167f40 ecx: 0000000f edx: decd51a4
Jul 20 15:04:51 ip54 kernel: esi: decd51a5 edi: de167f41 ebp: f5b17a8b esp: de167ef8
Jul 20 15:04:51 ip54 kernel: ds: 007b es: 007b ss: 0068
Jul 20 15:04:51 ip54 kernel: Process ciped-c (pid: 2724, threadinfo=de166000 task=dfe61a50)
Jul 20 15:04:51 ip54 kernel: Stack: de167f40 00000001 000089f3 00000000 c01fd890 de167f40 c01fe432 bfbf3ec4
Jul 20 15:04:51 ip54 kernel: c012f9fa de167f68 de2a543c df13b3c0 df13b404 dfb480ec 00000000 00000002
Jul 20 15:04:51 ip54 kernel: c0286e48 00000000 63706963 bfbf0030 0804cd32 00000063 bfbf3fa4 0000000a
Jul 20 15:04:51 ip54 kernel: Call Trace:
Jul 20 15:04:51 ip54 kernel: <c01fd890> dev_load+0x8/0x26 <c01fe432> dev_ioctl+0x35b/0x3a2
Jul 20 15:04:51 ip54 kernel: <c012f9fa> filemap_nopage+0x166/0x2c0 <c01f55a7> sock_ioctl+0x0/0x1a2
Jul 20 15:04:51 ip54 kernel: <c0150a52> do_ioctl+0x16/0x48 <c0150c86> vfs_ioctl+0x202/0x219
Jul 20 15:04:51 ip54 kernel: <c0150cc9> sys_ioctl+0x2c/0x43 <c010249f> syscall_call+0x7/0xb
Jul 20 15:04:51 ip54 kernel: Code: 04 8d 04 07 01 d0 6b f8 0b 4e 41 83 fe ff 75 e5 89 f8 25 ff 00 00 00 8b 2c 85 e0 9c 2f c0 eb 03 8b 6d 00 85 ed 75 04 31 d2 eb 2a <8b> 45 00 8d 44 20 00 8d 55 f0 b9 10 00 00 00 89 df 89 d6 49 78
Jul 20 15:04:51 ip54 kernel: EIP: [<c01fc4a8>] __dev_get_by_name+0x5b/0x8c SS:ESP 0068:de167ef8
Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c01f7348> lock_sock+0x84/0x8b
Jul 20 15:04:51 ip54 kernel: <c0135ee5> free_pgd_range+0x127/0x14a <c01f53ff> sock_fasync+0x54/0xf7
Jul 20 15:04:51 ip54 kernel: <c01f619f> sock_close+0x1e/0x2a <c01442d3> __fput+0x87/0x116
Jul 20 15:04:51 ip54 kernel: <c0141fb8> filp_close+0x4e/0x54 <c010fe3e> put_files_struct+0x63/0xa5
Jul 20 15:04:51 ip54 kernel: <c0110c7f> do_exit+0x190/0x624 <c010f270> printk+0x14/0x18
Jul 20 15:04:51 ip54 kernel: <c0102f25> die+0x1fd/0x205 <c010a9fb> do_page_fault+0x0/0x52b
Jul 20 15:04:51 ip54 kernel: <c010ae44> do_page_fault+0x449/0x52b <c010a9fb> do_page_fault+0x0/0x52b
Jul 20 15:04:51 ip54 kernel: <c01026c7> error_code+0x4f/0x54 <c01fc4a8> __dev_get_by_name+0x5b/0x8c
Jul 20 15:04:51 ip54 kernel: <c01fd890> dev_load+0x8/0x26 <c01fe432> dev_ioctl+0x35b/0x3a2
Jul 20 15:04:51 ip54 kernel: <c012f9fa> filemap_nopage+0x166/0x2c0 <c01f55a7> sock_ioctl+0x0/0x1a2
Jul 20 15:04:51 ip54 kernel: <c0150a52> do_ioctl+0x16/0x48 <c0150c86> vfs_ioctl+0x202/0x219
Jul 20 15:04:51 ip54 kernel: <c0150cc9> sys_ioctl+0x2c/0x43 <c010249f> syscall_call+0x7/0xb
Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c01f5497> sock_fasync+0xec/0xf7
Jul 20 15:04:51 ip54 kernel: <c01f619f> sock_close+0x1e/0x2a <c01442d3> __fput+0x87/0x116
Jul 20 15:04:51 ip54 kernel: <c0141fb8> filp_close+0x4e/0x54 <c010fe3e> put_files_struct+0x63/0xa5
Jul 20 15:04:51 ip54 kernel: <c0110c7f> do_exit+0x190/0x624 <c010f270> printk+0x14/0x18
Jul 20 15:04:51 ip54 kernel: <c0102f25> die+0x1fd/0x205 <c010a9fb> do_page_fault+0x0/0x52b
Jul 20 15:04:51 ip54 kernel: <c010ae44> do_page_fault+0x449/0x52b <c010a9fb> do_page_fault+0x0/0x52b
Jul 20 15:04:51 ip54 kernel: <c01026c7> error_code+0x4f/0x54 <c01fc4a8> __dev_get_by_name+0x5b/0x8c
Jul 20 15:04:51 ip54 kernel: <c01fd890> dev_load+0x8/0x26 <c01fe432> dev_ioctl+0x35b/0x3a2
Jul 20 15:04:51 ip54 kernel: <c012f9fa> filemap_nopage+0x166/0x2c0 <c01f55a7> sock_ioctl+0x0/0x1a2
Jul 20 15:04:51 ip54 kernel: <c0150a52> do_ioctl+0x16/0x48 <c0150c86> vfs_ioctl+0x202/0x219
Jul 20 15:04:51 ip54 kernel: <c0150cc9> sys_ioctl+0x2c/0x43 <c010249f> syscall_call+0x7/0xb
Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c0240f25> unix_release_sock+0x3c/0x179
Jul 20 15:04:51 ip54 kernel: <c01f5fa9> sock_release+0x11/0x63 <c01f61a7> sock_close+0x26/0x2a
Jul 20 15:04:51 ip54 kernel: <c01442d3> __fput+0x87/0x116 <c0141fb8> filp_close+0x4e/0x54
Jul 20 15:04:51 ip54 kernel: <c010fe3e> put_files_struct+0x63/0xa5 <c0110c7f> do_exit+0x190/0x624
Jul 20 15:04:51 ip54 kernel: <c010f270> printk+0x14/0x18 <c0102f25> die+0x1fd/0x205
Jul 20 15:04:51 ip54 kernel: <c010a9fb> do_page_fault+0x0/0x52b <c010ae44> do_page_fault+0x449/0x52b
Jul 20 15:04:51 ip54 kernel: <c010a9fb> do_page_fault+0x0/0x52b <c01026c7> error_code+0x4f/0x54
Jul 20 15:04:51 ip54 kernel: <c01fc4a8> __dev_get_by_name+0x5b/0x8c <c01fd890> dev_load+0x8/0x26
Jul 20 15:04:51 ip54 kernel: <c01fe432> dev_ioctl+0x35b/0x3a2 <c012f9fa> filemap_nopage+0x166/0x2c0
Jul 20 15:04:51 ip54 kernel: <c01f55a7> sock_ioctl+0x0/0x1a2 <c0150a52> do_ioctl+0x16/0x48
Jul 20 15:04:51 ip54 kernel: <c0150c86> vfs_ioctl+0x202/0x219 <c0150cc9> sys_ioctl+0x2c/0x43
Jul 20 15:04:51 ip54 kernel: <c010249f> syscall_call+0x7/0xb
Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c01f7348> lock_sock+0x84/0x8b
Jul 20 15:04:51 ip54 kernel: <c01f53ff> sock_fasync+0x54/0xf7 <c01f619f> sock_close+0x1e/0x2a
Jul 20 15:04:51 ip54 kernel: <c01442d3> __fput+0x87/0x116 <c0141fb8> filp_close+0x4e/0x54
Jul 20 15:04:51 ip54 kernel: <c010fe3e> put_files_struct+0x63/0xa5 <c0110c7f> do_exit+0x190/0x624
Jul 20 15:04:51 ip54 kernel: <c010f270> printk+0x14/0x18 <c0102f25> die+0x1fd/0x205
Jul 20 15:04:51 ip54 kernel: <c010a9fb> do_page_fault+0x0/0x52b <c010ae44> do_page_fault+0x449/0x52b
Jul 20 15:04:51 ip54 kernel: <c010a9fb> do_page_fault+0x0/0x52b <c01026c7> error_code+0x4f/0x54
Jul 20 15:04:51 ip54 kernel: <c01fc4a8> __dev_get_by_name+0x5b/0x8c <c01fd890> dev_load+0x8/0x26
Jul 20 15:04:51 ip54 kernel: <c01fe432> dev_ioctl+0x35b/0x3a2 <c012f9fa> filemap_nopage+0x166/0x2c0
Jul 20 15:04:51 ip54 kernel: <c01f55a7> sock_ioctl+0x0/0x1a2 <c0150a52> do_ioctl+0x16/0x48
Jul 20 15:04:51 ip54 kernel: <c0150c86> vfs_ioctl+0x202/0x219 <c0150cc9> sys_ioctl+0x2c/0x43
Jul 20 15:04:51 ip54 kernel: <c010249f> syscall_call+0x7/0xb
Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c01f5497> sock_fasync+0xec/0xf7
Jul 20 15:04:51 ip54 kernel: <c01f619f> sock_close+0x1e/0x2a <c01442d3> __fput+0x87/0x116
Jul 20 15:04:51 ip54 kernel: <c0141fb8> filp_close+0x4e/0x54 <c010fe3e> put_files_struct+0x63/0xa5
Jul 20 15:04:51 ip54 kernel: <c0110c7f> do_exit+0x190/0x624 <c010f270> printk+0x14/0x18
Jul 20 15:04:51 ip54 kernel: <c0102f25> die+0x1fd/0x205 <c010a9fb> do_page_fault+0x0/0x52b
Jul 20 15:04:51 ip54 kernel: <c010ae44> do_page_fault+0x449/0x52b <c010a9fb> do_page_fault+0x0/0x52b
Jul 20 15:04:51 ip54 kernel: <c01026c7> error_code+0x4f/0x54 <c01fc4a8> __dev_get_by_name+0x5b/0x8c
Jul 20 15:04:51 ip54 kernel: <c01fd890> dev_load+0x8/0x26 <c01fe432> dev_ioctl+0x35b/0x3a2
Jul 20 15:04:51 ip54 kernel: <c012f9fa> filemap_nopage+0x166/0x2c0 <c01f55a7> sock_ioctl+0x0/0x1a2
Jul 20 15:04:51 ip54 kernel: <c0150a52> do_ioctl+0x16/0x48 <c0150c86> vfs_ioctl+0x202/0x219
Jul 20 15:04:51 ip54 kernel: <c0150cc9> sys_ioctl+0x2c/0x43 <c010249f> syscall_call+0x7/0xb
Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c01f7348> lock_sock+0x84/0x8b
Jul 20 15:04:51 ip54 kernel: <c010303a> dump_stack+0x13/0x15 <c022a201> udp_destroy_sock+0x8/0x1a
Jul 20 15:04:51 ip54 kernel: <c01f7738> sk_common_release+0x11/0x89 <c0230168> inet_release+0x43/0x48
Jul 20 15:04:51 ip54 kernel: <c01f5fa9> sock_release+0x11/0x63 <c01f61a7> sock_close+0x26/0x2a
Jul 20 15:04:51 ip54 kernel: <c01442d3> __fput+0x87/0x116 <c0141fb8> filp_close+0x4e/0x54
Jul 20 15:04:51 ip54 kernel: <c010fe3e> put_files_struct+0x63/0xa5 <c0110c7f> do_exit+0x190/0x624
Jul 20 15:04:51 ip54 kernel: <c010f270> printk+0x14/0x18 <c0102f25> die+0x1fd/0x205
Jul 20 15:04:51 ip54 kernel: <c010a9fb> do_page_fault+0x0/0x52b <c010ae44> do_page_fault+0x449/0x52b
Jul 20 15:04:51 ip54 kernel: <c010a9fb> do_page_fault+0x0/0x52b <c01026c7> error_code+0x4f/0x54
Jul 20 15:04:51 ip54 kernel: <c01fc4a8> __dev_get_by_name+0x5b/0x8c <c01fd890> dev_load+0x8/0x26
Jul 20 15:04:51 ip54 kernel: <c01fe432> dev_ioctl+0x35b/0x3a2 <c012f9fa> filemap_nopage+0x166/0x2c0
Jul 20 15:04:51 ip54 kernel: <c01f55a7> sock_ioctl+0x0/0x1a2 <c0150a52> do_ioctl+0x16/0x48
Jul 20 15:04:51 ip54 kernel: <c0150c86> vfs_ioctl+0x202/0x219 <c0150cc9> sys_ioctl+0x2c/0x43
Jul 20 15:04:51 ip54 kernel: <c010249f> syscall_call+0x7/0xb
Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c022a20f> udp_destroy_sock+0x16/0x1a
Jul 20 15:04:51 ip54 kernel: <c01f7738> sk_common_release+0x11/0x89 <c0230168> inet_release+0x43/0x48
Jul 20 15:04:51 ip54 kernel: <c01f5fa9> sock_release+0x11/0x63 <c01f61a7> sock_close+0x26/0x2a
Jul 20 15:04:51 ip54 kernel: <c01442d3> __fput+0x87/0x116 <c0141fb8> filp_close+0x4e/0x54
Jul 20 15:04:51 ip54 kernel: <c010fe3e> put_files_struct+0x63/0xa5 <c0110c7f> do_exit+0x190/0x624
Jul 20 15:04:51 ip54 kernel: <c010f270> printk+0x14/0x18 <c0102f25> die+0x1fd/0x205
Jul 20 15:04:51 ip54 kernel: <c010a9fb> do_page_fault+0x0/0x52b <c010ae44> do_page_fault+0x449/0x52b
Jul 20 15:04:51 ip54 kernel: <c010a9fb> do_page_fault+0x0/0x52b <c01026c7> error_code+0x4f/0x54
Jul 20 15:04:51 ip54 kernel: <c01fc4a8> __dev_get_by_name+0x5b/0x8c <c01fd890> dev_load+0x8/0x26
Jul 20 15:04:51 ip54 kernel: <c01fe432> dev_ioctl+0x35b/0x3a2 <c012f9fa> filemap_nopage+0x166/0x2c0
Jul 20 15:04:51 ip54 kernel: <c01f55a7> sock_ioctl+0x0/0x1a2 <c0150a52> do_ioctl+0x16/0x48
Jul 20 15:04:51 ip54 kernel: <c0150c86> vfs_ioctl+0x202/0x219 <c0150cc9> sys_ioctl+0x2c/0x43
Jul 20 15:04:51 ip54 kernel: <c010249f> syscall_call+0x7/0xb
Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c01f7740> sk_common_release+0x19/0x89
Jul 20 15:04:51 ip54 kernel: <c0230168> inet_release+0x43/0x48 <c01f5fa9> sock_release+0x11/0x63
Jul 20 15:04:51 ip54 kernel: <c01f61a7> sock_close+0x26/0x2a <c01442d3> __fput+0x87/0x116
Jul 20 15:04:51 ip54 kernel: <c0141fb8> filp_close+0x4e/0x54 <c010fe3e> put_files_struct+0x63/0xa5
Jul 20 15:04:51 ip54 kernel: <c0110c7f> do_exit+0x190/0x624 <c010f270> printk+0x14/0x18
Jul 20 15:04:51 ip54 kernel: <c0102f25> die+0x1fd/0x205 <c010a9fb> do_page_fault+0x0/0x52b
Jul 20 15:04:51 ip54 kernel: <c010ae44> do_page_fault+0x449/0x52b <c010a9fb> do_page_fault+0x0/0x52b
Jul 20 15:04:51 ip54 kernel: <c01026c7> error_code+0x4f/0x54 <c01fc4a8> __dev_get_by_name+0x5b/0x8c
Jul 20 15:04:51 ip54 kernel: <c01fd890> dev_load+0x8/0x26 <c01fe432> dev_ioctl+0x35b/0x3a2
Jul 20 15:04:51 ip54 kernel: <c012f9fa> filemap_nopage+0x166/0x2c0 <c01f55a7> sock_ioctl+0x0/0x1a2
Jul 20 15:04:51 ip54 kernel: <c0150a52> do_ioctl+0x16/0x48 <c0150c86> vfs_ioctl+0x202/0x219
Jul 20 15:04:51 ip54 kernel: <c0150cc9> sys_ioctl+0x2c/0x43 <c010249f> syscall_call+0x7/0xb
Jul 20 15:04:51 ip54 kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
Jul 20 15:04:51 ip54 kernel: <c01126ae> local_bh_enable+0x25/0x58 <c01f776c> sk_common_release+0x45/0x89
Jul 20 15:04:51 ip54 kernel: <c0230168> inet_release+0x43/0x48 <c01f5fa9> sock_release+0x11/0x63
Jul 20 15:04:51 ip54 kernel: <c01f61a7> sock_close+0x26/0x2a <c01442d3> __fput+0x87/0x116
Jul 20 15:04:51 ip54 kernel: <c0141fb8> filp_close+0x4e/0x54 <c010fe3e> put_files_struct+0x63/0xa5
Jul 20 15:04:51 ip54 kernel: <c0110c7f> do_exit+0x190/0x624 <c010f270> printk+0x14/0x18
Jul 20 15:04:51 ip54 kernel: <c0102f25> die+0x1fd/0x205 <c010a9fb> do_page_fault+0x0/0x52b
Jul 20 15:04:51 ip54 kernel: <c010ae44> do_page_fault+0x449/0x52b <c010a9fb> do_page_fault+0x0/0x52b
Jul 20 15:04:51 ip54 kernel: <c01026c7> error_code+0x4f/0x54 <c01fc4a8> __dev_get_by_name+0x5b/0x8c
Jul 20 15:04:51 ip54 kernel: <c01fd890> dev_load+0x8/0x26 <c01fe432> dev_ioctl+0x35b/0x3a2
Jul 20 15:04:51 ip54 kernel: <c012f9fa> filemap_nopage+0x166/0x2c0 <c01f55a7> sock_ioctl+0x0/0x1a2
Jul 20 15:04:51 ip54 kernel: <c0150a52> do_ioctl+0x16/0x48 <c0150c86> vfs_ioctl+0x202/0x219
Jul 20 15:04:51 ip54 kernel: <c0150cc9> sys_ioctl+0x2c/0x43 <c010249f> syscall_call+0x7/0xb

Re: cipe-1.6.0 kernel 2.6.17.5 kubuntu 6.0.6

2006-07-18T10:34:32Z

Hello Keith,

just downloaded new kernel and cipe sources. Compiling works quit well and
loading the module was no problem. CIpe Interface exists and near the end of
the week i will connect the new gateway to my dsl device.

Many thanks for your good tip.

Regards

Am Dienstag, 18. Juli 2006 04:33 schrieben Sie:

> I got on 2.6.17.6/Slack 10.2
>
> Source/patches at http://www.ksmith.com top of page, or these links:
>
> http://www.ksmith.com/cipe/cipe-1.6.0-3.tar.bz2
>
> http://www.ksmith.com/cipe/cipe-1.6.0-1.6.0-3.diff
>
> YMMV, use at your own risk.
>
> Header file problems is all...
>
> --KS
>
> Dirk Jakobsmeier wrote:
> >Hello all,
> >
> >i´m trying to get cipe compiled on an 2.6.17.5 kernel. Applied
> >cipe-2.6.14.patch and the changes to cipe/output.c. While compiling i got
> > the following:
> >
> >/cipe-1.6.0/2.6.17.5gateway-i386-cb/output.c: In Funktion »cipe_xmit«:
> >/cipe-1.6.0/2.6.17.5gateway-i386-cb/output.c:176: Fehler: »struct
> > inet_sock« hat kein Element namens »inet«
> >/cipe-1.6.0/2.6.17.5gateway-i386-cb/output.c:198: Fehler: »struct
> > inet_sock« hat kein Element namens »inet«
> >make[3]: *** [/tmp/cipe-1.6.0/2.6.17.5gateway-i386-cb/output.o] Fehler 1
> >make[2]: *** [_module_/tmp/cipe-1.6.0/2.6.17.5gateway-i386-cb] Fehler 2
> >make[2]: Leaving directory `/usr/src/linux-2.6.17.5'
> >make[1]: *** [all25] Fehler 2
> >make[1]: Leaving directory `/tmp/cipe-1.6.0/2.6.17.5gateway-i386-cb'
> >make: *** [all] Fehler 2
> >
> >Can anybody help me finding this missing element called "inet" ;-) ?
> >
> >Regards
> >
> >Dirk
> >
> >--
> >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>

Re: cipe-1.6.0 kernel 2.6.17.5 kubuntu 6.0.6

2006-07-17T20:33:38Z

I got on 2.6.17.6/Slack 10.2

Source/patches at http://www.ksmith.com top of page, or these links:

http://www.ksmith.com/cipe/cipe-1.6.0-3.tar.bz2

http://www.ksmith.com/cipe/cipe-1.6.0-1.6.0-3.diff

YMMV, use at your own risk.

Header file problems is all...

--KS

Dirk Jakobsmeier wrote:

>Hello all,
>
>i´m trying to get cipe compiled on an 2.6.17.5 kernel. Applied
>cipe-2.6.14.patch and the changes to cipe/output.c. While compiling i got the
>following:
>
>/cipe-1.6.0/2.6.17.5gateway-i386-cb/output.c: In Funktion »cipe_xmit«:
>/cipe-1.6.0/2.6.17.5gateway-i386-cb/output.c:176: Fehler: »struct inet_sock«
>hat kein Element namens »inet«
>/cipe-1.6.0/2.6.17.5gateway-i386-cb/output.c:198: Fehler: »struct inet_sock«
>hat kein Element namens »inet«
>make[3]: *** [/tmp/cipe-1.6.0/2.6.17.5gateway-i386-cb/output.o] Fehler 1
>make[2]: *** [_module_/tmp/cipe-1.6.0/2.6.17.5gateway-i386-cb] Fehler 2
>make[2]: Leaving directory `/usr/src/linux-2.6.17.5'
>make[1]: *** [all25] Fehler 2
>make[1]: Leaving directory `/tmp/cipe-1.6.0/2.6.17.5gateway-i386-cb'
>make: *** [all] Fehler 2
>
>Can anybody help me finding this missing element called "inet" ;-) ?
>
>Regards
>
>Dirk
>
>--
>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>
>
>

signature.asc (352 bytes) Download Attachment
signature.asc (264 bytes) Download Attachment

Re: cipe-1.6.0 kernel 2.6.17.5 kubuntu 6.0.6

2006-07-16T12:26:37Z

Dirk Jakobsmeier writes:

> Hello all,
>
> iÂ´m trying to get cipe compiled on an 2.6.17.5 kernel. Applied
> cipe-2.6.14.patch and the changes to cipe/output.c. While compiling i got the
> following:
>
> /cipe-1.6.0/2.6.17.5gateway-i386-cb/output.c: In Funktion Â»cipe_xmitÂ«:
> /cipe-1.6.0/2.6.17.5gateway-i386-cb/output.c:176: Fehler: Â»struct inet_sockÂ«
> hat kein Element namens Â»inetÂ«
> /cipe-1.6.0/2.6.17.5gateway-i386-cb/output.c:198: Fehler: Â»struct inet_sockÂ«
> hat kein Element namens Â»inetÂ«
> make[3]: *** [/tmp/cipe-1.6.0/2.6.17.5gateway-i386-cb/output.o] Fehler 1
> make[2]: *** [_module_/tmp/cipe-1.6.0/2.6.17.5gateway-i386-cb] Fehler 2
> make[2]: Leaving directory `/usr/src/linux-2.6.17.5'
> make[1]: *** [all25] Fehler 2
> make[1]: Leaving directory `/tmp/cipe-1.6.0/2.6.17.5gateway-i386-cb'
> make: *** [all] Fehler 2
>
> Can anybody help me finding this missing element called "inet" ;-) ?

I can give you some clues. The problem lies in the definition of the
IOPT macro, which is defined in cipe/cipe.h. The stock cipe.h defines
IOPT as
#define IOPT(c) (&(c)->sock->inet)

That's OK for older 2.6 kernels, but newer kernels require
#define IOPT(c) ((c)->sock)

The 2.6.14 patch (assuming you're talking about my 2.6.14 patch)
changes the definition and wraps the change in a test of the kernel
release:
#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,12)
#define IOPT(c) (&(c)->sock->inet)
#else
#define IOPT(c) ((c)->sock)
#endif

(I'm not sure 2.6.12 is the correct branching point for this change,
but that won't affect kernels later than 2.6.12.)

It appears that
- You applied some patch other than mine, or
- Your build is picking up another cipe.h, or
- Your build is finding a kernel build directory for an older
release

For CIPE to live on, it needs someone or some group to step forward
and take on maintenance. For awhile I thought I might be in a
position to do that, but my life took a different turn. I believe
there is now a project to maintain CIPE, based on SourceForge I think.

--
Dick St.Peters, stpeters@...

--
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>

cipe-1.6.0 kernel 2.6.17.5 kubuntu 6.0.6

2006-07-16T02:37:12Z

Hello all,

i´m trying to get cipe compiled on an 2.6.17.5 kernel. Applied
cipe-2.6.14.patch and the changes to cipe/output.c. While compiling i got the
following:

/cipe-1.6.0/2.6.17.5gateway-i386-cb/output.c: In Funktion »cipe_xmit«:
/cipe-1.6.0/2.6.17.5gateway-i386-cb/output.c:176: Fehler: »struct inet_sock«
hat kein Element namens »inet«
/cipe-1.6.0/2.6.17.5gateway-i386-cb/output.c:198: Fehler: »struct inet_sock«
hat kein Element namens »inet«
make[3]: *** [/tmp/cipe-1.6.0/2.6.17.5gateway-i386-cb/output.o] Fehler 1
make[2]: *** [_module_/tmp/cipe-1.6.0/2.6.17.5gateway-i386-cb] Fehler 2
make[2]: Leaving directory `/usr/src/linux-2.6.17.5'
make[1]: *** [all25] Fehler 2
make[1]: Leaving directory `/tmp/cipe-1.6.0/2.6.17.5gateway-i386-cb'
make: *** [all] Fehler 2

Can anybody help me finding this missing element called "inet" ;-) ?

Regards

Dirk

--
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>

Re: Configure problems

2006-06-24T02:34:25Z

Hi Ken,

generally - not only for this case - you should have a link there. The files
almost all distros have copied there belong to their respective kernels, but
kernel.org (or others) may well vary. This is why you should link the trees if
starting to compile own kernels. Applications using these includes depend on
them fitting your kernel.
Let me stress: I do not know if this cures your problem, but nevertheless the
hint per se is correct.

Regards,
Stephan

On Fri, 23 Jun 2006 20:07:45 +0700
"Ken Hilliard" <ken@...> wrote:

> Stephan,
>
> In Fedora Core 2 both of the directories you referenced are directories
> that contain actual include files. It does look like they contain
> similar files but with different creation dates and sizes. Do I have to
> move the contents of "/usr/include/linux" to some new location and
> create a symlink to "/usr/src/linux/include/linux"? Is this
> requirement/procedure documented somewhere? I don't have any experience
> doing kernel rebuilds. Much thanks for the help.
>
> regards, Ken
>
> -----Original Message-----
> From: Stephan von Krawczynski [mailto:skraw@...]
> Sent: Friday, June 23, 2006 5:20 PM
> To: Ken Hilliard
> Cc: cipe-l@...
> Subject: Re: Configure problems
>
>
> Does your
>
> /usr/include/linux point to /usr/src/linux/include/linux ?
>
> Regards,
> Stephan
>
>
> On Fri, 23 Jun 2006 03:13:46 +0700
> "Ken Hilliard" <ken@...> wrote:
>
> > I'm using RedHat FC2, kernel version 2.6.5-1.358. I downloaded cipe
> > 1.6 and unziped it into a tmp directory. I then created a symlink
> > 'linux' that pointed to my kernel source directory:
> >
> > cd /usr/src
> > ln -s linux-2.6.5-1.358 linux
> >
> > I went back to the temp cipe directory and ran
> >
> > ./configure
> >
> > I got the following error message:
> >
> > ...error: no suitable configured kernel source tree found
> >
> > The source code is installed. I can run xconfig to check the kernel's
> > current configuration. I have no idea what to do. I saw several post
> > with this same problem but did not see any solutions.
> >
> > Help!
> >
> >
> >
> > --
> > 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>
>

RE: Configure problems

2006-06-23T07:07:45Z

Stephan,

In Fedora Core 2 both of the directories you referenced are directories
that contain actual include files. It does look like they contain
similar files but with different creation dates and sizes. Do I have to
move the contents of "/usr/include/linux" to some new location and
create a symlink to "/usr/src/linux/include/linux"? Is this
requirement/procedure documented somewhere? I don't have any experience
doing kernel rebuilds. Much thanks for the help.

regards, Ken

-----Original Message-----
From: Stephan von Krawczynski [mailto:skraw@...]
Sent: Friday, June 23, 2006 5:20 PM
To: Ken Hilliard
Cc: cipe-l@...
Subject: Re: Configure problems

Does your

/usr/include/linux point to /usr/src/linux/include/linux ?

Regards,
Stephan

On Fri, 23 Jun 2006 03:13:46 +0700
"Ken Hilliard" <ken@...> wrote:

> I'm using RedHat FC2, kernel version 2.6.5-1.358. I downloaded cipe
> 1.6 and unziped it into a tmp directory. I then created a symlink
> 'linux' that pointed to my kernel source directory:
>
> cd /usr/src
> ln -s linux-2.6.5-1.358 linux
>
> I went back to the temp cipe directory and ran
>
> ./configure
>
> I got the following error message:
>
> ...error: no suitable configured kernel source tree found
>
> The source code is installed. I can run xconfig to check the kernel's
> current configuration. I have no idea what to do. I saw several post
> with this same problem but did not see any solutions.
>
> Help!
>
>
>
> --
> 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>

Re: Configure problems

2006-06-23T04:19:34Z

Does your

/usr/include/linux point to /usr/src/linux/include/linux ?

Regards,
Stephan

On Fri, 23 Jun 2006 03:13:46 +0700
"Ken Hilliard" <ken@...> wrote:

> I'm using RedHat FC2, kernel version 2.6.5-1.358. I downloaded cipe 1.6
> and unziped it into a tmp directory. I then created a symlink 'linux'
> that pointed to my kernel source directory:
>
> cd /usr/src
> ln -s linux-2.6.5-1.358 linux
>
> I went back to the temp cipe directory and ran
>
> ./configure
>
> I got the following error message:
>
> ...error: no suitable configured kernel source tree found
>
> The source code is installed. I can run xconfig to check the kernel's
> current configuration. I have no idea what to do. I saw several post
> with this same problem but did not see any solutions.
>
> Help!
>
>
>
> --
> 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>
>

Configure problems

2006-06-22T14:13:46Z

I'm using RedHat FC2, kernel version 2.6.5-1.358. I downloaded cipe 1.6
and unziped it into a tmp directory. I then created a symlink 'linux'
that pointed to my kernel source directory:

cd /usr/src
ln -s linux-2.6.5-1.358 linux

I went back to the temp cipe directory and ran

./configure

I got the following error message:

...error: no suitable configured kernel source tree found

The source code is installed. I can run xconfig to check the kernel's
current configuration. I have no idea what to do. I saw several post
with this same problem but did not see any solutions.

Help!

--
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>

Re: How to install CIPE

2006-06-21T09:17:39Z

As described here
http://sites.inka.de/sites/bigred/devel/cipe-doc/cipe_2.html#SEC9
the module is named linke cipc* where the last letter is the cipher.

You can also search the module in your linux machine doing:

# modprobe -l | grep cipc

Regards,
Giacomo

Amaury Rodriguez ha scritto:

> I compiled CIPE 1.6.0 on a CentOS system, but I'm not
> sure what's the next. What's the name of the cipe
> module?
>
>
> Att. Amaury
>
> Amaury Rodríguez
>
>
> http://liberadospucmm.blogspot.com
> http://groups.msn.com/telematicaPUCMM2002
>
> Go OpenSource And Be FREE!!
>
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> --
> 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>
>
>

--

Giacomo Gorgellino
Contisoft srl
Str. del Drosso 128/35
10135 TORINO
Tel: +39-0113979808
Fax: +39-0113979353

--
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>

Re: How to install CIPE

2006-06-21T08:57:44Z

On Wed, 2006-06-21 at 06:38 -0700, Amaury Rodriguez wrote:
> I compiled CIPE 1.6.0 on a CentOS system, but I'm not
> sure what's the next. What's the name of the cipe
> module?

The module should be cipcb, but if you are just starting
with CIPE on a 2.6 kernel based system, I'd recommend using
OpenVPN instead. It has more current development and with
recent kernels you no longer need the interface-specific
code that CIPE provides.

--
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>

How to install CIPE

2006-06-21T07:38:11Z

I compiled CIPE 1.6.0 on a CentOS system, but I'm not
sure what's the next. What's the name of the cipe
module?

Att. Amaury

Amaury Rodríguez

http://liberadospucmm.blogspot.com
http://groups.msn.com/telematicaPUCMM2002

Go OpenSource And Be FREE!!

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

--
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>

Re: Compile error on kernel 2.6.16

2006-05-28T09:29:04Z

On 5/28/06, Erik Wallin <erikw@...> wrote:

> For recent kernels you need to apply a few patches to build cipe-1.6.0.
> Different ones are required from kernel 2.6.11 and upwards. The latest
> one is needed from kernel version 2.6.14 and upwards. I've tried it with
> success on 2.6.15 and 2.6.16 (but, see below). You can download it from
> the sourceforge project site:
>
> http://sourceforge.net/tracker/?group_id=66201&atid=513682
> <http://sourceforge.net/tracker/?group_id=66201&atid=513682>
>
> For kernel 2.6.16 you need an additional patch that I emailed to the
> list a few days ago. It's only a trivial addition of a missing include file.
>
> Add the following line to cipe/output.c
>
> #include <net/ip.h>
> +#include <net/route.h>
> #include <net/icmp.h>

I downloaded, and asuccessfully applied cipe-2.6.14.patch, and made
the change to cipe/output.c.

Compile still fails:

gcc -o ciped-cb ciped.o options.o ioctl.o ucrc32.o -L../lib -lcipe
gmake -C /usr/src/linux-2.6.16
SUBDIRS=/usr/src/cipe-1.6.0/2.6.16-i386-cb modules
gmake[2]: Entering directory `/usr/src/linux-2.6.16'
CC [M] /usr/src/cipe-1.6.0/2.6.16-i386-cb/module.o
In file included from /usr/src/cipe-1.6.0/2.6.16-i386-cb/module.c:15:
/usr/src/cipe-1.6.0/2.6.16-i386-cb/cipe.h:276:1: warning:
"CURRENT_TIME_SEC" redefined
In file included from include/linux/skbuff.h:20,
from include/linux/if_ether.h:110,
from include/linux/netdevice.h:29,
from /usr/src/cipe-1.6.0/2.6.16-i386-cb/cipe.h:152,
from /usr/src/cipe-1.6.0/2.6.16-i386-cb/module.c:15:
include/linux/time.h:94:1: warning: this is the location of the
previous definition
CC [M] /usr/src/cipe-1.6.0/2.6.16-i386-cb/device.o
In file included from /usr/src/cipe-1.6.0/2.6.16-i386-cb/device.c:15:
/usr/src/cipe-1.6.0/2.6.16-i386-cb/cipe.h:276:1: warning:
"CURRENT_TIME_SEC" redefined
In file included from include/linux/skbuff.h:20,
from include/linux/if_ether.h:110,
from include/linux/netdevice.h:29,
from /usr/src/cipe-1.6.0/2.6.16-i386-cb/cipe.h:152,
from /usr/src/cipe-1.6.0/2.6.16-i386-cb/device.c:15:
include/linux/time.h:94:1: warning: this is the location of the
previous definition
CC [M] /usr/src/cipe-1.6.0/2.6.16-i386-cb/sock.o
In file included from /usr/src/cipe-1.6.0/2.6.16-i386-cb/sock.c:15:
/usr/src/cipe-1.6.0/2.6.16-i386-cb/cipe.h:276:1: warning:
"CURRENT_TIME_SEC" redefined
In file included from include/linux/skbuff.h:20,
from include/linux/if_ether.h:110,
from include/linux/netdevice.h:29,
from /usr/src/cipe-1.6.0/2.6.16-i386-cb/cipe.h:152,
from /usr/src/cipe-1.6.0/2.6.16-i386-cb/sock.c:15:
include/linux/time.h:94:1: warning: this is the location of the
previous definition
CC [M] /usr/src/cipe-1.6.0/2.6.16-i386-cb/output.o
In file included from /usr/src/cipe-1.6.0/2.6.16-i386-cb/output.c:15:
/usr/src/cipe-1.6.0/2.6.16-i386-cb/cipe.h:276:1: warning:
"CURRENT_TIME_SEC" redefined
In file included from include/linux/skbuff.h:20,
from include/linux/if_ether.h:110,
from include/linux/netdevice.h:29,
from /usr/src/cipe-1.6.0/2.6.16-i386-cb/cipe.h:152,
from /usr/src/cipe-1.6.0/2.6.16-i386-cb/output.c:15:
include/linux/time.h:94:1: warning: this is the location of the
previous definition
/usr/src/cipe-1.6.0/2.6.16-i386-cb/output.c: In function `cipe_xmit':
/usr/src/cipe-1.6.0/2.6.16-i386-cb/output.c:176: error: structure has
no member named `inet'
/usr/src/cipe-1.6.0/2.6.16-i386-cb/output.c:198: error: structure has
no member named `inet'
gmake[3]: *** [/usr/src/cipe-1.6.0/2.6.16-i386-cb/output.o] Error 1
gmake[2]: *** [_module_/usr/src/cipe-1.6.0/2.6.16-i386-cb] Error 2
gmake[2]: Leaving directory `/usr/src/linux-2.6.16'
gmake[1]: *** [all25] Error 2
gmake[1]: Leaving directory `/usr/src/cipe-1.6.0/2.6.16-i386-cb'
make: *** [all] Error 2

--
aRDy Music and Rick Dicaire present:
http://www.ardynet.com
http://www.ardynet.com:9000/ardymusic.ogg.m3u

--
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>

Re: Compile error on kernel 2.6.16

2006-05-28T03:53:01Z

For recent kernels you need to apply a few patches to build cipe-1.6.0.
Different ones are required from kernel 2.6.11 and upwards. The latest
one is needed from kernel version 2.6.14 and upwards. I've tried it with
success on 2.6.15 and 2.6.16 (but, see below). You can download it from
the sourceforge project site:

http://sourceforge.net/tracker/?group_id=66201&atid=513682
<http://sourceforge.net/tracker/?group_id=66201&atid=513682>

For kernel 2.6.16 you need an additional patch that I emailed to the
list a few days ago. It's only a trivial addition of a missing include file.

Add the following line to cipe/output.c

#include <net/ip.h>
+#include <net/route.h>
#include <net/icmp.h>

/Erik

R Dicaire wrote:

> Hi folks, I used to use cipe a few years ago and was pleased with it
> immensely. I'm trying to implement it again, under linux kernel 2.6.16
> and get the following:

[...]

> In file included from /usr/src/cipe-1.6.0/2.6.16-i386-cb/cipe.h:161,
> from /usr/src/cipe-1.6.0/2.6.16-i386-cb/module.c:15:
> /usr/src/cipe-1.6.0/2.6.16-i386-cb/cryptoapi.h:94: error: redefinition
> of `crypto_tfm_ctx'
> include/linux/crypto.h:303: error: `crypto_tfm_ctx' previously defined
> here
> In file included from /usr/src/cipe-1.6.0/2.6.16-i386-cb/module.c:15:
> /usr/src/cipe-1.6.0/2.6.16-i386-cb/cipe.h:274:1: warning:
> "CURRENT_TIME_SEC" redefined
> In file included from include/linux/skbuff.h:20,
> from include/linux/if_ether.h:110,
> from include/linux/netdevice.h:29,
> from /usr/src/cipe-1.6.0/2.6.16-i386-cb/cipe.h:152,
> from /usr/src/cipe-1.6.0/2.6.16-i386-cb/module.c:15:
> include/linux/time.h:94:1: warning: this is the location of the
> previous definition
> gmake[3]: *** [/usr/src/cipe-1.6.0/2.6.16-i386-cb/module.o] Error 1
> gmake[2]: *** [_module_/usr/src/cipe-1.6.0/2.6.16-i386-cb] Error 2
>
> I've searched the mailing list archives and found nothing specific to
> this issue, is there a patch or other fix?
>

Compile error on kernel 2.6.16

2006-05-27T11:38:39Z

Hi folks, I used to use cipe a few years ago and was pleased with it
immensely. I'm trying to implement it again, under linux kernel 2.6.16
and get the following:

./configure --prefix=/usr --sysconfdir=/etc/cipe
creating 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... no
checking for makeinfo... makeinfo
checking for gmake... gmake
checking for kernel source tree... /usr/src/linux-2.6.16
checking for kernel version... 2.6.16
checking for architecture... i386
checking for SMP... no
checking for crypto API headers... yes
checking for kernel CRC function... yes
checking for assembler parts... bf-i386.o
checking for mlock... yes
checking for mlockall... yes
checking for OpenSSL... includes /usr/include, libs /usr/lib
checking for openssl... /usr/bin/openssl
checking OpenSSL version... 0.9.7e
updating cache ./config.cache
creating ./config.status
creating Makefile
creating 2.6.16-i386-cb/Makefile
creating lib/Makefile
creating pkcipe/Makefile
creating pkcipe/rsa-keygen
creating 2.6.16-i386-cb/config.h
creating pkcipe/config.h

I then start the make, and get the following:

gcc -o ciped-cb ciped.o options.o ioctl.o ucrc32.o -L../lib -lcipe
gmake -C /usr/src/linux-2.6.16
SUBDIRS=/usr/src/cipe-1.6.0/2.6.16-i386-cb modules
gmake[2]: Entering directory `/usr/src/linux-2.6.16'
CC [M] /usr/src/cipe-1.6.0/2.6.16-i386-cb/module.o
In file included from /usr/src/cipe-1.6.0/2.6.16-i386-cb/cipe.h:161,
from /usr/src/cipe-1.6.0/2.6.16-i386-cb/module.c:15:
/usr/src/cipe-1.6.0/2.6.16-i386-cb/cryptoapi.h:94: error: redefinition
of `crypto_tfm_ctx'
include/linux/crypto.h:303: error: `crypto_tfm_ctx' previously defined
here
In file included from /usr/src/cipe-1.6.0/2.6.16-i386-cb/module.c:15:
/usr/src/cipe-1.6.0/2.6.16-i386-cb/cipe.h:274:1: warning:
"CURRENT_TIME_SEC" redefined
In file included from include/linux/skbuff.h:20,
from include/linux/if_ether.h:110,
from include/linux/netdevice.h:29,
from /usr/src/cipe-1.6.0/2.6.16-i386-cb/cipe.h:152,
from /usr/src/cipe-1.6.0/2.6.16-i386-cb/module.c:15:
include/linux/time.h:94:1: warning: this is the location of the
previous definition
gmake[3]: *** [/usr/src/cipe-1.6.0/2.6.16-i386-cb/module.o] Error 1
gmake[2]: *** [_module_/usr/src/cipe-1.6.0/2.6.16-i386-cb] Error 2

I've searched the mailing list archives and found nothing specific to
this issue, is there a patch or other fix?

--
aRDy Music and Rick Dicaire present:
http://www.ardynet.com
http://www.ardynet.com:9000/ardymusic.ogg.m3u

--
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>