DSL actually working? #6
Comments
|
So I figured that the configuration of the virtual switch (with the VLAN ID 7) is somewhat the problem. But I'am not experienced enough to set this switch up. Could somebody please help? |
|
So this is the output of What is also wierd: The data rate shows only 20 Mbit... but it should be 100/40 :( |
|
Hi there. |
|
How did you manage to login?! I tried every combination with and without # etc. it never worked... |
|
I think, exactly as described within the post I previously linked. |
|
I tried the latest image, but no luck. Still 20 mbit and the version is very buggy. Always crashes when you try edit the config. Still couldn't log into my DSL, even with all of the switch settings like in the forum post. |
|
Sorry, I don't develop LuCI so I can't help with this. Maybe a newer version might be better. |
|
I tried the latest version from 4th of july but no luck, can't log the ppoe in. I cant add a new VLAN id, when I click the add button nothing happens. And its still at 20 mbit. These are all VLAN settings from a working EB conencted with telekom VDSL with the original image. |
|
I just tried to get DSL running, with success. Add the following Update the dsl section from to Reboot. As DSL firmware I used the vr9_dsl_fw_annex_b.bin (20MBit/s Downstream only). |
|
Thanks for the help with the VLAN setup! And then use the So this uses the Firmware of a FRITZ!Box 7490 FRITZ!OS 6.93. |
|
So after some intense testing I can say that it works, but you're not able to get 100 Mbit only ~76 Mbit/s. The |
|
Maybe we can unleash the dual core for this at the cost of that asterisk won't work anymore. |
|
The Asterisk is all the call handling? This would be not a big deal. How can I archieve it? Could you build a version and upload it to appbox? Otherwise I will setup an openWRT build environment :) https://forum.lede-project.org/t/how-can-we-make-the-lantiq-xrx200-devices-faster/9724 |
|
I can try to provide an experimental one... |
|
That would be awesome :) I tested 100 Mbit with the Vodafone firmware and the sirq raises to 70%. But another big problem is the WLAN of the easybox... It's unusable with the webinterface. You can only set WEP and nothing else, changig the password also is not working therefore WLAN is completely unusable for normal users. Can a working WLAN network be setted up via ssh? |
|
Can this issue be closed? I managed to get DSL working with VLAN as well, this box is not any different than any other OpenWRT router that does pppoe on a VLAN. I could post my /etc/config/network in case anyone still cares. The high load on a fast DSL could be another issue, same is true for the second core, and the wifi interface to luci. |
|
I will maybe open two other issues for the high CPU usage and one for the WLAN. And yes this can get closed. Is there somekind of official documentation for the VLAN pppoe? |
|
It would be great if you could post your
/etc/config/network file.
Right now I still have trouble during compilation. (Prebuilt did not work
for me, all changes on the Router were deleted after reboot).
But your /etc/config/network could really help me in the future.
Thanks in advance and Prost! (Cheers!)
|
|
This is for a dslite setup so it looks different to what you will need. |
|
Any news regardign the |
At least I added some builds with "smp" as prefix, which enables the second core. |
|
I would also test the new version. Translated with www.DeepL.com/TranslatorIch würde die neue Version auch testen. |
|
Since 30.8. the image contains smp, see the files in the directory. Maybe thats what causes the bootloop. We would need to connect a serial console and look into the bootlog. I quickly tested the newest build from 2. of september. Not working at all, you can't reboot the device, without it resetting itself. Even ssh thinks it's a new host, so it does a factory reset at every boot. @icke68746 I didn't got any bootloops or anything. |
|
So after some intense testing hours I can say that you first have to flash the stock image, then the openWrt recovery image, upload the NON-SMP image and flash it via the webinterface. Boot into the NON-SMP fw and then flash the SMP firmware from there. Everything else is creating a zombie-Wrt. |
|
@majuss it might be more useful to understand why the smp image can not be flashed directly and fix that, maybe bisection could give a clue |
|
That's really weird that this doesn't work :-( |
|
I think it has something to do with the partitioning. The SMP image can't create the partitions correctly and if you first flashed the non-SMP one the partitions are already set up in some wierd way (I hope that makes sense somehow). Are you sure that the asterisk (so fixed line telephony?) is not working anymore? For me it seemed pretty alive :D I will maybe test it. |
|
Still not able to get a reproducible working openWrt with smp -.- The overlay fs cant mount and so the config is getting lost after reboot. |
|
@Quallenauge could you look into the issue or hint me in a direction? I'am somewhat lost right now. |
|
Not really. But can you let me know the steps in detail how to to reach your current state; what steps are needed (in detail please). Actually I use the non-smp version. |
|
Ah thank you. So I should just try every annex and see if one yields 100 mbit? |
|
Maybe this helps. Please share your results. Sadly I can't verify and test atm. |
|
I tried testing it, no success it kills the connection every few seconds, totally bugged out. |
|
@majuss what do you mean by "kill connection"? Do you hear relay switching? This patch shouldn't impact on dsl modem, because it always connected to phone line directly. |
|
I will test it tomorrow and will upload my config and logs. |
This is the log when I hit the restart button on my WAN interface via the gui. For me it is stable at 60 Mbit, but yesterday with the connection of a friend, same Telekom 100 Mbit, the box got 100 Mbit but restarted randomly and kicked out the WAN interface, it thought that no cable is connected after all. My etc/config/network: |
|
Hi majuss, just curious, could you answer these questions:
|
|
The output: I did not wrote annex a in there, it was preconfigured that way. The GUI say "Annex a + b + ..." |
|
@majuss And could you please post here output for |
|
|
Ok. Let me check with my connection. I can compare speed with speedport hybrid from Telekom. |
|
Hi majuss, I guess he GUI does not say "Annex a + b + ...", but "Annex A + L + M...". Unless you have another GUI version than me.
|
|
Still 60 Mbit: |
|
Thanks for testing. Sorry, I cannot tell you the solution. But your reports are instructive. For example it looks like in your case it does not matter if the internal splitter (i.e. highpass for DSL) is/is not used. Also interesting would be to hear if your 60Mb/s connection is stable with the new settings. As kovz already indicated, your DSL values reported earlier are confusing. Downstream data rate is 60Mb/s, though it claims that max attainable rate were 113 Mb/s. In case you have access to another box, which also shows you the data rate (is this possible e.g. with Fritz!OS? I have no idea), you could check if this other box manages to get a better rate. Maybe your provider limits the downstream rate to 60 Mb/s? For example my DSL as agreed on with my provider is limitted to 50Mb/s. My DSL status shows a data rate of 51 Mb/s, while the max attainable rate is 128 Mb/s. Or lacking better ideas: maybe the non-smp kernel would help? |
|
Here are my new DSL values: Other boxes get 100 Mbit, the images before the DSL relay switch fix also got 100 Mbit. SMP is a must because the kernel interrupts eat so much CPU that you can't ever reach more than 70 Mbit. |
|
My interpretation of the new DSL status:
Result: higher max. attainable data rates, now 128.6/42.2 instead of 113.7/35.9 Mb/s. |
|
Hi majuss,
Because this looks so wierd, could you double-check this? Could you comment out the driver load line in /etc/modules.d/gpio-nxp-74hc164 by prefixing a '#' character, i.e. change the content from |
|
Nope exactly the same. |
Guess not loading the driver is like the situation before the relay switch.
Guess this is still true for you. Sorry, I am at a loss now. |
|
Hm you guess it :D? Can't I revert all chages to fbb617f but implement the disabling of the subpages, so I can check if anything changes? Btw. I tried the latest Fritz!Box Lab 7490 modem-firmware and it yields in these results: Which modem-firmware are you using? |
|
Reverting changes or cloning from fbb617f state, and then apply this patch: guess ;-) this is possible. And it is a good idea, because this could strengthen or dampen the impression that the latest changes indeed broke something. BTW, you also could omit the lcd display driver to make sure it does not impair DSL. The usage of some of the new gpios which are controlled by kovz' changes is unknown. Currently these are all set to value 1. I don't know what their default value after box init is. Maybe it is 0 and one of these also affect DSL processing. So before you reflash an older version, you could try out BTW, I am using this one. Think it is version 90D02 / 591407 and this is the latest. |
|
So as a first result, your linked firmware will crash the whole box, as soon as it tries to sync :D |
|
Strange. MD5 hash is ade291d69f28f2fdb6b1a4551d6eae9b. Permanently running here in two places in an o2 Box 6431 (ADSL2 annex-b 16 Mb/s, and in a bt homehub 5a (VDSL2 annex-b 50 Mb/s with vectoring). |
|
Same hash, so it seems that it's not usable with the EB. How can I disable the LCD driver? Didn't found something fitting in I only have these Pins in My self compiled image is crashing after few minutes :( Do I also need to compile an own recovery image? |
|
So I can contribute two new aspects: The image from 18.12.2018 is completely broken. I flashed the stock firmware, then the 18.10.2018 recovery and after that the smp image. But this crashes just after 4-5 seconds screen time. @Quallenauge please look into the issue. I prepared my EB with a modified stock image with enabled ssh and interesting enough, this image is also getting 54/32 Mbit. So maybe my connection has some kind of error, I will call Telekom tomorrow. |
|
So Telekom slowed my connection down because the DSLAM "sensed" some errors. Now I'am back to 110/37. But the latest image is still causing openWrt to crash directly after boot. It tries to load the screen and then it crashes. After 3-4 crashes the screen goes red and the EB won't boot anymore with the usual message. I compiled my own image yesterday without all the LCD stuff (because the EB crashed right when it tries to render the network stats) and without lualanes (because it gives a, for me, unsolvable dependency error). And this image is just working flawless. |
|
Hey majuss, Would you share your Image resource and what do you think about the DSL driver Problem? White just tried to download the official Firmware of the Vodafone site for this device and it was possible to extract all folders and files so maybe you can't just take this original driver which works on the 100/40 MBit/s Internet accesses well. I have two boxes one is still running der Original Firmware with stable 95/27, but that's a limitation of my provider. It had one day also 105/36. I would also love to get the Openwrt-wiki updated how to configure the device correctly. |
|
Which driver problem do you mean? You can use the DSL-Modem firmware from a FritzBox 7490 which has the exact same DSL-Modem and reaches 100/40 but you can't use the fixed telephone anymore. For the image, an install guide and configuration options see my repo: https://github.com/majuss/easybox904 |
|
Hey Majuss, would you share your newest image and development state of this eb904xdsl project? It seems to be a bit dead in the openwrt forum and there is none who wants to update the "TOH-Page" of the EB904. Thank you for your great work! I guess you use the device still with satisfying results. I saw there should be some improvements in 19.07 also for RALINK devices. So maybe the wifi performance and usabilty will improve. ;) |
|
I was not able to compile an image a week ago and I also don't use the EB anymore, since I upgraded to 250 Mbit 35b. |
Hi there!
When I enter all my DSL credentials via PPPoE, hit save and apply and reconnect the dsl0 interface, nothing happens and the box can't login into the DSL connection.
Should this be working right now or is it still work in progress?
The text was updated successfully, but these errors were encountered: