Belgacom’s BBox 2 is brain dead
16 November 2009 | Published in Belgium | 17 Comments
In advance of a planned migration of my home Internet access to VDSL2, I received a Belgacom BBox2 modem.
VDLS2 is actually a choice I had to make because ADSL technology is not really able to deliver in my area, due to the distance between my home and the phone exchange. On the other hand, Belgacom has been installing these fiber cabinets in every block recently in the framework of their FTTC project. Hence, a change of technology was needed for me if I wanted a faster Internet access.
The main issue with VDSL2 is the interoperability of equipment. The Broadband Forum is still working on this. As noted by the Belgian regulator IBPT in its latest consultation : “Interoperability between DSLAM and CPE is not guaranteed by an ITU standard and it may be more difficult to achieve due to the differentiation possibilities of the VDSL2 technology”.
Belgacom decided to purchase its VDSL2 equipment from Alcatel-Lucent. That equipment is using Ikanos Fusiv chips. Consequently, Belgacom delivers CPE devices based on the same chipset. There were few at the time when Belgacom chose its platform, so they went for a Sagem F@st 3464 modem, equipped with the Ikanos Fusiv Vx160 processor, which they repackaged (it’s ugly) and rebranded BBox2.
The Sagem box is not such a bad one, according to its specs. Unfortunately, Belgacom decided to design its own version of the firmware to adapt it to their commercial needs. Belgacom is agressively pursuing the triple play market. They wanted a modem that would be able to deliver two high definition TV streams at the same time it delivers Internet access.
The box uses Jungo’s OpenRG firmware , which is Linux-based. And although OpenRG offers lots of features, Belgacom managed to lobotomize it. Gone are the dynamic DNS, 802.11N, and IPv6 features, for example. While the dynamic DNS part is still there, although hidden, the IPv6 stack has been completely removed. Overall, this is the worst job of feature defacing I have seen in years.
As many new CPE devices, the BBox2 can be managed remotely by the telco using the TR-069 protocol. The good side is that it allows the telco to fix critical bugs, without user intervention. The bad side is that it also allows the telco to take complete control on your personal settings. For example, the BBox2 comes pre-configured to use the Belgacom VoIP service. While one can change the settings to use a competing offering, there is nothing that prevents Belgacom to reset the values remotely. Quite worrying from a competition point of view.
Which is why I foresee to move to a AVM Fritz!Box 7570 in the near future. I have had several AVM Fritzes in the past and was always delighted with their features and also the fact that the company is doing real innovation and development, rather than just repackaging someone else’s work. They currently have projects with Dutch ISP XS4All and Luxembourg P&T to deploy IPv6. The Fritz!Box 7570 has all you can expect. In addition to doing the basic work of connecting the home computers to the Internet, it also features a PABX with an integrated DECT base station, that will interact both with your landline but also with several VoIP providers, based on rules you set. The latest beta firmware for the box features complete IPv6 support, which, judging from this screen shot is fairly complete.
The Fritz!Box is based on the Infineon (now Lantiq) XWay Vinax chipset. It remains to be seen if it is compatible with the Ikanos chips in my provider’s infrastructure. At worst, I could use the Belgacom provided modem as a bridge to the Fritz.
20 November 2009 at 10:48 (#)
Could it be possible to flash the bbox2 with the original OpenRG’s firmware. Or has Belgacom prevented this?
I once came across a Gigaset SX763, it seemed nice although I don’t know its performance with VDSL2…
23 November 2009 at 19:24 (#)
Actually, the “original” firmware is not available. Neither Jungo nor Sagem wish to distribute it. The only way would be to ask the source code from Jungo through Belgacom and compile it yourself.
According to Siemens, the Gigaset SX763 does not work with VDSL2.
24 November 2009 at 16:54 (#)
how are you goning to connect to the BGC vdsl network iif you don’t receive you login/pass for the vdsl service since – as far as I know – the vdsl2 modems come preconfigured and the end user doens’t get these data. it seems that even the alternate providers don’t get the login/passwds
25 November 2009 at 9:33 (#)
Good question. I got my BBox2 from the Belgacom shop, but I am not yet on VDSL2. Right now, I am using it with my current ISP (not Belgacom) on ADSL. From what I read, BGC configures the box remotely once the VDSL2 connection becomes active.
I would expect Belgacom to send me the userid/password, like all ISPs do. If they don’t, I will call the support desk and insist. I will keep you updated on this.
12 December 2009 at 14:31 (#)
I have managed to compile some busybox and other stuff from the openwrt toolchain here:
http://www.zoobab.com/bbox2
12 December 2009 at 16:00 (#)
Great effort. Thank you. I will have a look at that over the next weeks.
19 January 2010 at 14:57 (#)
I just got the B-BOX myself and tried to find the “hidden” Dynamic DNS settings. No luck so far… Do you know where they can be found?
19 January 2010 at 15:16 (#)
To access the DynDNS settings:
- Connect to the modem from your browser witht eadmin password: http://192.168.1.1/index.cgi?user_name=admin&password=BGCVDSL2
- Once you see the status page, paste the following line in the browser bar and press “enter” : javascript:mimic_button(‘goto: 9035..’)
You can only use dyndns.org with the BBOX2. Other dynamic DNS service providers will not work.
5 February 2010 at 16:35 (#)
When will i receive my password and username id or whatever? is it by post?? My internet was supposed to be activated today 5th of feb 2010 but so far nothing in post..when does it usally come?
5 February 2010 at 18:34 (#)
@Andrea: I got a written confirmation, along with login details, two weeks before the agreed date for activation.
If you have received no confirmation up to now, call them (0800-33800). Belgacom in notoriously deficient on written communication, be it e-mail or letters.
6 February 2010 at 20:51 (#)
Dear Patrick,
Yesterday, I managed to install my bbox2. I tried to access the dyndns settings the way you described it but it didn’t work. I didn’t notice any changes when replacing the line http://192.168.1.1/index.cgi?user_name=admin&password=BGCVDSL2 by the line javascript:mimic_button(‘goto: 9035..’). All I get is the status page and it stays like that. Any other suggestions ? By the way … I have the impression Belgacom is trying to keep their customers as stupid as possible …
Thanks for your help.
Willem
6 February 2010 at 21:28 (#)
It should work. Be sure to first connect to the box as an admin with the line http://192.168.1.1/index.cgi?user_name=admin&password=BGCVDSL2
Once you get the status page, paste: javascript:mimic_button(‘goto: 9035..’) and press enter.
If it doesn’t, try javascript:mimic_button(‘goto: 730..’). You should get a nice menu full of icons. The DynDNS icon is at the bottom left.
Make sure javascript is enabled in your browser, of course.
8 February 2010 at 14:00 (#)
Hello,
I try to instal DYNDNS on my BBOX2.
The link to enter de BBox2 in admin mode ist OK but when i past the javascript nothing happen
Have you any idea what the problem can be?
Thanks
8 February 2010 at 14:07 (#)
See previous answers.
Once you get the status page, paste: javascript:mimic_button(‘goto: 9035..’) and press enter.
If it doesn’t, try javascript:mimic_button(‘goto: 730..’). You should get a nice menu full of icons. The DynDNS icon is at the bottom left.
Make sure javascript is enabled in your browser, of course.
22 February 2010 at 15:14 (#)
I use my BBox2 in bridge mode since 3 months with a basic WRT320N router that provides me everything I need (Wifi N, Gigabit Lan, DynDNS, …). The other problem I had was the BBox firewall who blocked my server packets, reason why I decided to configure it in bridge mode.
Recently, I’ve been disconnected from the WAN about 30 times a day. I was worried my router or my bbox was going to die.
I reseted the Bbox2 from scratch, waited she was connected and then reconfigured in bridge mode.
Now it is working but I will monitore for next days. Do you think Belgacom would block my box because bridge mode and because they cannot update the firmware ? (this is the only reason I see).
22 February 2010 at 15:25 (#)
I see no reason why Belgacom would block boxes configured in bridge mode. At worst, they could reset it to standard values. But I do not think they would anyway.
As far as I understand, firmware updates through the TR-069 protocol are performed by Belgacom over at private LAN in the 1.x.x.x range.
This private LAN remains active even if your set your box in bridge mode. You do not have any control on what is happening there.
22 February 2010 at 16:54 (#)
The only thing I see is they will unlock some features for next month and whenever Belgacom changes something on their side, we (poor customers) are faced with some troubles.
In this way, I was wondering if there was an error with my box configured as a bridge but you tell me not…
I can’t explain why suddenly my connection has become totally unstable. I Hope it will continue to work, otherwise I’ll change my Linksys (and the Bbox if does not solve the problem) but I’d rather to avoid in this way.
If you think to something that could help me