Aanhalen Harold Miller [EMAIL PROTECTED]:
Comments inline.
I'm new to the whole LEAF / LRP arena, but an old programmer. Started
my
first ISP with a single Linux/486DX4-100 box a while ago, sold it, and
now
have a dozen machines running at my home/office. I have a few questions.
I
read
On Tue, 9 Jul 2002, Jim Van Eeckhoutte wrote:
Dnscache.lrp doesn't seem to work. Ive installed as per instructions on
site. Daemontls.lrp is installed too. I noticed there is no log files in
/var/log/dnscache dir. How can I troubleshoot this thing? thnx
This is an insufficiently specific
Craig
At 01:10 10.07.2002, you wrote:
Hi folks,
For those who have replied, I'm running the vanilla, Dachstein CD. The
only thing I have changed from the default configuration is to uncomment
the correct NIC drivers, and changed the root password. That's it. I've
left everything else alone...if
This is it, thanks to all who answered!
Wonderful work guys and girls. Lynn's howto with Chad's windows setup info
makes a great combo.
IPSEC Its working!!
Thanks heaps,
Matt
I think the doc you are talking about is this ipsec howto, courtesy of
Lynn Avants, which describes four different
Jeff Newmiller wrote:
On Tue, 9 Jul 2002, Charles Steinkuehler wrote:
[ snip ]
After savelog rotates the logfile, $DAEMON is writing to logfile.0,
instead of logfile. Obviously, this is not acceptable ;
I assume that this has something to do with the original redirected
On Tue, 9 Jul 2002 21:15:23 -0700
Brock Nanson [EMAIL PROTECTED] wrote:
The Lucent is NOT a PRISM2 card. The orinoco_cs driver will work with
many PRISM2 cards, but I think what this suggests is that the
/etc/pcmcia/config file is being checked and the wrong card is found. I
don't know if
Mark,
you can add bridge_maxwait xxx to the interfaaces file
at the bridge config.
Maybe this can help.
Manfred
Mark A Nordstrand schrieb:
Manfred,
Have the eth entries commented out and the bridge
entry uncommented in /etc/network/interfaces. My
poking around in if-pre-up.d/bridge has
Manfred,
Added a maxwait of 600 and a -x to the sh to see
what's going on. The for loop on `brctl showstp...`
isn't being entered, so $BREADY is still true and
this kicks it out of the while loop.
Manfred Schuler wrote:
Mark,
you can add bridge_maxwait xxx to the interfaaces file
at the
Many thanks to those of you who gave valuable answers, especially Ray, Kim
and Phillip.
I'm currently running Dachstein, because I don't think the default Bering
dist will run on my 486CPU (2.4 kernel?) Someone correct me if I'm wrong.
So that leaves me using Seattle Firewall as my firewall
On Wed, 10 Jul 2002, Harold Miller wrote:
I'm currently running Dachstein, because I don't think the default Bering
dist will run on my 486CPU (2.4 kernel?) Someone correct me if I'm wrong.
I use 486's with Bering.
---
Bering rc2
This is the general procedure I use to bring up networking... I
understand there is a way to bring up an interface to listen to an
entire subnet, not just an address. Can someone help me with the ip
syntax?
Thanks,
// George
down () {
d=`ip -o link show | cut -d: -f2`
for i in $d
This bridge.lrp package should replace the one provided with any version of
Bering prior to and including rc3.
It fixes the following errors:
1) /var/lib/lrpkg/bridge.conf now points to the proper bridge scripts
2) The /etc/network/if-pre-up.d/bridge script is fixed
3)
Tom recently updated its shorewall package to version 1.3.3. See:
http://www.shorewall.net
The corresponding version for Bering is now available in the Bering update
directory.
It has been built following the procedure described here:
http://leaf.sourceforge.net/devel/jnilo/bishorwall.html
It
Bering will run on 486.
Bering has netfilter and iptables. Worth
moving up to after you get your bearings. duck
---
This sf.net email is sponsored by:ThinkGeek
Two, two, TWO treats in one.
http://thinkgeek.com/sf
Grabbed the new lrp posted recently hoping it was
in response to problems I have been seeing with
bridge, pcmcia, and wireless.
if-up.d/bridge still falls through the for loop
at the bottom. It does work fine if I log in
afterwards and stop and restart the network.
--
Mark
Linux, it is now
OK, I threw away a days worth of work, and switched to Bering. little sigh
It looks like it's operational. cheer
I still have a ways to go.
It seems that it takes a LONG time to back up all to a floppy (hour+??) Any
suggestions?
I got nothing out of the masqueraded systems untill I typed
On Wed, 10 Jul 2002, George Georgalis wrote:
Bering rc2
This is the general procedure I use to bring up networking... I
understand there is a way to bring up an interface to listen to an
entire subnet, not just an address.
Are you thinking of proxy-arp?
Hello,
I've been trying to get some Linmodem drivers to work correctly with Bering
1.0-rc3. The drivers work on my p350 with RedHat installed with both the
2.4.0 2.4.9-13 kernels. After compiling I end up with 2 files - pctel.o
ptserial.o. I've put both of these in /lib/modules made
On Wed, Jul 10, 2002 at 07:30:39PM -0700, Tom Eastep wrote:
--On Wednesday, July 10, 2002 21:13:53 -0500 guitarlynn
[EMAIL PROTECTED] wrote:
On Wednesday 10 July 2002 20:52, George Georgalis wrote:
Interesting, but not what I had in mind. I'm using nat for a dmz and
rather than bring up an
Thanks Jim!
-- Forwarded Message --
Subject: Re: [leaf-user] bridge update? still not working.
Date: Wed, 10 Jul 2002 23:35:56 -0500
From: Jim TerWee [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
I have used Bering alot as a bridge with pcmcia and ethernet. What I
had to do
20 matches
Mail list logo
