Menu
▾
▴
leaf-user
|
From: Timothy W. <ti...@ts...> - 2020-10-05 22:26:51
|
I have upgraded from 6.2.7 to 7.0.0-rc2 without incident. I have a fairly simple firewall setup, with the following in leaf.cfg: LRP=" license local dhcpcd keyboard shorwall dnsmasq bbntpd sshd ssh sshkey sftp lighttpd webconf elvis hdsupp patch haveged" My normal method of upgrading is to copy the new distribution files onto a previously used USB with syslinux already installed, then to copy leaf.cfg and configdb.lrp from my current setup. This is very quick to do, and almost always works, and leaves my old setup undisturbed on the old usb in case I need to go back. Occasionally a major upgrade requires starting with the default configuration and then changing it to what I need, which is much harder, but hasn't happened in a while. Simple question, is it ok to upgrade from 6.2.7 to 7.0.0-rc2by just copying leaf.cfg and configdb.lrp? Seems to be fine this time. Thanks for everything, Tim |
|
From: Erich T. <eri...@th...> - 2020-10-05 22:47:51
|
Am 05.10.2020 um 22:39 schrieb Timothy Wegner: > I have upgraded from 6.2.7 to 7.0.0-rc2 without incident. I have a fairly > simple firewall setup, with the following in leaf.cfg: > > LRP=" license local dhcpcd keyboard shorwall dnsmasq bbntpd sshd ssh sshkey > sftp lighttpd webconf elvis hdsupp patch haveged" > > My normal method of upgrading is to copy the new distribution files onto a > previously used USB with syslinux already installed, then to copy leaf.cfg > and configdb.lrp from my current setup. This is very quick to do, and > almost always works, and leaves my old setup undisturbed on the old usb in > case I need to go back. Occasionally a major upgrade requires starting with > the default configuration and then changing it to what I need, which is > much harder, but hasn't happened in a while. > > Simple question, is it ok to upgrade from 6.2.7 to 7.0.0-rc2by just copying > leaf.cfg and configdb.lrp? Seems to be fine this time. Probably without too much sweat, being biased I would thinkg using the upgrade tool might even be better. cheers ET -- Diese E-Mail wurde von AVG auf Viren geprüft. http://www.avg.com |
|
From: marko <le...@me...> - 2020-10-05 23:01:16
|
On Tuesday, 6 October 2020 7:39:54 AM AEDT Timothy Wegner wrote: > I have upgraded from 6.2.7 to 7.0.0-rc2 without incident. I have a fairly > simple firewall setup, with the following in leaf.cfg: > > LRP=" license local dhcpcd keyboard shorwall dnsmasq bbntpd sshd ssh sshkey > sftp lighttpd webconf elvis hdsupp patch haveged" > > My normal method of upgrading is to copy the new distribution files onto a > previously used USB with syslinux already installed, then to copy leaf.cfg > and configdb.lrp from my current setup. This is very quick to do, and > almost always works, and leaves my old setup undisturbed on the old usb in > case I need to go back. Occasionally a major upgrade requires starting with > the default configuration and then changing it to what I need, which is > much harder, but hasn't happened in a while. > > Simple question, is it ok to upgrade from 6.2.7 to 7.0.0-rc2by just copying > leaf.cfg and configdb.lrp? Seems to be fine this time. > > Thanks for everything, > > Tim > > ------------------------------------------------------------------------ > leaf-user mailing list: lea...@li... > https://lists.sourceforge.net/lists/listinfo/leaf-user > Support Request -- http://leaf-project.org/ Hi Tim, I have done this successfully from 6.2 to 7.0 I had a long chain of upgrades where I did this over many years and the only time it did not work when moving to version 6. Over time, the config files change significantly and you will not see new options appearing. My new policy is to modify new config files with each major version change. That said, I do a quick and dirty copy first and then modify another boot stick with clean config files. cheers Marko |
|
From: Robert K C. J. -I. F. D. Corp. <bco...@in...> - 2020-10-05 23:28:07
|
I have scripts to scp the new files over, retain the old, and then some md5 checks... This way I can do remote upgrades - providing that shorewall doesn't need an update! This worked for my last round of upgrades, but my current upgrades are requiring me to have someone on-site. - Bob On 10/5/2020 4:39 PM, Timothy Wegner wrote: > Simple question, is it ok to upgrade from 6.2.7 to 7.0.0-rc2by just copying > leaf.cfg and configdb.lrp? Seems to be fine this time. |
|
From: Timothy W. <ti...@ts...> - 2020-10-06 02:41:16
|
The wiki says "Bering-uClibc 7.x is basically Bering-uClibc 6.x brought up to date with the latest versions ..." so I'm probably OK for now, but as time has gone by, my configuration has probably gotten more and more out of date even though it still works. My shorewall setup is probably the most complex, most of the other packages are close to the defaults. Erich, I checked the docs and apparently there's both a command line upgrade and one accessible via Webconf. Are these basically the same thing, and is that what you are talking about? Would I have to go back to 6.2.7 and then upgrade? (I would think so). Can the upgrade tool upgrade to 7.0.0-rc2, or does it look for the release version? 7.0.0? The reason I haven't tried the upgrade capability is that my simple minded approach of adding leaf.cfg and configdb.lrp to the new Leaf packages leaves my old configuration intact on the old usb, so if my upgrade doesn't work I just plug in the old usb, and I am back where I was. Of course I could always copy the old usb first and then upgrade. I also appreciated Marko's and Bob's comments. It would be a good thing to start with the new packages and modify them as Marko does for a new major version (I have done this in the past). I don't have Bob's problem of maintaining off-site boxes, my firewall is here in my office. I just need to mess with it when my wife is not using her computer! Thanks again. I have been using Leaf since the Dave Cinege LRP days and appreciate it very much. Tim |
|
From: Erich T. <eri...@th...> - 2020-10-06 08:06:27
|
Am 06.10.2020 um 04:29 schrieb Timothy Wegner:
....
>
> Erich, I checked the docs and apparently there's both a command line
> upgrade and one accessible via Webconf. Are these basically the same thing,
> and is that what you are talking about?
Yes, the webconf is mostly a wrapper around the CLI version.
Would I have to go back to 6.2.7
> and then upgrade?
No, if you have a 7.0.0-xx running just let it run. If you are upgrading
from a real old version then sometimes upgrade is not foolproof, it has
evolved over the last few years.
(I would think so). Can the upgrade tool upgrade to
> 7.0.0-rc2, or does it look for the release version? 7.0.0?
If you start upgrade with the --help option you will see the usage.
It will typicall look for the 'stable' version.
leafinstaller# upgrade -c
6.2.7
upgrade: upgrade terminated successfully
For example, for 7.0.0-rc2 you can use
upgrade -c --latest
leafinstaller# upgrade -c --latest
7.0.0-rc2
upgrade: upgrade terminated successfully
or
leafinstaller# upgrade -c --release 7.0.0-rc2
7.0.0-rc2
upgrade: upgrade terminated successfully
to check for the files. If you leave away the -c option it will go and
start the upgrade.
Usage: upgrade [-c][ -s | -v | --verbose][--stable | --latest |
--release x.y.z][-u | --use_apkg]
-c just check the version on the server
-s | --silent run quietly
-v | --verbose be chatty about the progress
--stable upgrade to stable release
--latest upgrade to latest release
--release x.y.z upgrade to release x.y.z
-u | --use_apkg use apkg -u to handle modified packages
instead of the internal routines
-h | --help show this page
Mind you, upgrade relies heavily on the presence of patch.lrp on the
system.
>
> The reason I haven't tried the upgrade capability is that my simple minded
> approach of adding leaf.cfg and configdb.lrp to the new Leaf packages
> leaves my old configuration intact on the old usb, so if my upgrade doesn't
> work I just plug in the old usb, and I am back where I was. Of course I
> could always copy the old usb first and then upgrade.
I recommend a three partition set up on the media. Partition 1 for the
boot code, partition 2 for the standard set up and partition 3 for a
copy of the set up which can be selected from the console and be used
for either a backup copy or an alternative configuration.
>
> I also appreciated Marko's and Bob's comments. It would be a good thing to
> start with the new packages and modify them as Marko does for a new major
> version (I have done this in the past).
upgrade tries hard to do that for you, sometimes it fails on shorewall
but it leaves the affected files for inspection in /tmp. You can use
these files to find out what you need to correct manually.
If upgrade terminates without errors it will save the current
configuration. You can then reboot the box and check. If it detects
errors it _does_not_ save the configuration. This is basically what
would happen if you just keep leaf.cfg and configdb,lrp.
I don't have Bob's problem of
> maintaining off-site boxes, my firewall is here in my office. I just need
> to mess with it when my wife is not using her computer!
Well, upgrade has been written with Bob's problem in mind.
>
> Thanks again. I have been using Leaf since the Dave Cinege LRP days and
> appreciate it very much.
In that case you know all internals.
cheers
ET
--
Diese E-Mail wurde von AVG auf Viren geprüft.
http://www.avg.com
|
|
From: Timothy W. <ti...@ts...> - 2020-10-06 17:23:02
|
Erich, you wrote (after I mentioned my long history with Leaf/Lrp): > In that case you know all internals I have no knowledge of the internals at all, I'm just a very long time user with Leaf/Lrp on my home router. Thanks for all the information about the update app, enormously informative! I will experiment with it for the next release. I may also try a fresh start with 7.0.0-rc2 just to get a clean baseline for going forward. Thanks to all the Leaf developers! Tim On Tue, Oct 6, 2020 at 3:06 AM Erich Titl <eri...@th...> wrote: > Am 06.10.2020 um 04:29 schrieb Timothy Wegner: > .... > > > > Erich, I checked the docs and apparently there's both a command line > > upgrade and one accessible via Webconf. Are these basically the same > thing, > > and is that what you are talking about? > > Yes, the webconf is mostly a wrapper around the CLI version. > > Would I have to go back to 6.2.7 > > and then upgrade? > > No, if you have a 7.0.0-xx running just let it run. If you are upgrading > from a real old version then sometimes upgrade is not foolproof, it has > evolved over the last few years. > > (I would think so). Can the upgrade tool upgrade to > > 7.0.0-rc2, or does it look for the release version? 7.0.0? > > If you start upgrade with the --help option you will see the usage. > > It will typicall look for the 'stable' version. > > leafinstaller# upgrade -c > 6.2.7 > upgrade: upgrade terminated successfully > > For example, for 7.0.0-rc2 you can use > > upgrade -c --latest > > leafinstaller# upgrade -c --latest > 7.0.0-rc2 > upgrade: upgrade terminated successfully > > or > > leafinstaller# upgrade -c --release 7.0.0-rc2 > 7.0.0-rc2 > upgrade: upgrade terminated successfully > > to check for the files. If you leave away the -c option it will go and > start the upgrade. > > Usage: upgrade [-c][ -s | -v | --verbose][--stable | --latest | > --release x.y.z][-u | --use_apkg] > > -c just check the version on the server > -s | --silent run quietly > -v | --verbose be chatty about the progress > --stable upgrade to stable release > --latest upgrade to latest release > --release x.y.z upgrade to release x.y.z > -u | --use_apkg use apkg -u to handle modified packages > instead of the internal routines > -h | --help show this page > > Mind you, upgrade relies heavily on the presence of patch.lrp on the > system. > > > > > The reason I haven't tried the upgrade capability is that my simple > minded > > approach of adding leaf.cfg and configdb.lrp to the new Leaf packages > > leaves my old configuration intact on the old usb, so if my upgrade > doesn't > > work I just plug in the old usb, and I am back where I was. Of course I > > could always copy the old usb first and then upgrade. > > I recommend a three partition set up on the media. Partition 1 for the > boot code, partition 2 for the standard set up and partition 3 for a > copy of the set up which can be selected from the console and be used > for either a backup copy or an alternative configuration. > > > > > I also appreciated Marko's and Bob's comments. It would be a good thing > to > > start with the new packages and modify them as Marko does for a new major > > version (I have done this in the past). > > upgrade tries hard to do that for you, sometimes it fails on shorewall > but it leaves the affected files for inspection in /tmp. You can use > these files to find out what you need to correct manually. > > If upgrade terminates without errors it will save the current > configuration. You can then reboot the box and check. If it detects > errors it _does_not_ save the configuration. This is basically what > would happen if you just keep leaf.cfg and configdb,lrp. > > I don't have Bob's problem of > > maintaining off-site boxes, my firewall is here in my office. I just need > > to mess with it when my wife is not using her computer! > > Well, upgrade has been written with Bob's problem in mind. > > > > > Thanks again. I have been using Leaf since the Dave Cinege LRP days and > > appreciate it very much. > > In that case you know all internals. > > cheers > > ET > > > -- > Diese E-Mail wurde von AVG auf Viren geprüft. > http://www.avg.com > > > > ------------------------------------------------------------------------ > leaf-user mailing list: lea...@li... > https://lists.sourceforge.net/lists/listinfo/leaf-user > Support Request -- http://leaf-project.org/ > |
|
From: Robert K C. J. -I. F. D. Corp. <bco...@in...> - 2020-10-06 12:07:23
|
To be honest, I never looked at it. I'm not sure I knew it existed when I first created my scripts. I will definitely look into it now! - Bob On 10/6/2020 4:05 AM, Erich Titl wrote: > Well, upgrade has been written with Bob's problem in mind. |
|
From: Erich T. <eri...@th...> - 2020-10-06 12:30:03
|
Hi Bob Am 06.10.2020 um 14:06 schrieb Robert K Coffman Jr. -Info From Data Corp.: > To be honest, I never looked at it. I'm not sure I knew it existed when > I first created my scripts. The project was a bit underground and not documented. We feel that it is quite mature right now, which does not mean it is completely failsafe. But then if you follow the three partition layout there is always a way to recover. You may have seen in webconf there is an item to save what is running to your local system. This can help recovery in case something goes wrong and not just at upgrade (and it is poorly documented too :-( ) cheers ET. -- Diese E-Mail wurde von AVG auf Viren geprüft. http://www.avg.com |
