From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Test of cleanup branch Date: Thu, 01 Aug 2024 19:09:33 +0200 Message-ID: <5be0d390-b9db-451d-b27a-403b0b455bee@ipfire.org> In-Reply-To: <1a944540-af84-4c79-8a3b-74a93a372baa@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8651761636745756564==" List-Id: --===============8651761636745756564== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, More weird news. I created a fresh install of CU188 build ed2c97b7-dirty into a new vm. After installing it had the same issues as I had originally reported. I have = taken lots of screenshots of all the issues I previously just wrote about. I then shutdown that CU188 IPFire and started back up the CU186 IPFire vm. Th= at version then showed some of the issues I had seen in CU188. I cleared the = cache in my Firefox browser and CU186 went back to its normal look. I then stopped the CU186 and restarted CU188. It came up with all the issues = I originally reported. No matter what I tried I have not been able to get bac= k to the version I had where the colour coding came back and the long entry b= oxes were normal again. I tried clearing the browser cache several times but = nothing changed. I am wondering if when I went to the CU188 version where the colour coding ca= me back and the longer entry boxes disappeared that I was getting some cache = effects from when I had the CU186 version running. Anyway, either way I have been able to reproduce all my original reported iss= ues by re-installing the CU188 iso and this time despite several reboots and = clearing browser caches the results has stayed the same. I have lots of screenshots of all the issues in case it does go away again. Maybe I will try doing a third fresh install of CU188 build ed2c97b7-dirty=C2= =A0 and see if I get the same thing a third time. If yes, then my original is= sues feedback today is the correct status and the intermediate result where s= ome of the issues went away must be the anomaly, caused by some unknown seque= nce of steps that I have not been able to reproduce yet. I will place the screenshots I have in my IPFire People home directory (publi= c section). Regards, Adolf. On 01/08/2024 17:45, Adolf Belka wrote: > Hi Michael, > > So the strikethrough of the existing text did not get applied in my previou= s reply so the following is the feedback that applies now. > > All graphs have new selection buttons for Hour, Day, Weekly etc that are in= a vertical position below the graph. Pressing any of the buttons changes the= graph period being shown but the button does not change colour or anything t= o indicate it has been pressed. You have to look at the graph axis to figure = out which time period has been selected. > > Net-Traffic and ExtraHD have the same tables but instead of being centred o= n the page they are now on the Left Hand Side of the WUI page. > > On the Services page the first graph which should be titled Processes is la= belled 100%. > > On the System page the graphs have no name at all. On the vm I used they sh= ould have been labelled CPU and Load Avg. > > On the Pakfire page the list of available or installed addons do not show t= he pak_ver number so that you get alsa-1.2.10- instead of alsa-1.2.10-20 > > The vulnerabilities page has the left hand section now in black background = with white lettering and the right hand section of the table now has no colou= r coding. Everything is black lettering on a white background. > > The following menu items showed no change/issues except maybe for the graph= period selection buttons . > Backup > Shutdown > Credits > Mailservice > Memory > Media > Network External, Internal and Other > OpenVPN RW and N2N Statistics > WIO > Hardware graphs > Connections > Mdstat > DNS > Web Proxy > URL Filter > Update Accelerator > Edit Hosts > QOS > IP Address Blocklist > Location Block > IPTables > Firewall Groups > Firewall Options > Blue Access > Log Summary > Dynamic DNS > Proxy reports > Firewall logs > Firewall graphs - IP, Port & Country > IPS Logs > IP Address blocklist logs > OpenVPN RW logs > URL Filter Logs > System Logs > Captive portal > Connection Scheduler > Assign MAC Address > DHCP > DNS Forward > Static Routes > Wake on LAN > Time Server > Log Settings > Proxy Logs > > Regards, > > Adolf > > > On 01/08/2024 17:24, Adolf Belka wrote: >> Hi Michael, >> >> So I repeated a CU188 IPFire shutdown, start CU186 IPFire vm, shutdown it = down and restart the CU188 vm a few times. Nothing changed further so I am ed= iting my feedback below by striking through all my comments that no longer ap= ply. I have no idea what happened to cause what I experienced. >> >> Regards, >> >> Adolf >> >> >> On 01/08/2024 17:01, Adolf Belka wrote: >>> Hi Michael, >>> >>> Additional note written after all of the feedback below the dashed line w= as written. I did a shutdown of the vm with CU188 to check something in the C= U186 vm then went back to the CU188 version and things had changed. Most of t= he longer boxes are no longer longer and don't overlap other elements. The mi= ssing colours are back for IPSec, OpenVPN etc. >>> >>> The graph period selection previously was in a horizontal line under the = graph. Now it was still under the graph but it is now a vertical selection ch= oice which can't have been intended as it takes far too much space. However t= he key thing is that rebooting seems to be making things change, which should= n't be happening. I have started to take screenshots of things to have some e= vidence. >>> >>> Attached is a screenshot showing the graph period selectors which are now= vertically positioned at the bottom of the graphs. >>> >>> Also attached is a screenshot of the pakfire page that is still missing t= he pak_ver numbers. >>> >>> I don't know what is going on here. >>> >>> ---------------------------------------------- >>> >>> Okay, here is the feedback from reviewing a vm that actually included the= cleanup branch changes. >>> >>> The home and ssh items look better with the change. They now use alternat= ing shades of grey to highlight each line. >>> >>> All graphs have new selection buttons for Hour, Day, Weekly etc that show= in red when selected. This looks better. The default is the Day selection bu= t when you start with a graph it does not indicate that it is using the Day o= ption, ie all buttons are showing grey. >>> >>> Net-Traffic and ExtraHD have the same tables but instead of being centred= on the page they are now on the Left Hand Side of the WUI page. >>> >>> The Zone Config page looks much busier now. Previously the dropdown box f= or native or vlan selection was next to the vlan id box and the space was goo= d enough for that. Now they are placed one above the other, so wider, which i= s not needed but they now fill the whole space of the section before the next= nic interface starts. I think the previous version looked clearer. >>> >>> The IPS page and the Services page no longer show the red or green backgr= ound for running or stopped. You still see the words but they are now in whit= e on a light grey background or white on a slightly darker grey. >>> >>> On the Services page the first graph which should be titled Processes is = labelled 100%. >>> >>> On the System page the graphs have no name at all. On the vm I used they = should have been labelled CPU and Load Avg. >>> >>> On the Pakfire page the list of available or installed addons do not show= the pak_ver number so that you get alsa-1.2.10- instead of alsa-1.2.10-20 >>> >>> The IPSec and OpenVPN pages no longer show the green, red or blue colours= for the connection status. >>> >>> On the Firewall Rules page the table has no colours for Accept, Reject or= Drop for any of the rules. The alternate grey shading has got mixed up as it= is considering that if there is a remark line for a firewall rule that is a = separate line and the grey shading has to be changed. Definitely not right. S= ome of the Destinations have not had the right colour code applied for the zo= ne colour - left grey. The boxes giving the policy applied for each firewall = section are not colour coded for Allow or Blocked. >>> >>> On the actual firewall creation page, there are longer boxes that overlap= labels or other elements. There is no colour in the Drop, Reject, Accept sel= ection box just one shade of grey. >>> >>> The vulnerabilities page has the left hand section now in black backgroun= d with white lettering. Different but probably okay. After the reboot the Rig= ht Hand Side of the table now has no colour coding. Everything is black lette= ring on a white background. Screenshot of how this is now is attached. >>> >>> The following menu items showed longer entry boxes that overlap labels or= other elements >>> DHCP >>> DNS Forward >>> Static Routes >>> Wake on LAN >>> Time Server >>> Log Settings >>> Proxy Logs >>> >>> >>> The following menu items showed longer entry boxes that did not overlap o= ther elements but you end up with a much longer box length than is needed for= a day number for example >>> Firewall Groups >>> Firewall Options >>> Blue Access >>> Log Summary >>> Dynamic DNS >>> Proxy reports >>> Firewall logs >>> Firewall graphs - IP, Port & Country >>> IPS Logs >>> IP Address blocklist logs >>> OpenVPN RW logs >>> URL Filter Logs >>> System Logs >>> Captive portal >>> Connection Scheduler >>> Assign MAC Address >>> >>> >>> The following menu items showed no change/issues except maybe for the gra= ph period selection buttons . >>> Backup >>> Shutdown >>> Credits >>> Mailservice >>> Memory >>> Media >>> Network External, Internal and Other >>> OpenVPN RW and N2N Statistics >>> WIO >>> Hardware graphs >>> Connections >>> Mdstat >>> DNS >>> Web Proxy >>> URL Filter >>> Update Accelerator >>> Edit Hosts >>> QOS >>> IP Address Blocklist >>> Location Block >>> IPTables >>> >>> I am really sorry for giving false hope that the cleanup branch had gone = really well. >>> >>> Regards, >>> >>> Adolf. >>> >>> On 01/08/2024 12:50, Adolf Belka wrote: >>>> Hi Michael, >>>> >>>> On 25/07/2024 12:28, Adolf Belka wrote: >>>>> Hi Michael, >>>>> >>>>> On 25/07/2024 10:44, Michael Tremer wrote: >>>>>> Hello Adolf, >>>>>> >>>>>> Thank you for getting back on this so quickly. >>>>>> >>>> Maybe I got back too quickly!! >>>> >>>> I have just done a build with next for a bugfix patch and installed it i= nto my vm and the pages look quite different with some things missing, like t= he green and red colours for if services are running or not and some graph ti= tles are incorrect. >>>> >>>> I took the iso from the latest directory in the nightly build but it loo= ks like it was still linked to the previous version when I downloaded it as t= he b2 sum is for build 6460dbbf from the day before. >>>> >>>> Downloading the iso today from the latest directory gives me the build e= d2c97b7. >>>> >>>> I am going to install that version now but I suspect it will show the sa= me as I found with my build. >>>> >>>> So it looks like my original review was based on the version before the = cleanup branch changes were included. >>>> >>>> I will come back with new feedback of what I find from the latest branch= that I have now downloaded. >>>> >>>> Sorry. In future maybe I should wait till the following day, or download= from the build named directory instead of the directory named latest. >>>> >>>> Regards, >>>> >>>> Adolf >>>> >>>>>> I suppose this also means that the ISO in the next branch boots just f= ine, too? >>>>> >>>>> Yes, that is correct. I used the iso from the nightly next latest direc= tory. No problems with the install at all. >>>>> This tested out raid and all 4 interfaces. >>>>> >>>>> Regards, >>>>> Adolf. >>>>> >>>>>> >>>>>> Best, >>>>>> -Michael >>>>>> >>>>>>> On 25 Jul 2024, at 09:07, Adolf Belka wrot= e: >>>>>>> >>>>>>> Hi Michael, >>>>>>> >>>>>>> I installed CU188 from the nightly onto a vm system and looked though= all the WUI pages and everything looked fine. >>>>>>> >>>>>>> I then restored a CU187 backup from my testing and then checked the O= penVPN RW and N2N. Both worked fine with no problems. Also the logging for th= at all worked with no problems. >>>>>>> >>>>>>> Also checked out the IPS, IP Blocklists, Firewall groups and rules, D= NS ... >>>>>>> >>>>>>> Everything I have looked at shows no impact from the cleanup branch c= hanges. It looks good to me. >>>>>>> >>>>>>> Of course good for others to also evaluate. >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Adolf. >>>>>>> >>>>>> --===============8651761636745756564==--