On 00:35+0100, Jan 15, 2003, Wiktor Niesiobedzki wrote:
On Tue, Jan 14, 2003 at 01:18:02PM +0300, Maxim Konovalov wrote:
On 17:20+0100, Jan 13, 2003, Wiktor Niesiobedzki wrote:
It seems, that now logging with skipto is working correctly (I get expected
results), but funny thing, when
On 17:20+0100, Jan 13, 2003, Wiktor Niesiobedzki wrote:
On Sun, Jan 12, 2003 at 04:52:53PM +0300, Maxim Konovalov wrote:
Hello,
Please try a next patch:
It seems, that now logging with skipto is working correctly (I get expected
results), but funny thing, when there is no log rule,
On Tue, Jan 14, 2003 at 01:18:02PM +0300, Maxim Konovalov wrote:
On 17:20+0100, Jan 13, 2003, Wiktor Niesiobedzki wrote:
It seems, that now logging with skipto is working correctly (I get expected
results), but funny thing, when there is no log rule, the skipto command won't
work.
Yes,
On Sun, Jan 12, 2003 at 04:52:53PM +0300, Maxim Konovalov wrote:
Hello,
Please try a next patch:
It seems, that now logging with skipto is working correctly (I get expected
results), but funny thing, when there is no log rule, the skipto command won't
work.
Consider this results:
portal#
Hello,
On 17:34+0100, Nov 10, 2002, Wiktor Niesiobedzki wrote:
Hi,
Rule of the format:
ipfw add 100 skipto 400 log logamount 0 ip from 192.168.0.0/24 to 192.168.0.0/24
Will give this strange result:
Nov 10 17:01:05 portal kernel: ipfw: 100 SkipTo 400 TCP 192.168.0.1:139
192.168.0.2:1170
Hi,
Rule of the format:
ipfw add 100 skipto 400 log logamount 0 ip from 192.168.0.0/24 to 192.168.0.0/24
Will give this strange result:
Nov 10 17:01:05 portal kernel: ipfw: 100 SkipTo 400 TCP 192.168.0.1:139
192.168.0.2:1170 out via ed0
Nov 10 17:01:05 portal kernel: ipfw: 310 Pipe 2 TCP
