WIP: lantiq-xrx200: Add support for AVM FRITZ!Box 7430 #2270
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Recreation of #2268 |
github-actions
bot
added
3. topic: docs
|
Currently, the setup wizard still shows an option for the 5 GHz WLAN, while the device only has 2.4 GHz. Also the MAC address seems to be wrong (00:02:03:04:05:06) |
|
For the incorrect MAC address, check whether a valid MAC address is set for LAN in /etc/board.json. Check the OUI matches an AVM assignment. If this looks good, add the board to the corresponding special case in gluons primary-mac update script. For the wireless, the output of |
|
@blocktrron thank you for your quick reply. The output from iw phy shows the following. Interestingly, it says 5 GHz is supported, even though OpenWrt's toh says the opposite: |
|
Okay, so for the MAC address, just patch the primary mac script. Regarding the WiFi - the Chip might have non-advertised dualband capability or AVM didn't correctly program the calibration data. However, can you check if the wireless config configures the radio as 2.4 or 5 GHz? In Gluon this should happen with https://github.com/freifunk-gluon/gluon/blob/master/package/gluon-core/luasrc/lib/gluon/upgrade/200-wireless#L15 |
|
@blocktrron thanks for your reply. I am trying to get my hands on a 7430 right now. I created this branch just for a few community members who sadly don't have that much time to try things out right now. Once I get my hands on one, I'll report back on how things work out and also patch things if needed. |
|
I've tested the 7430 a while ago in OpenWrt. The ART offset is wrong. |
|
@s-2 just made me aware that it has been fixed: |
|
@GoliathLabs Can you check if it works now as expected or if we need to backport the linked patch? |
|
@blocktrron Hi, thanks for the nice Gluon RC3 meeting. I am currently trying to get my hands on a 7430. As soon as I or someone from FFMUC gets hold of one, the new changes can be tested accordingly |
|
@blocktrron Hi, I added a special case for this device's primary mac. I'm also happy to report that I also got my hands on a 7430. It has a proper MAC on the lan interface. I'm now building a new version of the firmware for further testing. |
|
It seems gluon configures the (unadvertised) 5 GHz WiFi on the 7430, which doesn't work |
|
Meanwhile, the other problem is that I can't seem to get a DHCP lease from my home router on the device. I've put one RJ45 in the LAN1 which didn't work. I also tried LAN4. Any ideas? |
|
@CodeFetch or @AiyionPrime, any ideas? Would love to see this device end up in the next release |
|
I'm sorry; my experience with lantiq targets is close to none. The current OpenWrt master does have the same issue? |
|
@AiyionPrime do you suggest I build gluon against the latest OpenWrt master, or should I try a snapshot of OpenWrt on the device and see if it still has the issue? |
|
@GoliathLabs Regarding the radio - Do i get this right that the signel WiFi radio is incorrectly configured as 5GHz? Does Regarding "obtaining DHCP lease on LAN1" - Is the link not coming up or the interface on the box dead? The Box itself should provide DHCP on all 4 LAN ports by default. |
|
@GoliathLabs the latter. I wanted to make sure you're not hunting something somebody might already have fixed upstream. |
|
@AiyionPrime @blocktrron I am in the process of rebuilding the firmware based on the gluon masters HEAD. Will report back this evening :) |
|
Do as you like; just keep in mind, gluons master does not match OpenWrts master. |
|
@GoliathLabs I really appreciate your work on this. But feel like you do not understand my request yet, or at least not how to fulfill it: No matter how often you update your gluon-build-tree, on gluons master branch you will never get OpenWrt's main. To fulfill my request to inspect, whether the problem of the second misdeclared phy does still exist in OpenWrt's main, you'd need to build OpenWrts most recent commit, not gluons. That said, it would be sufficient if you flashed yesterdays snapshot on it |
|
@AiyionPrime sorry, I did forget that gluon's master branch is based on the 21.02 OpenWrt branch. I'll give the OpenWrt snapshot a shot and report back. Thanks for your help on getting the problems diagnosed :) |
|
@GoliathLabs Looks like your iw phy output is from your Notebook / PC. If not, tell me your secret how you enabled 802.11ax capability on the FritzBox ;) For the radio - can you share a dump of your |
|
I've installed the latest OpenWrt snapshot just this evening. @blocktrron the dump of the /dev/mtd0 partition (as urlader lives in there according to As GitHub only allows specific filetypes, I've wrapped a zip file around the partition dump The |
|
@GoliathLabs Thanks for sharing your bootloader partition. I've extracted the EEPROM data from it and indeed the extracted calibration data looks incorrect:
I haven't yet further looked into whether the data on your device s back or the extraction tooling is misbehaving. But at lest this explains why the CLI output indicated 5GHz band support. |
|
@GoliathLabs Indeed the EEPROM extraction process seems to be broken. The deflated binary uses the incorrect byte-order. After revising aforementioned, We receive a better-looking result:
The first 4 bytes do however still need to be removed, as 6 bytes from the 3rd byte on should contain a MAC address, and after removing these 4 bytes, the resulting MAC-address is assigned to AVM. |
|
@GoliathLabs were you able to test out my proposal above? At least verification should be fairly easy by modifying the firmware itself, as it is loaded from userspace. |
|
Hi @blocktrron could you maybe provide more detailed instructions what to test? I have this router but it bootloops currently with firmware build from gluon-master - but can be resetted through eva_ramboot.py |
|
we tested the device in December (Gluon v2022.1.1). it only bootlooped in August because the bootloader was set to boot from the second partition. Maybe the first flash failed somehow. Everything appeared to work fine.The device managed 22,4mbit/s DL and 12,3mbit/s UL speeds over 250/40 VDSL2 35b over a Wireguard vpn from Freifunk Aachen to speedtest.net I'll do the checklist in early January on my device and create a new PR and credit @GoliathLabs (unless he doesn't want to be credited). |
|
Perfect. Credits are always welcome :P |
|
Done on Gluon 22 First some stuff I noticed myself: fritz_nand_tffs isn't working: bootlader environment mac addressesI will go through this thread comment by comment: uci show wireless
We map the primary MAC to the lan interface in /etc/board.jsonip aAs we can see: WiFi still uses the wrong mac, so I'll need to take a look at EEPROM. interestingly enough iw phy0 infoGluon logreadI don't want to accidentally loose any of the above, so I'll continue in a second post below. |
|
#2270 (comment) Flexible setups with Mesh-LAN probably aren't possible until #2393 is implemented. (unless someone wants to adjust the config manually on every update) here are the urlader and tffs of my device: offset 0x1e000 yields an empty result, offset 0x1e800 works. How I applied the required changes (removed 4 Bytes at the start and left all FF Bytes at the end): I replaced Could this be due to permission issues or is the extracted EEPROM calibration data not correct, yet? full boot log |
|
aaah, no idea why, but I needed to use 5 in the slice operator to actually remove 4 Bytes (not 3 Bytes) This looks way better now: edit: interfaces the eth0/lan(1/2/3/4) mac address (one) is different on each reboot still :/ |
|
suggested change to Does this work or would it cause issues since DSL is called wan in board.json? (easier for me to ask than to build in order to answer this question) The dsa lan1-lan4 interfaces match the "silkscreen" on the board (I verified this: the active port has UP instead of LOWERLAYERDOWN) |
dzzinstant
added a commit
to dzzinstant/gluon
that referenced
this pull request
May 14, 2024
Reconstruction of initial patch from freifunk-gluon#2270 by @GoliathLab * Add AVM Fritz!Box 7430 to list of supported devices and targets. * Add avm fritz7430 to primary-mac update script.
|
this is waiting on upstream for openwrt/openwrt#15501 to be merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
think
sysupgrade [-n]orfirstbootusually means: gluon profile name must match image name
(https://gluon.readthedocs.io/en/latest/features/configmode.html)
is_outdoor_devicefunction inpackage/gluon-core/luasrc/usr/lib/lua/gluon/platform.lua