similar to: New 2.0.2b .lrp and new .lrp policy

The 2.0.2 .lrp released yesterday contained the wrong version of /usr/share/shorewall/functions. I have updated the .lrp with the correct version of the functions file. [root@lists shorewall-2.0.2]# ls -l shorwall-2.0.2.lrp -rw-r--r-- 1 root ftp 78325 May 14 06:28 shorwall-2.0.2.lrp [root@lists shorewall-2.0.2]# grep shorwall 2.0.2.md5sums 3ae771fcbfe217006e88e69a597c6455

Attached please find updated build and publish scripts. They set the ''ulink.target'' parameter appropriately when converting docbook->HTML. I have always hacked my xhtml/params.xsl file to set this parameter; these updated scripts make that abomination unnecessary. Paul/Mike: It might be a good idea to add a CVS project for these scripts. -Tom -- Tom Eastep \ Nothing is

After gaining some experience with the new release model, it has become apparent to me that a small adjustment is warrented. I previously announced that updates to the stable release would only contain bug fixes. I''m modifying that slightly to allow for small low-risk enhancements; large and/or risky enhancements will still be restricted to the development release. We have seen this

-----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

---------- Original Message ---------------------------------- From: "Jim Van Eeckhoutte" <jim@vaneeckhoutte.com> Reply-To: <jim@vaneeckhoutte.com> Date: Mon, 8 Jul 2002 15:27:14 -0700 this is shorewall status output: tcp 6 431899 ESTABLISHED src=192.168.20.5 dst=64.4.12.45 sport=2185 dport=1863 src=64.4.12.45 dst=63.25.123.58 sport=1863 dport=2185 [ASSURED] use=1

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The packages that I uploaded earlier were unfortunately incorrect. I have uploaded the correct packages. The incorrect md5sums are: 14e8f2bfa08cc5ca2715c8b1179d5eb2 shorewall-2.0.10-1.noarch.rpm 54bcbb2216ad3db9870507cd9716fd99 shorewall-2.0.10.tgz c2fe0acc7f056acb56d089cf8dafa39a shorwall-2.0.10.lrp The correct md5sums are:

--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?":

Content is the same as RC2. http://shorewall.net/pub/shorewall/shorewall-2.0.3 ftp://shorewall.net/pub/shorewall/shorewall-2.0.3 The release will be coming to a mirror near you shortly. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

Hello, I would like to use .lrp version of 2.1.3 Shorewall development release. But it is not accessible on FTP/WWW server and LrpN project on the CVS Repository includes some old version. So my question is - is there any script for creating .lrp file from .tgz or .rpm instead of hand work? ;-) Thank you, Milos

Hi all .... I Have installed Bering LRP on Many sites and I am very pleased with the capabilites of shorewall. Howerver I came across a prob that I am unaware ot its solution. Using shorewall 2.0.2f Kernel 2.4.24 On one Site LRP box serves internet outgoing connections through ( static IP ) a DSL line AND an incoming dial-in PPP conection. My shorewall configuration Is based upon the fact

Hi I have noticed that some versions of syslinux later than 1.66 fail to install a working boot block on a CF card in Soekris net4521 board. The Bios is: comBIOS ver. 1.05 20020419 Copyright (C) 2000-2001 Soekris Engineering. The card is a 64M Sandisk and I am useing a version of LEAF called WISP-dist but I also experianced the same problem with the Bering distro. Here is my syslinux.cfg:

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.

i've got a nut.lrp package now for GLIBC-2.2 on wisp-dist 1.3 (linux-2.4.25), if someone is interested of. Michael Plourde Digicom Technologies Inc.

This is from Sean Covel: -------------------------------------------------------------------------- parsefw is a C program to parse Shorewall (netfilter) logfiles and display them in a pretty format similar to the old ipchains format. Some text is added about certain well-known destination ports, and they are linked to a FIREWALL FAQ website for further explaination. The original parsefw.c was

Hi, I own a UPS HP T750. Is there a driver for this UPS (either serial or USB)? thx kp

Javier Fernández-Sanguino Peña has discovered an exploitable vulnerability in the way that Shorewall handles temporary files and directories. The vulnerability can allow a non-root user to cause arbitrary files on the system to be overwritten. LEAF Bering and Bering uClibc users are generally not at risk due to the fact that LEAF boxes do not typically allow logins by non-root users. For 2.0

Hello, I am using syslinux to boot a Soekris net4801 into LRP/Lince 1.2 linux. Net4801 has no video card - it has only a serial port. During bootstrap syslinux writes the text file syslinux.dpy to the serial port but it breaks the line every 15th character. I tried syslinux versions 1.66 and 2.11 with same results. In the Archives from June 3, 2002 , there is a message on this subject

Newbie question here. I am doing some work with Bering uClibC and have been wondering about the meaning of the various parameters in the syslinux.cfg file. I have already read the FAQ (http://syslinux.zytor.com/faq.php) which leaves me wondering where to find more information on the 'default' and 'append' parameters. For example, what are all of the kernel and other arguments that

Hello all. I created a "plug and play" kind of solution for bridge-based QoS LAN-WAN traffic shaping. Based on the LEAF bering-uClibc branch, I''m calling it ''QBox'' and the project site for now is located at: http://content.cs.luc.edu/projects/comp412/q-box I''m interested in any feedback you might have. This is based off of experience I have over the

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 > >_______________________________________________________________ >