1
22.7 Legacy Series / Re: OPNSense 22.7_4 - Fatal error: Uncaught TypeError while setting WAN properties
« on: August 10, 2022, 03:23:30 am »
Thanks @franco
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.
Pages: [1]
2
22.7 Legacy Series / Re: OPNSense 22.7_4 - Fatal error: Uncaught TypeError while setting WAN properties
« on: August 09, 2022, 12:50:19 pm »
I also found that NAT is not working using WIFI as a WAN
in ifconfig the interface appears as iwm0_wlan0 but the NAT does not see this, so no automatic rules are generated.
Adding manual rules looks like
rdr nat on iwm0 inet …
manually change rules to change to iwmo_wlan0 appears to work
so fix is to edit /conf/config.xml from:
<wan><if>iwm0</if>
to be
<wan><if>iwm0_wlan0</if>
Next disable outbound NAT, save, apply.
Finally re enable automatic Nat, save, apply.
Now have working NAT with WIFI WAN.
in ifconfig the interface appears as iwm0_wlan0 but the NAT does not see this, so no automatic rules are generated.
Adding manual rules looks like
rdr nat on iwm0 inet …
manually change rules to change to iwmo_wlan0 appears to work
so fix is to edit /conf/config.xml from:
<wan><if>iwm0</if>
to be
<wan><if>iwm0_wlan0</if>
Next disable outbound NAT, save, apply.
Finally re enable automatic Nat, save, apply.
Now have working NAT with WIFI WAN.
3
22.7 Legacy Series / Re: OPNSense 22.7_4 - Fatal error: Uncaught TypeError while setting WAN properties
« on: August 09, 2022, 10:33:46 am »
Seems like it is a problem if WLAN is selected as a WAN device. The php tries to access:
$a_interfaces["wireless"]["mode"] but the wireless element is not an object, it is an empty string.
As a workaround I tried setting the mode in /config/config.xml i.e. find the line in the right interface block which shows:
<wireless/>
and use "vi" change it to
<wireless><mode>bss</mode></wireless>
this suppresses the error and allows further configuration.
After this I a was able to see that the wlan associated.
(all done via a shell from the console)
$a_interfaces["wireless"]["mode"] but the wireless element is not an object, it is an empty string.
As a workaround I tried setting the mode in /config/config.xml i.e. find the line in the right interface block which shows:
<wireless/>
and use "vi" change it to
<wireless><mode>bss</mode></wireless>
this suppresses the error and allows further configuration.
After this I a was able to see that the wlan associated.
(all done via a shell from the console)
4
20.7 Legacy Series / Re: Wireguard not working after upgrade.
« on: August 03, 2020, 09:19:51 am »
Deleting the 192.161.1.0/24 from the list, leaving only the Wireguard-IP/32 in all endpoints allows it to start
Also I can still ssh to a LAN machine at 192.168.1.100 so there seems to be no need to have that local setting in the endpoint config.
The web ui is also accessible with this setting.
Also I can still ssh to a LAN machine at 192.168.1.100 so there seems to be no need to have that local setting in the endpoint config.
The web ui is also accessible with this setting.
5
20.7 Legacy Series / Re: EFI boot fail: Device Path not found (20.7 fresh install) [SOLVED]
« on: August 03, 2020, 08:27:01 am »
It turns ou that the UEFI boot manager was set to boot "UEFI OS" first
then UEFI on the first HD
Solution was to delete the "UEFI OS" entry form the the UEFI boot list; then the system booted normally.
To be sure I did a reboot and a power-off for the console menu. Reboot ewas normal in both cases
then UEFI on the first HD
Solution was to delete the "UEFI OS" entry form the the UEFI boot list; then the system booted normally.
To be sure I did a reboot and a power-off for the console menu. Reboot ewas normal in both cases
6
20.7 Legacy Series / EFI boot fail: Device Path not found (20.7 fresh install) [SOLVED]
« on: August 03, 2020, 07:49:20 am »
Installed from: OPNsense-20.7-OpenSSL-vga-amd64.img.bz2
It seems that the loader is not getting the correct "currdev" setting and showing this error:
The system is then not responsive to keyboard
If I hit space immediately and type these command the system starts normally:
Is there a way to det the "currdev" value for the loader? Possibly it is an EFI setting?
It seems that the loader is not getting the correct "currdev" setting and showing this error:
Code: [Select]
Ignoring boot0002: Device Path not found
Failed to find bootable partitionThe system is then not responsive to keyboard
If I hit space immediately and type these command the system starts normally:
Code: [Select]
set currdev=disk0p3
load /boot/kernel/kernel
bootIs there a way to det the "currdev" value for the loader? Possibly it is an EFI setting?
Pages: [1]