Hi Charles.
thank you for your answer.
snip
Just download the modules tarball for your kernel version from FRS,
extract, copy the modules you need to /lib/modules add
to /etc/modules - save modules.lrp and restart.
Perhaps I didn't made myself quite clear.
As already said, the 2.4.26 modules
Hi,
I recently upgraded an old Dachstein firewall to ucBering 2.1 (I prepared it
awhile ago, but only now had a change to put it in place). This
firewall(router) is the default gateway for all the stations in the network
(local). But it isn't the only router in the network, there are 2 or 3 more
Thank you Eric.
You're right, of course. Although I'm getting my packages from the beta
2 repository, I was using the 2.x package listing to check dependencies.
I didn't check for dependencies on mawk.lrp, only ipsec.lrp.
Is there a dependency tree somewhere in the iso image? I didn't see one.
Hi Eric,
I'm still getting the same errors. I added libm.lrp to the LRP variable
in leaf.cfg and installed it on the second floppy.
This is a Bering-uClibc 2.3 beta2 distro initrd.lrp and ipsec.lrp
are updates from the 2.3 beta2 repository. The remaining packages not
from the diskette image
Hello Cal,
I don't see an obvious error, can you check the output of 'lrpkg -l' to see if
the libm package is really loaded.
An other problem can be that the libm package you use is compiled with gcc-2.9x
while the other libraries from the beta are compiled with gcc-3.3.3. I will
upload a
Hello Franco,
The modules you are talking about are the ones from 'Donald Becker', they where
never part of the official kernel tree and compiled seperately. It looks like
they are not maintained anymore and give a lot of trouble with recent kernels.
But there are two different 8139 modules in
Eric,
This is really strange... I must have changed something else without
realizing it. Now I'm getting this, regardless of whether I'm using the
original or updated initrd.lrp:
ipsec_setup: Starting Openswan IPsec 1.0.9...
insmod:
Hello Cal,
You need the ipsec module from the kernel tarball, it can be found in download
area (where also the images are placed).
Eric
Eric,
This is really strange... I must have changed something else without
realizing it. Now I'm getting this, regardless of whether I'm using the
original
Eric,
That did it! The errors are gone. Now I've just got some configuration
warnings to deal with:
--
ipsec_setup: Starting Openswan IPsec 1.0.9...
ipsec_setup: WARNING: eth0 has route filtering turned on, KLIPS may not
work
ipsec_setup:
Cal,
Great!
You can get rid of this warning by setting 'spoofprotect' to 'no' (lrcfg -
Network config - network options)
Eric
Eric,
That did it! The errors are gone. Now I've just got some configuration
warnings to deal with:
--
ipsec_setup:
Please, somebody comment on changes required to upgrade an existing v1.x
openvpn installation to this new version?
I have read about the enhancements, c.; but, I am wondering whether or
not an existing configuration will simply work in v2.0 ???
What do you think?
* On 2005:04:28:16:47:31-0500
Hello,
I am a new comer to Bering.
I managed to install Bering-uclibc 2.2.3 and create a bootable hard drive.
I have two questions:
1. If I would like to add other packages at a later stage to the hard disk,
what is the best way through a lan?
2. During installation, the userguide (section
12 matches
Mail list logo
