HELP: NETGATE 3100 - After updating from 22.05 to 23.01 unable to create/use GIF interfaces
-
Can you see what's in your config file when you hit that error?
Or the exact steps required to replicate it?
-
@stephenw10 Replicating it is easy:
- Navigate to Interfaces->Assignments, GIFs tab.
- Click + Add.
- Enter server IP address, GIF tunnel local address, and GIF tunnel remote address as appropriate (I took mine from my HE tunnel page).
- Select 64 for GIF tunnel subnet.
- Do not select ECN friendly behavior or Outer Source Filtering.
- Enter "HE IPv6 tunnel" for description.
- Click Save.
Expected result: GIF interface is created.
Actual result: PHP error:Fatal error: Uncaught TypeError: pfSense_interface_flags(): Argument #1 ($ifname) must be of type string, array given in /etc/inc/interfaces.inc:44 Stack trace: #0 /etc/inc/interfaces.inc(44): pfSense_interface_flags(Array, 1) #1 /etc/inc/interfaces.inc(1271): interfaces_bring_up(Array) #2 /usr/local/www/interfaces_gif_edit.php(124): interface_gif_configure(Array) #3 {main} thrown in /etc/inc/interfaces.inc on line 44 PHP ERROR: Type: 1, File: /etc/inc/interfaces.inc, Line: 44, Message: Uncaught TypeError: pfSense_interface_flags(): Argument #1 ($ifname) must be of type string, array given in /etc/inc/interfaces.inc:44 Stack trace: #0 /etc/inc/interfaces.inc(44): pfSense_interface_flags(Array, 1) #1 /etc/inc/interfaces.inc(1271): interfaces_bring_up(Array) #2 /usr/local/www/interfaces_gif_edit.php(124): interface_gif_configure(Array) #3 {main} thrown
-
Mmm, there must be something existing in your config or missing from that would usually be there by default when you attempt to apply that. It doesn't happen on a clean config as far as I can tell. Or at least I've failed to replicate it so far.
-
@stephenw10 I can send you my config, if you like. Just let me know where to send it.
-
Yes, please upload it here: https://nc.netgate.com/nextcloud/s/3kdTjgDRRC2txeQ
-
@stephenw10 Done.
-
Thanks. When you hit this error does the tunnel actually get created? Do you get additional config in the file?
-
@stephenw10 I don't know where to look at the config file (I'm ont a BSD guy), but Interfaces->Assignments, Interface Assignments tab, does not show the interface to assign.
-
If you look in Diag > Backup > Config History you can see any changes to the config file.
-
@stephenw10 Nope...last thing in the config history is the deletion of the GIF interface that I did trying to resolve the initial problem.
-
@stephenw10 I see the Redmine case is marked "more information needed". I'll be happy to provide more, but I still can't get the verification email from Redmine. What else is needed?
-
The same email address you're using here?
-
@stephenw10 Yes, that is correct.
-
Hmm, I'd try again, check you junk mail etc. The logs this end show the email being sent on March 4th at 8.07.
-
@stephenw10 No mail in my spam folder or anywhere else, either. I just asked for a re-send again...not received yet, but I'll keep looking.
Edit: ...and, of course,. as soon as I post that, it shows up. Activated.
-
Just to confirm you also had a Hurricane Electric tunnel?
Do you still see that error if you remove the WANV6_HE_TUNNEL_TUNNELV6 gateway before recreating the tunnel?
-
@stephenw10 Yes, it's a Hurricane Electric tunnel.
And deleting the gateway gives the same error on attempting to create the GIF.
-
Had EXACTLY the same issue, the same error, even the same line numbers in stacktrace
Rebooting pfSense did helped nothing.
But...
Menu Diagnostics -> Command Prompt -> Execute shell command
kldxref /boot/kernel/
Click execute
and now everything works just fine.
Created new GIF interface, ping is working fine. After reboot interface is up and everything looks fine -
Yes, we discovered later than the same error can affect multiple tunnel types:
https://redmine.pfsense.org/issues/13963Steve
-
This is a bit different from the tuntap issue. I've captured the details here. armv7 kernels currently differ from arm64 and amd64 in that they do not statically link the if_gif module, so it must be loaded at runtime. A change has been authored for this and an update to the System Patches package is forthcoming.