Re: [leaf-user] no shorewall log

2013-10-12 Thread david M brooke
On 10 Oct 2013, at 23:51, Victor McAllister wrote: By the way, I tried to remotely restart shorewall with shorewall restart - and it recompiled and started. when I sued the old command svi shorewall restart it did not restart and just said shorewall already running. One should not use

Re: [leaf-user] no shorewall log

2013-10-10 Thread Erich Titl
Hi Victor on 09.10.2013 23:27, Victor McAllister wrote: On 10/9/2013 1:48 PM, david M brooke wrote: Hi Victor, ... By the way, I am running one WRAP on a 16mb flash because I could not get them to boot properly on a newer flash - although I was using append libata.dma=3 usb_wait=3 Try

Re: [leaf-user] no shorewall log

2013-10-10 Thread KP Kirchdörfer
Hello Victor; Am Mittwoch, 9. Oktober 2013, 13:09:30 schrieb Victor McAllister: I manage two remote WRAP 486 firewalls running Bering 5.0.1. If I log in with putty, change shorewall rules - do svi shorewall restart - it says shorewall already running. I have to save configuration and a

Re: [leaf-user] no shorewall log

2013-10-10 Thread Victor McAllister
On 10/10/2013 9:43 AM, KP Kirchdörfer wrote: Hello Victor; Am Mittwoch, 9. Oktober 2013, 13:09:30 schrieb Victor McAllister: I manage two remote WRAP 486 firewalls running Bering 5.0.1. If I log in with putty, change shorewall rules - do svi shorewall restart - it says shorewall already

Re: [leaf-user] no shorewall log

2013-10-10 Thread KP Kirchdörfer
Am Donnerstag, 10. Oktober 2013, 10:28:17 schrieb Victor McAllister: On 10/10/2013 9:43 AM, KP Kirchdörfer wrote: Hello Victor; Am Mittwoch, 9. Oktober 2013, 13:09:30 schrieb Victor McAllister: I manage two remote WRAP 486 firewalls running Bering 5.0.1. If I log in with putty,

Re: [leaf-user] no shorewall log

2013-10-10 Thread Victor McAllister
On 10/10/2013 11:22 AM, KP Kirchdörfer wrote: Am Donnerstag, 10. Oktober 2013, 10:28:17 schrieb Victor McAllister: On 10/10/2013 9:43 AM, KP Kirchdörfer wrote: Hello Victor; Am Mittwoch, 9. Oktober 2013, 13:09:30 schrieb Victor McAllister: I manage two remote WRAP 486 firewalls running

[leaf-user] no shorewall log

2013-10-09 Thread Victor McAllister
I manage two remote WRAP 486 firewalls running Bering 5.0.1. If I log in with putty, change shorewall rules - do svi shorewall restart - it says shorewall already running. I have to save configuration and a reboot to implement shorewall changes. When it restarts - I get a shorewall-init.log

Re: [leaf-user] no shorewall log

2013-10-09 Thread david M brooke
Hi Victor, Based on a quick look at /etc/init.d/shorewall I reckon that the restart block might be broken - seems that it does start without stop. Most people use the shorewall command directly to do a restart. In other words just: shorewall restart not: svi shorewall restart (There are

Re: [leaf-user] no shorewall log

2013-10-09 Thread Victor McAllister
On 10/9/2013 1:48 PM, david M brooke wrote: Hi Victor, Based on a quick look at /etc/init.d/shorewall I reckon that the restart block might be broken - seems that it does start without stop. Most people use the shorewall command directly to do a restart. In other words just: shorewall

[leaf-user] Puzzling Shorewall Log entry.

2005-12-18 Thread Jim Ford
I'm getting a few entries in my Bering UClibC firewall like the following. They come in batches of 3 to 6 or so: Dec 18 13:33:31firewallall2all REJECT eth1local 192.168.1.6481.106.14.29TCP 211854321 0 65535 SYN 0 192.168.1.64 is the IP

RE: [leaf-user] Puzzling Shorewall log entry?

2005-12-12 Thread Robert K Coffman Jr - Info From Data
. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Ford Sent: Saturday, December 10, 2005 8:26 AM To: leaf-user Subject: [leaf-user] Puzzling Shorewall log entry? Trying to understand the Shrorewall logs on my Bering ULibC setup, I'm puzzled over

[leaf-user] Puzzling Shorewall log entry?

2005-12-10 Thread Jim Ford
Trying to understand the Shrorewall logs on my Bering ULibC setup, I'm puzzled over the following entry, of which I've had several: Dec 10 06:47:01firewallrfc1918 DROPeth0eth1 192.168.0.2 192.168.1.64TCP 259554321 1410215655 63659 ACK