Network page error

[ceejayemm]

I have just updated 2 RPi (1 x 3A and 1 x 3B+) to 20241011 and now I get the following error on the Network Page, always on the 3A but intermittently on the 3B+ :

Errors: Bad control character in string literal in JSON at position 244 (line 11 column 32) 
{
  "page" : "networks"
, "devicebt"    : true
, "deviceeth"   : false
, "devicewl"    : true
, "ap"          : false
, "apconf"      : false
, "apstartup"   : false
, "camilladsp"  : false
, "connectedwl" : true
, "gateway"     : "192.168.86.1>
wlan0"
, "hostname"    : "raudio-1.cmhomenet.lan"
, "ipsub"       : "192.168.86."
, "ipwl"        : "192.168.86.35"
, "listbt"      : [ { "mac" : "08:EB:ED:7F:C8:B7" , "name" : "SoundCore 2" , "connected" : false , "type" : "Sink" } ]
, "listeth"     : {
  "ADDRESS" : "192.168.86.35
192.168.86.35"
, "GATEWAY" : "192.168.86.1
wlan0"
, "STATIC"  : false
}
, "listwl"      : [ {
  "dbm"     : -46
, "gateway" : "192.168.86.1"
, "ip"      : "192.168.86.35"
, "ssid"    : "CMHomeNET"
} ]
}

Chris

[rern]

Please post output of: ip r

[ceejayemm]

As requested,

From wireless RPi 3A+:

rAudio-1:~  #  ip r
default via 192.168.86.1 dev wlan0 proto dhcp src 192.168.86.35 metric 3002 
192.168.86.0/24 dev wlan0 proto dhcp scope link src 192.168.86.35 metric 3002 

From wired RPi 3B+

RAOffice:~  #  ip r
default via 192.168.86.1 dev enu1u1 proto dhcp src 192.168.86.31 metric 1024 
192.168.86.0/24 dev enu1u1 proto kernel scope link src 192.168.86.31 metric 1024 
192.168.86.1 dev enu1u1 proto dhcp scope link src 192.168.86.31 metric 1024 
192.168.86.11 dev enu1u1 proto dhcp scope link src 192.168.86.31 metric 1024 

Thanks

Chris

[ceejayemm]

@rern
Did the information above provide any insights ?

Chris

[ceejayemm]

@rern
Still the same issue after update to 20241025.

Chris

[rern]

Please try:
sed -i 's/grep -v ^/grep -m1 -v ^/' /srv/http/bash/settings/networks-data.sh

[ceejayemm]

@rern
I am afraid this command makes no difference, the same error is shown after I have applied it.

Regards.

Chris

[rern]

Then try the UPDATE.

[ceejayemm]

@rern
Thanks, the Update branch resolves this issue.

Many thanks

Chris