10444 questions

12453 answers

19377 comments

21853 members

0 votes
177 views 3 comments
by

Dear Comunity,
I have issue with my fresh bought RUT950 (FW ver.: RUT9XX_R_00.06.07.7)
I am monitoring/controlling router with my own software (communication based on PyModbus library),
I can see after some period of proper communication, router starts responding with input registers to my holding registers request:

TCP dump from router:

No.    Time    Source    Destination    Protocol    Length    Info
34240    653.251509    192.168.3.100    192.168.3.1    Modbus/TCP    79    Response: Trans:  9849; Unit:   1, Func:   3: Read Holding Registers
34249    653.656460    192.168.3.1    192.168.3.100    Modbus/TCP    78       Query: Trans:  9850; Unit:   1, Func:   3: Read Holding Registers
34251    653.657071    192.168.3.100    192.168.3.1    Modbus/TCP    79    Response: Trans:  9850; Unit:   1, Func:   3: Read Holding Registers
34259    653.761472    192.168.3.1    192.168.3.100    Modbus/TCP    78       Query: Trans:  9851; Unit:   1, Func:   3: Read Holding Registers
34261    653.816600    192.168.3.100    192.168.3.1    Modbus/TCP    79    Response: Trans:  9851; Unit:   1, Func:   3: Read Holding Registers
34269    653.921070    192.168.3.1    192.168.3.100    Modbus/TCP    78       Query: Trans:  9852; Unit:   1, Func:   3: Read Holding Registers
34271    653.978999    192.168.3.100    192.168.3.1    Modbus/TCP    107    Response: Trans:  9852; Unit:   1, Func:   3: Read Holding Registers
34279    654.088174    192.168.3.1    192.168.3.100    Modbus/TCP    78       Query: Trans:  9853; Unit:   1, Func:   3: Read Holding Registers
34281    654.146484    192.168.3.100    192.168.3.1    Modbus/TCP    107    Response: Trans:  9853; Unit:   1, Func:   3: Read Holding Registers
34289    654.251090    192.168.3.1    192.168.3.100    Modbus/TCP    78       Query: Trans:  9854; Unit:   1, Func:   3: Read Holding Registers
34291    654.253821    192.168.3.100    192.168.3.1    Modbus/TCP    77    Response: Trans:  9854; Unit:   1, Func:   3: Read Holding Registers
34299    654.358234    192.168.3.1    192.168.3.100    Modbus/TCP    78       Query: Trans:  9855; Unit:   1, Func:   3: Read Holding Registers
34301    654.360071    192.168.3.100    192.168.3.1    Modbus/TCP    74    Response: Trans:  9855; Unit: 131, Func:   4: Read Input Registers[Malformed Packet]
34310    654.766112    192.168.3.1    192.168.3.100    Modbus/TCP    78       Query: Trans:  9856; Unit:   1, Func:   3: Read Holding Registers
34312    654.766787    192.168.3.100    192.168.3.1    Modbus/TCP    79    Response: Trans:  9856; Unit:   1, Func:   3: Read Holding Registers
34320    654.872266    192.168.3.1    192.168.3.100    Modbus/TCP    78       Query: Trans:  9857; Unit:   1, Func:   3: Read Holding Registers
34322    654.874172    192.168.3.100    192.168.3.1    Modbus/TCP    74    Response: Trans:  9857; Unit: 131, Func:   4: Read Input Registers[Malformed Packet]
34332    654.978056    192.168.3.1    192.168.3.100    Modbus/TCP    78       Query: Trans:  9858; Unit:   1, Func:   3: Read Holding Registers

As you can see after some time (20-30 min) system starts replying with input register to holding register request
What interesting it looses only part of sensors (registers 3,103, 139 (RSSI, net type, net info) are first in line to be shoot, register 205 (SIM in use) mostly like 2 mins after first line, and reg 1 (uptime) always works good). 

When looking at log files i can observe some errors/criticals in system.log:

Thu Apr 22 10:11:19 2021 user.notice firewall: Reloading firewall due to ifup of ppp (wwan0)
Thu Apr 22 10:11:19 2021 user.info Messaged[20018]: Start from new event "Backup" "Switched to main WAN (Mobile)"
Thu Apr 22 10:11:19 2021 local1.notice fwblock[20028]: Started fwblock
Thu Apr 22 10:11:19 2021 local1.notice fwblock[20028]: Applying SSH blocks
Thu Apr 22 10:11:19 2021 local1.notice fwblock[20028]: Applying WebUI blocks
Thu Apr 22 10:11:23 2021 local1.crit luci-reload[20375]: START==1
Thu Apr 22 10:11:24 2021 daemon.err insmod: module is already loaded - xt_multiport
Thu Apr 22 10:11:24 2021 daemon.err insmod: module is already loaded - xt_connmark
Thu Apr 22 10:11:24 2021 daemon.err insmod: module is already loaded - xt_comment
Thu Apr 22 10:11:24 2021 daemon.err insmod: module is already loaded - xt_length
Thu Apr 22 10:11:27 2021 local1.crit hotplug-netifd-netstate[20581]: ERROR: uci set (set)
Thu Apr 22 10:11:27 2021 local1.crit hotplug-netifd-netstate[20581]: ERROR code: uci err: Invalid argument
Thu Apr 22 10:11:27 2021 local1.info hotplug-gsmstate[20589]: envACT: ifup
Thu Apr 22 10:11:27 2021 local1.info hotplug-gsmstate[20589]: envDEV: wwan0
Thu Apr 22 10:11:29 2021 daemon.err insmod: module is already loaded - xt_multiport
Thu Apr 22 10:11:29 2021 daemon.err insmod: module is already loaded - xt_connmark
Thu Apr 22 10:11:29 2021 daemon.err insmod: module is already loaded - xt_comment
Thu Apr 22 10:11:29 2021 daemon.err insmod: module is already loaded - xt_length
Thu Apr 22 10:11:33 2021 daemon.err insmod: module is already loaded - xt_multiport
Thu Apr 22 10:11:33 2021 daemon.err insmod: module is already loaded - xt_connmark
Thu Apr 22 10:11:33 2021 daemon.err insmod: module is already loaded - xt_comment
Thu Apr 22 10:11:33 2021 daemon.err insmod: module is already loaded - xt_length
Thu Apr 22 10:12:19 2021 local1.crit luci-reload[23059]: START==1
Thu Apr 22 10:12:19 2021 local1.crit luci-reload[23059]: IF|
Thu Apr 22 10:12:19 2021 user.info Messaged[23075]: Start from new event "CONFIG" "Administration configuration has been changed"
Thu Apr 22 10:24:28 2021 local1.crit luci-reload[2596]: START==1
Thu Apr 22 10:24:42 2021 local1.crit luci-reload[2669]: START==1
Thu Apr 22 10:25:42 2021 user.info Messaged[2879]: Start from new event "Web UI" "TCP dump .pcap file was downloaded!"
Thu Apr 22 10:25:48 2021 local1.crit luci-reload[2952]: START==1

But when problem with modbus starts, I meet also issues with web UI, as:

http://192.168.3.100/cgi-bin/luci/;stok=54478fdc829886b7ce084af440b6fa97/admin/network/mobile
/usr/lib/lua/luci/dispatcher.lua:224: Failed to execute function dispatcher target for entry '/admin/network/mobile'.
The called action terminated with an exception:
/usr/lib/lua/luci/dispatcher.lua:224: Failed to execute cbi dispatcher target for entry '/admin/network/mobile/general'.
The called action terminated with an exception:
...b/lua/luci/model/cbi/admin_network/ifaces_mobile.lua:3: attempt to index local 'M' (a nil value)
stack traceback:
    [C]: in function 'assert'
    /usr/lib/lua/luci/dispatcher.lua:224: in function 'dispatch'
    /usr/lib/lua/luci/dispatcher.lua:98: in function </usr/lib/lua/luci/dispatcher.lua:98>

When I am trying to enter mobile settings. Also some dynamic data stopping to refresh on main page.
After restart of router all goes back to normal for another 20-30 min

I ve tried  to perform factory reset as well as downgrade (through web UI and bootloader) to versions RUT9XX_R_00.06.07.5 and RUT9XX_R_00.06.07, but with same result, so finally went back to RUT9XX_R_00.06.07.7

Once after downgrade 06.07.7 ->06.07.5 system was unable to connect to modem (as per mobile settings page), but when used "restart modem" option in mobile monitoring, communication was restored.

1 Answer

0 votes
by
Hello,

Could you download a troubleshoot file from your router when this issue occurs? You can do that by navigating System > Administration > Troubleshoot. Please send the file via private message and could you tell if this behavior is reproduced itself on a single router or you do have more?

Regards.
by
Hi VykintasKuzma,

Files sent to you on 5 of May.
by
How did you go with a resolution for this? I am getting the "local1.crit luci-reload" errors on one of our devices and need to work out how to fix it.
by
Hi Sam,

I have not received solution yet (and seems I'll not get further answers) . I've figured out problem is not appearing after downgrading to fw 06.05.3 (there are other issues, but at least router is stable).

Please keep in mind in my case problem is related to modbus communication  and can be reproduced on other router. If you have problem on one device only, I would suspect:

-hardware failure (replace router)

-config mismatch (compare carefuly with working device)

-filesystem error (reload software)