Hi.
Ermal Luçi wrote:
4- The node has these messages:
#ifdef NG_PF_DEBUG
NGM_PF_GET_STATS, (number of packets in/out)
NGM_PF_CLR_STATS,
NGM_PF_GETCLR_STATS,
#endif
What for comment them out? To save CPU on several addition operations?
This stats could be used not only
Hi.
Nikos Vassiliadis wrote:
In my case doing a few times:
ifconfig fxp0 192.168.1.71/16
ifconfig fxp0 192.168.1.71/24
locks the box.
Doing this you are dropping all routes going via that network. Probably
you are dropping route to your pptp peer which can lead to wrapping
tunnel inside
Hello,
I hope this is actually the right list and my request isn't too
outrageous.
I am looking for a working IGMP proxy for FreeBSD 6.2. My ISP is
offering TV over IP using IGMP. I use pfSense as a gateway.
Research so far gave my this:
1. Activating multicast routing in the kernel is easy -
Alexander,
the only reason i made them available only for debugging is cause of
int32_t types of those counter and these could overflow easily on
busy environments.
For 64bit counters on 32bit archs you need atomic operations and i
don't know how much overhead it will be!?(correct me if i am
Hi Everybody,
I had a code in Linux using datagram sockets to run over UDP and get/set
some ancillary options as well. Following are those options.
The socket has been opened using the following call.
sockfd = socket(AF_INET, SOCK_DGRAM, IPPROTO_UDP);
1 To send UDP datagram with UDP-Checksum
Hello,
The following options are available:
To unsubscribe send a message to:
[EMAIL PROTECTED]
To subscribe to the digest of this list send a message to:
[EMAIL PROTECTED]
To subscribe to the nomail version of this list send a message to:
[EMAIL PROTECTED]
The nomail version of a list
Ermal Luçi wrote:
the only reason i made them available only for debugging is cause of
int32_t types of those counter and these could overflow easily on
busy environments.
Yes it's could. But sometimes they can be needed just to see if/how it
works.
I just wanted to say that making it
On 5/29/07, Jack Vogel [EMAIL PROTECTED] wrote:
On 5/27/07, Jack Vogel [EMAIL PROTECTED] wrote:
On 5/27/07, Stefan Lambrev [EMAIL PROTECTED] wrote:
Hi Jack,
Jack Vogel wrote:
Stefan,
I am having a long weekend and am supposed to be doing
something other than this :)
OK, here it is with stats activated :).
On 5/30/07, Alexander Motin [EMAIL PROTECTED] wrote:
Ermal Luçi wrote:
the only reason i made them available only for debugging is cause of
int32_t types of those counter and these could overflow easily on
busy environments.
Yes it's could. But
Ermal Luçi wrote:
OK, here it is with stats activated :).
One more: all binary netgraph messages are hidden from user-level in
ng_pf.h. They are all covered with #ifdef _KERNEL. Specially?
--
Alexander Motin
___
freebsd-net@freebsd.org mailing
Does any driver do this now? And if a driver were to coalesce
packets and send something up the stack that violates mss
will it barf?
Jack
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe,
Jack Vogel wrote:
Does any driver do this now? And if a driver were to coalesce
packets and send something up the stack that violates mss
will it barf?
not that I know of..
transmit strictly according to the rules.
receive generously.
Jack
___
On Wed, May 30, 2007 at 04:45:05PM -0700, Jack Vogel wrote:
Does any driver do this now? And if a driver were to coalesce
packets and send something up the stack that violates mss
will it barf?
It would barf for things like bridging where the packet gets spit out a
different interface. The
Andrew Thompson wrote:
On Wed, May 30, 2007 at 04:45:05PM -0700, Jack Vogel wrote:
Does any driver do this now? And if a driver were to coalesce
packets and send something up the stack that violates mss
will it barf?
It would barf for things like bridging where the packet gets spit out a
On 5/30/07, Julian Elischer [EMAIL PROTECTED] wrote:
Andrew Thompson wrote:
On Wed, May 30, 2007 at 04:45:05PM -0700, Jack Vogel wrote:
Does any driver do this now? And if a driver were to coalesce
packets and send something up the stack that violates mss
will it barf?
It would barf for
I wanted to let everyone know that I will soon have a
new 10G driver to add to the tree. It is a PCI Express
MSI/X adapter, I would like to call this driver 'ix' rather
than follow Linux who are calling it 'ixgbe'. It is not
backwardly compatible with ixgb. Any objections
to the name? It would
According to the following thread, one must do more then just apply the NAT-T
patch and rebuild the kernel:
http://lists.freebsd.org/pipermail/freebsd-net/2006-September/011855.html
What other steps are necessary to apply the patch to a 6.x system? Can I get
away without
According to the following thread, one must do more then just apply the NAT-T
patch and rebuild the kernel:
http://lists.freebsd.org/pipermail/freebsd-net/2006-September/011855.html
What other steps are necessary to apply the patch to a 6.x system? Can I get
away without
18 matches
Mail list logo
