On Monday 12 April 2010 13:31:09 Tanstaafl wrote:
On 2010-04-11 9:20 AM, Graham Murray wrote:
Tanstaafl tansta...@libertytrek.org writes:
I'm a bit clueless when it comes to firewalls, and have no idea what
these numbers mean/do:
*raw
:PREROUTING ACCEPT [4911:886011]
:OUTPUT
On 2010-04-11 9:20 AM, Graham Murray wrote:
Tanstaafl tansta...@libertytrek.org writes:
I'm a bit clueless when it comes to firewalls, and have no idea what
these numbers mean/do:
*raw
:PREROUTING ACCEPT [4911:886011]
:OUTPUT ACCEPT [4546:2818732]
COMMIT
The numbers are [packets:bytes]
On Mon, Apr 12, 2010 at 8:31 AM, Tanstaafl tansta...@libertytrek.org wrote:
On 2010-04-11 9:20 AM, Graham Murray wrote:
Tanstaafl tansta...@libertytrek.org writes:
I'm a bit clueless when it comes to firewalls, and have no idea what
these numbers mean/do:
*raw
:PREROUTING ACCEPT
On 2010-04-10 10:26 PM, Kerin Millar wrote:
On 10/04/2010 23:17, Tanstaafl wrote:
This is on a server box, and I am *not* doing NAT on it...
Do I even need the nat table? If not, I'd like to build the kernel
without NAT support, but if there's a good reason not to do that, I
won't...
If
Tanstaafl tansta...@libertytrek.org writes:
I'm a bit clueless when it comes to firewalls, and have no idea what
these numbers mean/do:
*raw
:PREROUTING ACCEPT [4911:886011]
:OUTPUT ACCEPT [4546:2818732]
COMMIT
The numbers are [packets:bytes] which match the rule or table
concerned.
On 10/04/2010 23:17, Tanstaafl wrote:
Hello,
This is on a server box, and I am *not* doing NAT on it...
Do I even need the nat table? If not, I'd like to build the kernel
without NAT support, but if there's a good reason not to do that, I won't...
If you will not be populating the nat
6 matches
Mail list logo