Bug #13933
closed
Unable to make modifications to vlan descriptions
0%
Description
The issue is focused on interface heirarchy.
1. Attempting to change vlan description <clicking save> does not result in a changed description.
2. Re-assigning a network port results in the GUI showing the original assignment but the ARP table shows requests being received on new interface selected.
The fix so far is to edit the config.xml file and then clear the config cache.
Additionally, odd behavior occurs while changing an interface description where all interfaces seem to go through a soft reboot. newwanip script runs. This can be reproduced.
Feb 5 13:36:47 php-fpm 74771 /rc.newwanip: Netgate pfSense Plus package system has detected an IP change or dynamic WAN reconnection - 192.168.14.254 -> 192.168.14.254 - Restarting packages.
The issue is being tracked.
https://forum.netgate.com/topic/177571/unable-to-reassign-network-port/4?_=1675622285894
Files
Updated by Mike Moore over 2 years ago
- File interfaces down.JPG interfaces down.JPG added
Uploading log output jpeg. This occurs each time the vlan description is attempted to be changed but doesn't. There is a subsequent network outage.
Updated by Mike Moore over 2 years ago
This is a reproducible issue. Changes to VLAN description cause all interfaces to flap. I have the system.log file to show. Below is the snippet. Whatever the issue is here is most likly the reason why if you attempt to change network ports in the GUI, changes are not reflected in the GUI. If you make a change to the config.xml then changes are reflected in the GUI.
Feb 5 18:46:49 GA-FW1 kernel: igc2: link state changed to DOWN
Feb 5 18:46:49 GA-FW1 kernel: igc3: link state changed to DOWN
Feb 5 18:46:49 GA-FW1 kernel: lagg0: link state changed to DOWN
Feb 5 18:46:49 GA-FW1 kernel: lagg0.3: link state changed to DOWN
Feb 5 18:46:49 GA-FW1 kernel: lagg0.23: link state changed to DOWN
Feb 5 18:46:49 GA-FW1 kernel: lagg0.11: link state changed to DOWN
Feb 5 18:46:49 GA-FW1 kernel: lagg0.14: link state changed to DOWN
Feb 5 18:46:49 GA-FW1 kernel: lagg0.15: link state changed to DOWN
Feb 5 18:46:49 GA-FW1 kernel: vlan4: changing name to 'lagg0.17'
Feb 5 18:46:49 GA-FW1 check_reload_status423: Linkup starting igc2
Feb 5 18:46:49 GA-FW1 check_reload_status423: Linkup starting igc3
Feb 5 18:46:49 GA-FW1 check_reload_status423: Linkup starting lagg0
Feb 5 18:46:49 GA-FW1 tailscaled63392: 2023/02/05 18:46:49 magicsock: endpoints changed: 162.193.210.96:41641 (stun), 10.6.106.1:41641 (local), 10.32.112.190:41641 (local), 172.26.0.1:41641 (local), 172.28.0.2:41641 (local), 172.29.0.1:41641 (local), 192.168.3.1:41641 (local), 192.168.3.5:41641 (local), 192.168.11.254:41641 (local), 192.168.14.254:41641 (local), 192.168.15.1:41641 (local), 192.168.15.40:41641 (local), 192.168.15.77:41641 (local), 192.168.15.222:41641 (local), 192.168.15.241:41641 (local), 192.168.23.254:41641 (local), 192.168.50.100:41641 (local), 192.168.50.254:41641 (local)
Feb 5 18:46:49 GA-FW1 check_reload_status423: Linkup starting lagg0.3
Feb 5 18:46:49 GA-FW1 check_reload_status423: Linkup starting lagg0.23
Feb 5 18:46:49 GA-FW1 check_reload_status423: Linkup starting lagg0.11
Feb 5 18:46:49 GA-FW1 check_reload_status423: Linkup starting lagg0.14
Feb 5 18:46:49 GA-FW1 check_reload_status423: Linkup starting lagg0.15
Feb 5 18:46:49 GA-FW1 php-fpm82172: /interfaces_vlan_edit.php: Gateway, NONE AVAILABLE
Updated by Jim Pingle over 2 years ago
- Status changed from New to Rejected
I can't reproduce this as stated. Changes to descriptions are immediately reflected as expected. They are stored in the config and visible in the GUI, even on 22.05.
Any change to a VLAN will trigger it to be reconfigured on the parent interface and in some cases that may lead to an interface event as you see. However, that wouldn't affect the state of the firewall configuration.
Whatever you are seeing is almost certainly something in your environment, hardware, configuration, or packages. Without a lot more information, or at least a method to reproduce it on a fresh installation / minimal configuration, there isn't anything actionable here.
Updated by Mike Moore over 2 years ago
Although not a stock install of pfsense as there are other packages that needed to be installed via the repo[pfblockerNG, WireGuard] what could impact the state of the interfaces? If there is any input i can give to move this along please let me know.
Do i need to upload my config.xml so that you can review it? Is there a SFTP drop I can send this to? I can send any/all logs.
Nevertheless, an attempt to change the vlan description immediately results in all interfaces dropping. Whats the link?
Updated by Jim Pingle over 2 years ago
This site is not for support or diagnostic discussion, so that is something you'd need to keep on the forum thread and not here until a more definitive conclusion is reached.