kernel + moduły ipsec (freeswan)
Witam
Mam klopot z uruchomieniem ipseca :(
Gdy uzywam sourcow kernela 2.4.22 z debiana to:
asgard:~# ipsec setup --start
ipsec_setup: Starting FreeS/WAN IPsec 2.03...
ipsec_setup: /sbin/insmod -q
/lib/modules/2.4.22-17mar2004v6/kernel/net/ipv4/ah4
.o
ipsec_setup: Using /lib/modules/2.4.22-17mar2004v6/kernel/net/ipv4/ah4.o
ipsec_setup: Symbol version prefix 'smp_'
ipsec_setup: /lib/modules/2.4.22-17mar2004v6/kernel/net/ipv4/ah4.o:
init_module:
Resource temporarily unavailable
ipsec_setup: /lib/modules/2.4.22-17mar2004v6/kernel/net/ipv4/ah4.o:
insmod ah4 f
ailed
ipsec_setup: Hint: insmod errors can be caused by incorrect module
parameters, i
ncluding invalid IO or IRQ parameters
ipsec_setup: /sbin/insmod -q
/lib/modules/2.4.22-17mar2004v6/kernel/net/ipv4/esp
4.o
ipsec_setup: Using /lib/modules/2.4.22-17mar2004v6/kernel/net/ipv4/esp4.o
ipsec_setup: Symbol version prefix 'smp_'
ipsec_setup: /lib/modules/2.4.22-17mar2004v6/kernel/net/ipv4/esp4.o:
init_module
: Resource temporarily unavailable
ipsec_setup: /lib/modules/2.4.22-17mar2004v6/kernel/net/ipv4/esp4.o:
insmod esp4
failed
ipsec_setup: Hint: insmod errors can be caused by incorrect module
parameters, i
ncluding invalid IO or IRQ parameters
ipsec_setup: /sbin/insmod -q
/lib/modules/2.4.22-17mar2004v6/kernel/net/ipv4/ipc
omp.o
ipsec_setup: Using /lib/modules/2.4.22-17mar2004v6/kernel/net/ipv4/ipcomp.o
ipsec_setup: Symbol version prefix 'smp_'
ipsec_setup: /sbin/insmod -q
/lib/modules/2.4.22-17mar2004v6/kernel/net/xfrm/xfr
m_user.o
ipsec_setup: Using
/lib/modules/2.4.22-17mar2004v6/kernel/net/xfrm/xfrm_user.o
ipsec_setup: Symbol version prefix 'smp_'
ipsec_setup: WARNING: setkey not found.
asgard:~#
natomiast gdy uzywam sourcow z kernel.org (ta sama wersja) to dostaje
takie bledy przy buildowaniu z freeswanem:
+ '[' -x /root/bin/installkernel ']'
+ '[' -x /sbin/installkernel ']'
+ exec /sbin/installkernel 2.4.22-17mar2004v5 bzImage
/usr/src/linux-2.4.22/System.map ''
In order to use the new kernel image you have just installed, you
will need to reboot the machine. First, however, you will need to
either make a bootable floppy diskette, re-run LILO, or have GRUB
installed.
Checking for LILO...Yes, on /dev/sda
Should I run /sbin/lilo? (y/n) y
Warning: LBA32 addressing assumed
Added 2.4.22-install
Added mobiltek *
make[2]: Leaving directory `/usr/src/linux-2.4.22/arch/i386/boot'
make[1]: Leaving directory `/usr/src/linux-2.4.22'
packaging/utils/errcheck out.kinstall
***ERRORS DETECTED in out.kinstall (examine file for details):
depmod: *** Unresolved symbols in
/lib/modules/2.4.22-17mar2004v5/kernel/drivers/net/wan/comx.o
make[1]: *** [_modinst_post] Error 1
make: *** [kinstall] Error 1
+ '[' -x /root/bin/installkernel ']'
+ '[' -x /sbin/installkernel ']'
+ exec /sbin/installkernel 2.4.22-17mar2004v5 bzImage
/usr/src/linux-2.4.22/System.map ''
In order to use the new kernel image you have just installed, you
will need to reboot the machine. First, however, you will need to
either make a bootable floppy diskette, re-run LILO, or have GRUB
installed.
Checking for LILO...Yes, on /dev/sda
Should I run /sbin/lilo? (y/n) y
Warning: LBA32 addressing assumed
Added 2.4.22-install
Added mobiltek *
make[2]: Leaving directory `/usr/src/linux-2.4.22/arch/i386/boot'
make[1]: Leaving directory `/usr/src/linux-2.4.22'
packaging/utils/errcheck out.kinstall
***ERRORS DETECTED in out.kinstall (examine file for details):
depmod: *** Unresolved symbols in
/lib/modules/2.4.22-17mar2004v5/kernel/drivers/net/wan/comx.o
make[1]: *** [_modinst_post] Error 1
make: *** [kinstall] Error 1
i inne zabawne sytuacje sie pojawiaja
Natomiast gdy uzywam lat freeswana z debiana albo mi sie nie chce
kompilowac kernel rowniez (jeszcze inny blad) albo udalo mi sie raz
doprowadzic do sytuacji pozornego dzialania, ktora i tak wydaje sie ze w
koncu nie dziala i co chwile sieje do logow jakimis bledami albo od
freeswana albo od kernela (moduly)
Czy ktos mial podobne klopoty z ipsec i moglby ewentualnie naprowadzic
gdzie szukac bledu? Bo ja juz mam dosc po calodniowym googlowaniu :(
--
Pozdrawiam, Dominik Juszczyk
Reply to: