Wireguard display issues with 2.7.0.a.20221209.0600
-
Upgraded to 2.7.0.a.20221209.0600 this morning and wireguard is showing all of the config on in the Status Widgets + config page (wg/vpn_wg_tunnels.php) + status (/wg/status_wireguard.php)
WG is working but unable to edit config directly from the config page but can get to it from the status page.
array(4) { [0]=> string(7) "pfsense" [1]=> string(17) "installedpackages" [2]=> string(5) "avahi" [3]=> string(6) "config" } array(1) { [0]=> array(17) { ["enable"]=> string(3) "yes" ["carpstatusvid"]=> string(4) "none" ["action"]=> string(5) "allow" ["interfaces"]=> string(18) "lan,opt1,opt4,opt5" ["disable_ipv4"]=> string(0) "" ["disable_ipv6"]=> string(3) "yes" ["reflection"]=> string(3) "yes" ["override_hostname"]=> string(0) "" ["override_domain"]=> string(8) "REMOVED" ["publishing"]=> string(3) "yes" ["publish_addresses"]=> string(3) "yes" ["publish_hinfo"]=> string(3) "yes" ["publish_workstation"]=> string(3) "yes" ["publish_domain"]=> string(3) "yes" ["publish_ipv4_aaaa"]=> string(0) "" ["publish_ipv6_a"]=> string(0) "" ["filtering"]=> string(0) "" } } array(4) { [0]=> string(7) "pfsense" [1]=> string(17) "installedpackages" [2]=> string(9) "wireguard" [3]=> string(6) "config" } array(1) { [0]=> array(7) { ["enable"]=> string(2) "on" ["keep_conf"]=> string(3) "yes" ["resolve_interval"]=> string(3) "300" ["resolve_interval_track"]=> string(3) "yes" ["interface_group"]=> string(3) "all" ["hide_secrets"]=> string(3) "yes" ["hide_peers"]=> string(3) "yes" } } array(4) { [0]=> string(7) "pfsense" [1]=> string(17) "installedpackages" [2]=> string(16) "shellcmdsettings" [3]=> string(6) "config" } array(1) { [0]=> array(3) { ["cmd"]=> string(24) "service wireguardd start" ["cmdtype"]=> string(13) "earlyshellcmd" ["description"]=> string(45) "WireGuard earlyshellcmd (DO NOT EDIT/DELETE!)" } } array(4) { [0]=> string(7) "pfsense" [1]=> string(17) "installedpackages" [2]=> string(8) "arpwatch" [3]=> string(6) "config" } array(1) { [0]=> array(11) { ["enable"]=> string(0) "" ["active_interfaces"]=> string(9) "opt4,opt5" ["notifications_recipient"]=> string(18) "REMOVED" ["disable_cron"]=> string(2) "on" ["zeropad"]=> string(2) "on" ["disable_carp"]=> string(2) "on" ["disable_bogons"]=> string(0) "" ["disable_zero"]=> string(0) "" ["update_vendors"]=> string(2) "on" ["clear_database"]=> string(2) "on" ["row"]=> array(2) { [0]=> array(2) { ["mac"]=> string(17) "70:85:c2:72:76:49" ["notification_type"]=> string(3) "all" } [1]=> array(2) { ["mac"]=> string(17) "8e:14:0e:1c:e2:5e" ["notification_type"]=> string(3) "all" } } } } array(4) { [0]=> string(7) "pfsense" [1]=> string(17) "installedpackages" [2]=> string(10) "bandwidthd" [3]=> string(6) "config" } array(1) { [0]=> array(14) { ["enable"]=> string(2) "on" ["active_interface"]=> string(4) "opt1" ["interface_array"]=> array(4) { [0]=> string(3) "lan" [1]=> string(4) "opt1" [2]=> string(4) "opt4" [3]=> string(4) "opt5" } ["subnets_extra"]=> string(13) "172.16.5.0/24" -
That was an issue with that particular snapshot, it's not wireguard specific, it's fixed on any snapshot after that.
-
@jimp Thanks, ill update next time I get back home
-
I can confirm that I had this issue a couple of weeks ago, and that after updating to a newer snapshot today it is fixed.
