similar to: small typo in one of shorewall docs

In the first paragraph of Sweave.Rnw (./src/library/utils/vignettes/Sweave.Rnw), it reads for literate programming \cite{fla:Knuth:1984}. but probably should be for literate programming \citep{fla:Knuth:1984}. ^ kind regards Enrico -- Enrico Schumann Lucerne, Switzerland http://enricoschumann.net

shorewall-docs-html-1.4.10a is missing following files: Banner.htm Shorewall_index_frame.htm seattle_firewall_index.htm Or there should be different index.htm in tar. There might be other missing files but that''s what I found out immidiately when I tried to check local docs. -- Tuomo Soini <tis@foobar.fi> Linux and network services +358 40 5240030 Foobar Oy

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

Hi to all. I have a shorewall ver 2.0.13 running in Fedora Core 3, the machine has dual cpu, 1gb of ram, and 40GB of hard disk space. The machine runs shorewall only and had tested it to openvpn but most of the time just shorewall. The problem, there were instances when internet traffic coming from the local network just halts, I needed to restart shorewall in order the traffic to flow again.

I just downloaded the file ftp://ftp.stat.math.ethz.ch/Software/R/R-devel.tar.gz and within proc.time.Rd, the second paragraph of the \value section contains a typo: The resolution of the times will be system-specific; it is common for them to be recorded to of the order of 1/100 second, and elapsed [...] ^^^^^ I'd say replacing "to

Hi all well im using two interfaces.. e.g: eth0:202.188.9.2 is WAN and eth1;192.168.1.1 is LAN.. when im in LAN let say from 192.168.1.9 i cant open WAN IP address e.g: 202.188.9.2 .. why? how to set this?... i only can open 192.168.1.1 .. if possible i want to have both accessable.. thanks rgds amir

At Tom Eastep''s request, an informal Shorewall Documentation Support = Group (DSG) is hoping to relieve some of the writing and editing burdens = that come with maintaining and improving the Shorewall documentation. = The DSG welcomes and needs your suggestions and contributions about all = aspects of the documentation, including structure, content, references, = style, grammar --

On Wed, 24 Aug 2005 Weigand.Stephen at mayo.edu wrote: > I just downloaded the file > > ftp://ftp.stat.math.ethz.ch/Software/R/R-devel.tar.gz > > and within proc.time.Rd, the second paragraph of the \value > section contains a typo: I believe your understanding of the English language is different from the author here, who is English. (You on the other hand seem to think

I''m hoping someone can give me tips on how I need to set this up with Shorewall. right now I have my internal network masq''ed to my public nic card to share internet. So I use a line like this in my shorewall: ACCEPT masq fw tcp 80,443,53,22,25,109,110,143,3128 That works fine. Now, I set my computer clients up to manually access a proxy server at port 3128. I

Just a note that the 3.3 development release notes (ftp://shorewall.net/pub/shorewall/development/3.3/shorewall-3.3.0/relea senotes.txt) have a typo under the Migration Considerations. <current> /etc/shorewall/accounging. </current> <fixed> /etc/shorewall/accounting. </fixed. Regards, - Craig.

I''ve created a new document that discusses creating multiple zones accessed through a single firewall interface. See: http://shorewall.net/shorewall_quickstart_guide.htm Comments and corrections are welcome. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

Tom, While reading the Shorewall OpenVPN doc, I found that you have to many "7" in the example 77777 instead of 7777 in the text. Jim This entry in /etc/shorewall/tunnels opens the firewall so that OpenVPN traffic on the default port 5000/udp will be accepted to/from the remote gateway. If you change the port used by OpenVPN to 7777, you can define /etc/shorewall/tunnels like

Hello all, I’m running Shorewall 2.2.1 on linux kernel 2.6.10 with iptables 1.2.11. I recently ran a nessus scan of my firewall from a machine outside of the firewall and the nessus report told me that there are some ports open that I did not specify to be open. The ports are 32772/udp, 123/udp, 111/tcp, 32772/udp, and 53/udp. Why are these ports open when I did NOT specify them to be open

I have one question: Can I use routable and non-routable IP addreses together in the DMZ zone? I read the both three-interfaces setup and the Configuration Guide and each one explains how to do the either way? My problem is that, I have to use the public IP address for my DNS server (cannot change that), and setup additional web servers which will do port-forwarding (DNAT) through the firewall

John Anderson has pointed out that Upgrade Issues bullet #7 seemingly conflicts with the second item 4 in the Release Notes and on the Home Page. There is a typo in Bullet #7 -- "not" should be "now". The bullet should read: Late-arriving DNS replies are now dropped by default; there is no need for your own /etc/shorewall/common file simply to avoid logging these

hi, i installed and configured the shorewall-2.0.9 for standalone user interface in fc2,then removed the stop ,stopped and the routestopped files from the /etc/shorewall directory,and run the ''shorewall start'' command,at boot time the messages showing that it is not started,this is the /var/log/messages output fore shorewall: Jan 3 04:13:27 localhost netfs: Mounting other

Dear all, in the first paragraph in Section 4.3.2 of the "R Data Import/Export Manual", it is written 'We havew tested...'. Most likely it should be 'We have tested...' It is just such a minor thing that I was unsure whether to submit a bug report. I use now R 2.2.1 on Win32 but I guess this is independent of the platform and version. Best, Roland P.S. Thanks for

Not subscribed to the list so this may be a repeat. Running instal.sh gave error ./install.sh: line 543: -n: command not found install.sh line 543 was if -n "$first_install" ]; then should be if [ -n "$first_install" ]; then -- Russ Moore System Administrator

Hi all, I have just started using shorewall. So far so good. I have two questions which I cant find an answer to either on the website or googling. They may be stupid so please forgive my ignorance. 1) What is shorewalls preferred operating status, running or stopped? What I mean is, some firewalls start-up and run, and they do their thing, then they stop. But the firewall is still really

http://shorewall.net/pub/shorewall/2.0/shorewall-2.0.14 ftp://shorewall.net/pub/shorewall/2.0/shorewall-2.0.14 New Features: 1. Previously, when rate-limiting was specified in /etc/shorewall/policy (LIMIT:BURST column), any traffic which exceeded the specified rate was silently dropped. Now, if a log level is given in the entry (LEVEL column) then drops are logged