You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running the following command reveals the issue with the ip -j address command:
root@firewall:~# ip -j address | jq
parse error: Invalid string: control characters from U+0000 through U+001F must be escaped at line 1, column 3929
Expected behavior
The interface list should load properly without errors.
Actual behavior
The error is traced to invalid characters in the output of the ip -j address command, which causes the JSON to fail.
Investigation
The issue is related to a bad character or string in one of the interfaces created by qosify. Specifically, the interface ifb-pp<bad_char> causes issues with both the ifconfig and the JSON output of the ip command.
If the qosify service is stopped, the issue goes away:
/etc/init.d/qosify stop
Workaround
A temporary fix involves renaming the interface, particularly for pppoe interfaces, to shorter names (max 5 characters, avoiding special characters) to prevent this issue. For Ethernet interfaces, the name length limit is 13 characters.
This issue likely appeared after enabling qosify.
Additional context
If the partner cannot rename the pppoe interface due to system access limitations, the issue might persist until this can be done.
Components
NethSecurity Image: 8-23.05.4-ns.1.2.0
The text was updated successfully, but these errors were encountered:
Steps to reproduce
Create a PPPoE WAN interface named
WAN1_WiMe
.Enable QoS on the
WAN1_WiMe
interface.On a NethSecurity system, attempt to access the interface page from the GUI.
The system fails to load with an error, and logs show the following:
Running the following command reveals the issue with the
ip -j address
command:Expected behavior
Actual behavior
ip -j address
command, which causes the JSON to fail.Investigation
The issue is related to a bad character or string in one of the interfaces created by
qosify
. Specifically, the interfaceifb-pp<bad_char>
causes issues with both theifconfig
and the JSON output of theip
command.If the
qosify
service is stopped, the issue goes away:Workaround
A temporary fix involves renaming the interface, particularly for
pppoe
interfaces, to shorter names (max 5 characters, avoiding special characters) to prevent this issue. For Ethernet interfaces, the name length limit is 13 characters.This issue likely appeared after enabling
qosify
.Additional context
pppoe
interface due to system access limitations, the issue might persist until this can be done.Components
NethSecurity Image: 8-23.05.4-ns.1.2.0
The text was updated successfully, but these errors were encountered: