Dear List,
I am wondering if there is any newer version such as Freeswan 2.06 in a
.lrp that is available. I am running Bering 1.2 (kernel 2.4.20). The
current version of freeswan is 1.99.6.2.
TIA,
Rick.
---
This SF.Net email is
Dear List,
I am wondering if there is any newer version such as Freeswan
2.06 in a
.lrp that is available. I am running Bering 1.2 (kernel 2.4.20). The
current version of freeswan is 1.99.6.2.
FreeSWAN is now OpenSWAN. There are no updates for Bering. For
Bering-uclibc though, you can
Hmm.
I have not had luck with Bering uclibc -- some of my nics are natsemi,
and I could not get a working natsemi.o.
The freeswan site says that up through v2.03 will work on 2.4.17+
kernels. There is also a super-freeswan 1.99.8 -- with the x509 and
NAT-t patches.
I thought I would give that a
On the feature issue: We have had a problem with messages in the log
files saying no route available.
I have a successful road warrior from just outside the firewall, but
across campus, (beyond the next router) things stop working with the
above message.
I was hoping an upgrade to 1.99.8 or
Tibbs, Richard wrote:
On the feature issue: We have had a problem with messages in the log
files saying no route available.
I have a successful road warrior from just outside the firewall, but
across campus, (beyond the next router) things stop working with the
above message.
I was hoping an
Here is the ipsec.conf file. If you want a barf, let me know.
TIA Rick.
# /etc/ipsec.conf - FreeS/WAN IPsec configuration file
# More elaborate and more varied sample configurations can be found
# in FreeS/WAN's doc/examples file, and in the HTML documentation.
# basic
Tibbs, Richard wrote:
Here is the ipsec.conf file. If you want a barf, let me know.
TIA Rick.
As mentioned, you need a nexthop value...in your case, a rightnexthop
setting. This should be set to the default gateway of the leaf box.
Alternatively, you can set right=%defaultroute and the
Hello,
I had a problem with Leaf yesterday that surprised me a little bit. Last
night I rebooted it via Putty and well it never came back up. This morning I
showed up to find a kernel panic. This was a working system not something
new. It has been flawless for about 6 months now. It goes to load
Bad floppy drive/disks can give said effects. My drive/disk is currently
in that transient-problem state itself (I'm fairly certain it's the
drive, not the disk).
scott; canada
ALParada wrote:
Hello,
I had a problem with Leaf yesterday that surprised me a little bit. Last
I did backup root but never considered the memory issue. I'm using a 128 MB
stick and allocating 10 MB to the system with 3 MB for the logs. I can't say
I looked at the space thinking there must be plenty.
- Original Message -
From: Victor McAllister [EMAIL PROTECTED]
To: ALParada
Apparently, I didn't realize that when I responded to this earlier, it went
to ALParada personally and not to the list. (Sorry, I'm new on this
particular list.) I'm resending this to the list so that everyone can
benefit from the discusion:
-Original Message-
From: ALParada
Rick
At 21:14 10.11.2004 -0500, you wrote:
No, didn't set CLAMPMSS. The chief symptom so far has been a bad route.
I think it was an error like
Ioctlsroute or some such code.
What is the MSS that you would recommend for Ipsec? The SA is getting
established OK so far (so UDP is not the
Al
At 00:10 11.11.2004 -0500, ALParada wrote:
I did backup root but never considered the memory issue. I'm using a 128 MB
stick and allocating 10 MB to the system with 3 MB for the logs. I can't say
I looked at the space thinking there must be plenty.
I found one of the most frequent glitches I
13 matches
Mail list logo
