On 1/7/20 4:54 PM, Christopher Schultz wrote:
I have further confused you, because TCP packets+connections also have
state, and I misspoke.
Think nothing of it: at my age, I'm easily confused.
--
JHHL
-
To unsubscribe,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 1/7/20 7:22 PM, James H. H. Lampert wrote:
> On 1/7/20 4:17 PM, Christopher Schultz wrote:
>> iptables doesn't work on pipes, it works on packets. So you have
>> to redirect both incoming AND outgoing packets. That's why you
>> have the
On 1/7/20 4:17 PM, Christopher Schultz wrote:
iptables doesn't work on pipes, it works on packets. So you have to
redirect both incoming AND outgoing packets. That's why you have the
"output redirect" as well as the (more obvious) "input redirect".
Well, that just leaves me more puzzled than
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 1/7/20 12:28 PM, James H. H. Lampert wrote:
> On 1/7/20 7:32 AM, Christopher Schultz wrote:
>> Hah, sorry about that. Nobody thought of specifying that only
>> root can view the iptables stuff. :)
>
> Not your fault, nor that of anybody
On 1/7/20 7:32 AM, Christopher Schultz wrote:
Hah, sorry about that. Nobody thought of specifying that only root can
view the iptables stuff. :)
Not your fault, nor that of anybody else here; I blame the author of
iptables and iptables-save: it should either (a) allow *anybody* to
*see* the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 1/6/20 4:28 PM, James H. H. Lampert wrote:
> I think I found something, with the help of "MLu" on ServerFault:
>
> He advised me to try "iptables -L" and "iptables-save" again, only
> this time "sudo" them.
Hah, sorry about that. Nobody
Heureka!
Actually, I was thinking more "Sokath, his eyes uncovered!"
And actually, at this point, I'm thinking I'm better off with Apache
httpd handling port 80, since it would only be used for Let's Encrypt,
and Let's Encrypt and certbot currently play much more nicely with it
than with
James,
>> Am 06.01.2020 um 22:28 schrieb James H. H. Lampert
>> :
>>
>> I think I found something, with the help of "MLu" on ServerFault:
>>
>> He advised me to try "iptables -L" and "iptables-save" again, only this time
>> "sudo" them.
>>
>> When I did "iptables -L" under root
I think I found something, with the help of "MLu" on ServerFault:
He advised me to try "iptables -L" and "iptables-save" again, only this
time "sudo" them.
When I did "iptables -L" under root privileges, I still only got column
headings, but when I did "iptables-save" under root privileges,