On Monday 02 December 2019 07:46:22 Alessandro Vesely wrote:
> On Mon 02/Dec/2019 10:35:26 +0100 Andrei POPESCU wrote:
> > You might want to install iptables-persistent, otherwise you'll have
> > to roll-out your own solution.
>
> I'm not using iptables-persistent, but just looked at it out of
>
On Mon, Dec 02, 2019 at 01:46:22PM +0100, Alessandro Vesely wrote:
> ### BEGIN INIT INFO
> # Provides: netfilter-persistent
> # Required-Start:mountkernfs $remote_fs
> # Required-Stop: $remote_fs
> # Default-Start: S
> # Default-Stop: 0 1 6
> # Short-Description: Load
On Mon, Dec 02, 2019 at 01:46:22PM +0100, Alessandro Vesely wrote:
> On Mon 02/Dec/2019 10:35:26 +0100 Andrei POPESCU wrote:
> >
> > You might want to install iptables-persistent, otherwise you'll have to
> > roll-out your own solution.
>
> I'm not using iptables-persistent, but just looked at
On Mon 02/Dec/2019 10:35:26 +0100 Andrei POPESCU wrote:
>
> You might want to install iptables-persistent, otherwise you'll have to
> roll-out your own solution.
I'm not using iptables-persistent, but just looked at it out of curiosity.
Its LSB:
### BEGIN INIT INFO
# Provides:
apt install iptables-persistent
Em 14/05/2019, Vitor Hugo escreveu:
> A fim de segurar que somente a maquina de desenvolvimento ira acessar o
> servidor Postgres eu criei um script sh com as seguintes regras
> iptables, como eu faço para que estas regras sejam ativadas a cada
> inicialização do
Boa tarde!
Eu geralmente coloco elas no /etc/rc.local
At.te
Em 14/05/2019 12:36, Vitor Hugo escreveu:
> A fim de segurar que somente a maquina de desenvolvimento ira acessar o
> servidor Postgres eu criei um script sh com as seguintes regras
> iptables, como eu faço para que estas regras
A fim de segurar que somente a maquina de desenvolvimento ira acessar o
servidor Postgres eu criei um script sh com as seguintes regras
iptables, como eu faço para que estas regras sejam ativadas a cada
inicialização do sistema Debian?
IP servidor PostgreSQL: 192.168.0.27
IP Cliente PGAdmin:
On 2/14/18 4:51 PM, Rodary Jacques wrote:
I was just going to give up , and I even installed shorewall, when my last
attempt with my very old iptables config (from redhat 7.2) did work. I of
course to still get rid of stupid systemd config, but I don't really care since
my server is allways
I was just going to give up , and I even installed shorewall, when my last
attempt with my very old iptables config (from redhat 7.2) did work. I of
course to still get rid of stupid systemd config, but I don't really care since
my server is allways up!. Thank you anyway for your hints.
Jacques
Thank you.As soon as I can I will try it
On 1/31/18 12:28 PM, Jacques Rodary wrote:
Hi
Many things happened since my first message: I first had to get rid of connman
(connection manager), which insisted to preset iptables rules without any
notice. My Debian box is uset as a DNS chrooted server (also I had to modify
bind9.service
Hi
Many things happened since my first message: I first had
to get rid of connman (connection manager), which insisted to preset
iptables rules without any notice. My Debian box is uset as a DNS
chrooted server (also I had to modify bind9.service behaviour), and I
use
On Sun 21/Jan/2018 20:53:43 +0100 Ben Caradoc-Davies wrote:
> On 21/01/18 16:05, Mark Fletcher wrote:
>> To get you started [addressing the OP], here is the service file I use:
>
> Mine is slightly different and has the commands inline:
>
>
> $ cat /etc/iptables/iptables.service
> [Unit]
>
On 2018-01-21 1:02, Dejan Jocic wrote:
> On 20-01-18, Jacques Rodary wrote:
>> Hi
>> How can I start iptables at boot. I don't find an equivalent to " service
>> iptables start" with systemd and does'nt know how to create a new
>> iptables.service. The manpa
On 21/01/18 16:05, Mark Fletcher wrote:
To get you started [addressing the OP], here is the service file I use:
Mine is slightly different and has the commands inline:
$ cat /etc/iptables/iptables.service
[Unit]
Description=iptables rules
After=network.target
[Service]
Type=oneshot
On 21-01-18, Mark Fletcher wrote:
> On Sun, Jan 21, 2018 at 02:02:07AM +0100, Dejan Jocic wrote:
> > On 20-01-18, Jacques Rodary wrote:
> > > Hi
> > > How can I start iptables at boot. I don't find an equivalent to "
> > > service
> > >
On Sun, Jan 21, 2018 at 02:02:07AM +0100, Dejan Jocic wrote:
> On 20-01-18, Jacques Rodary wrote:
> > Hi
> > How can I start iptables at boot. I don't find an equivalent to " service
> > iptables start" with systemd and does'nt know how to create a new
> >
On 20-01-18, Jacques Rodary wrote:
> Hi
> How can I start iptables at boot. I don't find an equivalent to " service
> iptables start" with systemd and does'nt know how to create a new
> iptables.service. The manpages aren't quite clear for me. Thanks for any
> help.
>
Hi
How can I start iptables at boot. I don't find an equivalent to "
service iptables start" with systemd and does'nt know how to create a
new iptables.service. The manpages aren't quite clear for me. Thanks for
any help.
Jacques
Galera,
Antes usando o Etch usava o script abaixo para carregar minhas regras
no Iptables diretamente no boot, agora no Lenny ao utilizar este script
as regras so carregadas mas a navegao no possvel.
J descomentei a linha referente ao forward de ipv4 no arquivo
/etc/sysctl.conf, mas a cada
João para podermos ajuda-lo será necessário ver o conteúdo do arquivo
/etc/firewall/fire1 e neste arquivo que estão as regras propriamente
ditas.
2009/7/7 João Henrique Viana j...@engepel.com.br
Galera,
Antes usando o Etch usava o script abaixo para carregar minhas regras no
Iptables
Galera,
Antes usando o Etch usava o script abaixo para carregar minhas regras no
Iptables diretamente no boot, agora no Lenny ao utilizar este script as
regras são carregadas mas a navegação não é possível. Já descomentei a
linha referente ao forward de ipv4 no arquivo /etc/sysctl.conf
Hello,
I'm trying to implement some iptables rules for my
system. Unfortunately, (on etch) it appears that the boot sequence
doesn't allow for nfs mounts to be located (as nfs+portmap appear to
get started _before_ I've established an internet connection with my
network interface which relies
On Fri, Jul 28, 2006 at 03:08:33AM +1000, Joseph Le-Phan wrote:
Hello,
I'm trying to implement some iptables rules for my
system. Unfortunately, (on etch) it appears that the boot sequence
doesn't allow for nfs mounts to be located (as nfs+portmap appear to
get started _before_ I've
Try to use the old way. In /etc directory you'll find
subdirectories rcx.d where x is number between 0 to 6.
These directories (rcx.d) contain symlinks to related
startup scripts in /etc/init.d. If you use window
manager, please pay attention to rc5.d. In rc5.d,
you'll see something like S22sshd
On Sun, 02 Apr 2006 03:30:15 +0200, BTP [EMAIL PROTECTED] wrote:
I was wondering if someone would be able to give me the correct way of
disabling all network activity (iptables commands/script) during the
boot process so that my network is inoperable during bootup until I
activate it
From: Matthijs [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Subject: Re: iptables at boot
Date: Sun, 02 Apr 2006 11:28:16 +0200
On Sun, 02 Apr 2006 03:30:15 +0200, BTP [EMAIL PROTECTED] wrote:
I was wondering if someone would be able to give me the correct way of
disabling all network
Hi,
I was wondering if someone would be able to give me the correct way of
disabling all network activity (iptables commands/script) during the
boot process so that my network is inoperable during bootup until I
activate it manually.
I'm unsure in which startup script I would place this on
BTP wrote:
Hi,
I was wondering if someone would be able to give me the correct way of
disabling all network activity (iptables commands/script) during the
boot process so that my network is inoperable during bootup until I
activate it manually.
I'm unsure in which startup script I would place
Bonjour à tous,
J'utilise un petit script pour initialiser un firewall à l'aide de regle
iptables,
cela fonctionne parfaitement et je voudrais maintenant que ces règles soient
appliquer dès le démarrage de mon pc.
Pour cela j'ai essayé d'utiliser iptables save_active avec la méthode
proposée
Le mardi 29 avril 2003, KorHeve a écrit...
bonjour,
Pour cela j'ai essayé d'utiliser iptables save_active avec la méthode
proposée ici : http://www.debian-fr.org/article/articleview/15/1/11
mais rien à faire au boot lorsque je fait un iptables -L, je me retrouve
avec des règles qui
Le Tue, 29 Apr 2003 12:56:15 +0200
KorHeve [EMAIL PROTECTED] a écrit:
Bonjour à tous,
Bonjour,
J'utilise un petit script pour initialiser un firewall à l'aide de
regle iptables, cela fonctionne parfaitement et je voudrais maintenant
que ces règles soient appliquer dès le démarrage de
Le Tue, 29 Apr 2003 12:56:15 +0200
KorHeve [EMAIL PROTECTED] a écrit :
Bonjour à tous,
Bonjour,
J'utilise un petit script pour initialiser un firewall à l'aide de
regle iptables, cela fonctionne parfaitement et je voudrais maintenant
que ces règles soient appliquer dès le démarrage
On Tue, Apr 29, 2003 at 12:56:15PM +0200, KorHeve wrote :
Bonjour à tous,
Bonjour,
J'utilise un petit script pour initialiser un firewall à l'aide de regle
iptables,
cela fonctionne parfaitement et je voudrais maintenant que ces règles soient
appliquer dès le démarrage de mon pc.
Pour
bonsoir,
sur une debian woody / unstable je ne vois pas ou ajouter la ligne iptables
pour activer le nat au démarrage :
iptables --verbose -A POSTROUTING -t nat -o ppp0 -j MASQUERADE
de manière plus générale, existe t-il un équivalent de rc.local existant sur
les distribs RedHat et dérivées ?
tres simple :
tape ta commande iptable une fois
ensuite sauve la en faisant /etc/init.d/iptables save active
et hop le tour est joue
JM
Quoting Robin [EMAIL PROTECTED]:
bonsoir,
sur une debian woody / unstable je ne vois pas ou ajouter la ligne iptables
pour activer le nat au démarrage
On Wed, Jun 12, 2002 at 10:14:34PM +0200, Robin wrote:
bonsoir,
Bonsoir,
sur une debian woody / unstable je ne vois pas ou ajouter la ligne iptables
pour activer le nat au démarrage :
iptables --verbose -A POSTROUTING -t nat -o ppp0 -j MASQUERADE
Si c'est pour faire du masquerading il
ça marche :)
merci !
Je regarderai de plus près les scripts à l'avenir :)
Le Mercredi 12 Juin 2002 22:18, tu as tapoté :
tres simple :
tape ta commande iptable une fois
ensuite sauve la en faisant /etc/init.d/iptables save active
et hop le tour est joue
JM
Quoting Robin [EMAIL
a == arthur [EMAIL PROTECTED] writes:
[...]
Si c'est pour faire du masquerading il y a un paquet qui l'active au
démarrage. Je crois qu'il s'appelle ipmasq, apt-cache search ipmasq
devrait pouvoir te renseigner.
Mais non, iptables a déjà son script dans /etc/init.d/
Christian
--
To
Si c'est pour faire du masquerading il y a un paquet qui l'active au
démarrage. Je crois qu'il s'appelle ipmasq, apt-cache search ipmasq
devrait pouvoir te renseigner.
Mais non, iptables a déjà son script dans /etc/init.d/
l'un n' empeche pas l'autre
un extrait de /etc/defaults/iptables
40 matches
Mail list logo
