Beta2 looks very interesting!!!:)
Actually I forgot to write the "*" in the mail but I have tested with
"-S*"!
The code that you have pasted looks better to me then the old
test!!!:)
-Matt
On 1 Nov 2015 at 7:19, Tom Eastep wrote:
> On 11/1/2015 4:15 AM, matt darfeuille wrote:
> > Hi tom, tha
On 11/1/2015 4:15 AM, matt darfeuille wrote:
> Hi tom, thank you for explaining the changes you made!
>
> Are the patches also going to be in beta2?
Yes
>
> Patching WRTLOGGING1.patch failed!:
> $ patch ${HOME}/shorewall/5.0.1.1/shorewall-core-5.0.1.1/lib.cli
> WRTLOGGING1.patch
> (Stripping trai
Hi tom, thank you for explaining the changes you made!
Are the patches also going to be in beta2?
Patching WRTLOGGING1.patch failed!:
$ patch ${HOME}/shorewall/5.0.1.1/shorewall-core-5.0.1.1/lib.cli
WRTLOGGING1.patch
(Stripping trailing CRs from patch; use --binary to disable.)
patching file
/h
On 10/31/2015 10:00 AM, matt darfeuille wrote:
> Hi Tom,
>
> Thanks for the new patch; I will patch it later and do some testing
> tomorrow!
>
> I change a bit the install/uninstall/configure scripts:
> shorewall-core-5.0.1.1:
> configure script:
>
> if configure is invoke as:
> ./configure host=de
Hi Tom,
Thanks for the new patch; I will patch it later and do some testing
tomorrow!
I change a bit the install/uninstall/configure scripts:
shorewall-core-5.0.1.1:
configure script:
if configure is invoke as:
./configure host=default
it works but will fail if an atempt is made to use the shor
On 10/30/2015 03:41 PM, Tom Eastep wrote:
>
> Please give the attached patch a try, Matt.
>
Hi Matt,
You may also need this one on top of the last one.
-Tom
--
Tom Eastep\ When I die, I want to go like my Grandfather who
Shoreline, \ died peacefully in his sleep. Not screamin
On 10/30/2015 12:10 PM, matt darfeuille wrote:
> Hi tom,
>
> What need to be also changed:
>
> I have added a pattern for logd in the case statement in the function
> syslog_circular_buffer:
>
> syslog_circular_buffer() {
> local pid
> local tty
> local flags
> local cputime
>
Hi tom,
What need to be also changed:
I have added a pattern for logd in the case statement in the function
syslog_circular_buffer:
syslog_circular_buffer() {
local pid
local tty
local flags
local cputime
local path
local args
local arg
ps 2> /dev/null | while r
On 10/28/2015 2:06 PM, matt darfeuille wrote:
> Using both patches seems to do it(I will do more testing tomorrow)!
>
> Regarding loging on openwrt:
>
> Yes openwrt has changed from using syslogd to logd!
>
> "Older OpenWrt releases(AA and earlier ones) were using BusyBox's
> syslogd (and logread)
Using both patches seems to do it(I will do more testing tomorrow)!
Regarding loging on openwrt:
Yes openwrt has changed from using syslogd to logd!
"Older OpenWrt releases(AA and earlier ones) were using BusyBox's
syslogd (and logread) while the newer ones (BB and later) use
ubox's logd and l
On 10/28/2015 7:23 AM, matt darfeuille wrote:
Hi Tom,
After patching config.pm using the following command:
patch /usr/share/shorewall/shorewall/config.pm ENVIRONMENT.patch
I get the following:
$ shorewall compile -e -T
Compiling using Shorewall 5.0.1(same with 5.0.1.1)...
...
Use of uninitiali
Hi Tom,
After patching config.pm using the following command:
patch /usr/share/shorewall/shorewall/config.pm ENVIRONMENT.patch
I get the following:
$ shorewall compile -e -T
Compiling using Shorewall 5.0.1(same with 5.0.1.1)...
...
Use of uninitialized value $var in pattern match (m//) at
/usr/s
On 10/27/2015 5:54 PM, Tom Eastep wrote:
> On 10/27/2015 11:38 AM, matt darfeuille wrote:
>> On openwrt the logs are not saved in a file, would it be possible to
>> specify a command(logread) instead of a filename for the variable
>> LOGFILE in shorewall.conf?:)
>> EG:
>> LOGFILE=logread
>>
>
> Fo
On 10/27/2015 11:38 AM, matt darfeuille wrote:
Thank you Tom for the temporary fix!!!:)
While waiting for your answer I did it manually:
shorewall compile -e $PWD firewall
Then I "sshed" both files(firewall firewall.conf) to openwrt in the
VARLIB directory followed by shorewall-lite start whic
Thank you Tom for the temporary fix!!!:)
While waiting for your answer I did it manually:
shorewall compile -e $PWD firewall
Then I "sshed" both files(firewall firewall.conf) to openwrt in the
VARLIB directory followed by shorewall-lite start which give me the
following errors:
/etc/shorewall
On 10/26/2015 05:00 PM, matt darfeuille wrote:
> Hi,
>
> While attempting to run on cygwin the following command remote_start
> I get this usage message:
>
> $ shorewall remote_start
>
> Usage: shorewall [debug|trace] [nolock] [ -q ] [ -v[-1|{0-2}] ] [ -t
> ]
...
>
> $ shorewall version -a
>
Hi,
While attempting to run on cygwin the following command remote_start
I get this usage message:
$ shorewall remote_start
Usage: shorewall [debug|trace] [nolock] [ -q ] [ -v[-1|{0-2}] ] [ -t
]
where is one of:
add [:] ...
allow ...
[ check | ck ] [ -e ] [ -r ] [ -p ] [ -r ] [ -T
17 matches
Mail list logo
