search for: tana

Displaying 8 results from an estimated 8 matches for "tana".

Did you mean: tan
2013 Jun 21
0
[Bug 696] Extra tcp options for REJECT --reject-with tcp-reset-both / tcp-reset-destination
https://bugzilla.netfilter.org/show_bug.cgi?id=696 --- Comment #3 from Alessandro Vesely <vesely at tana.it> 2013-06-21 15:50:56 CEST --- (In reply to comment #2) > you have to put this REJECT rule before any RELATED/ESTABLISHED > conntrack ctstate match rules (which is suboptimal). No, I can use conntrack -D to have the connection unESTABLISHED. In general, it is polite to send a tcp-reset...
2013 Jun 22
0
[Bug 696] Extra tcp options for REJECT --reject-with tcp-reset-both / tcp-reset-destination
https://bugzilla.netfilter.org/show_bug.cgi?id=696 --- Comment #5 from Alessandro Vesely <vesely at tana.it> 2013-06-22 10:05:55 CEST --- (In reply to comment #4) >> The kernel manages the seq and ack_seq counters itself, so it doesn't have >> to try > > ...for locally terminated connections, yes. But what about forwarded traffic? > That is where the difficulty comes in....
2009 Nov 30
2
em interface slow down on 8.0R
...tors not avail2 = 0 em0: Std mbuf failed = 0 em0: Std mbuf cluster failed = 0 em0: Driver dropped packets = 0 em0: Driver tx dma failure in encap = 0 dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 6.9.14 dev.em.0.%driver: em dev.em.0.%location: slot=1 function=0 handle=\_SB_.PCI0.P0P2.TANA dev.em.0.%pnpinfo: vendor=0x8086 device=0x1019 subvendor=0x8086 subdevice=0x302c class=0x020000 dev.em.0.%parent: pci1 dev.em.0.debug: -1 dev.em.0.stats: -1 dev.em.0.rx_int_delay: 0 dev.em.0.tx_int_delay: 66 dev.em.0.rx_abs_int_delay: 66 dev.em.0.tx_abs_int_delay: 66 dev.em.0.rx_processing...
2003 Dec 01
0
No subject
...ivered-To: samba@lists.samba.org Received: from smtp.simicro-internet.mg (host-216-252-168-5.interpacket.net [216.252.168.5]) by lists.samba.org (Postfix) with ESMTP id 5EC35427C for <samba@lists.samba.org>; Fri, 17 Aug 2001 03:53:12 -0700 (PDT) Received: from simicro-internet.mg (indri.tana.simicro.net [192.168.10.98]) by smtp.simicro-internet.mg (Postfix) with ESMTP id 87C343DB4 for <samba@lists.samba.org>; Fri, 17 Aug 2001 13:46:33 +0300 (EAT) Message-ID: <3B7CF8F4.52AC8901@simicro-internet.mg> Date: Fri, 17 Aug 2001 13:59:00 +0300 From: Do-Risika RAFIEFERANTSIARON...
2003 Dec 01
0
No subject
...ivered-To: samba@lists.samba.org Received: from smtp.simicro-internet.mg (host-216-252-168-5.interpacket.net [216.252.168.5]) by lists.samba.org (Postfix) with ESMTP id EEDBA4C31 for <samba@lists.samba.org>; Tue, 14 Aug 2001 10:43:53 -0700 (PDT) Received: from simicro-internet.mg (indri.tana.simicro.net [192.168.10.98]) by smtp.simicro-internet.mg (Postfix) with ESMTP id E1DC03DAE for <samba@lists.samba.org>; Tue, 14 Aug 2001 20:37:28 +0300 (EAT) Message-ID: <3B7964C5.D7266FBF@simicro-internet.mg> Date: Tue, 14 Aug 2001 20:49:57 +0300 From: Do-Risika RAFIEFERANTSIARON...
2008 Sep 03
0
Upssched timers
Hi all, I've installed the current debian nut package, i.e. version 2.0.4. I've configured upssched with timers as follows: AT ONBATT black at localhost START-TIMER runonbattery 5 AT ONLINE black at localhost CANCEL-TIMER runonbattery AT ONLINE black at localhost START-TIMER backonline 5 AT ONBATT black at localhost CANCEL-TIMER backonline The idea is to send alerts in case of
2013 Sep 06
2
Bug#721946: Bug#721946: xen-hypervisor-4.1-amd64: dom0_mem cannot exceed some value
On Fri 06/Sep/2013 10:12:29 +0200 Ian Campbell wrote: > On Thu, 2013-09-05 at 20:52 +0200, Alessandro Vesely wrote: >> >> I tried GRUB_CMDLINE_XEN="dom0_mem=8192M": that delivers 6964868K total, then >> crashes when used=2837436K free=4127432K. > > On a modern dom0 kernel you need to specify the maximum memory as well, > i.e. dom0_mem=8192M,max:8192M
2013 Sep 05
4
Bug#721946: xen-hypervisor-4.1-amd64: dom0_mem cannot exceed some value
Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: normal I tried GRUB_CMDLINE_XEN="dom0_mem=8192M": that delivers 6964868K total, then crashes when used=2837436K free=4127432K. By crash I mean the gnome screen was blown away, replaced by a black screen with white log lines. That seems to happen every time dom0 uses a large amount of memory. After setting