Project

General

Profile

Actions

Regression #16105

closed

Config access error after changing an interface from DHCP to Static

Added by Steve Wheeler about 1 month ago. Updated 26 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Interfaces
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
25.03
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

When changing an interface from DHCP to Static the following error is shown:

Mar 23 16:51:02     php-fpm     10244     /interfaces.php: Configuration Change: admin@172.21.16.8 (Local Database): Interfaces settings changed
Mar 23 16:51:02     check_reload_status     731     Syncing firewall
Mar 23 16:51:02     php-fpm     10244     /interfaces.php: config warning: invalid path "gateways/gateway_item/" at /etc/inc/gwlb.inc:2402
Mar 23 16:51:02     php-fpm     10244     /interfaces.php: config warning: invalid path "gateways/gateway_item/" at /etc/inc/gwlb.inc:2459
Mar 23 16:51:02     php-fpm     10244     /interfaces.php: Configuration Change: admin@172.21.16.8 (Local Database): Gateway settings changed 

Tested in 24.11 and 25.03

Actions #1

Updated by Marcos M about 1 month ago

  • Category changed from Configuration Backend to Interfaces
  • Status changed from Confirmed to In Progress
  • Assignee set to Marcos M
Actions #2

Updated by Marcos M about 1 month ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 100
Actions #3

Updated by Marcos M about 1 month ago

  • Status changed from Feedback to Resolved
Actions #4

Updated by Jay Sols 28 days ago

Still seeing this error in 25.03 after applying patch to 3/6 beta.

Actions #5

Updated by Marcos M 28 days ago

Thanks for testing! A followup fix can be applied with f51505bf15e7af39c909d63356089d5e247cf781.

Actions #6

Updated by Jay Sols 26 days ago

Success, appears to be working in 25.03beta and 24.11. It should be noted, both patches above need to be applied in respective order. Applying the ...f781 without the ...5f60 will not work.

Also, when reverting back to dhcp, default gateway (under routing) remains set to the statically assigned gateway. By design?

Actions

Also available in: Atom PDF