[shdf]

FW 1.0.3- GUI 3.32
ieri ho fatto un reboot del modem (penso dopo l'upgrade a 3.29.x) è da questo giorno la "i" sul modem si illumina in rossa. tutto mi sembra funzionare normalmente, per il momento non vedo nulla di anormale ...Dopo aver riavviato il modem con la 3.32, la "i" rimane rossa.
Cosa vuole dire la "i" rossa ?

Vedo molte righe come questa nei log:

Dec 2 13:33:45   daemon.notice   transformer   [wansensing] Current Mode VDSL
Dec 2 13:33:45   daemon.notice   transformer   [wansensing] WAN Sensing L3 Up Checking
Dec 2 13:33:45   daemon.notice   transformer   [wansensing] (L3UpSense) runs L3UpMain.check(VDSL,timeout)
Dec 2 13:33:00   cron.info   crond[2540]   USER root pid 7362 cmd /sbin/trafficdata.lua
Dec 2 13:32:39   kern.warn   kernel   [ 7846.818000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.578000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.561000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.496000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.475000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.408000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.392000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.352000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.334000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.288000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.270000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.234000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.217000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.184000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.168000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.135000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.118000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.081000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:39   kern.warn   kernel   [ 7846.064000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:38   kern.warn   kernel   [ 7845.782000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:38   kern.warn   kernel   [ 7845.764000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:32:38   kern.warn   kernel   [ 7845.748000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7682.041000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7682.024000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.986000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.968000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.930000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.913000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.877000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.860000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.820000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.803000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.768000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.752000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.720000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.703000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.671000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.654000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.618000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.601000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.321000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.306000] netlink: 20 bytes leftover after parsing attributes.
Dec 2 13:29:54   kern.warn   kernel   [ 7681.286000] netlink: 20 bytes leftover after parsing attributes.

[-Mirco-]

Situazione bug aggiornata.

[Ansuel]

FW 1.0.3- GUI 3.32
ieri ho fatto un reboot del modem (penso dopo l'upgrade a 3.29.x) è da questo giorno la "i" sul modem si illumina in rossa. tutto mi sembra funzionare normalmente, per il momento non vedo nulla di anormale ...Dopo aver riavviato il modem con la 3.32, la "i" rimane rossa.
Cosa vuole dire la "i" rossa ?

Vedo molte righe come questa nei log:

Nulla di preoccupante ci sono sempre state e appaiono se apri la tab network

[shdf]

FW 1.0.3- GUI 3.28 a 3.32
 la "i" sul modem si illumina in rossa invece di verde.

Edit3: @Ansuel
dopo aver verificato, nella versione 3.25 non ci sono modifiche nella cartella /etc/ledfw/, arrivano le modifiche alla versione 3.28.x.
https://mega.nz/#F!nNcWXS4R!lU6RRMcIZwnsuC0dN8IykA

[shdf]

FW 1.0.3- GUI 3.32

Quando si tocca il NAT HELPER (ho disattivato/attivato) PPTP e SIP ... nei log si vedono molte righe di errori:

Sat Dec  2 16:54:51 2017 kern.info kernel: [19978.545000] xt_CT: No such helper "PPTP"
Sat Dec  2 16:54:51 2017 daemon.err fw-ext: Error adding CT helper PPTP for tcp ( --dport 1723) in helper_binds
Sat Dec  2 16:54:51 2017 kern.info kernel: [19978.562000] xt_CT: No such helper "SIP"
Sat Dec  2 16:54:51 2017 daemon.err fw-ext: Error adding CT helper SIP for udp ( --dport 5060) in helper_binds
Sat Dec  2 16:54:51 2017 kern.info kernel: [19978.576000] xt_CT: No such helper "SIP"
Sat Dec  2 16:54:51 2017 daemon.err fw-ext: Error adding CT helper SIP for udp ( --dport 5060) in helper_binds

Edit2:

Sat Dec  2 17:01:28 2017 daemon.warn nginx: 2017/12/02 17:01:28 [warn] 5220#0: *33 [lua] ui_helper.lua:72: mergeAttributes(): 'readonly' or 'disabled' attributes can be easily removed client side, making fields editable. Use labels or make sure your code does not process POST data containing rogue values for such fields! E.g. for handleTableQuery() use the 'readonly' property on your columns or use a validation function., client: 192.168.1.29, server: localhost, request: "POST /modals/nat-alg-helper-modal.Sat Dec  2 17:01:28 2017 daemon.warn nginx: 2017/12/02 17:01:28 [warn] 5220#0: *33 [lua] ui_helper.lua:72: mergeAttributes(): 'readonly' or 'disabled' attributes can be easily removed client side, making fields editable. Use labels or make sure your code does not process POST data containing rogue values for such fields! E.g. for handleTableQuery() use the 'readonly' property on your columns or use a validation function., client: 192.168.1.29, server: localhost, request: "POST /modals/nat-alg-helper-modal.Sat Dec  2 17:01:28 2017 daemon.warn nginx: 2017/12/02 17:01:28 [warn] 5220#0: *33 [lua] ui_helper.lua:72: mergeAttributes(): 'readonly' or 'disabled' attributes can be easily removed client side, making fields editable. Use labels or make sure your code does not process POST data containing rogue values for such fields! E.g. for handleTableQuery() use the 'readonly' property on your columns or use a validation function., client: 192.168.1.29, server: localhost, request: "POST /modals/nat-alg-helper-modal.Sat Dec  2 17:01:28 2017 daemon.warn nginx: 2017/12/02 17:01:28 [warn] 5220#0: *33 [lua] ui_helper.lua:72: mergeAttributes(): 'readonly' or 'disabled' attributes can be easily removed client side, making fields editable. Use labels or make sure your code does not process POST data containing rogue values for such fields! E.g. for handleTableQuery() use the 'readonly' property on your columns or use a validation function., client: 192.168.1.29, server: localhost, request: "POST /modals/nat-alg-helper-modal.Sat Dec  2 17:01:28 2017 daemon.warn nginx: 2017/12/02 17:01:28 [warn] 5220#0: *33 [lua] ui_helper.lua:72: mergeAttributes(): 'readonly' or 'disabled' attributes can be easily removed client side, making fields editable. Use labels or make sure your code does not process POST data containing rogue values for such fields! E.g. for handleTableQuery() use the 'readonly' property on your columns or use a validation function., client: 192.168.1.29, server: localhost, request: "POST /modals/nat-alg-helper-modal.Sat Dec  2 17:01:28 2017 daemon.warn nginx: 2017/12/02 17:01:28 [warn] 5220#0: *33 [lua] ui_helper.lua:72: mergeAttributes(): 'readonly' or 'disabled' attributes can be easily removed client side, making fields editable. Use labels or make sure your code does not process POST data containing rogue values for such fields! E.g. for handleTableQuery() use the 'readonly' property on your columns or use a validation function., client: 192.168.1.29, server: localhost, request: "POST /modals/nat-alg-helper-modal.Sat Dec  2 17:01:28 2017 daemon.warn nginx: 2017/12/02 17:01:28 [warn] 5220#0: *33 [lua] ui_helper.lua:72: mergeAttributes(): 'readonly' or 'disabled' attributes can be easily removed client side, making fields editable. Use labels or make sure your code does not process POST data containing rogue values for such fields! E.g. for handleTableQuery() use the 'readonly' property on your columns or use a validation function., client: 192.168.1.29, server: localhost, request: "POST /modals/nat-alg-helper-modal.Sat Dec  2 17:01:28 2017 daemon.warn nginx: 2017/12/02 17:01:28 [warn] 5220#0: *33 [lua] ui_helper.lua:72: mergeAttributes(): 'readonly' or 'disabled' attributes can be easily removed client side, making fields editable. Use labels or make sure your code does not process POST data containing rogue values for such fields! E.g. for handleTableQuery() use the 'readonly' property on your columns or use a validation function., client: 192.168.1.29, server: localhost, request: "POST /modals/nat-alg-helper-modal.Sat Dec  2 17:01:28 2017 daemon.warn nginx: 2017/12/02 17:01:28 [warn] 5220#0: *33 [lua] ui_helper.lua:72: mergeAttributes(): 'readonly' or 'disabled' attributes can be easily removed client side, making fields editable. Use labels or make sure your code does not process POST data containing rogue values for such fields! E.g. for handleTableQuery() use the 'readonly' property on your columns or use a validation function., client: 192.168.1.29, server: localhost, request: "POST /modals/nat-alg-helper-modal.root@livebox:~#

[shdf]

@-Mirco-
ho modificato il mio post #153
per me è un bug.

Ho sostituito il file /etc/ledfw/stateMachines.lua con quello di /rom/etc/ledfw/stateMachines.lua e dopo il reboot ora tutto va bene.
Dunque la modifica fatta in questo file a me non va.

[yhcim86]

Segnalo probabile bug in dispositivi connessi tramite ethernet mi da 0 invece ho connesso alla porta Ethernet 0 un cordless VoIP Siemens con indirizzo IP fisso e alla porta 1 il mio vecchio modem router dgnd4000 sempre con indirizzo IP fisso assegnato tramite Mac address.
A qualcuno è capitato il problema?
In più perché se connetto con il wifi il mio smartphone il DHCP gli assegna l'indirizzo 232 non dovrebbe assegnargli un indirizzo sequenziale tipo 4 visto che il 2 e3 li ho riservati???

[condor74]

@Ansuel
FW 104 009 - GUI 3.33
Impossibile fare login dopo aver immesso pswd admin non succede nulla rendendo impossibile accesso alla nuova GUI

[-Mirco-]

Trace aggiornato con le ultime 2 segnalazioni.

[Ansuel]

fixato.

[Diavulrus]

Segnalo quello che penso sia un bug che affligge solo me e il mio modem .
Non sono mai riuscito ad aggiornare la gui dalla gui stessa perché viene ricaricata la pagina senza eseguire l' aggiornamento.
Ho trovato questi errori nel file di log di nginx, non so se possono essere utili per risolvere il problema:

Codice: [Seleziona]

2017/12/03 15:54:26 [error] 22905#0: *37 [lua] sessionmgr.lua:231: redirectIfNotAuthorized(): Unauthorized request, client: 172.16.0.15, server: localhost, request: "GET / HTTP/1.1", host: "172.16.0.1"2017/12/03 15:56:20 [warn] 25067#0: duplicate MIME type "text/html" in /etc/nginx/nginx.conf:41
2017/12/03 15:56:30 [error] 25076#0: *2 [lua] sessionmgr.lua:231: redirectIfNotAuthorized(): Unauthorized request, client: 172.16.0.15, server: localhost, request: "POST /ajax/mobiletab.lua?auto_update=true HTTP/1.1", host: "172.16.0.1", referrer: "http://172.16.0.1/"
2017/12/03 15:56:31 [error] 25076#0: *2 [lua] sessionmgr.lua:231: redirectIfNotAuthorized(): Unauthorized request, client: 172.16.0.15, server: localhost, request: "GET / HTTP/1.1", host: "172.16.0.1", referrer: "http://172.16.0.1/"
2017/12/03 15:57:25 [error] 25076#0: *6 attempt to set ngx.header.HEADER after sending out response headers, client: 172.16.0.15, server: localhost, request: "POST /modals/internet-modal.lp?auto_update=true HTTP/1.1", host: "172.16.0.1", referrer: "http://172.16.0.1/"


[Patatrak]

Diavulrus, non sei il solo. Succede anche a me. Ogni volta sono costretto ad aggiornare con WinSCP

[Ansuel]

che versione? e il problema quale è ? non riesco a riprodurlo dalla mia
idee per riprodurlo ?

[-Mirco-]

fixato.

Quali? così li depenno

[Patatrak]

Nelle ultime versioni mi succede sempre. Al momento sto con la 3.32 (non ho aggiornato perchè ho letto del problema del login). Ps il bridge mode appare sempre disabilitato e pallino grigio.