Paul Hedderly wrote:
On Mon, Jan 27, 2003 at 12:44:06PM -0800, Patrick Morris wrote:In my experience, it's been unusable on anything big-endian.Nah many people use freeswan on sparc/alpha/PPC ...
I was unable to compile freeswan on Sun Ultra1 (sparc64) due use of two compilers. One for kernel (egcs64), other for userland. If a code is not written with this issue in mind (freeswan is not), then you will end with problems, when userland part of freeswan (compiled with gcc) will call code from kernel (which is compiled with egcs64).
So maybe it is working on sparc32, but in my experience not on sparc64.
<advertising> I'm using TINC now.... </advertising> ;-)
mARTin
-- PaulDaniel van Eeden wrote:Is it an sparc64 only problem or is ipsec also unusable on sparc32? Daniel van Eeden <daniel_e@dds.nl> Noah L. Meyerhans wrote:On Sun, Jan 26, 2003 at 11:06:51AM +0100, Ulrich Wurst wrote:Has anyone of you successfully managed to use ipsec on a sparc64 machine?I've still never managed to get it working. I've basically given up on freeswan on SPARC64. Hopefully the ipsec implementation that's going in to Linux 2.6 will give better results. I don't remember the details of the freeswan problem, but it has something to do with the way ioctls are implemented on sparc64. There's some kind of translation or something that goes on in kernel space. But that's only what I can recall from my vague memories of hearing it explained; I've never actually looked at the code, and don't know my way around the kernel source well enough to know where to look. noah-- To UNSUBSCRIBE, email to debian-sparc-request@lists.debian.orgwith a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
--
Martin Rusko
PhD student
Department of Automation and Measurement
Faculty of Mechanical Engineering
Slovak University of Technology
--
E-mail: rusko@sunsite.mine.nu
Web: http://sunsite.mine.nu/~rusko
--
motto: We are Microsoft! Resistance is futile. Open your
source code and prepare for assimilation.