1
23.1 Legacy Series / Re: Alias name restriction (Firewall:Alias)
« on: March 03, 2023, 10:34:09 pm »
ok, done.
thanx!
thanx!
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
23.1 Legacy Series / Alias name restriction (Firewall:Alias)
« on: March 03, 2023, 10:07:33 pm »
when trying to add a new device, i tried to do this according to the scheme i always did it so far.
unfortunately, this seems to be no longer accepted without obvious reason.
my scheme is:
<device type, 1 letter>_<device name>
as an example:
W_MyWifiDevice
this is not accepted and results in the message "The name must start with a letter or single underscore, be less than 32 characters and only consist of alphanumeric characters or underscores.". i think this is fulfilled.
but using
WW_MyWifiDevice
or
_W_MyWifiDevice
is accepted.
i'm running
OPNsense 23.1.1_2-amd64
is this a bug and will this be fixed?
thanx!
unfortunately, this seems to be no longer accepted without obvious reason.
my scheme is:
<device type, 1 letter>_<device name>
as an example:
W_MyWifiDevice
this is not accepted and results in the message "The name must start with a letter or single underscore, be less than 32 characters and only consist of alphanumeric characters or underscores.". i think this is fulfilled.
but using
WW_MyWifiDevice
or
_W_MyWifiDevice
is accepted.
i'm running
OPNsense 23.1.1_2-amd64
is this a bug and will this be fixed?
thanx!
3
22.7 Legacy Series / Re: sending datagram to 10.1.1.93:53 failed (on startup)
« on: October 14, 2022, 05:11:08 pm »
hm. i did all my config in the web gui and i can't remember to ever have used netflow.
...but at least it's fixed now ;-)
...but at least it's fixed now ;-)
4
22.7 Legacy Series / Re: sending datagram to 10.1.1.93:53 failed (on startup)
« on: October 14, 2022, 04:44:52 pm »
ok, so this means that everything is fine, right?
THANK YOU VERY MUCH!!!
THANK YOU VERY MUCH!!!
5
22.7 Legacy Series / Re: sending datagram to 10.1.1.93:53 failed (on startup)
« on: October 14, 2022, 04:16:40 pm »
sorry for sending not enough infos!
Generating configuration configd socket missing (@/var/run/configd.socket)
>>> Error in early script 'templates'
and
c_icap already running? (pid=78301).
>>> Error in start script 'c-icap'
Generating configuration configd socket missing (@/var/run/configd.socket)
>>> Error in early script 'templates'
and
c_icap already running? (pid=78301).
>>> Error in start script 'c-icap'
6
22.7 Legacy Series / Re: sending datagram to 10.1.1.93:53 failed (on startup)
« on: October 14, 2022, 02:25:23 pm »
hi franco
it really helps if you know where to look for ;-)
/etc/resov.conf
contains nothing suspicious, but in
/conf/config.xml
i found this IP in the list, defined as targets for netflow
(<targets>10.1.1.93:53,127.0.0.1:2056</targets>).
i can't remember that i have ever used netflow (don't really know what to do with it), so i have no idea how this came in. after deleting this IP from the config, the issue is gone.
so i think that's fine now ;-)
but as i can see now lots of other messages instead, there are two errors shown:
Error in early script 'templates'
and
Error in start script 'c-icap'
are these messages expected or do i need to change anything to get rid of those errors?
thanx very much for your help!
it really helps if you know where to look for ;-)
/etc/resov.conf
contains nothing suspicious, but in
/conf/config.xml
i found this IP in the list, defined as targets for netflow
(<targets>10.1.1.93:53,127.0.0.1:2056</targets>).
i can't remember that i have ever used netflow (don't really know what to do with it), so i have no idea how this came in. after deleting this IP from the config, the issue is gone.
so i think that's fine now ;-)
but as i can see now lots of other messages instead, there are two errors shown:
Error in early script 'templates'
and
Error in start script 'c-icap'
are these messages expected or do i need to change anything to get rid of those errors?
thanx very much for your help!
7
22.7 Legacy Series / sending datagram to 10.1.1.93:53 failed (on startup)
« on: October 14, 2022, 12:19:07 pm »
whenever rebooting OPNsense (running on a pc x86 hardware), i get a few lines of
"sending datagram to 10.1.1.93:53 failed: Invalid argument".
since i updated to OPNsense 22.7.6-amd64, this message is now repeaded for a few pages instead of just a few lines.
where does this message come from? can this just be ignored?
10.1.1.x is one of my local networks behind OPNsense and 10.1.1.93 is within it's dynamic DHCP range, but there's no device with this IP address. so i really wonder what OPNsense tries to do...
"sending datagram to 10.1.1.93:53 failed: Invalid argument".
since i updated to OPNsense 22.7.6-amd64, this message is now repeaded for a few pages instead of just a few lines.
where does this message come from? can this just be ignored?
10.1.1.x is one of my local networks behind OPNsense and 10.1.1.93 is within it's dynamic DHCP range, but there's no device with this IP address. so i really wonder what OPNsense tries to do...
8
22.7 Legacy Series / Re: strange message on logout
« on: September 27, 2022, 08:49:50 pm »
in the mean time, the problem disappeared and logout is as it used to be before...
but without doing any changes or updating something.
but without doing any changes or updating something.
9
22.7 Legacy Series / strange message on logout
« on: September 18, 2022, 01:16:28 pm »
i had to reinstall opnsense today because of a broken update. so now i'm on the latest version again.
as far as i remember, so far, when logging out from opnsense's web gui, the login screen has been shown.
but now, on logout, the browser shows:
Fatal error: Uncaught Error: Class "phpseclib3\Crypt\Common\AsymmetricKey" not found in /usr/local/share/phpseclib/Crypt/RSA.php:73 Stack trace: #0 /usr/local/etc/inc/certs.inc(34): require_once() #1 /usr/local/etc/inc/config.inc(41): require_once('/usr/local/etc/...') #2 /usr/local/www/guiconfig.inc(39): require_once('/usr/local/etc/...') #3 /usr/local/www/index.php(31): require_once('/usr/local/www/...') #4 {main} thrown in /usr/local/share/phpseclib/Crypt/RSA.php on line 73
this looks similar to the message i got in the console on boot, when booting has crashed after the broken update.
so i wonder why i get this message in the browser on logging off from opnsense.
- is this usual behavior with the latest opnsense version?
- is this a severe issue?
- will this be fixed with the next update?
- do i need to do anything else but waiting for the next update?
-
as far as i remember, so far, when logging out from opnsense's web gui, the login screen has been shown.
but now, on logout, the browser shows:
Fatal error: Uncaught Error: Class "phpseclib3\Crypt\Common\AsymmetricKey" not found in /usr/local/share/phpseclib/Crypt/RSA.php:73 Stack trace: #0 /usr/local/etc/inc/certs.inc(34): require_once() #1 /usr/local/etc/inc/config.inc(41): require_once('/usr/local/etc/...') #2 /usr/local/www/guiconfig.inc(39): require_once('/usr/local/etc/...') #3 /usr/local/www/index.php(31): require_once('/usr/local/www/...') #4 {main} thrown in /usr/local/share/phpseclib/Crypt/RSA.php on line 73
this looks similar to the message i got in the console on boot, when booting has crashed after the broken update.
so i wonder why i get this message in the browser on logging off from opnsense.
- is this usual behavior with the latest opnsense version?
- is this a severe issue?
- will this be fixed with the next update?
- do i need to do anything else but waiting for the next update?
-
10
German - Deutsch / Re: opnsense startet nicht mehr nach update !!HILFE!!
« on: September 18, 2022, 01:09:06 pm »
zwischenzeitlich hab ich opnsense neu installiert, basierend auf einem alten image.
so wie's aussieht scheint's nun wieder zu funktionieren.
so wie's aussieht scheint's nun wieder zu funktionieren.
11
22.7 Legacy Series / Re: opnsense is dead after update
« on: September 18, 2022, 01:07:44 pm »
thanx for your support!
in the mean time, i reinstalled an old image and run update for several times.
so far, it looks like opnsense is working fine again.
so this topic can be closed.
in the mean time, i reinstalled an old image and run update for several times.
so far, it looks like opnsense is working fine again.
so this topic can be closed.
12
22.7 Legacy Series / Re: opnsense is dead after update
« on: September 17, 2022, 12:31:06 pm »
yes, i assume that something went wrong while installing the updates.
i've seen before that the ramdisk with the log files was almost full. i assumed that updates are done using the ssd. so if they use the ramdisk instead, this could be the reason for failing.
so the question is now how to get out of this situation...
is there a way to revert to the old version, i.e. to 22.7.2?
i've seen before that the ramdisk with the log files was almost full. i assumed that updates are done using the ssd. so if they use the ramdisk instead, this could be the reason for failing.
so the question is now how to get out of this situation...
is there a way to revert to the old version, i.e. to 22.7.2?
13
German - Deutsch / Re: opnsense startet nicht mehr nach update !!HILFE!!
« on: September 17, 2022, 10:47:51 am »
einen hw defekt schliesse ich eigentlich aus. die hw ist etwa 3 jahre alt und bis zum update lief alles absolut störungsfrei.
die sache mit geblähten elkos ist eigentlich schon einige jahre kein thema mehr.
die sache mit geblähten elkos ist eigentlich schon einige jahre kein thema mehr.
14
22.7 Legacy Series / Re: opnsense is dead after update
« on: September 17, 2022, 10:10:42 am »
i'm really not sure which version this was.
as far as i remember, maybe 1-2 month ago, there was a mayor update, and after updating, there were again a few patches that had to be installed. so then i was on the latest version.
then last time i checked (might be 2-3 weeks ago), there were no updates available.
yesterday then, i've seen that there were updates (i remember the number 34, but i'm not sure if this was the number of patches to be installed) and i accepted to update...
and this crashed my system.
is there somewhere a log where i can see the details?
as far as i remember, maybe 1-2 month ago, there was a mayor update, and after updating, there were again a few patches that had to be installed. so then i was on the latest version.
then last time i checked (might be 2-3 weeks ago), there were no updates available.
yesterday then, i've seen that there were updates (i remember the number 34, but i'm not sure if this was the number of patches to be installed) and i accepted to update...
and this crashed my system.
is there somewhere a log where i can see the details?
15
22.7 Legacy Series / Re: opnsense is dead after update
« on: September 17, 2022, 10:03:42 am »
i'm quite sure that there's no such entry. at least grep can't find it too.