How to unlock the ECI B-FOCuS VDSL2 CPE modem:
Connect a serial cable to the PCB of the ECI and power up the device:
The bootloader should start:
ROM VER: 1.0.5
CFG 01 ...
DDR size from 0xa0000000 - 0xa1ffffff
DDR check ok... start booting...
U-Boot 1.0.4 (Feb 16 2011 - 13:53:56)
CLOCK CPU 333M RAM 166M
DRAM: 32 MB ..
FLASH MANUFACT: c2
FLASH DEVICEID: cb ..
The Linux kernel will auto boot:
Starting kernel ...
Infineon xDSL CPE VR9. ..
Linux version 2.6.20.19 (hyhuang@BSD7.localdomain)
(gcc version 3.4.6 (OpenWrt-2.0)) #1 Tue Aug 9 11:27:46 CST 2011 ..
Arriving finally at a login prompt.
Login with username admin and password admin:
login: admin
Password: admin
BusyBox v1.00 (2011.08.09-03:28+0000) Built-in shell (msh) ..
Alpha #
At the Alpha # prompt, enter the six commands below to 'unlock' the device:
Alpha # xmldbc -s /switch/lan_access_cpe_enable 1
Alpha # xmldbc -s /switch/port:2/activate 1
Alpha # xmldbc -D /var/tmp/rgdb.xml
Alpha # gzip /var/tmp/rgdb.xml
Alpha # rgcfg save -n /dev/mtdblock/3 -c /var/tmp/rgdb.xml.gz
Alpha # ifconfig br0 192.168.1.55 # adjust this IP address to suit your own subnet #
The unlocked ECI VDSL modem should now be accessible via telnet and web GUI at http://192.168.1.55.
N.B. the ECI web interface is too buggy for Firefox. Though Internet Exploder, Chromium, and Safari should all work okay.
Username and password for telnet and web login are, as above: admin and admin
Finally, the IP address of the ECI should be permanently changed through the web interface to suit local subnet. (The ECI's default IP is 192.168.168.168, as shown below)
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fwww5.picturepush.com%2Fphoto%2Fa%2F10070948%2Fimg%2FECI-B-FOCuS-VDSL2-modem---solderless-UART-connection%2Feci-lanconfig.png&hash=953cca81218237804881c9f4a3c31374b581d5d9) (http://picturepush.com/public/10070948)
cheers, a
EDIT: background info on what those commands are actually doing is at http://hackingecibfocusv2fubirevb.wordpress.com/
Thank you very much asbokid, The modem has been unlocked.
You're welcome. Glad to hear it worked out, winkingw :) One more modem liberated!
N.B. the ECI web interface is too buggy for Firefox.
Hi burakkucat,
EDIT:
It turns out that the Corrupted Content Error reported by Firefox is due to the embedded web server in the ECI. The server is Acme Labs' BSD-licensed thttpd. It is sending a corrupted HTTP header to the browser.
From Firefox in Linux:
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fwww1.picturepush.com%2Fphoto%2Fa%2F10069514%2F480%2FECI-B-FOCuS-VDSL2-modem---solderless-UART-connection%2Ffirefox-iceweasel-eci.png&hash=0adc139cfc55897e30099c1d0d52ace116d82498) (http://picturepush.com/public/10069529)
Uklad found exactly the same problem with the Firefox build for BillyGatesWare, so it isn't a Linux 'thing'. Only Firefox (and derivatives) are pedantic about the error. Three other browsers (Chromium, Epiphany and Konqueror) all work fine regardless:
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fwww3.picturepush.com%2Fphoto%2Fa%2F10069526%2F480%2FECI-B-FOCuS-VDSL2-modem---solderless-UART-connection%2Fbrowser-eci.png&hash=e2a89b770a4c1013532d24af13abde032cb4e67c)
(Click for full size) (http://www3.picturepush.com/photo/a/10069526/img/ECI-B-FOCuS-VDSL2-modem---solderless-UART-connection/browser-eci.png)
By packet-sniffing with Wireshark, the problem is clear. The HTTP header (Content-Length: -1) sent by the embedded web server has an invalid field value (-1). :(
Any Content-Length greater than or equal to zero is a valid value.
Sadly, with no source code for the ECI web server, a solution (hack) would have to be found in Firefox.
It's probably easier just to use another browser!
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fwww3.picturepush.com%2Fphoto%2Fa%2F10075556%2F480%2FECI-B-FOCuS-VDSL2-modem---solderless-UART-connection%2Fwireshark-problem.png&hash=054b4a397f3349e4a24b9d5ea9b43d68f0b1e594)
Wireshark Packet Sniffer
(click to enlarge)
(http://www3.picturepush.com/photo/a/10075556/img/ECI-B-FOCuS-VDSL2-modem---solderless-UART-connection/wireshark-problem.png)
cheers, a
[1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.13