Here i share my build. I am unhappy, the -initramfs-kernel.bin is bigger than 5MB and do not work for the same reason.
How it is possible to make tham smaler on the same build without much changing, specially for the the other devices.
I build it in 4 steps download, build-from-source, SDK-build, and build a imamage-via-imagebuilder.
See post 203
Downloaded packages and preparation for build: Ca 3,4GB split into 200MB parts
for add than together use this command:
As i say below the ramdisk will not work on this build. Use the old fullimage.img with kernel 4.19
Here the VPE image with Telefon support and the old working fullimage.img: eb904x-images-2020.10.03
fullimage.img
sha256: e56920cb5df61c2fd82ab887c32aaee4e4ded52e8985c6031c8a9c48b5ea9c26
openwrt-lantiq-xrx200-arcadyan_vgv952cjw33-e-ir-vpe-squashfs-sysupgrade.bin
sha256: 5f64e5190bdad861d5b44879d91b550fcdbfa81a1e2c734fdc24f6f57f452ce5
#############
Now i have to start to share my build in a separated thread the last is from 18.10.2020
Question to this build please in the additional thread.
The diagramm shows the entry on the Gray DSL connector: and when i right see is it:
WAN -> Ethernet on port4
or:
xDSL Modem
and:
??? TEA1 (N/U) on FXS1
or:
? ISDN input over "4B3T ISDN NT"
or:
? FXO POTS over Si3050 and Si3011
When i right understands work the Easybox 904xDSL on Ethernet WAN, Full-IP DSL line and various combination of DSL-lines with POTS or ISDN. (The splitter are inside the Box and i guess that is the reason why the EB904x have litle worse DSL signal like my Provider Fritzbox 7360)
In this diagram it looks like that FXS-1 have direkt access to the Provider-Landline. But no idea if general or under which circumstances (no power ?).
I fear that this diagramm does not show the S0-Bus.
Is it possible to use one of the LAN-ports as WAN with the 904xdsl?
I tried to set it up via a VLAN but I got puzzled because of the two switches.
My assumption was to create a second VLAN and assign one of the LAN-ports as untagged, but never got it to work as expected.
The webinterface never offered eth1.x and eth0.2 was already there before, but binding it to WAN (instead DSL) did not work.
Or might it be necessary to configure this via ssh instead of luci (similar to wifi)?
If you want to use the gray (DSL) port as ethernet WAN port than you can add the followig code
(but of course it is an example you can change the MAC etc.)
If you want to separate an single Yellow port for example as WAN Port use the following code
Port 3 means the port next the USB and power connector.
(it use vlan 7 and eth0.7 for example but the next free is normally 6)
Hi,
I just got an EasyBox 904 xDSL a few weeks ago. I'm planning to use it either as a gateway or as a dumb modem (via pppoe passthrough), with telephony (VPE) enabled.
I used Quallenauges fullimage.img from 2018 to flash an image I built from Plonk34s openwrt xrx200-1 github branch. I did a clean build (scripts/update and install, make menuconfig, make download, make -j5).
I flashed the image successfully (forceupgrade, version checks out).
I'm now trying to get VDSL to work. My ISP is Vodafone Germany (used to be Arcor), but I'm sure it's a Telekom line (there's a Telekom logo on the TAE). Speed should be 50/10Mbit.
The EasyBox 804 states the 'DSL Mode' is G.993.5. It also has always falsely claimed the speed to be 110/37Mbit, but that's probably the unthrottled speed.
I'm aware that specific points have been raised in this thread before (and elsewhere).
Still, here are some things I am not sure about:
VLAN ID: Should be 7 for Telekom. Do I configure the physical DSL port (switch0 port 4) as untagged VLAN 7? Or do I just use 'dsl0.7' in the wan section?
PTM: for VDSL, xfer_mode in dsl section should be 'ptm'. Do I have to create a ptm device section? Do I keep the atm-bridge section? Do I use dsl or ptm for wan interface?
My /etc/config/network:
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fdba:2027:3db5::/48'
# Is this section needed when using ptm?
config atm-bridge 'atm'
option vpi '1'
option vci '32'
option encaps 'llc'
option payload 'bridged'
option nameprefix 'dsl'
#Or do I need a section like this one:
#config device 'ptm_dev'
# option ifname 'dsl0'
# option name 'dsl0.7'
# option type '8021q'
# option mtu '1500'
# option vid '7'
config dsl 'dsl'
# or annex b?.
option annex 'j'
# option firmware '/lib/firmware/lantiq-vrx200-b.bin'
# ^ no vectoring; fritzbox firmware:
option firmware '/lib/firmware/fb/vr9-B-dsl.bin'
option line_mode 'vdsl'
option xfer_mode 'ptm'
config interface 'lan'
option type 'bridge'
option proto 'static'
option ipaddr '192.168.2.8'
option dns '1.1.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
list ifname 'eth0.1'
list ifname 'eth0.66'
config device 'lan_eth0_1_dev'
option name 'eth0.1'
option macaddr '9c:80:df:91:5a:60'
config interface 'wan'
option ifname 'dsl0.7'
option proto 'pppoe'
option username 'vodafone-vdsl.komplett/vk0123456789'
option password 'secret'
option ipv6 '0'
config device 'wan_dsl0_dev'
option name 'dsl0'
option macaddr '9c:80:df:91:5a:61'
config interface 'wan6'
option ifname '@wan'
option proto 'dhcpv6'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 6t'
# DSL/WAN port, was set to VLAN 2
config switch_vlan
option device 'switch0'
option vlan '7'
option vid '7'
option ports '4 6t'
config switch
option name 'switch1'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch1'
option vlan '1'
option ports '0 1 2 3 6t'
config device 'inic_dev'
option name 'eth0.3'
config interface 'inic'
option proto 'none'
option ifname 'eth0.3'
config switch_vlan
option device 'switch0'
option vlan '3'
option vid '3'
option fid '3'
option ports '5 6t'
config device 'wlan_dev'
option name 'eth0.66'
config device 'guest_wlan_dev'
option name 'eth0.71'
config switch_vlan
option device 'switch0'
option vlan '4'
option vid '66'
option fid '4'
option ports '5t 6t'
config switch_vlan
option device 'switch0'
option vlan '5'
option vid '71'
option fid '5'
option ports '5t 6t'
With the non-vectoring firmware, I got a DSL link once.
The pppoe-wan interface even got an address, but I could only ping the pppoe-peer.
After a reboot I didn't even have a dsl interface anymore.
I apologize for my post being a bit of a mess, but I don't get many maintenance (breaking the internet) windows and I'm mostly one-handed at the moment.
Anyway, I will try to get more detailed information on my next 'maintenance window'.
It is right you have VDSL2 with Vectoring and enought SNR (because your ATTNDR is higher them you use) ?
The switch should not involved but i never try differnt configs like the default.
option annex 'j' is totally wrong on VDSL2
Try:
# the following part should not be relevant but it works by me
config atm-bridge 'atm'
option vpi '1'
option vci '32'
option encaps 'llc'
option payload 'bridged'
option nameprefix 'dsl'
config dsl 'dsl'
# option annex 'b'
option tone 'av'
option xfer_mode 'ptm'
option line_mode 'vdsl'
# option firmware '/lib/firmware/extra-dsl-fw/fb7490-7.21/vr9-B-dsl.bin'
option firmware '/lib/firmware/extra-dsl-fw/eb904x-4.13/dsl_vr9_firmware_xdsl-05.07.03.03.00.07_05.07.04.03.01.02.bin'
config device 'dsl_dev'
option name 'dsl0'
# option macaddr 'c8:0e:46:ed:83:07'
config interface 'wan'
option ifname 'dsl0.7'
option proto 'pppoe'
option username 'USERNAME'
option password 'PASSWORD'
option ipv6 '1'
option defaultroute '1'
config interface 'wan6'
option ifname '@wan'
option proto 'dhcpv6'
option iface_dslite '0'
option reqaddress 'try'
option reqprefix 'auto'
Note on VDSL it does not make sense to use "option annex" and "option firmware" because the right annex will be choice by the FW the dsl_control script make only a choice between annex-A or annex-B Firmware.
Try different DSL-FW if it not works.
On me (i have a regional ISP without Vektoring) i have the strange "problem" (but it works well) that i must set "option tone 'av'" then it works well but it show my that i am cannected via Annex-A.
If i do not my DSL-line are extrem unstable. This is totally strange and i never found the reason.
Please print alway the result with:
/etc/init.d/dsl_control dslstat
If you have an sync please post the result of
ifconfig
too
Normally the telekom line have an fallback to VDSL2 without vectoring, with maxspeed 20Mbit/s.
It is a good strategie to use the default FW ("option annex 'b'" without "option firmware", be shure that the default FW are installed), because they is more stable, after that works try different FWs.
Hi Plonk34,
I really appreciate your reply.
This morning I got a maintenance window again. I used the xDSL firmware I mentioned ( 5.9.0.C.1.7-5.9.0.A.0.2). I got VDSL running with the following dsl section:
Because it seemed illogical to me that I could only ping the peer on the ppoe-wan interface while also having an address not in the usual range, I checked my documents again and it turned out I used wrong (outdated) DSL credentials
After I put in the right ones, it worked!
This is my dslstat:
ATU-C Vendor ID: Broadcom 192.26
ATU-C System Vendor ID: Broadcom
Chipset: Lantiq-VRX200
Firmware Version: 5.9.0.12.1.7
API Version: 4.17.18.6
XTSE Capabilities: 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex: B
Line Mode: G.993.5 (VDSL2 with down- and upstream vectoring)
Profile: 17a
Line State: UP [0x801: showtime_tc_sync]
Forward Error Correction Seconds (FECS): Near: 0 / Far: 163548
Errored seconds (ES): Near: 0 / Far: 183
Severely Errored Seconds (SES): Near: 0 / Far: 3
Loss of Signal Seconds (LOSS): Near: 0 / Far: 0
Unavailable Seconds (UAS): Near: 147 / Far: 147
Header Error Code Errors (HEC): Near: 0 / Far: 0
Non Pre-emtive CRC errors (CRC_P): Near: 0 / Far: 0
Pre-emtive CRC errors (CRCP_P): Near: 0 / Far: 0
Power Management Mode: L0 - Synchronized
Latency [Interleave Delay]: 0.15 ms [Fast] 0.0 ms [Fast]
Data Rate: Down: 109.981 Mb/s / Up: 36.996 Mb/s
Line Attenuation (LATN): Down: 7.6 dB / Up: 5.5 dB
Signal Attenuation (SATN): Down: 7.6 dB / Up: 5.6 dB
Noise Margin (SNR): Down: 14.3 dB / Up: 9.2 dB
Aggregate Transmit Power (ACTATP): Down: -3.6 dB / Up: 14.4 dB
Max. Attainable Data Rate (ATTNDR): Down: 108.840 Mb/s / Up: 40.574 Mb/s
Line Uptime Seconds: 2907
Line Uptime: 48m 27s
Speed test checked out (50/14 Mbit).
It is a good strategie to use the default FW ("option annex 'b'" without "option firmware", be shure that the default FW are installed), because they is more stable, after that works try different FWs.
Do you mean the firmware installed by dsl-vrx200-firmware-xdsl-b? That one isn't vectoring capable, right? Or can the xdsl firmware be extracted from the vendor firmware?
Anyway, I just got everything up and running. Time and tests will tell how stable everything is.
You can also refer to my experiments with different vectoring-enabled firmwares from August this year (see above).
Your line is in fact a DTAG line leased by Vodafone (they do not lease the naked copper line, but they rather purchase IP-based connectivity). The DSLAM is configured to limit your DSL connections to 110000/37000 kbps (apparently that's the profile used for such configurations). The IP data stream should be limited to your subscription's parameters, which I guess are 50 Mbps downstream and 10 Mbps upstream (those browser-based speed tests are not necessarily too accurate).
Thanks to this data rate capping the Easybox 904 is fast enough to sustain the throughput (would be a different picture if you had a 100 Mbps subscription).
I finally got my hands on an Easybox 904LTE. Are there any OpenWRT images available for inastallation via tftp? Am I correct that the LTE modem is not supported by OpenWRT at this point?
My box has the AT904L-03.18 firmware installed, so no telnet support
Despite the title, this thread is more about the xDSL variant and not the LTE device. While the xDSL variant is mostly supported out-of-tree (as there are considerable difficulties to support it in a way that doesn't break other lantiq devices), there hasn't been a lot of development for the LTE variant so far.
Hey,
I got a 940 for free and tried to install openWRT. unfortunatly I failed getting the Boox to download the iso over tftp server. I tried both my Windows and my ubuntu Laptops. has anyone a clue?
Is ther a better way?
Gratings from Erlangen
Axel
Ps.: ( I'd like to try to ad an usb lte Card and later maybe use it for freifunk...)
If there hope for getting the wifi working beyond ap? I just want it to turn it into a wifi repeater. If this is already possible what am i not seeing? If this is a stupid comment then i apologize in advance.
