search

Ansuel / tch-nginx-gui

Modified file to apply to a stock technicolor GUI
GNU General Public License v3.0
343 stars 52 forks source link

Extension Card missing in Bridge Mode #241

Closed Kherby closed 5 years ago

Kherby commented 5 years ago

I did an update from 8.7.2 to 8.8.37 and now i can't see the GUI State Card anymore. Has it been removed on purpose? I'm using the device in bridge mode but my modem has internet connectivity.

FrancYescO commented 5 years ago

It's just renamed to Extensions

Kherby commented 5 years ago

I don't have a Extension Card/Option either... There are only 9 cards after the Update (Gateway, Broadband, Wireless, Local Network, Diagnostics, Management, IP Extras, System Extras, xDSL Config). I haven't rebooted my DGA after the update, maybe that's the problem?

edit: went back to 8.7.2-stable and the GUI State card returned... There must be some kind of issue with 8.8.37 and the GUI State/Extensions Card.

FrancYescO commented 5 years ago

yeah please first try with a reboot (or a nginx restart)

Kherby commented 5 years ago

Can't do it right now (heavy network usage) but i do have a spare DGA4130 and i'll test it with this device and let you know.

Kherby commented 5 years ago

Can't test it atm as my DGA4130 seems to be on tilt. It was kinda messed up so i flashed fw 1.0.3 via autoflashtool. I still got root ssh acces but after i flash any custom GUI version i cannot connect to the webinterface anymore. I can see the login screen but after i type admin/admin i get "ERR_EMPTY_RESPONSE"...

Any idea?

root@modemtim:~# cat /proc/banktable/activeversion
16.3.7636-2781008-20170411105953-718b590506a915e24be58946f4755c0c617d9c8d
root@modemtim:~#  cat /proc/banktable/active
bank_1
FrancYescO commented 5 years ago

after you receive ERR_EMPTY_RESPONSE do a logread and post here the result. try to go to directly to http://192.168.1.1/cards.lp to see if it work

Kherby commented 5 years ago

http://192.168.1.1/cards.lp:

404 Not Found
nginx
root@modemtim:~# logread
Mon Oct  1 17:05:49 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:05:49 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:05:49 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 69
Mon Oct  1 17:05:49 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:05:51 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:06:00 2018 cron.info crond[2717]: USER root pid 6181 cmd /sbin/trafficdata.lua
Mon Oct  1 17:06:51 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:06:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:06:58 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 26.
Mon Oct  1 17:06:58 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:06:58 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:06:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 27
Mon Oct  1 17:06:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:06:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:06:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 65
Mon Oct  1 17:06:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:07:51 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:08:03 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:08:03 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 27.
Mon Oct  1 17:08:03 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:08:03 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:08:03 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 28
Mon Oct  1 17:08:03 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:08:03 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:08:03 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 69
Mon Oct  1 17:08:03 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:08:51 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:09:00 2018 cron.info crond[2717]: USER root pid 6225 cmd /sbin/trafficdata.lua
Mon Oct  1 17:09:12 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:09:12 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 28.
Mon Oct  1 17:09:12 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:09:12 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:09:12 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 29
Mon Oct  1 17:09:12 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:09:12 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:09:12 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 66
Mon Oct  1 17:09:12 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:09:51 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:10:00 2018 cron.info crond[2717]: USER root pid 6241 cmd /sbin/trafficmon.lua
Mon Oct  1 17:10:18 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:10:18 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 29.
Mon Oct  1 17:10:18 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:10:18 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:10:18 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 30
Mon Oct  1 17:10:18 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:10:18 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:10:18 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 73
Mon Oct  1 17:10:18 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:10:51 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:11:31 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:11:31 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 30.
Mon Oct  1 17:11:31 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:11:31 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:11:31 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 31
Mon Oct  1 17:11:31 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:11:31 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:11:31 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 61
Mon Oct  1 17:11:31 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:11:51 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:12:00 2018 cron.info crond[2717]: USER root pid 6271 cmd /sbin/trafficdata.lua
Mon Oct  1 17:12:33 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:12:33 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 31.
Mon Oct  1 17:12:33 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:12:33 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:12:33 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 32
Mon Oct  1 17:12:33 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:12:33 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:12:33 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 64
Mon Oct  1 17:12:33 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:12:51 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:13:37 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:13:37 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 32.
Mon Oct  1 17:13:37 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:13:37 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:13:37 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 33
Mon Oct  1 17:13:37 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:13:37 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:13:37 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 76
Mon Oct  1 17:13:37 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:13:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:14:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:14:53 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:14:53 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 33.
Mon Oct  1 17:14:53 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:14:53 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:14:53 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 34
Mon Oct  1 17:14:53 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:14:53 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:14:53 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 75
Mon Oct  1 17:14:53 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:15:00 2018 cron.info crond[2717]: USER root pid 6315 cmd /sbin/trafficdata.lua
Mon Oct  1 17:15:50 2018 kern.crit kernel: [ 1992.614000] eth0 (Ext switch port: 0) (Logical Port: 8) Link UP 1000 mbps full duplex
Mon Oct  1 17:15:50 2018 kern.info kernel: [ 1992.622000] br-lan: port 1(eth0) entered forwarding state
Mon Oct  1 17:15:50 2018 kern.info kernel: [ 1992.627000] br-lan: port 1(eth0) entered forwarding state
Mon Oct  1 17:15:50 2018 daemon.notice netifd: Network device 'eth0' link is up
Mon Oct  1 17:15:50 2018 daemon.info dnsmasq-dhcp[3528]: DHCPREQUEST(br-lan) 192.168.1.241 xxx
Mon Oct  1 17:15:50 2018 daemon.info dnsmasq-dhcp[3528]: DHCPACK(br-lan) 192.168.1.241 xxx Desktop-XYZ
Mon Oct  1 17:15:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:15:52 2018 kern.info kernel: [ 1994.632000] br-lan: port 1(eth0) entered forwarding state
Mon Oct  1 17:16:07 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:16:07 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 34.
Mon Oct  1 17:16:07 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:16:07 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:16:07 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 35
Mon Oct  1 17:16:07 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:16:07 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:16:07 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 66
Mon Oct  1 17:16:07 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:16:37 2018 authpriv.info dropbear[6341]: Child connection from 192.168.1.241:52995
Mon Oct  1 17:16:40 2018 authpriv.notice dropbear[6341]: Password auth succeeded for 'root' from 192.168.1.241:52995
Mon Oct  1 17:16:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:17:13 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:17:13 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 35.
Mon Oct  1 17:17:13 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:17:13 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:17:13 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 36
Mon Oct  1 17:17:13 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:17:13 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:17:13 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 76
Mon Oct  1 17:17:13 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:17:31 2018 authpriv.info dropbear[6370]: Child connection from 192.168.1.241:52996
Mon Oct  1 17:17:31 2018 authpriv.notice dropbear[6370]: Password auth succeeded for 'root' from 192.168.1.241:52996
Mon Oct  1 17:17:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:18:00 2018 cron.info crond[2717]: USER root pid 6398 cmd /sbin/trafficdata.lua
Mon Oct  1 17:18:29 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:18:29 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 36.
Mon Oct  1 17:18:29 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:18:29 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:18:29 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 37
Mon Oct  1 17:18:29 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:18:29 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:18:29 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 80
Mon Oct  1 17:18:29 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:18:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:19:36 2018 kern.crit kernel: [ 2218.700000] eth0 (Ext switch port: 0) (Logical Port: 8) Link DOWN.
Mon Oct  1 17:19:36 2018 kern.info kernel: [ 2218.707000] br-lan: port 1(eth0) entered disabled state
Mon Oct  1 17:19:36 2018 daemon.notice netifd: Network device 'eth0' link is down
Mon Oct  1 17:19:49 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:19:49 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 37.
Mon Oct  1 17:19:49 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:19:49 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:19:49 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 38
Mon Oct  1 17:19:49 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:19:49 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:19:49 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 69
Mon Oct  1 17:19:49 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:19:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:20:00 2018 cron.info crond[2717]: USER root pid 6526 cmd /sbin/trafficmon.lua
Mon Oct  1 17:20:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:20:55 2018 kern.crit kernel: [ 2297.327000] eth0 (Ext switch port: 0) (Logical Port: 8) Link UP 1000 mbps full duplex
Mon Oct  1 17:20:55 2018 kern.info kernel: [ 2297.335000] br-lan: port 1(eth0) entered forwarding state
Mon Oct  1 17:20:55 2018 kern.info kernel: [ 2297.340000] br-lan: port 1(eth0) entered forwarding state
Mon Oct  1 17:20:55 2018 daemon.notice netifd: Network device 'eth0' link is up
Mon Oct  1 17:20:57 2018 kern.info kernel: [ 2299.344000] br-lan: port 1(eth0) entered forwarding state
Mon Oct  1 17:20:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:20:58 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 38.
Mon Oct  1 17:20:58 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:20:58 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:20:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 39
Mon Oct  1 17:20:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:20:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:20:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 80
Mon Oct  1 17:20:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:21:00 2018 cron.info crond[2717]: USER root pid 6542 cmd /sbin/trafficdata.lua
Mon Oct  1 17:21:00 2018 daemon.info dnsmasq-dhcp[3528]: DHCPREQUEST(br-lan) 192.168.1.241 xxx
Mon Oct  1 17:21:00 2018 daemon.info dnsmasq-dhcp[3528]: DHCPACK(br-lan) 192.168.1.241 xxx Desktop-XYZ
Mon Oct  1 17:21:02 2018 authpriv.info dropbear[6554]: Child connection from 192.168.1.241:53031
Mon Oct  1 17:21:02 2018 authpriv.notice dropbear[6554]: Password auth succeeded for 'root' from 192.168.1.241:53031
Mon Oct  1 17:21:19 2018 daemon.err nginx: 2018/10/01 17:21:19 [error] 5347#0: *10 open() "/www/docroot/theme/style.css" failed (2: No such file or directory), client: 192.168.1.241, server: localhost, request: "GET /theme//style.css HTTP/1.1", host: "192.168.1.1", referrer: "http://192.168.1.1/"
Mon Oct  1 17:21:25 2018 daemon.err nginx: 2018/10/01 17:21:24 [error] 5347#0: *10 lua entry thread aborted: runtime error: [string "004_wireless.lp"]:44: attempt to index a nil value
stack traceback:
coroutine 0:
        [string "004_wireless.lp"]:44: in function 'content'
        /usr/lib/lua/web/lp.lua:171: in function 'include'
        [string "/gateway.lp"]:225: in function 'content'
        /usr/lib/lua/web/web.lua:249: in function 'process'
        content_by_lua(nginx.conf:163):4: in function <content_by_lua(nginx.conf:163):1>, clieMon Oct  1 17:21:25 2018 daemon.err nginx: 2018/10/01 17:21:25 [error] 5347#0: *11 lua entry thread aborted: runtime error: [string "004_wireless.lp"]:44: attempt to index a nil value
stack traceback:
coroutine 0:
        [string "004_wireless.lp"]:44: in function 'content'
        /usr/lib/lua/web/lp.lua:171: in function 'include'
        [string "/gateway.lp"]:225: in function 'content'
        /usr/lib/lua/web/web.lua:249: in function 'process'
        content_by_lua(nginx.conf:163):4: in function <content_by_lua(nginx.conf:163):1>, clieMon Oct  1 17:21:25 2018 daemon.err nginx: 2018/10/01 17:21:25 [error] 5347#0: *12 lua entry thread aborted: runtime error: [string "004_wireless.lp"]:44: attempt to index a nil value
stack traceback:
coroutine 0:
        [string "004_wireless.lp"]:44: in function 'content'
        /usr/lib/lua/web/lp.lua:171: in function 'include'
        [string "/gateway.lp"]:225: in function 'content'
        /usr/lib/lua/web/web.lua:249: in function 'process'
        content_by_lua(nginx.conf:163):4: in function <content_by_lua(nginx.conf:163):1>, clie
root@modemtim:~# logread
Mon Oct  1 17:10:18 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:10:18 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 73
Mon Oct  1 17:10:18 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:10:51 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:11:31 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:11:31 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 30.
Mon Oct  1 17:11:31 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:11:31 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:11:31 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 31
Mon Oct  1 17:11:31 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:11:31 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:11:31 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 61
Mon Oct  1 17:11:31 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:11:51 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:12:00 2018 cron.info crond[2717]: USER root pid 6271 cmd /sbin/trafficdata.lua
Mon Oct  1 17:12:33 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:12:33 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 31.
Mon Oct  1 17:12:33 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:12:33 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:12:33 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 32
Mon Oct  1 17:12:33 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:12:33 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:12:33 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 64
Mon Oct  1 17:12:33 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:12:51 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:13:37 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:13:37 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 32.
Mon Oct  1 17:13:37 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:13:37 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:13:37 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 33
Mon Oct  1 17:13:37 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:13:37 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:13:37 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 76
Mon Oct  1 17:13:37 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:13:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:14:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:14:53 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:14:53 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 33.
Mon Oct  1 17:14:53 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:14:53 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:14:53 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 34
Mon Oct  1 17:14:53 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:14:53 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:14:53 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 75
Mon Oct  1 17:14:53 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:15:00 2018 cron.info crond[2717]: USER root pid 6315 cmd /sbin/trafficdata.lua
Mon Oct  1 17:15:50 2018 kern.crit kernel: [ 1992.614000] eth0 (Ext switch port: 0) (Logical Port: 8) Link UP 1000 mbps full duplex
Mon Oct  1 17:15:50 2018 kern.info kernel: [ 1992.622000] br-lan: port 1(eth0) entered forwarding state
Mon Oct  1 17:15:50 2018 kern.info kernel: [ 1992.627000] br-lan: port 1(eth0) entered forwarding state
Mon Oct  1 17:15:50 2018 daemon.notice netifd: Network device 'eth0' link is up
Mon Oct  1 17:15:50 2018 daemon.info dnsmasq-dhcp[3528]: DHCPREQUEST(br-lan) 192.168.1.241 xxx
Mon Oct  1 17:15:50 2018 daemon.info dnsmasq-dhcp[3528]: DHCPACK(br-lan) 192.168.1.241 xxx Desktop-XYZ Mon Oct  1 17:15:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:15:52 2018 kern.info kernel: [ 1994.632000] br-lan: port 1(eth0) entered forwarding state
Mon Oct  1 17:16:07 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:16:07 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 34.
Mon Oct  1 17:16:07 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:16:07 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:16:07 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 35
Mon Oct  1 17:16:07 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:16:07 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:16:07 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 66
Mon Oct  1 17:16:07 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:16:37 2018 authpriv.info dropbear[6341]: Child connection from 192.168.1.241:52995
Mon Oct  1 17:16:40 2018 authpriv.notice dropbear[6341]: Password auth succeeded for 'root' from 192.168.1.241:52995
Mon Oct  1 17:16:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:17:13 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:17:13 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 35.
Mon Oct  1 17:17:13 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:17:13 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:17:13 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 36
Mon Oct  1 17:17:13 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:17:13 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:17:13 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 76
Mon Oct  1 17:17:13 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:17:31 2018 authpriv.info dropbear[6370]: Child connection from 192.168.1.241:52996
Mon Oct  1 17:17:31 2018 authpriv.notice dropbear[6370]: Password auth succeeded for 'root' from 192.168.1.241:52996
Mon Oct  1 17:17:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:18:00 2018 cron.info crond[2717]: USER root pid 6398 cmd /sbin/trafficdata.lua
Mon Oct  1 17:18:29 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:18:29 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 36.
Mon Oct  1 17:18:29 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:18:29 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:18:29 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 37
Mon Oct  1 17:18:29 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:18:29 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:18:29 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 80
Mon Oct  1 17:18:29 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:18:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:19:36 2018 kern.crit kernel: [ 2218.700000] eth0 (Ext switch port: 0) (Logical Port: 8) Link DOWN.
Mon Oct  1 17:19:36 2018 kern.info kernel: [ 2218.707000] br-lan: port 1(eth0) entered disabled state
Mon Oct  1 17:19:36 2018 daemon.notice netifd: Network device 'eth0' link is down
Mon Oct  1 17:19:49 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:19:49 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 37.
Mon Oct  1 17:19:49 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:19:49 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:19:49 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 38
Mon Oct  1 17:19:49 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:19:49 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:19:49 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 69
Mon Oct  1 17:19:49 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:19:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:20:00 2018 cron.info crond[2717]: USER root pid 6526 cmd /sbin/trafficmon.lua
Mon Oct  1 17:20:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:20:55 2018 kern.crit kernel: [ 2297.327000] eth0 (Ext switch port: 0) (Logical Port: 8) Link UP 1000 mbps full duplex
Mon Oct  1 17:20:55 2018 kern.info kernel: [ 2297.335000] br-lan: port 1(eth0) entered forwarding state
Mon Oct  1 17:20:55 2018 kern.info kernel: [ 2297.340000] br-lan: port 1(eth0) entered forwarding state
Mon Oct  1 17:20:55 2018 daemon.notice netifd: Network device 'eth0' link is up
Mon Oct  1 17:20:57 2018 kern.info kernel: [ 2299.344000] br-lan: port 1(eth0) entered forwarding state
Mon Oct  1 17:20:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:20:58 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 38.
Mon Oct  1 17:20:58 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:20:58 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:20:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 39
Mon Oct  1 17:20:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:20:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:20:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 80
Mon Oct  1 17:20:58 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:21:00 2018 cron.info crond[2717]: USER root pid 6542 cmd /sbin/trafficdata.lua
Mon Oct  1 17:21:00 2018 daemon.info dnsmasq-dhcp[3528]: DHCPREQUEST(br-lan) 192.168.1.241 xxx
Mon Oct  1 17:21:00 2018 daemon.info dnsmasq-dhcp[3528]: DHCPACK(br-lan) 192.168.1.241 xxx Desktop-XYZ
Mon Oct  1 17:21:02 2018 authpriv.info dropbear[6554]: Child connection from 192.168.1.241:53031
Mon Oct  1 17:21:02 2018 authpriv.notice dropbear[6554]: Password auth succeeded for 'root' from 192.168.1.241:53031
Mon Oct  1 17:21:19 2018 daemon.err nginx: 2018/10/01 17:21:19 [error] 5347#0: *10 open() "/www/docroot/theme/style.css" failed (2: No such file or directory), client: 192.168.1.241, server: localhost, request: "GET /theme//style.css HTTP/1.1", host: "192.168.1.1", referrer: "http://192.168.1.1/"
Mon Oct  1 17:21:25 2018 daemon.err nginx: 2018/10/01 17:21:24 [error] 5347#0: *10 lua entry thread aborted: runtime error: [string "004_wireless.lp"]:44: attempt to index a nil value
stack traceback:
coroutine 0:
        [string "004_wireless.lp"]:44: in function 'content'
        /usr/lib/lua/web/lp.lua:171: in function 'include'
        [string "/gateway.lp"]:225: in function 'content'
        /usr/lib/lua/web/web.lua:249: in function 'process'
        content_by_lua(nginx.conf:163):4: in function <content_by_lua(nginx.conf:163):1>, clieMon Oct  1 17:21:25 2018 daemon.err nginx: 2018/10/01 17:21:25 [error] 5347#0: *11 lua entry thread aborted: runtime error: [string "004_wireless.lp"]:44: attempt to index a nil value
stack traceback:
coroutine 0:
        [string "004_wireless.lp"]:44: in function 'content'
        /usr/lib/lua/web/lp.lua:171: in function 'include'
        [string "/gateway.lp"]:225: in function 'content'
        /usr/lib/lua/web/web.lua:249: in function 'process'
        content_by_lua(nginx.conf:163):4: in function <content_by_lua(nginx.conf:163):1>, clieMon Oct  1 17:21:25 2018 daemon.err nginx: 2018/10/01 17:21:25 [error] 5347#0: *12 lua entry thread aborted: runtime error: [string "004_wireless.lp"]:44: attempt to index a nil value
stack traceback:
coroutine 0:
        [string "004_wireless.lp"]:44: in function 'content'
        /usr/lib/lua/web/lp.lua:171: in function 'include'
        [string "/gateway.lp"]:225: in function 'content'
        /usr/lib/lua/web/web.lua:249: in function 'process'
        content_by_lua(nginx.conf:163):4: in function <content_by_lua(nginx.conf:163):1>, clieMon Oct  1 17:21:30 2018 daemon.err nginx: 2018/10/01 17:21:30 [error] 5347#0: *13 lua entry thread aborted: runtime error: [string "004_wireless.lp"]:44: attempt to index a nil value
stack traceback:
coroutine 0:
        [string "004_wireless.lp"]:44: in function 'content'
        /usr/lib/lua/web/lp.lua:171: in function 'include'
        [string "/gateway.lp"]:225: in function 'content'
        /usr/lib/lua/web/web.lua:249: in function 'process'
        content_by_lua(nginx.conf:163):4: in function <content_by_lua(nginx.conf:163):1>, clieMon Oct  1 17:21:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:22:02 2018 daemon.err nginx: 2018/10/01 17:22:00 [error] 5347#0: *14 lua entry thread aborted: runtime error: [string "004_wireless.lp"]:44: attempt to index a nil value
stack traceback:
coroutine 0:
        [string "004_wireless.lp"]:44: in function 'content'
        /usr/lib/lua/web/lp.lua:171: in function 'include'
        [string "/gateway.lp"]:225: in function 'content'
        /usr/lib/lua/web/web.lua:249: in function 'process'
        content_by_lua(nginx.conf:163):4: in function <content_by_lua(nginx.conf:163):1>, clieMon Oct  1 17:22:18 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:22:18 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 39.
Mon Oct  1 17:22:18 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:22:18 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:22:18 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 40
Mon Oct  1 17:22:18 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:22:18 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:22:18 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 66
Mon Oct  1 17:22:18 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:22:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:23:03 2018 daemon.err nginx: 2018/10/01 17:23:02 [error] 5347#0: *15 lua entry thread aborted: runtime error: [string "004_wireless.lp"]:44: attempt to index a nil value
stack traceback:
coroutine 0:
        [string "004_wireless.lp"]:44: in function 'content'
        /usr/lib/lua/web/lp.lua:171: in function 'include'
        [string "/gateway.lp"]:225: in function 'content'
        /usr/lib/lua/web/web.lua:249: in function 'process'
        content_by_lua(nginx.conf:163):4: in function <content_by_lua(nginx.conf:163):1>, clieMon Oct  1 17:23:24 2018 daemon.info cwmpd[5693]: PROT_TRACE: Events are waiting, need to contact ACS
Mon Oct  1 17:23:24 2018 daemon.info cwmpd[5693]: CONNECTION: Connecting to server retry 40.
Mon Oct  1 17:23:24 2018 daemon.err cwmpd[5693]: APP_TRACE: bad address '▒c~▒'
Mon Oct  1 17:23:24 2018 daemon.crit cwmpd[5693]: CONNECTION: Failed to resolve.
Mon Oct  1 17:23:24 2018 daemon.info cwmpd[5693]: PROT_TRACE: Nb of retries 41
Mon Oct  1 17:23:24 2018 daemon.info cwmpd[5693]: PROT_TRACE: Min retry wait time 61
Mon Oct  1 17:23:24 2018 daemon.info cwmpd[5693]: PROT_TRACE: Max retry wait time 80
Mon Oct  1 17:23:24 2018 daemon.info cwmpd[5693]: PROT_TRACE: Effective retry wait time 72
Mon Oct  1 17:23:24 2018 daemon.info cwmpd[5693]: PROT_TRACE: LAST STATE: <Idle>
Mon Oct  1 17:23:52 2018 daemon.notice transformer: [mobiled] (WaitingForDevice) runs WaitingForDevice-Main.check(timeout, 1, PlatformConfigure)
Mon Oct  1 17:24:00 2018 cron.info crond[2717]: USER root pid 6642 cmd /sbin/trafficdata.lua
Kherby commented 5 years ago

As I said, my DGA4130 is kinda messed up at the moment. So i'm asking myself if there is a safe way to completly wipe everything and start from the scratch...?

My plan would be: Vanilla 1.0.3 with root > Upgrade to 1.1.0 via Autoflashtool, install latest Ansuel GUI Bank1: 1.1.0 with root Bank2: 1.0.3 with or without root

Any advice?

FrancYescO commented 5 years ago

Execute these commands to try a "soft" restore

curl -k https://repository.ilpuntotecnico.com/files/Ansuel/AGTEF/GUI_dev.tar.bz2 --output /tmp/GUI_dev.tar.bz2
bzcat /tmp/GUI_dev.tar.bz2 | tar -C / -xvf -
/etc/init.d/rootdevice force
Ansuel commented 5 years ago

@Kherby

Reinstall my gui stable then upgrade dev or just install stable

Kherby commented 5 years ago

My DGA4130 has no internet connection but i allready tried to install the GUI version (latest dev and 8.7.2-stable) by copying the GUI file manualy to /tmp Stable: bzcat /tmp/GUI.tar.bz2 | tar -C / -xvf - && rm /tmp/GUI.tar.bz2 && /etc/init.d/rootdevice force Dev: bzcat /tmp/GUI_dev.tar.bz2 | tar -C / -xvf - && rm /tmp/GUI_dev.tar.bz2 && /etc/init.d/rootdevice force

No success... As i said i would like to wipe everything and start from the scratch but i'm not sure if it's safe and how. I dont have a working backup bank2 and that's why i'm worried...

Log:

root@modemtim:~# bzcat /tmp/GUI_dev.tar.bz2 | tar -C / -xvf -
BLAHBLAHBLAH
root@modemtim:~# /etc/init.d/rootdevice force
Root Script: Rooting in progress...
ash: by: unknown operand
cp: '/rom/usr/bin/transformer' and '/usr/bin/transformer' are the same file
bzcat: /root/GUI_dev.tar.bz2: No such file or directory
tar: short read

Login Screenshot: https://imgur.com/zmaRy81

Kherby commented 5 years ago

@Ansuel I've allready tried to install the stable version but the same login error appears. It's really weird. I think something is messed up in my overlay folder or somewhere else. I never had such a problem before...

Do you have any advice howto wipe everything and start from the scratch?

Ansuel commented 5 years ago

press reset button on the back of the modem for 7 second and wait reboot after that reinstall stable (root will stay)

Kherby commented 5 years ago

@Ansuel Now i'm completly shocked... I tried to install 8.7.2-stable once again and tis time it did work and now i'm able access the Webinterface and for some reason i do see GUI State + Extension Card.

Screenshot: https://imgur.com/a/Kj7lPmx

Active Bank bank_1 Active Version 16.3.7636-2781008-20170411105953-718b590506a915e24be58946f4755c0c617d9c8d Passive Bank bank_2 Passive Version Firmware not present in this bank

Is it safe to delete the Bank1 + Bank2 folder from /overlay (bank1 still has some stuff from a GUI version 8.6.x and maybe that's why my DGA4130 is messed up? So what do i have to do now? Full Reset via GUI (incl root)? Than flash 1.1.0 via Autoflashtool with 1.0.3 root inactive ticket? I'm kinda lost... :/

Ansuel commented 5 years ago

NEVER EVER DO THE RESET INCLUDE ROOT... OR MANUALLY DELETE THE CONTENT OF OVERLAY DIR...

IF YOU WANT TO RESET USE THE BUTTON OR THE DEFAULT RESET BUTTON IN THE GATEWAY TAB (NOT THE ADVANCED RESET BUTTON)

and having the bank_2 blank is not a problem...

Kherby commented 5 years ago

Thanks for letting me know... But i think there are some old messed up files in the Bank1 overlay from an older GUI version. So my idea was to fully wipe the DGA4130 so there are no more old files present and than start from the scratch... I'm at 1.0.3, so the root proccess should not be problem, am i right?

My goal would be to have 1.1.0 rooted at Bank1 and 1.0.3 at Bank2 (as a failsafe backup). From what i read it should work if i have a stock 1.0.3 without root at Bank1 and flash 1.1.0 via autoflashtool with option 1.0.3 root and then finally i flash 1.0.3 with option root inactive .

Ansuel commented 5 years ago

the reset will wipe everything but it will reinstall root that's all...

i would not call it reset if it didn't clean the file ahaha

reset will clean all the junk on that bank

Kherby commented 5 years ago

Okay. I did a reset via reset button and then i went for the route with 1.1.0 via autoflashtool and after that i flashed 1.0.3 with root incative option ticked. All went fine but after 3 reboots i ended up with 1.0.3 rooted on both banks. Not sure if something went wrong at Bank2 or if it's corrupt....

root@modemtim:~# cat /proc/banktable/activeversion
16.3.7636-2781008-20170411105953-718b590506a915e24be58946f4755c0c617d9c8d
root@modemtim:~# cat /proc/banktable/passiveversion
16.3.7636-2781008-20170411105953-718b590506a915e24be58946f4755c0c617d9c8d
root@modemtim:~# cat /proc/banktable/active
bank_1

Anyway now i'm going to install your latest stable GUI and flash 1.1.0 from there.... Hopefully i won't end up with a brick. My DGA4130 seems to be a weird little douchebag... ;)

Edit: First try with 8.7.2 ended up with the same login error but the second try via the winSCP console worked fine. I dont understand this but ok...

Edit2: Upgrade to 1.1.0 via GUI went fine and the 8.7.2 GUI was also still intact after the Upgrade process... Now i'm going to install 8.8.37 to see if the Card Bug still appears.

Edit3: Update to 8.8.37 via WinSCP console doesn't went well and after a reboot i do get the "ERR_EMPTY_RESPONSE" Error again. Console screenshot: https://imgur.com/a/2N8Tt3C So it seems that there is something is wrong with 8.8.37, at least when upgrading from 8.7.2-stable.

I'm doing a reset via button again and then i'm going to install 8.7.2-stable and leave it for now. To be honest i'm pretty much done for today but i really don't understand why my DGA4132 did not had this problem with 8.8.37 (except for the missing GUI State/Extension Card)... :/

kevdagoat commented 5 years ago

Never delete content of overlay. I did it and it rebooted and rebuilt itself

On 2 Oct 2018, at 5:04 am, Kherby notifications@github.com wrote:

Okay. I did a reset via reset button and then i went for the route with 1.1.0 via autoflashtool and after that i flashed 1.0.3 with root incative option ticked. All went fine but after 3 reboots i ended up with 1.0.3 rooted on both banks. Not sure if something went wrong at Bank2 or if it's corrupt....

root@modemtim:~# cat /proc/banktable/activeversion 16.3.7636-2781008-20170411105953-718b590506a915e24be58946f4755c0c617d9c8d root@modemtim:~# cat /proc/banktable/passiveversion 16.3.7636-2781008-20170411105953-718b590506a915e24be58946f4755c0c617d9c8d root@modemtim:~# cat /proc/banktable/active bank_1 Anyway now i'm going to install your latest stable GUI and flash 1.1.0 from there.... Hopefully i won't end up with a brick. My DGA4130 seems to be a weird little douchebag... ;)

Edit: First try with 8.7.2 ended up with the same login error but the second try via the winSCP console worked fine. I dont understand this but ok...

Edit2: Upgrade to 1.1.0 via GUI went fine and the 8.7.2 GUI was also still intact after the Upgrade process... Now i'm going to install 8.8.37 to see if the Card Bug still appears.

Edit3: Update to 8.8.37 via WinSCP console doesn't went well and after a reboot i do get the "ERR_EMPTY_RESPONSE" Error again. Console screenshot: https://imgur.com/a/2N8Tt3C So it seems that there is something is wrong with 8.8.37, at least when upgrading from 8.7.2-stable.

I'm doing a reset via button again and then i'm going to install 8.7.2-stable and leave it for now. To be honest i'm pretty much done for today but i really don't understand why my DGA4132 did not had this problem with 8.8.37 (except for the missing GUI State/Extension Card)... :/

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

FrancYescO commented 5 years ago

The risk is to lose root access if you are on a unrootable firmware

From: Kevdagoat notifications@github.com Sent: Tuesday, October 2, 2018 1:23:03 AM To: Ansuel/tch-nginx-gui Cc: Francesco M; Comment Subject: Re: [Ansuel/tch-nginx-gui] GUI state card missing after update to 8.8.37-dev (#241)

Never delete content of overlay. I did it and it rebooted and rebuilt itself

On 2 Oct 2018, at 5:04 am, Kherby notifications@github.com wrote:

Okay. I did a reset via reset button and then i went for the route with 1.1.0 via autoflashtool and after that i flashed 1.0.3 with root incative option ticked. All went fine but after 3 reboots i ended up with 1.0.3 rooted on both banks. Not sure if something went wrong at Bank2 or if it's corrupt....

root@modemtim:~# cat /proc/banktable/activeversion 16.3.7636-2781008-20170411105953-718b590506a915e24be58946f4755c0c617d9c8d root@modemtim:~# cat /proc/banktable/passiveversion 16.3.7636-2781008-20170411105953-718b590506a915e24be58946f4755c0c617d9c8d root@modemtim:~# cat /proc/banktable/active bank_1 Anyway now i'm going to install your latest stable GUI and flash 1.1.0 from there.... Hopefully i won't end up with a brick. My DGA4130 seems to be a weird little douchebag... ;)

Edit: First try with 8.7.2 ended up with the same login error but the second try via the winSCP console worked fine. I dont understand this but ok...

Edit2: Upgrade to 1.1.0 via GUI went fine and the 8.7.2 GUI was also still intact after the Upgrade process... Now i'm going to install 8.8.37 to see if the Card Bug still appears.

Edit3: Update to 8.8.37 via WinSCP console doesn't went well and after a reboot i do get the "ERR_EMPTY_RESPONSE" Error again. Console screenshot: https://imgur.com/a/2N8Tt3C So it seems that there is something is wrong with 8.8.37, at least when upgrading from 8.7.2-stable.

I'm doing a reset via button again and then i'm going to install 8.7.2-stable and leave it for now. To be honest i'm pretty much done for today but i really don't understand why my DGA4132 did not had this problem with 8.8.37 (except for the missing GUI State/Extension Card)... :/

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Ansuel/tch-nginx-gui/issues/241#issuecomment-426096198, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEXNgc1UkvggKWB7ELliiBzNm_NcRlGqks5ugqPXgaJpZM4XCQzK.

kevdagoat commented 5 years ago

I had 16.3, so it didn’t really matter and I needed to remove ansuels GUI :)

On 2 Oct 2018, at 7:27 am, Francesco M notifications@github.com wrote:

The risk is to lose root access if you are on a unrootable firmware

From: Kevdagoat notifications@github.com Sent: Tuesday, October 2, 2018 1:23:03 AM To: Ansuel/tch-nginx-gui Cc: Francesco M; Comment Subject: Re: [Ansuel/tch-nginx-gui] GUI state card missing after update to 8.8.37-dev (#241)

Never delete content of overlay. I did it and it rebooted and rebuilt itself

On 2 Oct 2018, at 5:04 am, Kherby notifications@github.com wrote:

Okay. I did a reset via reset button and then i went for the route with 1.1.0 via autoflashtool and after that i flashed 1.0.3 with root incative option ticked. All went fine but after 3 reboots i ended up with 1.0.3 rooted on both banks. Not sure if something went wrong at Bank2 or if it's corrupt....

root@modemtim:~# cat /proc/banktable/activeversion 16.3.7636-2781008-20170411105953-718b590506a915e24be58946f4755c0c617d9c8d root@modemtim:~# cat /proc/banktable/passiveversion 16.3.7636-2781008-20170411105953-718b590506a915e24be58946f4755c0c617d9c8d root@modemtim:~# cat /proc/banktable/active bank_1 Anyway now i'm going to install your latest stable GUI and flash 1.1.0 from there.... Hopefully i won't end up with a brick. My DGA4130 seems to be a weird little douchebag... ;)

Edit: First try with 8.7.2 ended up with the same login error but the second try via the winSCP console worked fine. I dont understand this but ok...

Edit2: Upgrade to 1.1.0 via GUI went fine and the 8.7.2 GUI was also still intact after the Upgrade process... Now i'm going to install 8.8.37 to see if the Card Bug still appears.

Edit3: Update to 8.8.37 via WinSCP console doesn't went well and after a reboot i do get the "ERR_EMPTY_RESPONSE" Error again. Console screenshot: https://imgur.com/a/2N8Tt3C So it seems that there is something is wrong with 8.8.37, at least when upgrading from 8.7.2-stable.

I'm doing a reset via button again and then i'm going to install 8.7.2-stable and leave it for now. To be honest i'm pretty much done for today but i really don't understand why my DGA4132 did not had this problem with 8.8.37 (except for the missing GUI State/Extension Card)... :/

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Ansuel/tch-nginx-gui/issues/241#issuecomment-426096198, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEXNgc1UkvggKWB7ELliiBzNm_NcRlGqks5ugqPXgaJpZM4XCQzK. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

Kherby commented 5 years ago

To be honest I would like to remove /overlay/bank2 because it contains the rootdevice file of 8.8.37, which was a total disaster on my DGA4130. I'm not even sure if my Bank2 (1.0.3) is working and not corrupt at this point.

Basicaly I'm still looking for a safe way to flash 1.0.3 on bank2 (as a backup)...

sysupgrade -o -s  AGTEF_1.0.3_CLOSED.rbi
echo bank_1 > /proc/banktable/active

Would this work? Or is it better to flash 1.0.3 via Autoflashtool and do a switchover?

FrancYescO commented 5 years ago

@Kherby can you check if your /etc/config/wireless file is still here?

On a DGA4132 1.2.0_001 i was on 8.8.14, done rtfd and gone back to stock with root, than installed 8.7.2, and than 8.8.37 with no issue at all.

i think the problem is some of your config files got corrupted (and looking at logs i guess wireless) and you still have not done a factory reset.

@kevdagoat no problem if you have an exploit for root, but DGA4130/2 are a lot risky as we have no exploits for firmwares >=1.1.1 so mantain the rootdevice script as a trojan is critical.

Kherby commented 5 years ago

@FrancYescO I did a factory reset via reset button and even reflashed fw 1.0.3 + 1.1.0 again... At my DGA4132 i dont have Wifi active and hostapd disabled as well (dont need it in bridge mode).

What exactly do you mean with factory reset? Should i flash 1.0.3 once again on both banks and factory reset + remove root and start from the scratch? What's the proper way to ensure that everything is wiped?

Btw, i never flashed anything higher than 1.1.0 as i use my DGA's in bridge mode only and higher firmware versions doesn't seem to benefit my setup.

FrancYescO commented 5 years ago

factory reset = rtfdfrom ssh or press the reset button after this is still not clear to me if you can access to the webif, you should find the stock one after a factory reset.. reflash the firmware is pretty useless in this case.

Kherby commented 5 years ago

After the reset i had the stock GUI but root was still active... So I flashed 8.7.2 and after i verified that the login was working i flashed 8.8.37 again but the login error came back. Flashing 8.7.2 once again fixed it.

Later im going to delete overlay/bank2 and enter rtfd from ssh. I need to ensure everything is proper wiped and how to use Autoflashtool to get a working 1.0.3 on Bank2 as a backup and 1.1.0 with root at Bank1.

FrancYescO commented 5 years ago

how you flashed 8.7.2 and specially 8.8.37? have you upgraded to the dev via the GUI from Gateway modal? the logread after you get error 500 was the same? we need to know what is causing you to get the unreachable GUI to fix... Autoflashtool should ever flash in the passive bank and will never blank the overlay.

Kherby commented 5 years ago

I flashed both GUI version manualy via commandline...

bzcat /tmp/GUI_dev.tar.bz2 | tar -C / -xvf -
/etc/init.d/rootdevice force

Haven't had any time today but I'm still planing to wipe everything and start from the scratch with a clean config. Anyway i still don't know a bulletproof method to wipe everything safely...

kevdagoat commented 5 years ago

Try: jffs2reset && firstboot Or mtdreset

On 3 Oct 2018, at 8:03 am, Kherby notifications@github.com wrote:

I flashed both GUI version manualy via commandline...

bzcat /tmp/GUI_dev.tar.bz2 | tar -C / -xvf - /etc/init.d/rootdevice force Haven't had any time today but I'm still planing to wipe everything and start from the scratch with a clean config. Anyway i still don't know a bulletproof method to wipe everything safely...

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

FrancYescO commented 5 years ago

try to install 8.7.2 and than upgrade to dev 8.8.x via GUI (Gateway modal>set dev branch>check for update>upgrade) if you get again error 500 please post a logread.

Kherby commented 5 years ago

Try: jffs2reset && firstboot Or mtdreset

Thanks. I do think that my Bank2 is corrupt at this point. So first of all i would need to flash Bank2 with stock 1.0.3, wipe everything and than flash 1.1.0 with root at Bank1 to make sure there are no leftovers. Any advice how to do so? Should i flash 1.0.3 at both banks and than do the mtdreset command?

@FrancYescO I'm using my DGA in Bridge Mode only, i do have internet connection with my DGA but there is no "check for Update" button in bridge mode. https://imgur.com/a/0jDoghS But i can manualy upddate via file at the GUI...

FrancYescO commented 5 years ago

try to manually put the GUI_dev file in the upload form, or try with the commands you posted above, but don't set bridge mode when you are on 8.7.2

Kherby commented 5 years ago

@FrancYescO I did that with my DGA4132 (put the GUI_dev file in the upload form), maybe that's why the update to 8.8.37 went fine over there...

Anyway i want to make sure that there are no leftovers which can cause trouble, so i've just deleted the content of /overlay/bank2 and rebooted. Now i'll try to flash 1.0.3 and factory reset + mtdreset on both banks and Upgrade to 1.1.0 via Autoflashtool with option DGA4130 root inactive ticked. Once everything went fine i'm going to install 8.7.2 and than 8.8.x via Ansuel GUI (in Router Mode)... I guess that should fix the login error problem.

Kherby commented 5 years ago

I did a switchover via console to see if bank2 had a working and non corrupt firmware installed. And Bank2 had a working non-rooted stock 1.0.3 installed (maybe non-rooted because i deleted overlay/bank2)... So i went ahead and rooted this one real quick and after everything went well i did a switchover again. At least now i know that Bank2 has working and rooted 1.0.3 installed which is always good as a backup if something goes wrong at Bank1...

So howto proceed further now? Want me to factory reset 1.1.0 (bank1) without loosing root and than flash GUI 8.7.2 via console and install 8.8.x-dev via GUI (upload form) right after without touching any settings before (Router Mode)? Or should i flash 1.0.3 at bank1, factory reset it (mtdrease), root it once again, install Ansuel 8.7.2-stable, install 1.1.0 and if everything went well install 8.8.x-dev via GUI?

Sorry for all my questions but i want to make sure that i'm doing it right this time. It allready cost me a few hours yesteday and i never got to the point where i had a working 8.8.x-dev GUI on my DGA4130...

Kherby commented 5 years ago

Well, i installed the latest GUI_dev via GUI (upload Form) and this time it worked (even in bridge mode without wifi and hostapd disabled). Anway the Extensions Card is still missing, it's the same as with my DGA4132. A reboot + clear browser chache also did not help. https://imgur.com/CHG9RwW

  1. It might be related to my config (bridge mode) where i also have several services disabled via init.d.
  2. Extension Card is missing in Bridge mode (Bug?)

The last thing that i can try is to factory reset once again, install GUI 8.7.2 via console, install 8.8.x-dev via GUI (upload form) and check if the Extension Card will appear in vanilla Router Mode. Please let me know if i can do something else...

And btw, thanks for all of your time! :)

Ansuel commented 5 years ago

All this mess and the problem is the bridge mode as you should not have internet connection then you can't use the auto magic scripts

Il Mer 3 Ott 2018, 03:55 Kherby notifications@github.com ha scritto:

Well, i installed the latest GUI_dev via GUI (upload Form) and this time it worked (even in bridge mode without wifi and hostapd disabled). Anway the Extensions Card is still missing, it's the same as with my DGA4132. A reboot + clear browser chache also did not help. https://imgur.com/CHG9RwW

  1. It might be related to my config (bridge mode) where i also have several services disabled via init.d.
  2. Extension Card is missing in Bridge mode (Bug?)

The last thing that i can try is to factory reset once again, install GUI 8.7.2 via console, install 8.8.x-dev via GUI (upload form) and check if the Extension Card will appear in vanilla Router Mode. Please let me know if i can do something else...

And btw, thanks for all of your time! :)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Ansuel/tch-nginx-gui/issues/241#issuecomment-426487145, or mute the thread https://github.com/notifications/unsubscribe-auth/ATWWQijswsJpSPIZH0dyslwJS27naK3Cks5uhBkJgaJpZM4XCQzK .

Kherby commented 5 years ago

So I did a factory reset, installed 8.2.7-stable, rebooted and installed 8.8.40-dev via Ansuel GUI (Upload form). Result: ERR_EMPTY_RESPONSE > can't reach the GUI. It's so odd :/

I went ahead and installed 8.7.2 once again, downgraded the Firmware to 1.0.3 via GUI and did a reset to factory defaults (incl. remove root). After the reset was done and the stock Firmware without root successfully booted i did another factory reset via the offical TIM GUI. I think that i can't do more to make sure that everything was fully wiped...

Then I rooted 1.0.3 (bank1) and installed Ansuel GUI 8.7.2, rebooted again and installed fw 1.1.0 via Ansuel GUI. Now I'm at fw 1.1.0 with GUI 8.7.2-stable and there is only bank1 folder at /overlay/, so i guess the Reset with remove root also wiped root at 1.0.3 Bank2... Anyway, fw 1.0.3 at bank2 is still intact.

For now I'm going to leave it like this and wait for the next stable GUI Version as I'm too scared to install any dev GUI version at the moment and mess up the device again.

At least i learned howto Install a backup firmware at Bank2. So all the trouble wasn't for nothing...

Kherby commented 5 years ago

@Ansuel With my second try i didn't set bridge mode and didn't change any default settings. result was the same... As i wrote above i wiped everything (at least i tried) and installed everything from the scratch.

I'm not going to install the latest dev version once again as I'm happy with 8.7.2-stable in Bridge Mode. The only thing that botherd me at 8.7.2-stable was that the xDSL Bits Graphic is messed up but i use DSLstats so it's no big deal for me. I do have a internet connection in bridge mode to be able to install htop and Luci and it would be nice if we could also to update the GUI version (via internet) in bridge mode...

Btw, i finally got a working network config without pppoerelayd for the bridge mode where all LED's are green, so no more red blinking when DSL has been synchronised. I understand that the most people are using their DGA as real router but let me know if u want to implement the config for the bridge mode... I think it would be a good default config for the bridge mode.

Anyway, I'm looking forward to the next stable GUI version... :)

FrancYescO commented 5 years ago

The real issue is that if we cannot identify what actually break your GUI when going to the dev version, releasing a new stable will break in the same way your device

From: Kherby notifications@github.com Sent: Wednesday, October 3, 2018 8:41:40 AM To: Ansuel/tch-nginx-gui Cc: Francesco M; Mention Subject: Re: [Ansuel/tch-nginx-gui] GUI state card missing after update to 8.8.37-dev (#241)

@Ansuelhttps://github.com/Ansuel With my second try i didn't set bridge mode and didn't change any default settings. result was the same... As i wrote above i wiped everything (at least i tried) and installed everything from the scratch.

I'm not going to install the latest dev version once again as I'm happy with 8.7.2-stable in Bridge Mode. The only thing that botherd me at 8.7.2-stable was that the xDSL Bits Graphic is messed up but i use DSLstats so it's no big deal for me. I do have a internet connection in bridge mode to be able to install htop and Luci and it would be nice if we could also to update the GUI version (via internet) in bridge mode...

Btw, i finally got a working network config without pppoerelayd for the bridge mode where all LED's are green, so no more red blinking when DSL has been synchronised. I understand that the most people are using their DGA as real router but let me know if u want to implement the config for the bridge mode... I think it would be a good default config for the bridge mode.

Anyway, I'm looking forward to the next stable GUI version... :)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/Ansuel/tch-nginx-gui/issues/241#issuecomment-426528172, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEXNgRAMXb2Kefr6nbBMv4fdNS1HbZeXks5uhFwkgaJpZM4XCQzK.

Kherby commented 5 years ago

@FrancYescO I would like to help, so later i'm going to install 8.8.40-dev once again and let you know how it went. The good thing is that now i can be sure that there are no odd config leftovers as i wiped everything before. If it still breaks the GUI access now i'm out of ideas...

The other weird thing is that i'm the only one with this kind of a problems as no one else posted a similar issue... So i guess it must be something with my config or my device.

FrancYescO commented 5 years ago

Exactly... at least if we find a way to replicate we can easily fix but actually we should find what is causing as for me an upgrade from stable to the latest dev give me no issue,

Remember to do from ssh a logreadand post here the result just after you get an ERR_EMPTY_RESPONSE error, this log is the only thing that can really help us

Kherby commented 5 years ago

@FrancYescO Do you update via GUI or manual via console?

FrancYescO commented 5 years ago

GUI, with pretty nothing changed in the configs after a rtfd and Stable install

Kherby commented 5 years ago

I couldn't resist and did the update to the latest dev version via GUI. All went fine this time! The only error i can see in logread is: Wed Oct 3 09:41:08 2018 daemon.err transformer[2822]: async exec of '/usr/share/transformer/scripts/upgradegui' failed exit code=143

And the Extension Card is still missing in Bridge Mode, so it would be nice if you can fix this in Bridge Mode....

FrancYescO commented 5 years ago

Finally, good to hear that was only something messed up with your old config

FrancYescO commented 5 years ago

Btw, having the Extension card in bridge mode is pretty useless as it needs to download the packages and in bridge the modem have no WAN connection

Kherby commented 5 years ago

Finally, good to hear that was only something messed up with your old config

I'm also quite relieved about that fact....

Btw, having the Extension card in bridge mode is pretty useless as it needs to download the packages and in bridge the modem have no WAN connection

It's definitly not useless and I have no problem to download the extension packages in bridge mode as my DGA has a working internet connection (granted via my main OpenWRT router)... My DGA4130 is now connected to my DSL Line and i've allready installed htop via opkg update; opkg install htop.

And I've installed Luci via GUI before with my DGA4132 in bridge mode, which afaik also requires a working internet connection.

Ansuel commented 5 years ago

can this be closed?

Kherby commented 5 years ago

@Ansuel The GUI installation worked fine after the full wipe but the Extension Card is still missing in Bridge Mode and the main topic was about the missing Card in Bridge mode. We just drifted away as i had these login Problems with 8.8.x-dev....

So the Bug is still present or did you removed the Extenstion card on purpose when the device is in bridge mode?

Kherby commented 5 years ago

I've just upgraded to 8.8.47-dev (via GUI) and the Extension card is now showing up in Bridge mode. Thanks for fix... Topic can be closed! :)