Hi,
I sent a question about compiling Super-Freeswan user mode
application for Bering into Freeswan mailing list. Then I found
this LEAF mailing list and I think that this is better place
for the question.
So, below is the question (slightly modified) I posted to Freeswan
mailing list a few days ago.
-mike
Hello,
Few days ago I asked about problems compiling Super-Freeswan-kb2 for
Bering V1.0 floppy firewall Linux kernel.
The problem was that kernel does compile and kernel IPSEC modules seem
to work, but user mode applications pluto and whack
throws segmentation fault error message.
Thanks for Ken Bantoft for leading me to use ldd command to check the
required libraries in pluto and whack binaries.
ldd pluto
Well, this seemed to be just fine in my system because there were
libgmp.so.3, libresolv.so.2, libc.so.6 and ld-linux.so.2.
Then Arne pointed out clearly that my desktop RedHat with libc.2.2.2
and Bering with libc.2.0.7 is most likely the problem. He gave a
good tip about using UML virtual Linux within host linux to use
older libc environment to compile user mode pluto, whack
etc IPSEC apps. Thanks for the tip Arne.
I downloaded UML woody and slink environments from a website
pointed in Bering web page
(http://leaf.sourceforge.net/devel/jnilo/uml.html)
I compiled a new Linux 2.4.19 kernel with Super-Freeswan IPSEC
statically linked into the kernel within woody environment.
This worked just fine. IPSEC enabled kernel booted up just fine.
Well, I had managed to do this already with desktop RedHat so I
didn't even expect any problems.
But then I struct into the same segmentation fault with pluto and
whack. IPSEC app binaries compiled in woody virtual linux seem to
use libc-2.2.x environment too. At least those are the only libc
I could see in the system.
Then I booted up SLink virtual linux environment and I was delighted
to see that it uses libc-2.0.7 which is in Bering too.
I installed Linux 2.4.19 kernel sources, Super-Freeswan sources and
Openssl sources in Slink environment.
But, I could not compile Super-Freeswan in this environment.
Compiler throws compilation errors like
unexpected identifier in freeswan.h
undefined __u8
undefined __u16
etc
SLink env does have gcc 2.7.x version. People in Freeswan list
suggested that this might be too old compiler for Super-Freeswan.
Probably true, because GCC 2.7.x is veeery old compiler and
it is distributed with old header files and libs.
I'm curious to know about IPSEC509.LRP package found on Bering
web site and about this SLink UML enviromment.
Does anyone use this SLink UML env to compile IPSEC[509].LRP for
Bering kernel or do you use Woody UML env to compile pluto/whack
etc binaries?
If you use SLink env to compile IPSEC.LRP package for Bering
then do you use GCC 2.7.x compiler and standard header files
found in stock SLink UML environment?
Does anyone know where and how applicaations in IPSEC[509].LRP
package were compiled (GCC version and LIBC version and OS env)?
I'm running out of options to find a way to compile Super-Freeswan
for Bering disk image (pluto, whack etc user mode programs. No problems
to compiler kernel which doesn't use libc at all).
Super-Freeswan works fine in my RedHat, but I cant use it as a
firewall OS.
The ultimate solution would be if there is customized SLink UML
disk image somewhere in Internet with ready-to-use GCC compiler and
libs for Bering LIBC-2.0.7 environment.
Thanks in advance,
- mike
--
__
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
One click access to the Top Search Engines
http://www.exactsearchbar.com/mailcom
---
This SF.net email is sponsored by: Microsoft Visual Studio.NET
comprehensive development tool, built to increase your
productivity. Try a free online hosted session at:
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
