Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #70357 > unrolled thread
| Started by | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| First post | 2025-08-05 08:14 +0000 |
| Last post | 2025-08-23 05:43 +0000 |
| Articles | 20 on this page of 113 — 24 participants |
Back to article view | Back to comp.os.linux.misc
Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-05 08:14 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Marc Haber <mh+usenetspam1118@zugschl.us> - 2025-08-05 11:22 +0200
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Marco Moock <mm@dorfdsl.de> - 2025-08-05 11:34 +0200
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-08-05 11:30 -0400
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use The Natural Philosopher <tnp@invalid.invalid> - 2025-08-05 19:56 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-06 01:06 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use John McCue <jmclnx@gmail.com.invalid> - 2025-08-06 01:32 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-06 04:20 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use c186282 <c186282@nnada.net> - 2025-08-06 01:33 -0400
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-08-06 09:31 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-06 08:56 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Nuno Silva <nunojsilva@invalid.invalid> - 2025-08-06 10:35 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-08-06 11:38 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-07 00:06 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-08-11 11:50 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-11 22:02 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-08-12 08:39 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Marc Haber <mh+usenetspam1118@zugschl.us> - 2025-08-12 10:49 +0200
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use The Natural Philosopher <tnp@invalid.invalid> - 2025-08-12 10:54 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-08-12 18:47 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-12 23:36 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use "Carlos E. R." <robin_listas@es.invalid> - 2025-08-12 12:08 +0200
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use rbowman <bowman@montana.com> - 2025-08-12 19:35 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-12 23:07 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-08-13 09:47 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-14 00:41 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use "Carlos E.R." <robin_listas@es.invalid> - 2025-08-19 12:35 +0200
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-08-19 12:18 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Marc Haber <mh+usenetspam1118@zugschl.us> - 2025-08-19 15:16 +0200
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-20 01:02 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-08-27 06:56 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-28 00:50 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-08-28 09:40 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-29 00:56 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use John Ames <commodorejohn@gmail.com> - 2025-08-29 08:10 -0700
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-08-29 19:16 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2025-08-30 16:59 +0300
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-08-30 18:45 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2025-08-31 21:24 +0300
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-09-01 17:02 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-31 03:25 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-30 06:34 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Nuno Silva <nunojsilva@invalid.invalid> - 2025-08-30 08:39 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use The Natural Philosopher <tnp@invalid.invalid> - 2025-08-30 08:45 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Harold Stevens <wookie@trixie.localdomain> - 2025-08-30 05:37 -0500
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use John Ames <commodorejohn@gmail.com> - 2025-09-02 09:59 -0700
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Harold Stevens <wookie@aspen.localdomain> - 2025-09-02 12:59 -0500
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Richard Kettlewell <invalid@invalid.invalid> - 2025-08-30 17:48 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-20 01:01 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use "Carlos E.R." <robin_listas@es.invalid> - 2025-08-20 12:52 +0200
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-20 22:36 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use "Carlos E.R." <robin_listas@es.invalid> - 2025-08-21 11:44 +0200
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use The Natural Philosopher <tnp@invalid.invalid> - 2025-08-21 11:34 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use "Carlos E.R." <robin_listas@es.invalid> - 2025-08-21 14:36 +0200
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Nuno Silva <nunojsilva@invalid.invalid> - 2025-08-21 14:27 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use "Carlos E.R." <robin_listas@es.invalid> - 2025-08-21 21:37 +0200
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Nuno Silva <nunojsilva@invalid.invalid> - 2025-08-22 10:33 +0100
Manuals [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] "Carlos E.R." <robin_listas@es.invalid> - 2025-08-22 12:39 +0200
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-22 01:12 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-22 01:06 +0000
Documentation [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] "Carlos E.R." <robin_listas@es.invalid> - 2025-08-22 12:26 +0200
Re: Documentation [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-23 23:13 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use John Ames <commodorejohn@gmail.com> - 2025-08-20 07:47 -0700
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-20 22:37 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-08-20 19:25 +0000
tldr [WAS: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] "Carlos E.R." <robin_listas@es.invalid> - 2025-08-21 12:04 +0200
Re: tldr [WAS: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-08-23 12:40 +0000
Re: tldr [WAS: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] "Carlos E.R." <robin_listas@es.invalid> - 2025-08-24 00:40 +0200
Re: tldr [WAS: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-23 23:15 +0000
Re: tldr [WAS: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-08-24 11:22 +0000
Re: tldr [WAS: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-24 22:18 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Anssi Saari <anssi.saari@usenet.mail.kapsi.fi> - 2025-08-21 12:40 +0300
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Richard Kettlewell <invalid@invalid.invalid> - 2025-08-06 14:21 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use The Natural Philosopher <tnp@invalid.invalid> - 2025-08-06 16:24 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use The Natural Philosopher <tnp@invalid.invalid> - 2025-08-06 10:12 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Anssi Saari <anssi.saari@usenet.mail.kapsi.fi> - 2025-08-07 11:43 +0300
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use John McCue <jmclnx@gmail.com.invalid> - 2025-08-06 11:55 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Marc Haber <mh+usenetspam1118@zugschl.us> - 2025-08-06 07:40 +0200
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-06 06:31 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Marc Haber <mh+usenetspam1118@zugschl.us> - 2025-08-06 11:06 +0200
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Richard Kettlewell <invalid@invalid.invalid> - 2025-08-06 14:25 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Marc Haber <mh+usenetspam1118@zugschl.us> - 2025-08-06 17:11 +0200
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-06 23:59 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Marc Haber <mh+usenetspam1118@zugschl.us> - 2025-08-07 08:37 +0200
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-07 06:52 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Rich <rich@example.invalid> - 2025-08-18 16:49 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use "Carlos E.R." <robin_listas@es.invalid> - 2025-08-06 12:46 +0200
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-08-06 23:56 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use "Carlos E.R." <robin_listas@es.invalid> - 2025-08-19 12:41 +0200
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-20 01:07 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Nuno Silva <nunojsilva@invalid.invalid> - 2025-08-20 09:48 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use The Natural Philosopher <tnp@invalid.invalid> - 2025-08-20 11:13 +0100
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-20 22:40 +0000
Re: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use vallor <vallor@cultnix.org> - 2025-08-21 00:27 +0000
ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] "Carlos E.R." <robin_listas@es.invalid> - 2025-08-20 13:04 +0200
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] The Natural Philosopher <tnp@invalid.invalid> - 2025-08-20 12:30 +0100
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-20 22:44 +0000
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] "Carlos E.R." <robin_listas@es.invalid> - 2025-08-21 12:15 +0200
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-22 01:18 +0000
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] "Carlos E.R." <robin_listas@es.invalid> - 2025-08-22 12:45 +0200
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] The Natural Philosopher <tnp@invalid.invalid> - 2025-08-22 19:37 +0100
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] "Carlos E.R." <robin_listas@es.invalid> - 2025-08-22 22:32 +0200
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] The Natural Philosopher <tnp@invalid.invalid> - 2025-08-22 21:56 +0100
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-23 00:28 +0000
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] rbowman <bowman@montana.com> - 2025-08-23 05:51 +0000
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] The Natural Philosopher <tnp@invalid.invalid> - 2025-08-23 11:23 +0100
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-23 23:12 +0000
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-08-29 19:40 +0000
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] rbowman <bowman@montana.com> - 2025-08-30 05:59 +0000
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-30 06:36 +0000
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] Marc Haber <mh+usenetspam1118@zugschl.us> - 2025-08-30 10:36 +0200
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-08-31 01:25 +0000
Re: ISP router [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] rbowman <bowman@montana.com> - 2025-08-23 05:43 +0000
Page 4 of 6 — ← Prev page 1 2 3 [4] 5 6 Next page →
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-08-22 12:26 +0200 |
| Subject | Documentation [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] |
| Message-ID | <28tlnlx7n5.ln2@Telcontar.valinor> |
| In reply to | #71890 |
On 2025-08-22 03:06, Lawrence D’Oliveiro wrote: > On Thu, 21 Aug 2025 11:44:47 +0200, Carlos E.R. wrote: > >> I do not want reference documentation. > > Then you can’t work in this field. Haw, haw! :-D -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-08-23 23:13 +0000 |
| Subject | Re: Documentation [Was: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] |
| Message-ID | <108dhuu$2f5h3$5@dont-email.me> |
| In reply to | #71910 |
On Fri, 22 Aug 2025 12:26:42 +0200, Carlos E.R. wrote: > On 2025-08-22 03:06, Lawrence D’Oliveiro wrote: >> >> On Thu, 21 Aug 2025 11:44:47 +0200, Carlos E.R. wrote: >> >>> I do not want reference documentation. >> >> Then you can’t work in this field. > > Haw, haw! :-D Says one who didn’t even know the relevant information existed until I pointed it out.
[toc] | [prev] | [next] | [standalone]
| From | John Ames <commodorejohn@gmail.com> |
|---|---|
| Date | 2025-08-20 07:47 -0700 |
| Message-ID | <20250820074700.00002ac1@gmail.com> |
| In reply to | #71697 |
On Wed, 20 Aug 2025 01:01:32 -0000 (UTC) Lawrence D’Oliveiro <ldo@nz.invalid> wrote: > >> What's wrong with a couple of clear examples, plus the detail to > >> expand on them? > >> > > +1 > > There’s a whole website devoted to that, as I mentioned elsewhere. That's a fine thing to have in *addition* to proper man pages, but when you're in a scenario where you don't necessarily have Internet access, it does you little good - and that makes it especially absurd for core networking tools to take this approach to documentation. (It's also a bundle of fun when link rot sets in; wish I could remember the specifics, but I have at least once been trying to figure out some freenix package whose man page was literally nothing but a "for actual documentation, see the project webpage," which had undergone reverse metamorphosis into a blank Github stub. Can't recall if archive.org even had the old version or not...)
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-08-20 22:37 +0000 |
| Message-ID | <1085inp$j3am$12@dont-email.me> |
| In reply to | #71761 |
On Wed, 20 Aug 2025 07:47:00 -0700, John Ames wrote: > On Wed, 20 Aug 2025 01:01:32 -0000 (UTC) > Lawrence D’Oliveiro <ldo@nz.invalid> wrote: > >>>> What's wrong with a couple of clear examples, plus the detail to >>>> expand on them? >>>> >>> +1 >> >> There’s a whole website devoted to that, as I mentioned elsewhere. > > That's a fine thing to have in *addition* to proper man pages ... Which nftables already has, as I have also pointed out.
[toc] | [prev] | [next] | [standalone]
| From | Stéphane CARPENTIER <sc@fiat-linux.fr> |
|---|---|
| Date | 2025-08-20 19:25 +0000 |
| Message-ID | <68a62128$0$28050$426a74cc@news.free.fr> |
| In reply to | #71642 |
Le 19-08-2025, Carlos E.R. <robin_listas@es.invalid> a écrit : > On 2025-08-12 09:39, Mike Scott wrote: >> On 11/08/2025 23:02, Lawrence D'Oliveiro wrote: >>> I don’t know. I’m just able to read documentation. I thought that was a >>> skill that was so commonplace among folks who work with computers for a >>> living that you could take it for granted, but apparently not. >> >> The horror is manuals written by the code-writer. They describe in >> intimate detail each and every function; but not how it all hooks up. In >> this case, I'd not even seen the nft man page, because I'd been >> searching for the wrong terms, hadn't got there because I'd got drowned >> in a morass of ipfilter and similar stuff, now apparently out-of-date; >> and gave it up as a bad job. >> >> What's wrong with a couple of clear examples, plus the detail to expand >> on them? >> > > +1 Just "man tldr". In fact no. Install tldr with your distro package manager. Then "tldr tldr". Enjoy. -- Si vous avez du temps à perdre : https://scarpet42.gitlab.io
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-08-21 12:04 +0200 |
| Subject | tldr [WAS: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] |
| Message-ID | <vh7jnlx5be.ln2@Telcontar.valinor> |
| In reply to | #71779 |
On 2025-08-20 21:25, Stéphane CARPENTIER wrote: > Le 19-08-2025, Carlos E.R. <robin_listas@es.invalid> a écrit : >> On 2025-08-12 09:39, Mike Scott wrote: >>> On 11/08/2025 23:02, Lawrence D'Oliveiro wrote: >>>> I don’t know. I’m just able to read documentation. I thought that was a >>>> skill that was so commonplace among folks who work with computers for a >>>> living that you could take it for granted, but apparently not. >>> >>> The horror is manuals written by the code-writer. They describe in >>> intimate detail each and every function; but not how it all hooks up. In >>> this case, I'd not even seen the nft man page, because I'd been >>> searching for the wrong terms, hadn't got there because I'd got drowned >>> in a morass of ipfilter and similar stuff, now apparently out-of-date; >>> and gave it up as a bad job. >>> >>> What's wrong with a couple of clear examples, plus the detail to expand >>> on them? >>> >> >> +1 > > Just "man tldr". In fact no. Install tldr with your distro package > manager. Then "tldr tldr". > > Enjoy. I was curious, so I installed it. cer@Telcontar:~> man tldr No manual entry for tldr cer@Telcontar:~> cer@Telcontar:~> tldr tldr Error: Page cache not found. Please run `tldr --update` to download the cache. Note: You can optionally enable automatic cache updates by adding the following config to your config file: [updates] auto_update = true The path to your config file can be looked up with `tldr --show-paths`. To create an initial config file, use `tldr --seed-config`. You can find more tips and tricks in our docs: https://dbrgn.github.io/tealdeer/config_updates.html cer@Telcontar:~> It said that yesterday for root, I run "update", and now it says the same for my user. So each user has its own cache? What config file, where is it? cer@Telcontar:~> l .tldr ls: cannot access '.tldr': No such file or directory cer@Telcontar:~> cer@Telcontar:~> ls /etc/tldr ls: cannot access '/etc/tldr': No such file or directory cer@Telcontar:~> cer@Telcontar:~> rpm -ql tealdeer /usr/bin/tldr /usr/share/doc/packages/tealdeer /usr/share/doc/packages/tealdeer/README.md /usr/share/licenses/tealdeer /usr/share/licenses/tealdeer/LICENSE-APACHE /usr/share/licenses/tealdeer/LICENSE-MIT cer@Telcontar:~> Where is that configuration file? «The path to your config file can be looked up with `tldr --show-paths`.» cer@Telcontar:~> tldr --show-paths Config dir: /home/cer/.config/tealdeer/ (OS convention) Config path: /home/cer/.config/tealdeer/config.toml Cache dir: /home/cer/.cache/tealdeer (OS convention) Pages dir: /home/cer/.cache/tealdeer/tldr-pages/ Custom pages dir: /home/cer/.local/share/tealdeer/pages/ (OS convention) cer@Telcontar:~> So each user has its own cache? Is not that a waste? «To create an initial config file, use `tldr --seed-config`.» cer@Telcontar:~> tldr --seed-config Successfully created seed config file here: /home/cer/.config/tealdeer/config.toml cer@Telcontar:~> So now I have: [updates] auto_update = true auto_update_interval_hours = 720 Now "tldr tldr" works. Directory "/home/cer/.cache/tealdeer" contains 17 MB. And another one for root. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Stéphane CARPENTIER <sc@fiat-linux.fr> |
|---|---|
| Date | 2025-08-23 12:40 +0000 |
| Subject | Re: tldr [WAS: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] |
| Message-ID | <68a9b6ad$0$3388$426a74cc@news.free.fr> |
| In reply to | #71837 |
Le 21-08-2025, Carlos E.R. <robin_listas@es.invalid> a écrit : > On 2025-08-20 21:25, Stéphane CARPENTIER wrote: >> >> Just "man tldr". In fact no. Install tldr with your distro package >> manager. Then "tldr tldr". >> >> Enjoy. > > I was curious, so I installed it. > > cer@Telcontar:~> man tldr > No manual entry for tldr > cer@Telcontar:~> > > cer@Telcontar:~> tldr tldr > Error: Page cache not found. Please run `tldr --update` to download the > cache. > I'm really surprised. I installed it on archlinux, ubuntu and guix and it worked out of the box on those three systems. > Note: You can optionally enable automatic cache updates by adding the > following config to your config file: I ran "tldr --update" and I see no difference. I have no config file on my computer. I'm really surprised about that requirement. > Where is that configuration file? I have no clue. I have none and everything's OK. > «The path to your config file can be looked up with `tldr --show-paths`.» That option doesn't exist on my computer. > So each user has its own cache? Is not that a waste? Agreed. It's a waste of space and a waste of work because you need to launch the update for each user. > Directory "/home/cer/.cache/tealdeer" contains 17 MB. It looks like you are running tealdeer instead of tldr. When I'm running tldr. From what I see, tealdeer is a rewrite of tldr in rust. Maybe that explain the differences. But anyway, once it works, it grants you what you are looking for: simple examples to use unknown commands without the need to read the full documentation. -- Si vous avez du temps à perdre : https://scarpet42.gitlab.io
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-08-24 00:40 +0200 |
| Subject | Re: tldr [WAS: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] |
| Message-ID | <8kspnlx355.ln2@Telcontar.valinor> |
| In reply to | #72039 |
On 2025-08-23 14:40, Stéphane CARPENTIER wrote: > Le 21-08-2025, Carlos E.R. <robin_listas@es.invalid> a écrit : >> On 2025-08-20 21:25, Stéphane CARPENTIER wrote: >>> >>> Just "man tldr". In fact no. Install tldr with your distro package >>> manager. Then "tldr tldr". >>> >>> Enjoy. >> >> I was curious, so I installed it. >> >> cer@Telcontar:~> man tldr >> No manual entry for tldr >> cer@Telcontar:~> >> >> cer@Telcontar:~> tldr tldr >> Error: Page cache not found. Please run `tldr --update` to download the >> cache. >> > > I'm really surprised. I installed it on archlinux, ubuntu and guix and > it worked out of the box on those three systems. > >> Note: You can optionally enable automatic cache updates by adding the >> following config to your config file: > > I ran "tldr --update" and I see no difference. I have no config file on > my computer. I'm really surprised about that requirement. > >> Where is that configuration file? > > I have no clue. I have none and everything's OK. > >> «The path to your config file can be looked up with `tldr --show-paths`.» > > That option doesn't exist on my computer. > >> So each user has its own cache? Is not that a waste? > > Agreed. It's a waste of space and a waste of work because you need to > launch the update for each user. > >> Directory "/home/cer/.cache/tealdeer" contains 17 MB. > > It looks like you are running tealdeer instead of tldr. When I'm running > tldr. From what I see, tealdeer is a rewrite of tldr in rust. Maybe that > explain the differences. Likely. > > But anyway, once it works, it grants you what you are looking for: > simple examples to use unknown commands without the need to read the full > documentation. Yes, that it does. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-08-23 23:15 +0000 |
| Subject | Re: tldr [WAS: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] |
| Message-ID | <108di1k$2f5h3$6@dont-email.me> |
| In reply to | #72039 |
On 23 Aug 2025 12:40:13 GMT, Stéphane CARPENTIER wrote: > But anyway, once it works, it grants you what you are looking for: > simple examples to use unknown commands without the need to read the > full documentation. If only there were a simple example for how to get this command set up without the need to read the full documentation ...
[toc] | [prev] | [next] | [standalone]
| From | Stéphane CARPENTIER <sc@fiat-linux.fr> |
|---|---|
| Date | 2025-08-24 11:22 +0000 |
| Subject | Re: tldr [WAS: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] |
| Message-ID | <68aaf613$0$414$426a74cc@news.free.fr> |
| In reply to | #72093 |
Le 23-08-2025, Lawrence D’Oliveiro <ldo@nz.invalid> a écrit : > On 23 Aug 2025 12:40:13 GMT, Stéphane CARPENTIER wrote: > >> But anyway, once it works, it grants you what you are looking for: >> simple examples to use unknown commands without the need to read the >> full documentation. > > If only there were a simple example for how to get this command set up > without the need to read the full documentation ... For archlinux, guix and Ubuntu, tldr run without further steps. I don't know why it was different for him. Maybe is distro is configured differently. Or, probably, tealdeer, unlike tldr, is not configured by default. -- Si vous avez du temps à perdre : https://scarpet42.gitlab.io
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-08-24 22:18 +0000 |
| Subject | Re: tldr [WAS: Yes, You Need A Firewall On Linux - Here’s Why And Which To Use] |
| Message-ID | <108g332$32gqg$13@dont-email.me> |
| In reply to | #72148 |
On 24 Aug 2025 11:22:59 GMT, Stéphane CARPENTIER wrote: > Le 23-08-2025, Lawrence D’Oliveiro <ldo@nz.invalid> a écrit : >> >> On 23 Aug 2025 12:40:13 GMT, Stéphane CARPENTIER wrote: >> >>> But anyway, once it works, it grants you what you are looking for: >>> simple examples to use unknown commands without the need to read the >>> full documentation. >> >> If only there were a simple example for how to get this command set up >> without the need to read the full documentation ... > > [Missed the irony]
[toc] | [prev] | [next] | [standalone]
| From | Anssi Saari <anssi.saari@usenet.mail.kapsi.fi> |
|---|---|
| Date | 2025-08-21 12:40 +0300 |
| Message-ID | <sm0ms7tf1wz.fsf@lakka.kapsi.fi> |
| In reply to | #70838 |
Mike Scott <usenet.16@scottsonline.org.uk.invalid> writes: > What's wrong with a couple of clear examples, plus the detail to > expand on them? Nothing wrong with that. I think the nftables devs agree since they provide examples in their wiki, such as "Simple ruleset for a workstation", "Simple ruleset for a server", "Simple ruleset for a home router".
[toc] | [prev] | [next] | [standalone]
| From | Richard Kettlewell <invalid@invalid.invalid> |
|---|---|
| Date | 2025-08-06 14:21 +0100 |
| Message-ID | <wwvpld88u1k.fsf@LkoBDZeT.terraraq.uk> |
| In reply to | #70457 |
Nuno Silva <nunojsilva@invalid.invalid> writes: > On 2025-08-06, Lawrence D'Oliveiro wrote: >> On Wed, 6 Aug 2025 09:31:16 +0100, Mike Scott wrote: >>> I'm far more used to pf on a freebsd server at home. It's >>> (reasonably) clear to configure, and flexible to use. I had plans to >>> switch to linux - but abandoned them purely because of the linux >>> firewall's (to me) opacity and lack of particular needed features. >> >> It’s nftables on Linux now. I wonder what features you needed, that >> presumably you were able to get on BSD, given that the Linux network >> stack is generally considered the most advanced these days. > > Is it really nftables instead of iptables now or is this one of your > "Wayland has replaced Xorg" and "systemd has replaced all other init > systems" moments? nftables is the current implementation, iptables is now just a translation layer from the historical iptables interface. You can use whichever interface you prefer. -- https://www.greenend.org.uk/rjk/
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-08-06 16:24 +0100 |
| Message-ID | <106vs3i$3evgn$3@dont-email.me> |
| In reply to | #70479 |
On 06/08/2025 14:21, Richard Kettlewell wrote: > nftables is the current implementation, iptables is now just a > translation layer from the historical iptables interface. You can use > whichever interface you prefer. Thank you. -- "And if the blind lead the blind, both shall fall into the ditch". Gospel of St. Mathew 15:14
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-08-06 10:12 +0100 |
| Message-ID | <106v69j$39a16$4@dont-email.me> |
| In reply to | #70447 |
On 06/08/2025 09:31, Mike Scott wrote:
> On 06/08/2025 06:33, c186282 wrote:
>> I'm gonna argue that, while powerful, IPTABLES is
>> just WAY too obscure, too weird.
>
> I have to agree there. I'm far more used to pf on a freebsd server at
> home. It's (reasonably) clear to configure, and flexible to use. I had
> plans to switch to linux - but abandoned them purely because of the
> linux firewall's (to me) opacity and lack of particular needed features.
>
> The linux desktop boxes at home don't have a firewall configured, but
> they're protected from inbound stuff by the NAT router.
>
Iptables describes the low level actions of the firewall. It is, if you
like, written in Assembler :-)
But I don't find it that hard, and once its done, its done
--
“Ideas are inherently conservative. They yield not to the attack of
other ideas but to the massive onslaught of circumstance"
- John K Galbraith
[toc] | [prev] | [next] | [standalone]
| From | Anssi Saari <anssi.saari@usenet.mail.kapsi.fi> |
|---|---|
| Date | 2025-08-07 11:43 +0300 |
| Message-ID | <sm0a54biktj.fsf@lakka.kapsi.fi> |
| In reply to | #70425 |
c186282 <c186282@nnada.net> writes: > I'm gonna argue that, while powerful, IPTABLES is > just WAY too obscure, too weird. This is why there > are a number of GUI helpers ... iptables is also only a hollow shell over nftables since 2014 so over a decade now. I learned nftables a few years ago since I didn't want to bother with different tools for a firewall, like iptables and ip6tables, separately. Also not too keen on the frontend flavor of the week; is it ufw or firewalld or something else this week in this distro and what about that other distro? I have to say I quite like nftables. My router rules are based on their router example, other computers have a basic thing with usually just common things like ICMP(6) and ssh allowed in. Then, if a machine serves something more (like radius or nfs or mosh here), then I can put a few lines in an include dir and they get read in. Anyways, this is all very basic and traditionial. As I understand it, eBPF is what the big boys play with these days. Also it's apparently becoming an everything-VM in the Linux kernel with the sched_ext stuff for process scheduling for example and who knows what. eBPF I would classify as too hard for me and not generally needed for the home user.
[toc] | [prev] | [next] | [standalone]
| From | John McCue <jmclnx@gmail.com.invalid> |
|---|---|
| Date | 2025-08-06 11:55 +0000 |
| Message-ID | <106vfsa$3bj58$1@dont-email.me> |
| In reply to | #70420 |
Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
> On Wed, 6 Aug 2025 01:32:20 -0000 (UTC), John McCue wrote:
>
>> FWIW, this is a snippet of what I have to restrict pings,
===================^^^^^^^
<snip>
> Ummm ... where exactly do you drop the ping packets that
> don’t match those rules?
The script, it is rather large so I only included the
ping portion. There are many DROP statements throughout
the script.
People can use one of the many generators and add those
lines to what was generated :) Do you want the drop
statements ?
--
[t]csh(1) - "An elegant shell, for a more... civilized age."
- Paraphrasing Star Wars
[toc] | [prev] | [next] | [standalone]
| From | Marc Haber <mh+usenetspam1118@zugschl.us> |
|---|---|
| Date | 2025-08-06 07:40 +0200 |
| Message-ID | <106upsa$1bicl$1@news1.tnib.de> |
| In reply to | #70416 |
John McCue <jmclnx@gmail.com.invalid> wrote: >###########START------------------------- ># ICMP (ping) ># ICMP rules, allow the bare essential types of ICMP ># only. Ping request is blocked, ie we won't respond to ># someone else's pings, but can still ping out. First, you're not blocking anything with those rules, as Lawrence correctly noted. Second, blocking incoming echo requests makes debugging harder and doesn't give you increased security. You're just standing in the middle of town square, screaming "YOU DONT SEE ME YOU DONT SEE ME!!!". That is a rule set from the earliy 2000s, with the establishing method of the late 1990ies. Greetings Marc -- ---------------------------------------------------------------------------- Marc Haber | " Questions are the | Mailadresse im Header Rhein-Neckar, DE | Beginning of Wisdom " | Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 6224 1600402
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-08-06 06:31 +0000 |
| Message-ID | <106usrd$379q9$1@dont-email.me> |
| In reply to | #70427 |
On Wed, 06 Aug 2025 07:40:25 +0200, Marc Haber wrote: > Second, blocking incoming echo requests makes debugging harder and > doesn't give you increased security. When a certain server I had responsibility for was undergoing a security audit for PCI compliance many years ago, I was told, not to turn off ICMP replies, but to turn off timestamps on them. Apparently, knowing the server’s idea of the correct time was seen as a potential security vulnerability.
[toc] | [prev] | [next] | [standalone]
| From | Marc Haber <mh+usenetspam1118@zugschl.us> |
|---|---|
| Date | 2025-08-06 11:06 +0200 |
| Message-ID | <106v5ui$1cg69$1@news1.tnib.de> |
| In reply to | #70435 |
Lawrence D'Oliveiro <ldo@nz.invalid> wrote: >On Wed, 06 Aug 2025 07:40:25 +0200, Marc Haber wrote: > >> Second, blocking incoming echo requests makes debugging harder and >> doesn't give you increased security. > >When a certain server I had responsibility for was undergoing a security >audit for PCI compliance many years ago, I was told, not to turn off ICMP >replies, but to turn off timestamps on them. > >Apparently, knowing the server’s idea of the correct time was seen as a >potential security vulnerability. Those consultants are paid to find things. Hence, they find things. Or they make things up. The persons who hire them don't care as long as there is a report. Greetings Marc -- ---------------------------------------------------------------------------- Marc Haber | " Questions are the | Mailadresse im Header Rhein-Neckar, DE | Beginning of Wisdom " | Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 6224 1600402
[toc] | [prev] | [next] | [standalone]
Page 4 of 6 — ← Prev page 1 2 3 [4] 5 6 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web