A problem was detected. Click here for more information.

Started by cranky, March 27, 2021, 03:15:18 PM

Previous topic - Next topic
So i get this message on top, and see this error:

User-Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.90 Safari/537.36
FreeBSD 12.1-RELEASE-p12-HBSD #0  3c6040c7243(stable/21.1)-dirty: Mon Jan 25 12:27:52 CET 2021     root@sensey:/usr/obj/usr/src/amd64.amd64/sys/SMP amd64
OPNsense 21.1 500892915
Plugins os-dyndns-1.23
Time Sat, 27 Mar 2021 15:15:00 +0100
OpenSSL 1.1.1i  8 Dec 2020
PHP 7.3.26


[27-Mar-2021 15:03:32 Europe/Amsterdam] PHP Warning:  implode(): Invalid arguments passed in /usr/local/www/firewall_nat_edit.php on line 216

All i did was make port forwards with aliasses for port ranges (they are formed port:port).


March 27, 2021, 06:41:40 PM #2 Last Edit: March 27, 2021, 06:47:46 PM by marjohn56
Quote from: cranky on March 27, 2021, 03:15:18 PM

All i did was make port forwards with aliasses for port ranges (they are formed port:port).
Where does it say you can enter port ranges?


Edit: Interesting, never noticed that, but it works on my chrome , same version. I am running OPNsense 21.7.a_268-amd64, so if there was a bug, it may well have been fixed.
OPNsense 25.7a - Qotom Q355G4 - ISP - Squirrel 1Gbps.

Team Rebellion Member

i removed the aliasses, and just used the premade fields, this makes the error go away. (see screenshot)
However, port forwarding doesnt seem to work , in any way shape or form.

> OPNsense 21.1 500892915

Why no update to 21.1.3 before report? :)


Cheers,
Franco

Because i was updating every time, but i cant get fowards to work, so i reinstalled the machine again from usb.
I was planning on upgrade as soon as i have forwards working.
But ill make sure i upgrade before i post anything again.

I'm pretty sure this warning got fixed in 21.1.1 or 21.1.2. It's a warning but has no operational impact. Long story short a lot of buzz for no gain.


Cheers,
Franco

Quote from: franco on March 27, 2021, 07:42:19 PM
I'm pretty sure this warning got fixed in 21.1.1 or 21.1.2. It's a warning but has no operational impact. Long story short a lot of buzz for no gain.


Cheers,
Franco

Updated and the error is indeed gone.
However, portforwarding is still a nogo. :/

Quote from: marjohn56 on March 27, 2021, 06:41:40 PM
Quote from: cranky on March 27, 2021, 03:15:18 PM

All i did was make port forwards with aliasses for port ranges (they are formed port:port).
Where does it say you can enter port ranges?

In the manual, under aliasses, it says you can specify a port range, for now i did it manually tho.