Go Back   DaemonForums > FreeBSD > FreeBSD General

FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below.

Thread Tools Display Modes
  #1   (View Single Post)  
Old 6th August 2010
putrycy putrycy is offline
New User
Join Date: Aug 2010
Posts: 1
Default netstat -s -p ip output meaning

Hey, I'd like to ask you all a question, that is ought to be simple -- what exactly does each field of netstat -s -p ip output mean ?, E.g.

        26740727 total packets received
        14 bad header checksums
        0 with size smaller than minimum
        0 with data size < data length
        0 with ip length > max ip packet size
        0 with header length < data size
        0 with data length < header length
        0 with bad options
        0 with incorrect version number
        365 fragments received
        0 fragments dropped (dup or out of space)
        0 fragments dropped after timeout
        122 packets reassembled ok
        26734571 packets for this host
        5847 packets for unknown/unsupported protocol
        0 packets forwarded (0 packets fast forwarded)
        37 packets not forwardable
        0 packets received for unknown multicast group
        0 redirects sent
        28384081 packets sent from this host
        0 packets sent with fabricated ip header
        0 output packets dropped due to no bufs, etc.
        0 output packets discarded due to no route
        6054 output datagrams fragmented
        27879 fragments created
        0 datagrams that can't be fragmented
        0 tunneling packets that can't find gif
        0 datagrams with bad address in header
Im especially interested in 'packets not forwardable'.
What does presence of "not forwardable packets" mean ? Thanks in advance for Your kind help.
Reply With Quote
  #2   (View Single Post)  
Old 20th August 2010
sharris sharris is offline
Package Pilot
Join Date: Jun 2010
Posts: 146

We're in the same boat but I did get Packet-Filter installed. I guest you know by now you got a lot of googling to do and be sure to read all you can about Packet-Filter and do a forum search right here under Open-BSD mostly. Than you get a good idea about how networking really works just by understanding pf. Open-BSD Packet-Filter RULES!



Reply With Quote
  #3   (View Single Post)  
Old 20th August 2010
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Helpful companion
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223

The version of OpenBSD's pf that was ported to FreeBSD/NetBSD is ancient, 4.0/4.2 era and lacks recent development.

It may indeed be better than whatever else is available for FreeBSD/NetBSD, but there have been some fundamental changes in configuration syntax with the recent releases of OpenBSD, especially around scrub/nat/rdr rules.

So if you're going to use OpenBSD's pf documentation, you may wish to grab an older PDF copy from here.

Peter N. M. Hansteen's Book of PF would still be helpful for FreeBSD/NetBSD users, and for smaller configurations his famous pf tutorial is still updated occasionally.

The FreeBSD/NetBSD folks need to stop referring to OpenBSD for their outdated fork of pf, as do users of those operating systems.. as it's only going to frustrate them.

Good luck.
Reply With Quote
  #4   (View Single Post)  
Old 20th August 2010
ocicat ocicat is offline
Join Date: Apr 2008
Posts: 3,298

Originally Posted by BSDfan666 View Post
The FreeBSD/NetBSD folks need to stop referring to OpenBSD for their outdated fork of pf, as do users of those operating systems.. as it's only going to frustrate them.
I am sure BSDfan666 meant "...stop referring to OpenBSD 's documentation for their outdated forks of pf(4), ...".

Otherwise, I completely agree with his analysis. Henning Brauer, the primary OpenBSD developer working on pf(4), has rearchitected much of its internals over several recent OpenBSD releases. These rapid changes have made it hard enough for the OpenBSD community to keep up; it must be virtually impossible for the other *BSD projects.

Syntax which may have been correct a few releases (of OpenBSD) ago will now create errors. I'm sure the converse is true too -- using the current OpenBSD pf(4) documentation on the older versions integrated into FreeBSD & NetBSD must be as equally frustrating in creating viable rulesets.
Reply With Quote

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
What is the meaning of "remote hole" bruguiea OpenBSD General 6 2nd May 2010 05:43 PM
output to a file in java c0mrade Programming 4 15th October 2009 07:55 AM
C and file input/output 18Googol2 Programming 3 20th August 2008 04:02 PM
netstat state LISTEN change CTOS OpenBSD General 1 4th May 2008 10:52 PM

All times are GMT. The time now is 10:56 PM.

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick