Here are a part of the kernel logs from today:
I would change network cables to new ones. ( Those that connect to red and green)
1 Like
I would consider the possibility of a problem in the driver of the network card. Maybe there has been a change from Linux 5.10 to 5.15 which has exposed a bug?
If the new/different cables do not help, please include a portion of the message log:
cat /var/log/messages
Search through the log for the date & times that lines up with the dead space in the graphs:
and include lines before and after the dead space. You don’t have to find every dead space, just a few recent ones as examples.
You may want to cleanse the message log of private information (e.g., IP & Mac addresses)
Did you try the rebuild as @dlfuller suggested?
1 Like
In the logs @ip-mfg has already posted I can see plenty of errors of the wifi or ethernet card (RT8211E). It seems the kernel looks for the firmware, loads it and then the link goes down.
1 Like
Hi,
this sounds related to a known XHCI regression in Linux kernel 5.15.x - please see this post for details.
Thanks, and best regards,
Peter Müller
1 Like
Sorry for beeing so short and a lit of pushy, but I am really in the soup.
I have for children at home 2 are working for the university and 1 for business. If I can’t fix the problem soon, they will leave to their homes and the Christmas holidays are spoiled.
The hardware I use is a less then 2 years old box from tx-team.
Both networks, green and blue are effected.
With more users in the network, the brake downs of the network are more offen.
If I were in your place, I would backup your settings, downgrade to core 161 by fresh install and restore the backup. This should take no more than 20/30 min. I believe this is the most logical course of action given your predicament. Then, when you have more time, you can deal with the upgrade.
2 Likes
I can try it tonight, but
- the download area of ipfire offers only 162
- I haven’t done a fresh install since my first installation two years ago.
That means connect VGA and keyboard to the ipfire, put the usb inside and make a cold reset? Backup from the pc connected via ipfire.local domain?
Just change the url in the browser to 161 at the end instead of 162 and you will get the page for the 161 downloads.
1 Like
got it and created bootable image.
Thanks
https://www.ipfire.org/download/ipfire-2.27-core161
Yes. Briefly:
- you first download the image and use balena etcher or an equivalent imager to create a bootable usb stick;
- then, you plug the usb memory stick on your machine, make sure the firmware will boot from that disk and not from the internal hd,
- boot and proceed with the fresh installation (reformat of the internal hard disk included);
- proceed with the setup and make sure you choose the right structure (e.g. blue+green+orange+red or whatever you have) and correctly assign the network cards; also, make sure to correctly configure the red interface so that when IPFire reboots you can access internet (i.e. look how you did it and take note before proceeding);
- once finished, then you should be able to connect (https://ipfire.localdomain:444/cgi-bin/index.cgi) to the web user interface (WUI) using a laptop or a desktop in your LAN and restore the backup from your hard disk (see my next paragraph below).
Have a look to the documentation to refresh your memory.
Yes, please read the documentation page first. Again, briefly: before doing anything else you do a backup from the WUI and download the backup files in your laptop or desktop from where you will do the restore later. You will need them once you finish the 161 re-installation process to restore them using the same page in the WUI.
Take care to:
- do not change the backup files name;
- before restoring a plug in, reinstall the plug in first using packfire from the WUI and then proceed to restore from the backup file;
- if you have any special, non standard configuration, to have that included in the backup you need to include the files or the directories by editing
/var/ipfire/backup/include.user
there you have to use the console to do that. Again check the documentation.
From my text it might seem daunting but really it is not. It is pretty straightforward. I had problems only once, when I thought that the backup would restore also the configuration of the red interface, which for some reason it did not. Therefore now I make sure I remember how to set it up correctly from the setup interface used by IPFire during the installation procedure.
Good luck.
2 Likes
Luck was with me.
ipfire 161 is running on my machine and - the last 2 hours - without any brake down.
Great thank you to you cfusco and to all the others of the community for the quick response and the offered help.
3 Likes
Congratulations, very happy for you.
If you would be so inclined, whenever and if you decide to update, would be great if you could open a bug report, with as much documentation as possible, including the output of lspci and lsusb console commands. I would also save from the present installation /var/log/bootlog and include it in the report together with the bootlog of 162 and the kernel logs.
To me it seems clear there is an hardware issue with your ethernet card triggered by some change happened between Linux 5.10 to 5.15 and would be very useful to document it.
2 Likes
Hi all,
for the records:
https://lists.ipfire.org/pipermail/development/2021-December/011856.html
Thanks, and best regards,
Peter Müller
2 Likes
Unfortunately that won’t do.
After running the 3 h without brake downs the PC didn’t accept the green line on a suddon. I tried to connect with another pc direct to the ipfire - same result. The cable tested with the old fritz-box worked.
The usb-port with wlan reports “restricted access”
Presently I have no access to the box and after reading pmueller concerning the tx-team duo box I am a little bit at a loss.
If I can do a little bit more of testing I will do it.
On the other hand I can not exclude that the box has a hardware defect although the box is less them 2 years old.
Now there I am an “experienced installer of ipfire” I can wait for the next update and give the box another try.
2 Likes
Status update:
I did a second fresh installation to my tx-team-box with ipfire-161 and it works since one weak absolutely perfect. I have also the goodies web proxy and IPS on the green and the blue network running. So the sun is shining again 
Open task:
Well I can’t stick to the version 161 for ever. Presently I avoid upgrading to the currant version of ipfire (162).
o Shall I wait for version 163 for updating?
o If yes can I use the update process or have I to start a fresh installation?