freifunk-franken
/
firmware
9
7
Fork 13
Code Issues 48 Pull Requests 7 Releases 17 Wiki Activity

Fritzbox 4040 zeigt Bad Request mit Chromium 99.0.4844.51 #220

New Issue
Closed
opened 2022-03-16 01:28:49 +01:00 by fbl · 7 comments
fbl commented 2022-03-16 01:28:49 +01:00
Owner
Copy Link

Firmware geflashed und das war’s dann. 3h etwa versucht auf den Router zu kommen, hat sich weder im Monitoring gemeldet noch war er sonst irgendwie erreichbar. trainstation.freifunk war hin und wieder mal verfügbar, aber ohne funktionstüchtiges DHCP.

> Firmware geflashed und das war’s dann. 3h etwa versucht auf den Router zu kommen, hat sich weder im Monitoring gemeldet noch war er sonst irgendwie erreichbar. trainstation.freifunk war hin und wieder mal verfügbar, aber ohne funktionstüchtiges DHCP.
fbl added this to the 20220405-beta milestone 2022-03-16 01:28:49 +01:00
fbl added the
bug
 label 2022-03-16 01:28:49 +01:00
fbl self-assigned this 2022-03-16 01:28:49 +01:00
SebaBe commented 2022-03-20 13:47:34 +01:00
Copy Link

Tested with node-20211224
Device got upgraded from adsc_20201028

Device has potential problems, not easy to reproduce.

Once the node froze completely after bootup. It was reachable for a few seconds via ping and ssh.

Ping via ETH to fdff::1 has average 1.5ms (80 packets). Seems a bit high.

Inital setup via WebUI was successfull. Password change, too.
But changing the posion -> "Submit" results in a "Bad Request" error screen.
Postion change via ssh was successfull.

After above mentioned problems the node is now running smooth and functional from the client perspective, Internet is working.

Tested with node-20211224 Device got upgraded from adsc_20201028 Device has potential problems, not easy to reproduce. Once the node froze completely after bootup. It was reachable for a few seconds via ping and ssh. Ping via ETH to fdff::1 has average 1.5ms (80 packets). Seems a bit high. Inital setup via WebUI was successfull. Password change, too. But changing the posion -> "Submit" results in a "Bad Request" error screen. Postion change via ssh was successfull. After above mentioned problems the node is now running smooth and functional from the client perspective, Internet is working.
4040-Bad_Request-Error.png
24 KiB
4040-Bad_Request-Error.png
SebaBe commented 2022-03-20 13:53:01 +01:00
Copy Link

Node froze again after some minutes.
Client was connected via WiFi. No more Internet connectivity available.

While reconnecting to the WiFi the client is not able to obtain an IP configuration.

Node froze again after some minutes. Client was connected via WiFi. No more Internet connectivity available. While reconnecting to the WiFi the client is not able to obtain an IP configuration.
SebaBe commented 2022-03-20 15:49:26 +01:00
Copy Link

tested with https://fw.sgstbr.de/fff-node-20211224-27-g128a748-avm_fritzbox-4040-sysupgrade.bin

First finding: Bad Request Error in WebUI after setting a new password.

Tried using Firefox, works -> Chromium Version 99.0.4844.51 has problems on two different PCs.
(I configured a GL-INET 150 with that Chromium without problems. This 4040 was the first device with that behaviour)

tested with https://fw.sgstbr.de/fff-node-20211224-27-g128a748-avm_fritzbox-4040-sysupgrade.bin First finding: Bad Request Error in WebUI after setting a new password. Tried using Firefox, works -> Chromium Version 99.0.4844.51 has problems on two different PCs. (I configured a GL-INET 150 with that Chromium without problems. This 4040 was the first device with that behaviour)
fbl commented 2022-03-20 19:00:05 +01:00
Author
Owner
Copy Link

tested with https://fw.sgstbr.de/fff-node-20211224-27-g128a748-avm_fritzbox-4040-sysupgrade.bin

Abgesehen von dem etwas besonderen Problem mit dem WebUI geht mit dem aktuellen master (das Image aus dem Link) alles? Dann war das Problem wahrscheinlich das gleiche wie #203, #209 gewesen.

> tested with https://fw.sgstbr.de/fff-node-20211224-27-g128a748-avm_fritzbox-4040-sysupgrade.bin Abgesehen von dem etwas besonderen Problem mit dem WebUI geht mit dem aktuellen master (das Image aus dem Link) alles? Dann war das Problem wahrscheinlich das gleiche wie #203, #209 gewesen.
fbl added the
node
 label 2022-03-20 19:00:43 +01:00
SebaBe commented 2022-03-20 19:25:37 +01:00
Copy Link

Die Fritzbox lief nun 4h stabil mit dem Build und auch nach einem reboot tut alles wie erwartet.

Die Fritzbox lief nun 4h stabil mit dem Build und auch nach einem reboot tut alles wie erwartet.
fbl changed title from Fritzbox 4040 mit node scheint kaputt zu sein (20211224) to Fritzbox 4040 zeigt Bad Request mit Chromium 99.0.4844.51 2022-03-21 11:16:14 +01:00
fbl modified the milestone from 20220405-beta to next-bugfix 2022-03-21 11:16:22 +01:00
fbl removed the
node
 label 2022-03-21 11:16:31 +01:00
fbl commented 2022-04-05 14:05:23 +02:00
Author
Owner
Copy Link

Hab das Problem mit Chromium 99.0.4844.84 und Firmware 20211224-47-g20ecca3 nicht reproduziert bekommen.

Hab das Problem mit Chromium `99.0.4844.84` und Firmware `20211224-47-g20ecca3` nicht reproduziert bekommen.
fbl added the
more details required
 label 2022-04-05 14:05:54 +02:00
fbl modified the milestone from next-bugfix to 20220814 2022-04-21 13:10:21 +02:00
fbl commented 2022-04-21 13:10:37 +02:00
Author
Owner
Copy Link

Scheint nicht wieder aufgetreten zu sein.

Scheint nicht wieder aufgetreten zu sein.
fbl closed this issue 2022-04-21 13:10:37 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
0.5.x
20240401
20240401-beta
20240119-beta
20230330
20230321-beta
20160213-beta
20221201
20221019
20220814
20220413
20220405-beta
20211224
20211220
20211201-beta
20210226
20210218
20210211-beta
20200501
20200423-beta
20200118
20191224
20191214-beta
20191130-alpha
20191123-alpha
20181202
20181128-beta
20180802
20180802-beta
20180726-beta
20180304-alpha
20180303-alpha
20170918
20170918-beta
20170218-alpha
20170110
20170110-beta
20161105-beta
20161008-beta
20160506
20160506-beta
20160310
0.5.2
0.5.2-b2
0.5.2-b1
0.5.1
0.5.1-b2
0.5.1-b1
0.5.0
0.5.0-b1
0.4.3
0.4.2
0.4.1
0.4.0ol
0.4.0f
0.4.0rc5f
0.4.0rc4ol
0.4.0rc4f
0.4.0rc3f
0.4.0rc2f
0.3.999f
0.3.999
0.3.998
0.3.99
0.3
0.2.1
0.2
0.1
Labels
Clear labels   
RFC

   
RFT

   
WIP

   
blocked

   
bsp

touching bsp files or adding devices

  
bug

Something is not working

  
build/scripts/tools

touching buildscript or other tools

  
duplicate

This issue or pull request already exists

  
feature

New feature

  
fixed

Issue that got resolved

  
layer3

only for layer3 FW

  
mantis

Imported from mantis

  
more details required

Reported information is insufficient to debug the issue

  
needs changes

   
node

only for node FW

  
packages/fff

touching our packages

  
rejected

Rejected or won't fix

  
security

   
trivial

simple non-functional changes that are mostly matter of taste

  
upstream

touching upstream version, build or feed patches

No Label
RFC
RFT
WIP
blocked
bsp
bug
build/scripts/tools
duplicate
feature
fixed
layer3
mantis
more details required
needs changes
node
packages/fff
rejected
security
trivial
upstream
Milestone
Clear milestone
No items
No Milestone
20220814
Assignees
Clear assignees
No Assignees
fbl
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: freifunk-franken/firmware#220
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?