public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Jonatan Schlag <jonatan.schlag@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Start local and uplink network independent
Date: Fri, 18 Aug 2023 12:30:03 +0200	[thread overview]
Message-ID: <e59632b41e58f91f12cb90ce60b57f7930a5310b.camel@ipfire.org> (raw)
In-Reply-To: <5912CCFF-CAEC-4156-AC8F-11E50ED95616@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 4168 bytes --]

Hi list,

Am Mittwoch, dem 24.05.2023 um 09:59 +0100 schrieb Michael Tremer:
> Hello Jonatan,
> 
> Thanks for this *huge* patchset.
> 
> What I do not quite understand from your email is the motivation for
> this. Starting the SSH daemon a little bit sooner is not justifying
> such massive change.

Starting the SSH-Daemon earlier was not the only reason. The main
reason was 

a) to debug problems with the red interface via ssh and via console
b) Wait infinitely for a dhcp lease. We currently only wait 30 seconds.
If we do not get a lease, red stays down forever. 

> 
> I consider this a highly risky patchset as we are touching code that
> is already incredibly fragile and the smallest changes might
> introduce more problems.
> 

I know that this is a risky patch set. But not touching these code does
not improve it. It gets worse each day. Never touch a running system
turns against us here. So both change and no change have a risk here.

My further plan for this patch set is to split it up even further. My
builder is currently running with all the patches you already agreed
to. I will send this patch set in the next days. When this is merged, I
will go on to review the other patches.

Greetings Jonatan

> But I have to say that I like how you split this into small patches
> that can be reviewed easier.
> 
> > On 23 May 2023, at 18:23, Jonatan Schlag
> > <jonatan.schlag(a)ipfire.org> wrote:
> > 
> > Hi,
> > 
> > this is the first try for a patch series which makes the startup of
> > local and uplink networks independent. This resolves in the end
> > #11502. It should further allow us to keep waiting for a DHCP
> > lease, because at least our local networks are all up when we get
> > to the red network. This might have some small quirks, even when my
> > testing so far shows no problems. I still think it is now better to
> > share result, then to wait any longer.
> > As this touches quite important parts of our network stack, I might
> > be a could idea to merge this in two stages. After the patch,
> > titled "network startup: Clean up duplicated Code ", might be a
> > good breaking point.  But in the end, this is up to you. Please
> > keep in mind, I only tested the full patch set:
> > 
> >  Remove ipsec interface creation from network startup
> >  Remove Start/Stop links for client175
> >  Use bash as shebang in network initscripts
> >  network initscripts: check if the zone in the current config
> > exists
> >  network initscripts: Remove code for old zone scheme
> >  network scripts: remove check for AUTOCONNECT
> >  network startup: Reload routing informations for every interface
> >  network startup: Always cleanup before red gets started
> >  network startup: check for correct action at start
> >  network startup: Refactor how cmd args are processed
> >  network startup: Clean up duplicated Code
> >  network script: add extra scripts for action that depend on a
> > network
> >  network startup: Add scripts for local and uplink
> >  network startup: Start local and uplink network independent
> >  network startup: Only work with configured zones
> > 
> > config/rootfiles/common/aarch64/initscripts   |  31 +++--
> > config/rootfiles/common/riscv64/initscripts   |  31 +++--
> > config/rootfiles/common/x86_64/initscripts    |  31 +++--
> > lfs/initscripts                               |  36 +++---
> > src/initscripts/networking/any                |  31 ++++-
> > src/initscripts/networking/functions.network  |  14 +-
> > src/initscripts/networking/red                |   5 +-
> > .../networking/red.up/99-pakfire-update       |   2 +-
> > src/initscripts/system/depends-on-network     |  40 ++++++
> > src/initscripts/system/network                | 121 ++++++++-------
> > ---
> > 10 files changed, 218 insertions(+), 124 deletions(-)
> > create mode 100644 src/initscripts/system/depends-on-network
> > 
> > 
> > Looking forward to your feedback
> > 
> > Greetings
> > Jonatan
> > 
> 



      reply	other threads:[~2023-08-18 10:30 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 17:23 Jonatan Schlag
2023-05-23 17:23 ` [Patch RFC 01/15] Remove ipsec interface creation from network startup Jonatan Schlag
2023-05-24  8:59   ` Michael Tremer
2023-05-23 17:23 ` [Patch RFC 02/15] Remove Start/Stop links for client175 Jonatan Schlag
2023-05-23 17:23 ` [Patch RFC 03/15] Use bash as shebang in network initscripts Jonatan Schlag
2023-05-24  8:59   ` Michael Tremer
2023-05-23 17:23 ` [Patch RFC 04/15] network initscripts: check if the zone in the current config exists Jonatan Schlag
2023-05-24  9:00   ` Michael Tremer
2023-08-18 12:55     ` Jonatan Schlag
2023-08-21  9:40       ` Michael Tremer
2023-05-23 17:23 ` [Patch RFC 05/15] network initscripts: Remove code for old zone scheme Jonatan Schlag
2023-05-24  9:00   ` Michael Tremer
2023-05-23 17:23 ` [Patch RFC 06/15] network scripts: remove check for AUTOCONNECT Jonatan Schlag
2023-05-24  9:00   ` Michael Tremer
2023-05-23 17:23 ` [Patch RFC 07/15] network startup: Reload routing informations for every interface Jonatan Schlag
2023-05-24  9:00   ` Michael Tremer
2023-05-23 17:23 ` [Patch RFC 08/15] network startup: Always cleanup before red gets started Jonatan Schlag
2023-05-24  9:00   ` Michael Tremer
2023-05-23 17:23 ` [Patch RFC 09/15] network startup: check for correct action at start Jonatan Schlag
2023-05-24  9:00   ` Michael Tremer
2023-08-18 10:23     ` Jonatan Schlag
2023-05-23 17:23 ` [Patch RFC 10/15] network startup: Refactor how cmd args are processed Jonatan Schlag
2023-05-24  9:00   ` Michael Tremer
2023-05-23 17:23 ` [Patch RFC 11/15] network startup: Clean up duplicated Code Jonatan Schlag
2023-05-24  9:00   ` Michael Tremer
2023-05-23 17:23 ` [Patch RFC 12/15] network script: add extra scripts for action that depend on a network Jonatan Schlag
2023-05-24  9:00   ` Michael Tremer
2023-05-23 17:23 ` [Patch RFC 13/15] network startup: Add scripts for local and uplink Jonatan Schlag
2023-05-24  9:00   ` Michael Tremer
2023-05-23 17:23 ` [Patch RFC 14/15] network startup: Start local and uplink network independent Jonatan Schlag
2023-05-24  9:00   ` Michael Tremer
2023-05-23 17:23 ` [Patch RFC 15/15] network startup: Only work with configured zones Jonatan Schlag
2023-05-24  9:00   ` Michael Tremer
2023-05-24  8:59 ` Start local and uplink network independent Michael Tremer
2023-08-18 10:30   ` Jonatan Schlag [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e59632b41e58f91f12cb90ce60b57f7930a5310b.camel@ipfire.org \
    --to=jonatan.schlag@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox