This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
German / Re: DHCP, DNS und SAMBA funktionieren nicht nach nächtlichem Upgrade von Samba
« on: March 09, 2023, 09:07:19 pm »
Vielen Dank!
Diese Lösung hat perfekt funktioniert.
Diese Lösung hat perfekt funktioniert.
2
Other modules / Error starting bind9.service
« on: January 03, 2018, 04:27:32 pm »
Unable to start bind9.service
Code: [Select]
ldb: unable to dlopen /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/asq.so : /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/asq.so: failed to map segment from shared object
ldb: unable to dlopen /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/ldap.so : /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/ldap.so: failed to map segment from shared object
ldb: unable to dlopen /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/paged_results.so : /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/paged_results.so: failed to map segment from shared object
ldb: unable to dlopen /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/paged_searches.so : /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/paged_searches.so: failed to map segment from shared object
ldb: unable to dlopen /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/rdn_name.so : /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/rdn_name.so: failed to map segment from shared object
ldb: unable to dlopen /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/sample.so : /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/sample.so: failed to map segment from shared object
ldb: unable to dlopen /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/server_sort.so : /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/server_sort.so: failed to map segment from shared object
ldb: unable to dlopen /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/skel.so : /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/skel.so: failed to map segment from shared object
ldb: unable to dlopen /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/tdb.so : /usr/lib/x86_64-linux-gnu/ldb/modules/ldb/tdb.so: failed to map segment from shared object
03-Jan-2018 13:23:06.497 samba_dlz: ldb: Unable to find backend for '/var/lib/samba/private/dns/sam.ldb' - do you need to set LDB_MODULES_PATH?
03-Jan-2018 13:23:06.497 samba_dlz: Failed to connect to /var/lib/samba/private/dns/sam.ldb
03-Jan-2018 13:23:06.497 dlz_dlopen of 'AD DNS Zone' failed
03-Jan-2018 13:23:06.497 SDLZ driver failed to load.
03-Jan-2018 13:23:06.497 DLZ driver failed to load.
03-Jan-2018 13:23:06.497 loading configuration: failure
03-Jan-2018 13:23:06.497 exiting (due to fatal error)
3
Portuguese / Re: Conectividade Social - Liberar
« on: March 21, 2012, 04:50:22 pm »
Eis ai a solução pra que a Conectividade social funcione no Zentyal...
Essa regra se aplica caso você use o filtro de conteúdo, caso não esteja usando a porta usada será a 3128...
Deixe o arquivo /etc/zentyal/hooks/firewall.postservice deste jeito:
Substitua eth1 pela sua interface interna e 192.168.1.1 pelo IP do seu servidor
Depois torne o arquivo executavel
chmod +x /etc/zentyal/hooks/firewall.postservice
E por ultimo reinicie o serviço
/etc/init.d/zentyal firewall restart
Confira as regras do firewall com o seguinte comando:
iptables -t nat -L -n -v
Deverá obter o seguinte resultado
Se você estiver usando Politicas de Objetos para permitir que algums IPs não sejam filtrados você precisará criar regras pra cada um dos IPs não filtrados no arquivo firewall.postservice...
Essa regra se aplica caso você use o filtro de conteúdo, caso não esteja usando a porta usada será a 3128...
Deixe o arquivo /etc/zentyal/hooks/firewall.postservice deste jeito:
Code: [Select]
#!/bin/sh
# This is the firewall postservice script and it's run after Zentyal
# has finished setting up the firewall.
# You can add here custom rules that you might need for your firewall
# The script will receive a command line argument indicating whether the
# module is enabled (1) or not (0).
if [ "$1" -eq "1" ]
then
#add custom rules here
sudo iptables -t nat -I premodules -i eth1 ! -d 200.201.0.0/16 -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 3129
sudo iptables -t nat -D premodules -i eth1 ! -d 192.168.1.1 -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 3129
true
fi
exit 0
Substitua eth1 pela sua interface interna e 192.168.1.1 pelo IP do seu servidor
Depois torne o arquivo executavel
chmod +x /etc/zentyal/hooks/firewall.postservice
E por ultimo reinicie o serviço
/etc/init.d/zentyal firewall restart
Confira as regras do firewall com o seguinte comando:
iptables -t nat -L -n -v
Deverá obter o seguinte resultado
Quote
Chain premodules (1 references)
pkts bytes target prot opt in out source destination
161 8368 REDIRECT tcp -- eth1 * 0.0.0.0/0 !200.201.0.0/16 tcp dpt:80 redir ports 3129
Se você estiver usando Politicas de Objetos para permitir que algums IPs não sejam filtrados você precisará criar regras pra cada um dos IPs não filtrados no arquivo firewall.postservice...
Pages: [1]