At 16:44 15.07.2004 +0300, [EMAIL PROTECTED] wrote:
I 've noticed that when installing the default shorewall configuration of=
Bering-*
there is no block of rfc1918 packets going out to NET
That is traceroute from LOC of any address not included in LOCAL LAN but in=
the RFC1918
HI AGAIN,
I am new to LEAF and have just got my Leaf system running.
However, I have been reading about dropbear, dropbearkeys, and SSH and it seems if
these have to do with some sort of remote admin packages. Am I right? Is there some
good beginer information you could point me to to read
Hi!
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, July 16, 2004 7:06 AM
To: [EMAIL PROTECTED]
Subject: Re: [leaf-user] RFC1918 packets to NET
At 16:44 15.07.2004 +0300, [EMAIL PROTECTED] wrote:
I 've noticed that when installing the
Hi!
I 've noticed that when installing the default shorewall
configuration of=
Bering-*
there is no block of rfc1918 packets going out to NET
That is traceroute from LOC of any address not included in
LOCAL LAN but in=
the RFC1918 range will go out and traverse the
Ben,
I want to use LEAF as a simple router inside my internal
networks. I don't need any firewalling or NAT.
if you have Bering-uClibc 2.1:
- delete all references to shorewall in syslinux.cfg
if you have Bering-uClibc 2.2:
- delete all references to shorewall in leaf.cfg
In both cases
Erich Titl wrote:
Charles
interesting approach do you do any mac based filtering?
Not at the moment...filtering is strictly based on IP (and on the
interface a system is connected to).
--
Charles Steinkuehler
[EMAIL PROTECTED]
---
This SF.Net
The first thing that came to mind to do this was to change the following in
the shorewall policy file:
all all REJECT ULOG
to
all all ACCEPT
However this doesn't meet the requirement of getting rid of shorewall.
Also, I don't know what
Erich Titl wrote:
Charles
At 06:57 16.07.2004 -0500, Charles Steinkuehler wrote:
Erich Titl wrote:
Charles
interesting approach do you do any mac based filtering?
Not at the moment...filtering is strictly based on IP (and on the interface a system is connected to).
Thanks, one more question
Hello everyone,
I am cross compiling a arm program using
arm-linux-gcc.
Now i want to use a debugger to trace my program using
arm-linux-gdb
from being in a x86 machine.
That is - cross debug arm-linux program from
linux-i386 machine.
i would also like to know where would the simulator be
??
Tom
At 06:36 16.07.2004 -0700, you wrote:
Erich Titl wrote:
Charles
At 06:57 16.07.2004 -0500, Charles Steinkuehler wrote:
Erich Titl wrote:
Charles
interesting approach do you do any mac based filtering?
Not at the moment...filtering is strictly based on IP (and on the interface a
system is
Just what does this gave to do with LEAF?
I think this is very off topic and as such is SPAM!!!
As a guru you should have known this!
On Fri, 16 Jul 2004, karthik bala guru wrote:
Date: Fri, 16 Jul 2004 06:52:03 -0700 (PDT)
From: karthik bala guru [EMAIL PROTECTED]
To: Robert K Coffman Jr - Info
Thanks all,
I removed shorewall from the syslinux.cfg and set ip_forward=yes. I
setup a temporary route on my firewall to point to the network behind
the LEAF router and it's working!
Ben
On Fri, 16 Jul 2004 12:17:42 +0200, Frank Dauer [EMAIL PROTECTED] wrote:
Ben,
I want to use LEAF as
HI,
I am new to leaf and am running bering_uclibc 2.1.3. Ihave only just recently got my
firewall up and runnng, protecting my local network using the default shorewall
settings. However,in Weblet, I have a red light for Firewall under LEAF status and it
says error. When I click on the red
Hello list:
In booting up Bering 1.2, one of the messages in auth.log is:
Jul 16 13:07:15 firewall pluto[25864]: including NAT-Traversal patch
(Version0.5a) [disabled]
How does one enable NAT traversal -- and is it right for what I want to
do (pretty sure it is but thought I would ask the
Hi all,
I'm having trouble getting a Mailman server (using Exim 3.35) to resolve
names properly. It is situated in the DMZ (192.168.2.x) of a network using
Dachstein CD102. I have an Exchange mail server in the internal network
(192.168.1.x).
I have tinyDNS running on the firewall. The internal
Doug Sampson wrote:
Hi all,
I'm having trouble getting a Mailman server (using Exim 3.35) to resolve
names properly. It is situated in the DMZ (192.168.2.x) of a network using
Dachstein CD102. I have an Exchange mail server in the internal network
(192.168.1.x).
I have tinyDNS running on the
Folks,
Back to the issue of getting daemontl.lrp to load. There was a previous
thread on the list titled:
[leaf-user] Bering 1.2 CD won't load daemontl.lrp
There, I was using a syslinux.cfg line and leaf.cfg as follows:
default linux initrd=initrd.lrp init=/linuxrc rw root=/dev/ram0
Tibbs, Richard wrote:
Folks,
Back to the issue of getting daemontl.lrp to load. There was a previous
thread on the list titled:
[leaf-user] Bering 1.2 CD won't load daemontl.lrp
There, I was using a syslinux.cfg line and leaf.cfg as follows:
default linux initrd=initrd.lrp init=/linuxrc rw
Erich Titl wrote:
At 17:11 16.07.2004, Charles Steinkuehler wrote:
Erich Titl wrote:
Charles
At 06:57 16.07.2004 -0500, Charles Steinkuehler wrote:
Erich Titl wrote:
Charles
interesting approach do you do any mac based filtering?
Not at the moment...filtering is strictly based on IP (and on the
Charles
At 23:10 16.07.2004, Charles Steinkuehler wrote:
Erich Titl wrote:
...
The way I understand proxy arp is that the interface which is the proxy
replies to arp requests for the corresponding IP.
So I have to enter all addresses of all the other interfaces to each of
the interfaces for them
--
steve [EMAIL PROTECTED]
---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click
I have followed the directions listed below and have gotten
the 2.1 version to boot fine off my CF (16mb)
http://leaf.sourceforge.net/doc/guide/buc-install.html
http://leaf.sourceforge.net/doc/guide/bucu-ide.html
but wheb I try to boot up with the 2.2 version I get a kernal panic.
The last of
I could not get timydns to answer for two internal networks. My
solution is:
.private.network::localhost
.1.168.192.in-addr.arpa::localhost
=tworoute.private.network:192.168.1.254
=localhost.private.network:192.168.1.1
.dmz.network::localhost
.2.168.192.in-addr.arpa::localhost
Today we received an update of dropbear to v 0.43 fixing potential security
problems.
The new lrp is in cvs:
http://cvs.sourceforge.net/viewcvs.py/leaf/bin/packages/uclibc-0.9/20/?sortby=date#dirlist
To update your dropbear version:
1) scp the new dropbear.lrp to your boot media's root.
2) on
Hi Andrew, If you can send me your log file I can have a look to see what
is being reported. Some of these may be harmless DNS or traceroute queries
that can be dropped from logging.
Darcy Parker ([EMAIL PROTECTED])
Message: 4
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Fri, 16 Jul 2004
Do you use the initrd_ide_cd.lrp from
http://cvs.sourceforge.net/viewcvs.py/leaf/bin/bering-uclibc/beta/
kp
Am Samstag, 17. Juli 2004 00:55 schrieb steve:
I have followed the directions listed below and have gotten
the 2.1 version to boot fine off my CF (16mb)
Am Freitag, 16. Juli 2004 08:53 schrieb [EMAIL PROTECTED]:
HI AGAIN,
I am new to LEAF and have just got my Leaf system running.
However, I have been reading about dropbear, dropbearkeys, and SSH and it
seems if these have to do with some sort of remote admin packages. Am I
right?
It's
How does Shorewall handle AOL Instant messenger? I have noticed that when
my two daughters are both using AIM there is a lot of activity in the
firewall log (it turns to red very quickly).
I found the following in an AIM FAQ:
What can I do if I'm having trouble using Instant Messenger at work?
28 matches
Mail list logo
