Pakfire no updates with PPP setting "VDSL "

Networking Static/Dynamic Routing
1

Hello,

the IPFire 2.25 (i586) - Core Update 158 was previously running RED on a DSL router with DHCP.
There were no problems here.
3 days ago I switched from DSL to fiber.
The converter supplied by the provider delivers a VDSL signal.
The changeover worked perfectly without any problems.

But when I wanted to install a package today, I found that I.:

  • I can not update any updates
  • I cannot execute any updates 158 → 159
  • can’t install new packages (following the message from Pakfire)

You want to install the following packages: squidclamav Possibly these packages have dependencies, i.e. other packages must be installed additionally. You can see a list of them below.

PAKFIRE ERROR: You need to be online to run pakfire![0m

Do you want to agree to install all packages?

2

Hi @pic18f2550

Welcome to the IPFire community.

When you say

how did you define “worked perfectly”.
Were you able to access the internet?
Did you try downloading an addon package from pakfire?

Is accessing the internet also blocked now?

What is the status of the Internet connection showing on the main WUI page?

If you ping the gateway of your supplier, shown on the main page do you get a response or not?

1 Like
3

I can access the Internet with all PCs via green without any problems.
Only the IPFire says that it is not accessible.

Neue Bitmap (2)
Neue Bitmap (2)1049×581 31.2 KB

Neue Bitmap (3)
Neue Bitmap (3)1028×470 30.1 KB

4

OK, then we need to find why Pakfire is having problems accessing the internet.

You need to look in the Pakfire logs to see what it says.

You can access them either on the Logs - System Logs WUI page, selecting Pakfire in the dropdown box and pressing Update or in the console by using the following command:-

less /var/log/messages | grep pakfire
5

IPFire diagnostics
Abschnitt: pakfire
Datum: August 25, 2021

14:55:58 pakfire: PAKFIRE ERROR: You need to be online to run pakfire!
14:55:58 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25 started!
12:39:11 pakfire: PAKFIRE ERROR: You need to be online to run pakfire!
12:39:11 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25 started!
12:39:05 pakfire: PAKFIRE ERROR: You need to be online to run pakfire!
12:39:05 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25 started!
12:38:59 pakfire: PAKFIRE ERROR: You need to be online to run pakfire!
12:38:59 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25 started!
12:24:02 pakfire: PAKFIRE ERROR: You need to be online to run pakfire!
12:24:02 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25 started!
04:13:26 pakfire: PAKFIRE ERROR: You need to be online to run pakfire!
04:13:26 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25 started!

6

Locate the beginning of those errors. So either earlier in that day or a day or two before those errors.

7

No idea what does not fit here.
The top picture is after a reboot I did today at noon. ( no IP no hostname or gateway )

Now I have cleaned up something on the IPFire since samba and cups are not needed I have removed them.

And after the reboot suddenly something like this -->>

Neue Bitmap (3)
Neue Bitmap (3)1019×600 32.4 KB

And Packfire is working again, too.
How am I supposed to understand this!
3 days for the cat. :slight_smile:

I suspect that switching from RED DHCP to VDSL somehow got tangled up with Samba or Cups.

1 Like
8

IPFire diagnostics
Abschnitt: pakfire
Datum: August 22, 2021

23:08:14 pakfire: PAKFIRE ERROR: You need to be online to run pakfire!
23:08:14 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25 started!
01:15:02 pakfire: PAKFIRE ERROR: You need to be online to run pakfire!
01:15:02 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25 started!

IPFire diagnostics
Abschnitt: pakfire
Datum: August 21, 2021

00:31:41 pakfire: PAKFIRE ERROR: You need to be online to run pakfire!
00:31:41 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25 started!

IPFire diagnostics
Abschnitt: pakfire
Datum: August 20, 2021

17:56:23 pakfire: PAKFIRE ERROR: You need to be online to run pakfire!
17:56:23 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25 started!
<<<<- switch from DHCP to VDSL
17:33:11 pakfire: PAKFIRE INFO: Pakfire has finished. Closing.
17:33:11 pakfire: Giving up: There was no chance to get the file lists/core-list.db from any available server. There was an error on the way. Please fix it.
17:33:11 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 500 - 500 Can’t connect to mirror.uta.edu.ec:443 (Name or service not known)
17:33:11 pakfire: DOWNLOAD INFO: ipfire/pakfire2/2.25/lists/core-list.db has size of bytes
17:33:11 pakfire: DOWNLOAD INFO: Host: mirror.uta.edu.ec (HTTPS) - File: ipfire/pakfire2/2.25/lists/core-list.db
17:33:11 pakfire: MIRROR INFO: 25 servers found in list
17:33:11 pakfire: DOWNLOAD STARTED: lists/core-list.db
17:33:11 pakfire: CORE INFO: core-list.db is 3902 seconds old. - DEBUG: force
17:33:11 pakfire: Giving up: There was no chance to get the file lists/packages_list.db from any available server. There was an error on the way. Please fix it.
17:33:11 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 500 - 500 Can’t connect to ftp.nluug.nl:443 (Name or service not known)
17:33:11 pakfire: DOWNLOAD INFO: os/Linux/distr/ipfire/pakfire2/2.25/lists/packages_list.db has size of bytes
17:33:11 pakfire: DOWNLOAD INFO: Host: ftp.nluug.nl (HTTPS) - File: os/Linux/distr/ipfire/pakfire2/2.25/lists/packages_list.db
17:33:11 pakfire: MIRROR INFO: 25 servers found in list
17:33:11 pakfire: DOWNLOAD STARTED: lists/packages_list.db
17:33:11 pakfire: DB INFO: packages_list.db is 3905 seconds old. - DEBUG: force
17:33:11 pakfire: Giving up: There was no chance to get the file 2.25/lists/server-list.db from any available server. There was an error on the way. Please fix it.
17:33:11 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 500 - 500 Can’t connect to pakfire.ipfire.org:443 (Name or service not known)
17:33:11 pakfire: DOWNLOAD INFO: 2.25/lists/server-list.db has size of bytes
17:33:10 pakfire: DOWNLOAD INFO: Host: pakfire.ipfire.org (HTTPS) - File: 2.25/lists/server-list.db
17:33:10 pakfire: DOWNLOAD STARTED: 2.25/lists/server-list.db
17:33:10 pakfire: MIRROR INFO: server-list.db is 3905 seconds old. - DEBUG: force
17:33:10 pakfire: PAKFIRE INFO: IPFire Pakfire 2.25 started!