Quallenauge
DSL actually working?
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?
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 ifconfig on a original FW easybox. I think with that information someone could reconstruct the Switch settings for openWRT.
What is also wierd: The data rate shows only 20 Mbit... but it should be 100/40 :(
root@easy:~# ifconfig
br-lan Link encap:Ethernet HWaddr XXX
inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:624541 errors:0 dropped:0 overruns:0 frame:0
TX packets:370049 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:56594044 (53.9 MiB) TX bytes:81366278 (77.5 MiB)
br-lan1 Link encap:Ethernet HWaddr YYY
inet addr:192.168.3.1 Bcast:192.168.3.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:24690 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:1482544 (1.4 MiB)
eth0 Link encap:Ethernet HWaddr XXX
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4391218 errors:0 dropped:117 overruns:0 frame:0
TX packets:13245353 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:556435907 (530.6 MiB) TX bytes:113289512 (108.0 MiB)
eth0.66 Link encap:Ethernet HWaddr XXX
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:978680 errors:0 dropped:0 overruns:0 frame:0
TX packets:370052 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:184983722 (176.4 MiB) TX bytes:82846724 (79.0 MiB)
eth0.71 Link encap:Ethernet HWaddr YYY
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:24692 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:1581480 (1.5 MiB)
imq1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16000 Metric:1
RX packets:329062 errors:0 dropped:0 overruns:0 frame:0
TX packets:329058 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:33462241 (31.9 MiB) TX bytes:33462033 (31.9 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:57415 errors:0 dropped:0 overruns:0 frame:0
TX packets:57415 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8897588 (8.4 MiB) TX bytes:8897588 (8.4 MiB)
ppp50 Link encap:Point-to-Point Protocol
inet addr:AAA P-t-P:AAA Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:144027 errors:0 dropped:0 overruns:0 frame:0
TX packets:328961 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:63227971 (60.2 MiB) TX bytes:33426084 (31.8 MiB)
ptm0 Link encap:Ethernet HWaddr ZZZ
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12817835 errors:0 dropped:0 overruns:0 frame:0
TX packets:3774190 errors:0 dropped:12 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:547722283 (522.3 MiB) TX bytes:54648004 (52.1 MiB)
ptm0.7 Link encap:Ethernet HWaddr ZZZ
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:160123 errors:0 dropped:0 overruns:0 frame:0
TX packets:345062 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:65696950 (62.6 MiB) TX bytes:42526629 (40.5 MiB)
ra0 Link encap:Ethernet HWaddr XXY
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
ra1 Link encap:Ethernet HWaddr XXY
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
rai0 Link encap:Ethernet HWaddr XXZ
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
rai1 Link encap:Ethernet HWaddr XYZ
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Hi there. Sadly the ifconfig doesn't show the switch settings. Also some settings are set within the vendor kernel. At least I was able to connect to the T-DSL VDSL provider with low speed (20MB/s). I'm not sure, but I guess the speed is a limitation from the used vdsl modem. Maybe a newer release would help, but I don't know. lantiq-vdsl-fw: update to provide recent vectoring firmware I have a look how the setting was made for this, I think it was close to your settings. Try to set also the CPU port 0 to "tagged", see here: https://telekomhilft.telekom.de/t5/Telefonie-Internet/Wie-OpenWRT-Router-am-FTTH-Anschluss-betreiben/td-p/2283926
How did you manage to login?! I tried every combination with and without # etc. it never worked... Could you implement the new modem firmware to your openWRT release?
I think, exactly as described within the post I previously linked. Newer builds should contain the vdsl firmware, but I haven't tried that. https://app.box.com/s/hvqg535dnubt4r2ontpmtodpvt6ydf00/folder/36913951101
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. Also the kind how the switches are connected together isn't and straight forward. (You can easily lock out yourself from the device and have to use the recovery.)
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.
enable_vlan@vlan = 1
lan_netdevice@vlan = eth0
wan_netdevice@vlan = eth1
switch_port_num@vlan = 8
logical_port_num@vlan = 7
logical_total_port_num@vlan = 8
logical_cpu_port@vlan = 6
port_phyconf@vlan = 0 0 0 0 5 4 6 7
max_vlan@vlan = 4
lan_vlan_id@vlan = 66
lan_port@vlan = 0 1 2 3 4
wan_port@vlan = 5
wlan_port@vlan = 4
active_vlan@vlan = 3
vlan1_name@vlan = default LAN
vlan2_name@vlan =
vlan3_name@vlan =
vlan4_name@vlan =
vlan1_id@vlan = 71
vlan2_id@vlan = 66
vlan3_id@vlan = 66
vlan4_id@vlan = 4
vlan1_tagged@vlan = 1
vlan2_tagged@vlan = 0
vlan3_tagged@vlan = 1
vlan4_tagged@vlan = 0
vlan1_port@vlan = 4
vlan2_port@vlan = 0 1 2 3
vlan3_port@vlan = 4
vlan4_port@vlan =
vlan1_ssid@vlan = 0
vlan2_ssid@vlan =
vlan3_ssid@vlan =
vlan4_ssid@vlan =
vlan1_brwan@vlan = 0
vlan2_brwan@vlan = 0
vlan3_brwan@vlan = 0
vlan4_brwan@vlan = 0
vlan1_bind_rtwan@vlan = 0
vlan2_bind_rtwan@vlan = 0
vlan3_bind_rtwan@vlan = 0
vlan4_bind_rtwan@vlan = 0
wan_lan_share@vlan = 0
vlan_tagged@lan0 = 0
vlan_1p@lan0 = 0
vlan_id@lan0 = 0
vlan_tagged@lan1 = 0
vlan_1p@lan1 = 0
vlan_id@lan1 = 0
vlan_tagged@wan100 = 1
vlan_id@wan100 = 132
vlan_tagged@wan101 = 1
vlan_id@wan101 = 232
vlan_tagged@wan102 = 1
vlan_id@wan102 = 332
vlan_tagged@wan000 = 0
vlan_id@wan000 = 0
vlan_tagged@wan001 = 0
vlan_id@wan001 = 0
vlan_tagged@wan002 = 0
vlan_id@wan002 = 0
vlan_tagged@wan050 = 1
vlan_id@wan050 = 7
vlan_tagged@wan051 = 1
vlan_id@wan051 = 232
vlan_tagged@wan052 = 1
vlan_id@wan052 = 332
vlan_tagged@wan300 = 0
vlan_id@wan300 = 5
vlan_tagged@wan301 = 1
vlan_id@wan301 = 3
vlan_tagged@wan302 = 1
vlan_id@wan302 = 5
vlan_tagged@wan303 = 0
vlan_id@wan303 = 5
vlan_tagged@wan200 = 0
vlan_id@wan200 = 0
I just tried to get DSL running, with success.
Try the following:
nano /etc/config/network
Add the following
config switch_vlan
option device 'switch0'
option vlan '7'
option ports '4t'
option vid '7'
Update the dsl section from
config interface 'wan'
option ifname 'dsl0'
option proto 'pppoe'
option ipv6 '1'
...
to
config interface 'wan'
option ifname 'dsl0.7'
option proto 'pppoe'
option ipv6 '1'
...
Reboot. As DSL firmware I used the vr9_dsl_fw_annex_b.bin (20MBit/s Downstream only).
There's also a firmware version which can be downloaded with vdsl_fw_install.sh it connects after a while with ~100MBit/s Downstream but reconnects after a few seconds. Maybe another FW will help.
Thanks for the help with the VLAN setup! I finally got everything working also with 100 Mbit, connection was stable for 6 minutes, intense download, tomorrow I will test it in the long run. What I did:
wget http://download.avm.de/fritzbox/fritzbox-7490/deutschland/fritz.os/FRITZ.Box_7490.113.06.93.image
7z e FRITZ.Box_7490.113.06.93.image -r filesystem.image
7z e filesystem.image filesystem_core.squashfs
unsquashfs4-avm-be filesystem_core.squashfs -e lib/modules/dsp_vr9/
And then use the vr9-B-dsl.bin in openWRT by copying it into lib/firmware/ and then enter the full path in the webGUI. Note that you will need the binary for unsquashfs4-avm-be you can get it by get the freetz source and run make tools.
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 sirq and ksoftirqd are then eating 100 % CPU, which indicates the CPU can't handle the interrupts fast enough. Thats a pity because everything else seems fine. Maybe I will try a different firmware.
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 This thread is also quite interesting... They state that the original vendors can use other hw acc. features to get the full 100 Mbit.
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.
Some things might not be required. The key is the ifname in wan .
config dsl 'dsl'
option annex 'b'
option tone 'av'
option xfer_mode 'ptm'
option line_mode 'vdsl'
option firmware '/lib/firmware/lantiq-vrx200-b.bin'
...
config interface 'wan'
option ifname 'dsl0.40'
option proto 'pppoe'
option ipv6 '1'
option username '..'
option password '..'
option mtu '1492'
config device 'wan_dev'
option name 'dsl0'
option macaddr '..'
config interface 'wan6'
option proto 'dhcpv6'
option ifname '@wan'
config interface 'wan4'
option proto 'dslite'
option peeraddr '..'
option mtu '1444'
option encaplimit 'ignore'
...
Any news regardign the sirq problem? I'am ready to test some build, or build them by myself if somebody can guide me a little.
Any news regardign the
sirqproblem? I'am ready to test some build, or build them by myself if somebody can guide me a little.
At least I added some builds with "smp" as prefix, which enables the second core.
I would also test the new version. I had the bootloop, the last two versions of https://app.box.com/s/hvqg535dnubt4r2ontpmtodpvt6ydf00/folder/36913951101 Hans Mueller. Furthermore, I can't use the WLAN and the DSL, it can also be due to a wrong DSL setting, the original firmware did a lot by itself, I still have to get used to it. @Quallenauge I cannot compile the image. Could you provide the image?
Translated with www.DeepL.com/Translator
Ich würde die neue Version auch testen. Bei mir kam es zum Bootloop, bei den letzten beiden Versionen von https://app.box.com/s/hvqg535dnubt4r2ontpmtodpvt6ydf00/folder/36913951101 Hans Mueller. Des Weiteren kann ich das WLAN und das DSL nicht in Betrieb nehmen, es kann auch an einer falschen Einstellung bei DSL liegen, die Original-Firmware hat vieles selbst gemacht, da muß ich mich noch einarbeiten. @Quallenauge Ich kann das Image nicht kompilieren. Könntest Du das Image zur Verfügung stellen?
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. I will publish a guide for that exhausting procedure in my repo very soon. 100 Mbit, WLAN etc. is working fine!
@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 thought I switched from normal to smp and vice versa in the past without such problems. Sure Asterisk won't work due missing vpe cababilities but the other things should work, since the image contains all needed components (kernel + drivers). The remaining components doesn't rely on a smp/no-smp compiled kernel.
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 -.-
root@OpenWrt:~# dmesg | grep mount
[ 3.972340] Waiting 7 sec before mounting root device...
[ 19.161224] mount_root: loading kmods from internal overlay
[ 21.034874] [<801ce084>] ubifs_mount+0x1034/0x1850
[ 21.039678] [<8012a06c>] mount_fs+0x20/0xc4
[ 21.043839] [<8014f114>] vfs_kern_mount.part.9+0x60/0x170
[ 21.049230] [<80152ab0>] do_mount+0x9dc/0xe58
[ 21.053587] [<801532d4>] SyS_mount+0xb8/0xfc
[ 21.149069] [<801ce084>] ubifs_mount+0x1034/0x1850
[ 21.153857] [<8012a06c>] mount_fs+0x20/0xc4
[ 21.158036] [<8014f114>] vfs_kern_mount.part.9+0x60/0x170
[ 21.163435] [<80152ab0>] do_mount+0x9dc/0xe58
[ 21.167779] [<801532d4>] SyS_mount+0xb8/0xfc
[ 21.480181] CPU: 1 PID: 638 Comm: mount_root Not tainted 4.14.72 #0
[ 21.571560] [<801ce084>] ubifs_mount+0x1034/0x1850
[ 21.576356] [<8012a06c>] mount_fs+0x20/0xc4
[ 21.580519] [<8014f114>] vfs_kern_mount.part.9+0x60/0x170
[ 21.585917] [<80152ab0>] do_mount+0x9dc/0xe58
[ 21.590264] [<801532d4>] SyS_mount+0xb8/0xfc
[ 21.609096] CPU: 1 PID: 638 Comm: mount_root Not tainted 4.14.72 #0
[ 21.686183] [<801ce084>] ubifs_mount+0x1034/0x1850
[ 21.690979] [<8012a06c>] mount_fs+0x20/0xc4
[ 21.695148] [<8014f114>] vfs_kern_mount.part.9+0x60/0x170
[ 21.700544] [<80152ab0>] do_mount+0x9dc/0xe58
[ 21.704896] [<801532d4>] SyS_mount+0xb8/0xfc
[ 21.728806] mount_root: failed to mount -t ubifs /dev/ubi0_1 /tmp/overlay: Bad message
[ 23.182035] [<801ce084>] ubifs_mount+0x1034/0x1850
[ 23.186839] [<8012a06c>] mount_fs+0x20/0xc4
[ 23.191002] [<8014f114>] vfs_kern_mount.part.9+0x60/0x170
[ 23.196402] [<80152ab0>] do_mount+0x9dc/0xe58
[ 23.200748] [<801532d4>] SyS_mount+0xb8/0xfc
[ 23.296232] [<801ce084>] ubifs_mount+0x1034/0x1850
[ 23.301024] [<8012a06c>] mount_fs+0x20/0xc4
[ 23.305197] [<8014f114>] vfs_kern_mount.part.9+0x60/0x170
[ 23.310593] [<80152ab0>] do_mount+0x9dc/0xe58
[ 23.314944] [<801532d4>] SyS_mount+0xb8/0xfc
[ 23.340512] mount_root: unable to set filesystem state
[ 23.344460] mount_root: switching to ubifs overlay
[ 23.349311] mount_root: switching to ubifs failed - fallback to ramoverlay
root@OpenWrt:~# mount
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
tmpfs on /tmp/root type tmpfs (rw,noatime,mode=755)
overlayfs:/tmp/root on / type overlay (rw,noatime,lowerdir=/,upperdir=/tmp/root/upper,workdir=/tmp/root/work)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000)
debugfs on /sys/kernel/debug type debugfs (rw,noatime)
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.