Re: subnet subset blocked

To: debian-user@lists.debian.org
Subject: Re: subnet subset blocked
From: Adam Weremczuk <adamw@matrixscience.com>
Date: Wed, 25 Sep 2024 14:38:31 +0100
Message-id: <[🔎] 5311e3a2-ad10-4aed-9984-2d95805cc56a@matrixscience.com>
In-reply-to: <[🔎] 77a5dc1e-11df-4ecc-a821-b0a3fb5f0a41@rail.eu.org>
References: <[🔎] 0a1c1171-dac0-407d-a8dc-344e28861f5f@matrixscience.com> <[🔎] 20240924212944.pezsx4xuxpt4ulcp@randomstring.org> <[🔎] 74a7b1dd-bf2f-47fc-a03c-e0f5ec01662d@matrixscience.com> <[🔎] 77a5dc1e-11df-4ecc-a821-b0a3fb5f0a41@rail.eu.org>

That was it, thanks everyone.

On 25/09/2024 13:39, Erwan David wrote:

It should be "netmask 255.255.252.0" or (I prefer) just set
"address 192.168.4.12/22"
without netmask (man says it is deprecated)

Reply to:

References:
- subnet subset blocked
  - From: Adam Weremczuk <adamw@matrixscience.com>
- Re: subnet subset blocked
  - From: Dan Ritter <dsr@randomstring.org>
- Re: subnet subset blocked
  - From: Adam Weremczuk <adamw@matrixscience.com>
- Re: subnet subset blocked
  - From: Erwan David <erwan@rail.eu.org>

Prev by Date: Re: Is the CPU microcode updated?
Next by Date: Re: Is the CPU microcode updated?
Previous by thread: Re: subnet subset blocked
Next by thread: Re: subnet subset blocked
Index(es):
- Date
- Thread