Hi,
Is it possible to take a packet from netgraph to userspace and drop it
there? ie, can I
insert some netgraph node between say lower and upper of a ng_ether
push the packets to
userspace [snort] for some processing and possibly either drop it there?
I know that NgSendData and NgRecvData can
On 12/08/06, Mike Silbersack <[EMAIL PROTECTED]> wrote:
On Fri, 11 Aug 2006, Simon Walton wrote:
> Is there any reason why the default initial timeout for keep alive
> packets needs to be as long as two hours? This period causes the dynamic
> rules in my firewall filter to timeout.
>
> Is the
Hi,
I am struggling with udp drops that show up with netstat -s -p udp as
'dropped due to no socket' and 'dropped due to full socket buffers'.
I am encountering such drops to various degrees on virtually all the
FreeBSD servers I'm testing for a VoIP platform.
For example, the RTP proxy (runn
Hi Mark,
I have bge and fxp interface on the system. I enabled the NETGRAPH by
enabling the NETGRAPH in the config file and compiled the new kernel.
Then, booted with the new kernel.
fxp0: flags=8843 mtu 1500
options=8
inet6 fe80::290:27ff:fe85:8b8c%fxp0 prefixlen 64 scopeid 0x1
On Thu, Aug 17, 2006 at 09:59:37AM +0200, Daniel Ryslink wrote:
>
> I really appreciate your help, but since the machine in question is a
> mission critical router in a production environment, with many housed
> customers connected, I cannot really experiment with its settings anymore.
>
I really appreciate your help, but since the machine in question is a
mission critical router in a production environment, with many housed
customers connected, I cannot really experiment with its settings anymore.
Both my superiors and the customers are quite upset by the recent
problems, I
On Thu, Aug 17, 2006 at 09:45:50AM +0200, Daniel Ryslink wrote:
>
> Hello,
>
> Thank you very much for your assistance.
>
> I am happy to report that we have been able to fix this problem. I just
> wanted to wait a day or two to be sure that it won't resurface again.
>
> The last step
Hello,
Thank you very much for your assistance.
I am happy to report that we have been able to fix this problem. I just
wanted to wait a day or two to be sure that it won't resurface again.
The last steps we did were:
1) Upgrade SuperMicro SS5015M-T BIOS from version 1.1 to version 1.1a
2)
