similar to: Re: [leaf-user] Bering Multiple Internal Networks

I have been using the LEAF Bering firewall for a year or so. It boots with Syslinux 1.75. But Bering is too large for a 1440KB floppy, so it formats the diskette as 1680KB. Recently I found a small Compaq 2266 box to replace a larger Compaq 7170 to run the firewall. But when I try to boot the Bering diskette on the 2266 I get the following message: Loading Linux ............ Boot failed:

Finally, it''s out. All the details are here: http://leaf.sourceforge.net/article.php?sid=63 We will probably take a rest for a while :-) Enjoy! Jacques & Eric ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate:

At 00:14 17/06/2002, Jacques Nilo wrote: Great work, but is there an easy way to upgrade from rc2 to rc3. Will it kill the adjustments made to initrd.lrp to be able to run glib2.2 & boot of cdrom I made? Thanks >See: > >http://leaf.sourceforge.net/article.php?sid=43 > >Jacques & Eric > >_______________________________________________________________ >

Shorewall 1.3.14 is now available. Thanks go to Francesca Smith for helping with updating the sample configurations. New in 1.3.14: 1) An OLD_PING_HANDLING option has been added to shorewall.conf. When set to Yes, Shorewall ping handling is as it has always been (see http://www.shorewall.net/ping.html). When OLD_PING_HANDLING=No, icmp echo (ping) is handled via rules and

Beta 1 is now available at: http://www.shorewall.net/pub/shorewall/Beta ftp://ftp.shorewall.net/pub/shorewall/Beta Features include: 1) An OLD_PING_HANDLING option has been added to shorewall.conf. When set to Yes, Shorewall ping handling is as it has always been (see http://www.shorewall.net/ping.html). When OLD_PING_HANDLING=No, icmp echo (ping) is handled via rules and

When an interface name appears in the second column of an entry in /etc/shorewall/masq, Shorewall will detect all hosts and subnets routed through that interface and will masquerade traffic from those hosts and subnets. This is slightly more general than what I posted recently on the users list since it uses the routing table rather than the IP configuration of the interface. Example:

Does anyone know a PPPoE Server for Bering ? I don''t know anything about Bering (a quick search shows an Internet Firewall device and Floppy distro...) but anyways; I have had luck with RP-PPPoE (http://www.roaringpenguin.com/products/rp-pppoe/) which does include a PPPoE server. I have my pppd patched to support RADIUS so that it can talk to my FreeRadius rig in the testing lab.... IF

Updated with a 2.4.18 linux kernel & shorewall 1.2.9. Check: http://leaf.sourceforge.net/article.php?sid=31 Enjoy Jacques & Eric http://leaf.sourceforge.net/devel/jnilo

Hi, I''m trying let the windows clients behind my leaf ( bering rc4) talk through msn messenger. I found linux-igd.sourceforge.net that seems to be the missing piece... I used the ideas from www.wix.net.nz/LEAF/glibc.html to build a leaf cd using the redhat 7.3 glibc ( It''s alot easier to test applications because I can simply copy the binary ( and the .so) on the bering

Sometimes a group sid does not get resolved to its name. Is this a settings problem? Looks like winbind deamon went dormant for a while and then woke up? I am using interface wbcLookupSid provided by the library libwbclient.so for resolving sids to names. These are the winbind related parameters in /etc/samba/smb.conf [global] # separate domain and username with '\', like

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In this release: 1) Dynamic Ipsec Zones now work. 2) Output Traffic Accounting by user/group is supported (thanks to Tuomas Jormola). 3) The following negative test options are added in /etc/shorewall/ipsec and /etc/shorewall/masq: reqid!=<number> spi!=<number> proto!=esp|ah|ipcomp mode!=tunnel|transport

--On Wednesday, January 15, 2003 8:57 AM +0000 Julian Church <jc@ljchurch.co.uk> wrote: > Tom > > There''s no reason you should let a complete stranger question your better > judgement, but weren''t you supposed to be taking a break from all of this? > The problem I am having is "Now what do I do with myself in the early mornings and evenings?":

On Mon, 2004-12-13 at 11:03 -0800, Tom Eastep wrote: > On Mon, 2004-12-13 at 10:45 -0800, Tom Eastep wrote: > > On Mon, 2004-12-13 at 13:43 -0500, M Lu wrote: > > > Tom, can he specify openvpn twice in the tunnel file, e.g. > > > > > > openvpn:udp:5000 > > > openvpn:udp:5001 > > > > > > I think I had the problems with that so I use

Gents, I have build a four interface firewall using Redhat V7.3 using a kernel supplied from the PoPTop website. Obviously I have poptop installed, and it seems to be working just fine. Anyway, I also have Shorewall installed, and it seems to be working just dandy except for one small problem. A little infor first. The interfaces/zones are ... net eth0 loc eth1 192.168.10.0/24 wlan eth2

Hi I have 2nic firewall . I had to open some ranges of udp and tcp ports . I faced a problem that although all the ports are open Some functionality was not working . Any body used shorewall with H323 Voip traffic DNATed . Any help is appretiated . Thanks ----- Original Message ----- From: <shorewall-users-request@lists.shorewall.net> To: <shorewall-users@lists.shorewall.net> Sent:

This is becoming a FAQ and should probably be added to the docs. Thanks, -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net ---------- Forwarded message ---------- Date: Sun, 28 Apr 2002 16:09:01 -0700 (Pacific Daylight Time) From: Tom Eastep <teastep@shorewall.net> To: Carl Spelkens

---------- Forwarded Message ---------- Subject: Re: [Shorewall-users] strange UDP scan results on a Shorewall=20 firewall Date: Sun, 3 Mar 2002 08:33:20 -0800 From: Tom Eastep <teastep@shorewall.net> To: "Scott Duncan" <sduncan@cytechconsult.com> On Saturday 02 March 2002 04:30 am, Scott Duncan wrote: > Yes, the net->all policy is the same on all three (REJECT log

Anton, With regard to the gfortran test cases which don't fail on x86_64 Linux, these are the exact gfortran.log entries for them under i686 Darwin9... > FAIL: gfortran.dg/array_constructor_12.f90 -O0 (internal compiler error) > FAIL: gfortran.dg/array_constructor_12.f90 -O0 (test for excess errors) Executing on host:

Hi I have using a Bering (LRP) box with shorewall, and I must enable IP masquedare only a few hosts on my network. I want to enable only masquerade from 192.168.0.2 to 192.168.0.25. What I must do ? I known that I have to configure the /etc/shorewall/masq file, but I don''t known how. Thanks in advance.

On Wed, Mar 20, 2013 at 6:42 AM, Jack Howarth <howarth at bromo.med.uc.edu> wrote: > Current llvm svn fails make check when built for only x86... Ah, right, need to put that behind a "requires"... hrm. (or I could just drop it & let the machines that are armv5 native catch this) > > [100%] Running the LLVM regression tests > FAIL: LLVM ::