Comments for DiegoWoitasen

Comment on About me by Diego Woitasen

Diego Woitasen — Thu, 26 Jan 2012 16:28:40 +0000

En qué sitio web? Estoy flojo de memoria.

Lo único que necesité algunas veces es el archiving/hsm, que no está en le versión Open y en éste Zextras (que no lo conocía) parece que tampoco está.

Igual parece interesante el proyecto, aunque medio probe todavía. Lo voy a ir observando. gracias.

saludos!

Comment on About me by johnny

johnny — Thu, 26 Jan 2012 16:15:44 +0000

Hola Diego, vi tu comentario en el sitio web, queria comentarte que existe una aplicación para Zimbra open source que permite tener las funcionalidades de la network incluso con algunas mejoras que aquella no tiene. Se llama zextras y se puede probar gratis.

Comment on How to install 389 Directory Server in Debian by Roldyx

Roldyx — Wed, 30 Nov 2011 17:42:33 +0000

Thanks so much information!!

Comment on Zimbra archiving with compression, the numbers by Diego Woitasen

Diego Woitasen — Wed, 30 Nov 2011 13:08:47 +0000

Yes. I have to write a HOWTO about archiving setup. In the meanwhile, I’ll give you some tips. For archiving you need a second volume. You have to create a directory in the filesystem (zimbra:zimbra owner and group) and then you have to add a volume in the server tab in the configuration interface (there is a checkbox if you want compression). Sqlalchemy Python module is required to run the script (there is a package in Debian/Ubuntu).

I’ll write a howto this week. You should notice that I have this script running with Zimbra 6.x, I haven’t tested it with 7.x (also in my TODO list).

Regards,
Diego

Comment on Zimbra archiving with compression, the numbers by Jaijo

Jaijo — Wed, 30 Nov 2011 07:04:42 +0000

I have tried your script. While executing, I have got an error “Archive volume doesn’t exist”. Could you please help me out on this..Any help must be appreciated .

Comment on Confusion using Iptables, nat and bridge by Nancy Donald

Nancy Donald — Sat, 08 Oct 2011 06:25:38 +0000

Appreciated the share!
Nancy

Comment on Synchronizing files with Csync2 by Nancy

Nancy — Sat, 01 Oct 2011 07:40:32 +0000

Thanks for the share!
Nancy.R

Comment on Confusion using Iptables, nat and bridge by Diego Woitasen

Diego Woitasen — Sun, 25 Sep 2011 02:34:50 +0000

The double invocation happens when you have bridging+routing the same host. In real life, I’ve only seen this in virtualization when you have the host as gateway. The packet is processed by Iptables in the bridge (bridge-nf-call-iptables=1) and routing. There is no problem with his network topoligy.

This scenario is easy to reproduce, just configure a virtualization host as gateway in one of your VMs and insert a LOG rule in the nat table.

Comment on Confusion using Iptables, nat and bridge by Confusion using Iptables, nat and bridge » DiegoWoitasen | Linux Blog

Confusion using Iptables, nat and bridge » DiegoWoitasen | Linux Blog — Thu, 22 Sep 2011 04:45:28 +0000

[...] He has a one virtual machine (Qemu/KVM) connected to the world using … Continued here: Confusion using Iptables, nat and bridge » DiegoWoitasen This entry was posted in Uncategorized and tagged chatting-via, irc, kvm, one-virtual, the-guy, [...]

Comment on Confusion using Iptables, nat and bridge by reader

reader — Wed, 21 Sep 2011 21:47:59 +0000

>he never saw the packet in the POSTROUTING chain. Why? The quick answer is “packets don’t cross nat table twice”.

Packets do pass through the NF_INET_POST_ROUTING hook; it’s just “nat” that is special (it’s a config db of sorts). I dunno where the double invocation stems from, but remember that if one and the same packet enters the host twice, and thus NFCT twice, there will be surprises. (Note lo is exempt because such packets never enter the host because they never leave the host.) Because you gave the user no time and just slapped bridge-nf-call-iptables=0 into the room and he subsequently went his ways, there was no time to reason more about his network topology, and he may now have a half “broken” iptables setup — I’m waiting for the moment he returns to make aware that $something does not function as it traverses FORWARD on the bridge layer.