some services show can't start
-
Yes, my native language is not English.
I'm talking about things, not targeting anyone. I want pfsense to be better, that's why I say so much. I found that the development team may have different philosophies, so there may be differences in how to do things. My philosophy is to use the most advanced technology, but the development is suitable for strict technical quality control. Every change developed must be tested in different internal environments, especially some that may cause serious problems and cannot be taken outside at all.
I found that the current philosophy of the Pfsense team is that they are afraid to use advanced technologies, especially some new technologies that they dare not try and need to wait for a long time. Technology is advancing with the times, and many technologies are time-sensitive and cannot be used for a long time. We must be brave enough to try the latest Instead of avoiding things for fear of problems, it is best to control the quality of every detail is crucial. If you don’t try new technologies and find problems, users are likely to use them in conjunction with various new technologies or new equipment. If the team has not used new technologies, it will be difficult to integrate them with user needs. Computer technology relies heavily on innovation. The change in one year can be huge and it is impossible to wait until a year later to use it.There is a difference between opnsense and pfsense in adopting new technologies. OP is more willing to try new technologies or new things. I am used to various settings of pfsense, so it is difficult for me to change.
-
I recently used DTLS technology for udp tunnel, I contacted the developer directly to provide various suggestions and improvements were quickly implemented. He is a Ukrainian developer and I think he is very patient.
So if pfsense can consider adding new technology features, I recommend it.
The website of his works is this
https://github.com/Snawoot/dtlspipe
-
This is an example. These could have been discovered through internal review. It's too obvious. So why am I tired of reporting bugs? I'm not a technical developer and I don't know the specific details of the code. I can only report from the superficial phenomenon. Regarding the specific details, Technical issues require investigation and judgment by your technical staff. It is too difficult to leave it to ordinary users to investigate.
-
I use DTLS to protect wireguard, Wiregaurd has obvious characteristic shortcomings. The handshake part of the data packet is too easy to be detected and blocked by DPI.
Tested using DTLS and the result is that there are obvious benefits. It is currently not blocked by DPI and reduces interference. I worked with this developer to improve it.
-
@stephenw10 said in some services show can't start:
Ok, that is a bug I can easily replicate that.
-
-
This should actually be fixed in todays build (
23.09.b.20231013.0600) are you testing that?Existing rules will need to be resaved to populate the aliases correctly.
Steve
-
@stephenw10 JFC Steve - you need these developers working on the latest and greatest to up their quality testing and make sure every possible thing works before you release the snapshots ;)
hahaah
An intelligent man is sometimes forced to be drunk to spend time with his fools
If you get confused: Listen to the Music Play
Please don't Chat/PM me for help, unless mod related
SG-4860 24.11 | Lab VMs 2.7.2, 24.11 -
Mmmm. We should have caught that one but.... that's what dev builds are for.
But in all seriousness we cannot possibly test every possible config and, especially for complex and unusual configs, we expect to see more bugs reported at each stage in the release.
If you have such a config I encourage you take part in the release testing process to find those bugs as early s possible.
Steve
-
There are so many mistakes that I can’t even count them on two hands. Upgrading is not that easy.
pfSense-upgrade -dy ERROR: It was not possible to determine pkg remote version >>> Updating repositories metadata... Updating pfSense-core repository catalogue... pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header repository pfSense-core has no meta file, using default settings pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header repository pfSense has no meta file, using default settings pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header Unable to update repository pfSense Error updating repositories! ERROR: It was not possible to determine pfSense-upgrade remote version ERROR: It was not possible to determine pfSense-upgrade remote version >>> Upgrading pfSense-upgrade... Updating pfSense-core repository catalogue... pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header repository pfSense-core has no meta file, using default settings pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header repository pfSense has no meta file, using default settings pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header Unable to update repository pfSense Error updating repositories! [23.09-BETA][admin@]/root: pkg update Updating pfSense-core repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.pkg: 100% 2 KiB 1.6kB/s 00:01 Processing entries: 100% pfSense-core repository update completed. 5 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.pkg: 100% 191 KiB 17.8kB/s 00:11 Processing entries: 100% pfSense repository update completed. 727 packages processed. All repositories are up to date. -
I participate in a lot of software development tests and provide suggestions. pfsense is the one where I see the most errors, and the most important ones are a lot of errors that have a major impact. Other software test versions do not have major errors that make the system unusable.
-
haha。。 The pfsense team is too conservative. Many of the software developments I have participated in are innovative technologies that do not exist today, and we have developed and created them ourselves. However, pfsense does not even dare to follow up and use them.
-
That http header error is just extra noise, it's been removed from the latest package version.
But it is a sign it could not fetch the file which is interesting since pkg update succeeds.
Does it still fail if you run
pfSense-repocfirst? -
After entering this command, nothing happens.
[23.09-BETA][admin@]/root: pfSense-repoc [23.09-BETA][admin@]/root: -
That's expected. Can it now upgrade?
-
waiting for this long time
[23.09-BETA][admin@]/root: pfSense-upgrade -dy ERROR: It was not possible to determine pkg remote version >>> Updating repositories metadata... Updating pfSense-core repository catalogue... pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header repository pfSense-core has no meta file, using default settings pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header repository pfSense has no meta file, using default settings pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header Unable to update repository pfSense Error updating repositories! ERROR: It was not possible to determine pfSense-upgrade remote version ERROR: It was not possible to determine pfSense-upgrade remote version >>> Upgrading pfSense-upgrade... Updating pfSense-core repository catalogue... pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header repository pfSense-core has no meta file, using default settings pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header repository pfSense has no meta file, using default settings pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header Unable to update repository pfSense Error updating repositories! -
IIRC you previously had issues with IPv6 failing there. Try:
pfSense-upgrade -d4 -
[23.09-BETA][admin@]/root: pfSense-upgrade -d4 ERROR: It was not possible to determine pkg remote version >>> Updating repositories metadata... Updating pfSense-core repository catalogue... pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header repository pfSense-core has no meta file, using default settings pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header repository pfSense has no meta file, using default settings pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header Unable to update repository pfSense Error updating repositories! ERROR: It was not possible to determine pfSense-upgrade remote version ERROR: It was not possible to determine pfSense-upgrade remote version >>> Upgrading pfSense-upgrade... Updating pfSense-core repository catalogue... pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header repository pfSense-core has no meta file, using default settings pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header repository pfSense has no meta file, using default settings pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header pkg-static: An error occured while fetching package pkg-static: Impossible to get the value from Last-Modified HTTP header Unable to update repository pfSense Error updating repositories! -
And I assume the same if you force v6?
-
Oct 15 01:31:53 php_wg 53450 /usr/local/pkg/wireguard/includes/wg_service.inc: Configuration Change: (system): [pfSense-pkg-WireGuard] De-installed earlyshellcmd(s).
Oct 15 01:31:53 check_reload_status 507 Syncing firewall
Oct 15 01:31:53 php_wg 53450 /usr/local/pkg/wireguard/includes/wg_service.inc: Configuration Change: (system): [pfSense-pkg-WireGuard] Installed earlyshellcmd(s).
Oct 15 01:31:53 check_reload_status 507 Syncing firewall
Oct 15 01:31:54 php_wg 53450 /usr/local/pkg/wireguard/includes/wg_service.inc: Configuration Change: (system): [pfSense-pkg-WireGuard] De-installed interface group (WireGuard).
Oct 15 01:31:54 php_wg 53450 /usr/local/pkg/wireguard/includes/wg_service.inc: Configuration Change: (system): [pfSense-pkg-WireGuard] Installed interface group (WireGuard).
Oct 15 01:31:55 php_wg 53450 /usr/local/pkg/wireguard/includes/wg_service.inc: Configuration Change: (system): [pfSense-pkg-WireGuard] De-installed Unbound ACL group (WireGuard).
Oct 15 01:31:55 check_reload_status 507 Syncing firewall
Oct 15 01:31:55 php_wg 53450 /usr/local/pkg/wireguard/includes/wg_service.inc: Configuration Change: (system): [pfSense-pkg-WireGuard] Installed Unbound ACL group (WireGuard).
Oct 15 01:31:55 check_reload_status 507 Syncing firewall
Oct 15 01:31:56 php_wg 53450 /usr/local/pkg/wireguard/includes/wg_service.inc: Configuration Change: (system): [pfSense-pkg-WireGuard] Applied package default settings as necessary.
