From: [EMAIL PROTECTED]
To: Leaf User [EMAIL PROTECTED]
Subject: RE: [leaf-user] Bering rc3 - cant load ramdisk
Date: Fri, 12 Jul 2002 09:30:34 +0100
How much ram is in the machine?
Antony Briggs
...Pentium 100 with 48mB RAM
When I try to boot the bering rc3, it stops at a prompt with ...
On Fri, 2002-07-12 at 16:43, Chad Carr wrote:
On 12 Jul 2002 12:48:01 +0200
Ronny Aasen [EMAIL PROTECTED] wrote:
Hello
i have a a testing setup with ipsec between 3 linux bering firewalls and
a zywall 10 router, all on static ip address i also have roadwarrior
support from dhcp
- Original Message -
From: Brock Nanson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Date: Fri, 12 Jul 2002 06:55:52 -0700
Subject: Re: [leaf-user] eth1:Tx timeout! Resetting card
- Original Message -
From: Taewoon.Goo [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
That's the info I needed - THANKS!
- Original Message -
From: Kim Oppalfens [EMAIL PROTECTED]
To: Larry Platzek [EMAIL PROTECTED]; Christopher Barry
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Sunday, July 14, 2002 4:47 PM
Subject: Re: [leaf-user] expanding /dev/root on diskless LEAF
From your post:
--
+ iptables -L -v -n
Chain INPUT (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
0 0 ACCEPT ah -- lo * 0.0.0.0/0
0.0.0.0/0
952
I use e-smith for this - it is a stripped down linux server distribution.
http://www.e-smith.org
Of course it would require a second computer. But it is very easy
to install and manage.
Doug
I have already asked about the availability of a halfway recent samba
package about a month ago.
Just a thought... a couple of months ago, my ISP moved their DHCP server to an RFC1918
private address. My firewall was therefore blocking the necessary port 67 and 68
packets for renewals. On the initial boot, it would work fine because the DHCP lease
was obtained before the firewall rules
Le Lundi 15 Juillet 2002 18:03, Will Stacey a écrit :
Hi Jacques,
I've been using a bering router for some time, and before that LRP. I
appreciate the work you have put into the router project and the fine
documentation.
I am trying to set up the bering router to be accessable from serial
Tony:
Heya. Yes, the 10.x.y.z private IP address range is blocked
by the default firewall script that comes with Dachstein. You may
want to try echowall.lrp which I built for Dachstein which doesn't
do this. I had the same trouble with the standard Dachstein ruleset,
and before long I had
Why don't u just do this at HardWare level, with the SETUP program
provided by the Manufacturer..
That's what I did with all my cards, and don't have to worry my head
with the driver options..
Do hope this advise helps
-Original Message-
From: Rob Fegley [mailto:[EMAIL PROTECTED]]
Just a thought... a couple of months ago, my ISP moved their DHCP server to
an RFC1918 private
address. My firewall was therefore blocking the necessary port 67 and 68
packets for renewals. On the initial boot, it would work fine because the
DHCP lease was obtained before the firewall
rules
On Mon, Jul 15, 2002 at 07:15:24PM +, Scott C. Best wrote:
Tony:
Heya. Yes, the 10.x.y.z private IP address range is blocked
by the default firewall script that comes with Dachstein. You may
want to try echowall.lrp which I built for Dachstein which doesn't
do this. I had the same
The Alcatel Speedtouch PCI ADSL card is based on an ITEX Apollo chipset.
Alcatel does not provide a linux driver for it's PCI ADSL card
ITEX has closed down, as far as I understand.
Two drivers in binary form are available. They are here:
Same problem with Bering RC3 and IPSEC509 package,
when i try to start ipsec he gives me the error:
unable to determine address of eth0 (i have %defaultroute as interface in
ipsec.conf)
and i have many AH fields in the iptables -L output (AH is Authenticated
Headers, right ???, but i cant find
On Tue, 16 Jul 2002, Marco Cintolesi wrote:
Same problem with Bering RC3 and IPSEC509 package,
when i try to start ipsec he gives me the error:
unable to determine address of eth0 (i have %defaultroute as interface in
ipsec.conf)
and i have many AH fields in the iptables -L output (AH
On Tue, 16 Jul 2002, Marco Cintolesi wrote:
Heres the debug from the shorewall, let me know if i make something
wrong..
You haven't defined your ipsec tunnel in /etc/shorewall/tunnels -- that
will prevent klips from working. Nevertheless, nothing in the trace shows
why we're seeing
Jon Clausen wrote:
On Mon, Jul 15, 2002 at 07:15:24PM +, Scott C. Best wrote:
Tony:
Heya. Yes, the 10.x.y.z private IP address range is blocked
by the default firewall script that comes with Dachstein. You may
want to try echowall.lrp which I built for Dachstein which doesn't
On Mon, 15 Jul 2002, David Pitts wrote:
Thanks Jaques. Does that imply that the old version won't work? I
tried to use it and got a bunch of 'unresolvable symbol' errors?
Does that sound right?
Unresolved symbols commonly means either:
a) you forgot to insmod a required module BEFORE
Grasping for straws:
Do you have any bios shadowing enabled? Or any other memory options in
bios that can be mucked with?
On Mon, 15 Jul 2002, me name wrote:
From: [EMAIL PROTECTED]
To: Leaf User [EMAIL PROTECTED]
Subject: RE: [leaf-user] Bering rc3 - cant load ramdisk
Date: Fri, 12 Jul
ifup ppp0 and ifdown ppp0 are probably the better way to do this.
On Mon, 15 Jul 2002, Jay Langford wrote:
pon to turn the link on
poff turns it off
~jay
- Original Message -
From: Brain Miller SMITH [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, July 15, 2002 2:33 PM
On Mon, 15 Jul 2002, Harold Miller wrote:
Greetings LEAF Sages,
I'm running Bering RC3. I can check the DHCP lease renewal and expiration
time using pump -s. I see my box getting disconnected, and all stats
getting set to 0 at the expiration time.
Running svi networking restart buys me
Eyal:
Heya. The problem adding some ACCEPT rules to allow
one address to work, though, is that these rules must be
inserted into the ipchains input chain *before* the rule
which DENY's the whole range. Else the packet will be dropped
before it gets to the forward chain.
Me, I'm
On Mon, 15 Jul 2002, Jeff Newmiller wrote:
Look in /var/log/messages and/or /var/log/syslog for firewall messages of
complaining about port 67 or 68. You probably need to set up an accept
line for the replies in your shorewall rules file. Shorewall gets enabled
after the networking
Hmmm DHCP IS already specified in my external interfaces entry.
I DO have log complaints about RFC1819 dropping UDP Port 67 packets
(specifically from 10.213.0.1 )
So I think we have the problem identified. The last question, where is the
most appropriate place to add the firewall exception
24 matches
Mail list logo
