On 5/5/18 1:33 am, Jeff Kletsky wrote:
On 5/3/18 6:35 AM, Julian Elischer wrote:
On 3/5/18 12:08 am, Michael Sierchio wrote:
On Mon, Apr 30, 2018 at 10:48 AM, Jeff Kletsky
wrote:
"not recv any" doesn't seem to be helpful either
$ sudo ipfw add 64000 count ip from any to any out xmit
On 5/3/18 6:35 AM, Julian Elischer wrote:
On 3/5/18 12:08 am, Michael Sierchio wrote:
On Mon, Apr 30, 2018 at 10:48 AM, Jeff Kletsky
wrote:
"not recv any" doesn't seem to be helpful either
$ sudo ipfw add 64000 count ip from any to any out xmit any not
recv
any
The loopback inter
On 3/5/18 12:08 am, Michael Sierchio wrote:
On Mon, Apr 30, 2018 at 10:48 AM, Jeff Kletsky wrote:
"not recv any" doesn't seem to be helpful either
$ sudo ipfw add 64000 count ip from any to any out xmit any not recv
any
The loopback interface, lo0 ?
On Mon, Apr 30, 2018 at 10:48 AM, Jeff Kletsky wrote:
>
> "not recv any" doesn't seem to be helpful either
>
> $ sudo ipfw add 64000 count ip from any to any out xmit any not recv
> any
The loopback interface, lo0 ?
___
freebsd-net@freebsd.org mai
On Tue, May 01, 2018 at 09:04:36PM +0800, Julian Elischer wrote:
> On 1/5/18 2:02 am, Eugene Grosbein wrote:
> >01.05.2018 0:48, Jeff Kletsky wrote:
> >
> >> From time to time, I rewrite my firewall rules to take advantages of the
> >> ever-improving set of features that ipfw provides. One of the
On 1/5/18 2:02 am, Eugene Grosbein wrote:
01.05.2018 0:48, Jeff Kletsky wrote:
From time to time, I rewrite my firewall rules to take advantages of the
ever-improving set of features that ipfw provides. One of the challenges I have
faced in the past was selecting packets that are generated o
01.05.2018 0:48, Jeff Kletsky wrote:
> From time to time, I rewrite my firewall rules to take advantages of the
> ever-improving set of features that ipfw provides. One of the challenges I
> have faced in the past was selecting packets that are generated on the
> firewall host itself, as oppose
