search for: tanas

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

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

Hi, I noticed that network connection of one of my boxes got significantly slow just after upgrading it to 8.0R. The box has an em0 (82547EI) and worked fine with 7.2R. The symptoms are: - A ping to a host on the same LAN takes 990ms RTT, it reduces gradually to around 1ms, and then it returns to around 1s. The rate was about 2ms/ping. - The response is quite slow, but no packet

copy d:\bugs.ps \\ouessant\lexmark after having deleted all the samba log files and restarted the SMBd daemon from the SWAT Web interface. This leads to the INTERNAL ERROR, see samba.oulx Now, to locate the problem, I tried the same kind of command on the same file, bugs.ps, but using the SMBCLIENT application from the Linux server itself, without changing anything, nor restarting the SMBd

When I try the command nmblookup -M TESTGROUP querying TESTGROUP on 192.168.255.255 name_query failed to find name TESTGROUP #1d My /etc/hosts file is # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost localhost.localdomain 192.168.100.101 testpc 192.168.100.100 linuxserver /etc/samba/lmhosts is 127.0.0.1 localhost

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

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

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