From: | ourdiaspora <ourdiaspora(at)protonmail(dot)com> |
---|---|
To: | |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: php connection failure |
Date: | 2021-08-11 10:27:55 |
Message-ID: | pZBblQaDjxM47y8isjbVf36xFRRwpDAMqfEX1xSFXaiLBDccTiktTxbNal_2V1I8U-k62d2jlnnt42ZNIBN5F_Xi0549Am6v71pEjHu-oWA=@protonmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, August 10th, 2021 at 2:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The postgres process is listening, but this has nothing to do with
>
> whether the kernel will allow any packets to arrive there.
>
Installed 'nftables'. According to the documentation (https://wiki.debian.org/nftables) there are no filter rules by default, so the assumption is that there is no filtration of packets by the software at the kernel stage.
The configuration file '/etc/nftables.conf':
#!/usr/sbin/nft -f
flush ruleset
table inet filter {
chain input {
type filter hook input priority 0;
}
chain forward {
type filter hook forward priority 0;
}
chain output {
type filter hook output priority 0;
}
}
Is it correct to interpret this configuration file that filtration is _not_ active?
From | Date | Subject | |
---|---|---|---|
Next Message | ourdiaspora | 2021-08-11 11:09:40 | Re: php connection failure |
Previous Message | Bryn Llewellyn | 2021-08-10 20:30:17 | Re: PL/pgSQL: Spurious 22P02 error on "select col into var" when col is user-defined type |