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.
Pages:
@Patrick
Let’s hope that the Sagem will update to the new firmware when I get my VDSL connection working (still on ADSL now). Is there a way to do it yourself? I did find in /home/httpd/html the upgradefirm.html, which works if you got to http://192.168.1.1/upgradefirm.html, but you need the firmware file.
@Seb This was also the case with earlier BBox2 firmware versions. The last two firmware versions do not exhibit that behaviour anymore.
The only workaround I found was to have all devices connected through the same Ethernet switch and use an independent WIFI access point connected to the switch.
AAH my EDPnet Sagem is driving me nuts. I just discovered that the Bonjour protocol (I have a lot of Apple stuff) isn’t working because the Sagem is dropping multicast on the local LAN (wtf?). They totally hid the web interface for this, but if you connect with telnet and type:
fw_dump -c 20 (dump firewall chain 20)
You get (selection)
…
(AND // Broadcast/Multicast protection
(OR
IP_SRC_MASK(224.0.0.0:f0.00.00.00)
IP_SRC_BCAST
)
(DO
VAR_ADD(0, 1)=0 // Broadcast/Multicast protection
DROP
EXIT
)
…
Does anyone know how to change this from the command line? I don’t think you can do it with rg_conf_set fw/protect etc. It looks very much like an ipchains config, but I can’t find any of the ipchains related config riles or command in /bin.
Hey,
great site and posts!
I just got the SAGEM from EDPnet, and was surprised to see the Belgacom logo everywhere … anyway … just wanted to say it’s the same firmware (Runtime Code: 6001G0-6000G0), and the telnet admin password is: BGCVDSL2
Just in case someone was wondering.
Pfff… I’m really spamming this thread. Anyway, I got the DynDNS working on my EDPnet provided Sagem by adding rg_conf_set ddns/device ppp0 (WAN interface). Took me a while to figure it out. Oh and after chaning this, it helps to disconnect/connect your WAN connection so it updates DynDNS.
Btw, it only works with DynDNS. I tried DtDNS as a provider, but that doesn’t work. And you can’t use dyndns.com, only dyndns.org. I think this is by default set this way, but you can change it with rg_conf_set ddns/provider dyndns.org.
@Bert
Did you get the Dynamic DNS settings working? I’ve put all the settings in, saved, rebooted etc. but the status never updates beyond:
(ddns
(status(1))
(provider(dyndns.org))
(response())
(last_update(0))
(username(littlebighuman))
(password(xxxxxxxxxxxxxxx))
(hostname(somehostname.dyndns.org))
)
Hi,
I’ve got the VDSL2 from EDPNET last week, also Voip to get rid of the Belgacom subscription. It all works fine, no problems at all. In the Sagem there is a “sip call history”.
How can I get this call-log into some file on my PC so I can use in a spreadsheet, hope someone knows.
(BTW the Sagem also gets very hot, I’ve increased the length of its legs by 1cm and it cools a lot better.)
Patrick,
(can’t edit my own post, so I add a new one)
I figured out how to get past the “Only one WAN connection can be enslaved by each bridge” message. You just have to deselect all the WAN interfaces that are set to bridge with the LAN interface/bridge. They don’t make any sense anyway, because you don’t use these WAN’s as far as I can tell.
If put some instructions on my own blog (click on my name above). I’m now going to set some static IP-addresses per your tricks page
Hi Patrick,
Just got the EDPnet VDSL modem and it looks like it’s very similair if not exactly the same as the one that Belgacom ships. The default password was BGCVDSL2. Not sure about ADSL2 as I’m connected via ADSL one now (6 mbit).
I took a screenshot and saved it here: http://imgur.com/b9aAW.png
Now I’m looking for a way to change the LAN subnet from 192.168.1.1 to something else, so that I don’t have to reconfigure all the static IP’s in my current network. For some reason I go to Network Interfaces > LAN Bridge > Settings and try to change the LAN IP-address I get “Only one WAN connection can be enslaved by each bridge” when I try to save. Actually, even when I don’t change anything or change something else I get this same message.
Good article, good comments. I’m going to keep this bookmarked. I just reluctantly ordered EDPnet VDSL, because I get the Sagem modem for free if I order before 1 July. Reluctantly, because I’m not happy with the broadband situation in Belgium (I’ve been living in Belgium for 4 years now, before that I lived in the Netherlands) and try to avoid anything that has to do with Belgacom or Telenet. But let’s make it into an anti-monopolist-rant
Do you know if the EPDnet modem will have Belgacoms firmware on it?
@Seb From what I heard, the Sagem firmware is slightly different from the BBOX2 one. The BBOX2 does ADSL2, while the Sagem does not. The default admin password is different, too. There may be others, too.
Hi Patrick,
(I don’t want to hijack your page about bbox, so feel free to not publish or edit this post)
I could not resist
I got my Fritz 7570 2 days ago. I’m beginning to play with it.
I’m still in ADSL; I should be in VDSL by the end of this month.
I had to upgrade to the latest firmware (75.04.82) in order to get a connection. The syncing was ok but it was not possible to specify the Encapsulation method with the old firmware.
If you want, I’ll keep you updated after switching to VDSL. I might have to come back here (or ad-bc, I think you’re there too) to set up bridging in the bbox
Loved your article.
thanks,
d.
Hi,
just received the Sagem modem from EDPnet for my VDSL2 subscription and trying to install my dyndns account.
In the Telnet session (Puttytel) however I get the following:
[admin @ home]$ rg_conf_set ddns/XXXXXX
Wrong number of arguments
rg_conf_set Set OpenRG configuration path to value
Usage:
rg_conf_set
Returned 1
Any thoughts?
Thanks
@Bert: See my other page on the BBOX2 DynDNS settings
Hi Patrick,
Did you get your AVM Fritz!Box 7570 ?
The international version (I’m not sure what it means ?) seems to be available around 250€ (inc. VAT).
I’m ready to pay that price to leave Belgacom out of my network.
But for now, I’m still in ADSL (not even ADSL2, tested with SMC and USR modems) although I’ve got the Intense stuff. I think I’ll get BGTV, try the bbox and the VDSL2 if I’m eligible (the BGTV site tells me “OK, 2 HD TVs”, but I doubt).
Then I’ll decide which *serious* modem to buy.
(I don’t care about the TV anyway).
Any advice ?
Thx.
@PiR I briefly tested a Fritz!Box 7570 modem on my VDSL2 line. The VDSL synching just did not happen, which was more or less expected. Unfortunately, I could not make additional tests. I am now waiting for an Annex A version of the Fritz!Box 7390, which uses Ikanos Fusiv chips. The rumor is that it could be there this summer.
@Koen: Yes and No.
As long as the PPoE session is not established, you will not get an IP address.
The BBox2 does use TR-069 to autoconfigure itself, when used on its own, This includes the PPoE parameters. This is friendly to non-technie customers.
But in your case, you would have to configure the session yourself.
Someone told me it is possible to get an IP on the router behind without using the credentials on that router.
Is this true?
Hey, can someone please tell me how to put the bbox2 in bridge mode? So the cisco behind it gets the external ip.
Thanks
Google is your friend. See here:
http://userbase.be/forum/viewtopic.php?f=43&t=22588#p286050 In Dutch.
http://belgacomtv.hesamedia.be/BBox2_bridge.htm In French.
For the Router behind to get an IP, you then need to configure the PPoE session with your credentials.
Thank you Patrick. I am using JDownloader to manage downloads from many differnt hosts (e.g. Hotfile, Megaupload, etc.). With the correct script the program can get a new external IP in automatic by re-conecting the modem. In any case your idea of scheduling the address change seams good. I went to the web interface and pasted the java script in the browser bar but nothing happened.
Hi Patrick,
I have a BBox and I am trying to find the script to force a reconection and, therefore, a change of the external IP. Can you help me?
Thxs!
If all you want to do is get a new IP address every 24 hours or so, please check my post here/a>.
However, if you want to change your IP address on the spot, the best way would be to use the web interface. On the main page, disconnect VLAN10 and reconnect it. Be aware though that the whole process takes about 2 or 3 minutes to complete. Which is why I schedule my address change at 4am.
I agree.
It looks like that every BBOX is running verry hot. Mine is lying beside of a radiator and with mesuring the max temp I receved was 32° Celsius, with isn’t verry hot to me. My ADSL modem was at least above 40° (DLink DSL-320B). My CPU is also at 100% all the time. Don’t know why mine isn’t going that hot?
Also I’ve tested SSH using port 22 instead of 2200 and noticed when I waited for 10 minutes, my tests actualy worked. To my saying the BBOX is slow on comprehension.
Indeed. The box gets real hot. This seems to be due to some process taking 98% of the CPU all the time. See my blog post.The main issue is that the box cannot use this CPU power for anything else. The other issue is that a system running at 100% resources all the time wears out much faster.
The BBOX2 was really designed for the Belgacom TV service. The fact it works for Internet access seems to be an afterthought , more than a design constraint. We really need an alternative.
I’ve tested it again and it works now. Didn’t change a thing after configuring port 2200. Looks like I just had to wait a litle bit.
Next step is WakeOnLan (or Wan actualy).
Thanks for helping me out. You’re THE BBOX2 specialist.
Hi again.
Still no luck. I pushed it a step further now and installed a packet tracer (wireshark). No SSH packets went from the BBOX2 to my home PC. The packet tracer worked because it captured my internal SSH packets. Looks to me that the Belgacom firmware is just made to get internet access and television. Tomorrow I’m going to try if I get the BBOX in to bridge mode and let my router handle the ‘tricky’ parts. I’m also going to try RDP (Remote Desktop). See if that works.
Thanks for the quick reply Patrick. Until the next problem(s).
It should work. Make sure you connect from outside your network using your BBox’s public IP address and mention the port you wish to connect to (e.g. 2200).
Do not try to use your external IP address from the local LAN. Somehow, the Box filters that out. You really needto connect from the public Internet.
Hi Patrick.
I’ve read that you can connect to you Unix box at home from the web.
I added a TCP and UDP line to forward port 22 (SSH) to my PC. I used the following in LAN Servers:
Public start port: 22
Public end port: 22
LAN start port: 22
Local IP: 192.168.1.2 (home PC)
When I want to connect with SSH I get: Connection refused on port 22.
Is there something I forgot? I have set my firewall to minimal to rule out this problem.
Thanks in advance.
Hi Dries,
I would suggest using another public port than 22. You could use 2200 for example, and indicate that in your ssh client. With Putty, this is easily done.
I suspect that the BBOX2 treats ports like 22, 23 and 80 in a special way. You example would thus become:
Public start port: 2200
Public end port: 2200
LAN start port: 22
Local IP: 192.168.1.2 (home PC)
hey there,
I have now a vdsl2 connection ran form EDPNEt. It is off course just the same as the belgacom one but they ship the sagem router. Well, you are working your nerve on the bbox2, i cna tell you that the sagem standard version is … worst: same all ultra basic features which i can live with as i just want it to bridge PPPOE from vdsl to ethernet, but .. the re is a crucial design flow on this router: heat ! air flow design was probably made by a non interested brain dead engineer working on a napkin, and, at the end … overheat, hang, etc…
Am looking for a cheap bbox2, no choice
J.
BBox-2 modems tend to become quite hot, too. One possible reason is that fact that the CPU is used at 100% most of the time. See my other post on the subject. I would tend to think this is also the case of the Sagem boxes.
The permanent (ab)use of limited system resources by the software does not help in keeping the modem cool and a cause of instability.
Hello Patrick,
wondering if you can help me too with a VOIP issue.
I just swapped to vdsl2 and b-box2 with belgacom; before that I was using normal phone plugged in a linksys spa3012 (fixed ip )to connect to eutelia voip provider, though a cisco 800 adsl router lan port.
I have been playing with the config of the b-box since yesterday, and now I am finally able to start calls from my phone, but still cannot receive any.
The spa is connected to pc port 2 and has fixed ip 192.168.1.200 (tried .10, .100 too)
so far I have tried the following:
-disabling b-box2 telephony and changing sip ports to 4080
-disabling vlan 20 (voip)
-put the spa fixed ip in dmz
-set port triggering rules
-set lan servers to open the ports to my spa fixed ip (UDP 5060, range for UDP for rtp, UDP 8000 for rtpc and also 3745 for eutelia stun server)
-set the static ip on the lan bridge for my spa (weird it always reports as expired, as the lease is marked to end on 1970/01/01 00:00:00)
all these alone or combined…still, I cannot receive any call.
Do you have any suggestion before I quit the task and move to set the B-box in bridge mode in front of my old cisco router?
Thank you in advance,
Stefano
DDNS is ok now.
The telnet command help configuring it but you miss a command that activate it
Problem is that it looks like all ports are closed now.
At least all UDP.
TCP seem to be able to go out but not to come back in .
I checked with BGC but they say they are open.
Problem is that, before the firmware update it was working and now not anymore.
… something fishy
Thanks
So this means that
DMZ and port triggering are not necessary ?
When would you youse them then ?
Gianmarco
Gianmarco,
The undocumented javascript commands have apparently been removed with the latest firmware update.
Have a look at my BBOX2 tricks page to see how to do that through a telnet session on the modem. (bottom of the post).
Regarding the remote access to your network camera: I use a similar setup to access a local Unix box at home. Indeed, you should have a forwarding rule in LAN Servers to redirect an incoming port to the IP address and port of the local device behind the modem.
The “authorized Access yes/no” only deals with allowing remote access to the management of the Box.
And do not forget that Belgacom now blocks by default the access to port 80 of the modem from the Internet. This can be changed in the eServices through the Belgacom web site.
Patrick,
I just checked, and the FW does not seem to have changed so possibly simply some sort of limitation been added by belgacom?
other question
I am trying to access my camera from the web using DDNS but apparently using DDN and setting the port forwarding is not sufficient.
Should I set something in the firewall ?
I see a DMZ host and port triggering is it there where I should cange someting?
or I should play with the “authorized Access yes/no” in the lan servers config ?
Obviusly this if I am able to access the DDNS menu again
Dear Patrck
Fantastic expalanations thanks
For a while I had the feeling I could fully master the BBOX following your advises
Unfortunately I believe there has been some sort of firmware update as the BBOX does not allow me to acces the DDNS using
javascript:mimic_button(‘goto: 730..’) nor
javascript:mimic_button(‘goto: 9035..’) anylonger
Any advise ?
P.S.
On a previous comment someone was not able to use this command but this was due to the wrong apostrofe, it was actually
javascript:mimic_button(‘goto: 730..’)
I like your BBox2 trick page, will keep checking back. Anybody any idea what the USB port on the side of the BBox2 is for? Just wondering.
Thanks
Heiko
Heiko,
This post explain how to use the USB port to mount a USB memory stick (page in French), although it seems that the newest firmware revision has disabled this feature. I have not tried it, though.
Hi Patrik,
thanks for all this helpfull information. I just got my b-box2 today and I will let you all know how this will end up.
I prefer to run this in bridge mode and use my fritz 7270 with all features and different sip accounts f.e. at Sipgate and other.
let’s see how this will work out.
/Detlev
I have been looking at the Belgacom Sagem 3464 today.
I discovered you can telnet it at 192.168.1.1, and then
login with ‘admin’ and ‘OLOVDSL2′.
Now, there are commands to handle the registry. There is
a whole lot in the registry.
I see lots of things described in the registry, and would like to try some things, like:
- Enable the 4 Ethernet ports for my LAN
- Route outgoing VOIP calls over a low-cost provider, eg 12voip.
Could any of you help me ?
Henri,
- How to enable the 4 Ethernet ports for the LAN:
In the web interface, go to “Advanced Settings”, “Route” and select the “Routing” tab. In the “Port TV selection”, uncheck the ones dedicated to TV. They are now active as normal LAN ports.
- Route outgoing VOIP calls over another provider
In the web interface, go to “Advanced Settings”, “Telephone” and point to the VoIP provider server, instead of the default ones. Make sure “Gateway Configuration” interface is ppp0, rather the Eth 1.20.
This is from memory and reasoning. I do not use the VoIP features. I have a BBoX2 with Belgacom firmware. The one delivered with the Sagem for Scarlet customers may be a bit different. YMMV. If necessary, call the Scarlet help desk.
Interesting article…
In fact, I’ve been running my VDSL2 connection since december on a Zyxel P870HW-51a-v2 for testing purposes both in Router as in Bridge mode.
Main reason for this is as a reseller of Zyxel products we prefer to stay with a user interface already known to us, and for using dyndns I don’t want to rely on an unsupported hack.
However featurewise the bbox2 seems like quite a complete product, it really stuns me why they would deactivate some useful options, and as you said, it really lacks documentation.
Today however I have been unable in supporting my colleague into getting a bbox2 to run in bridge mode, using a procedure we’ve been already following successfully in the past.
I’m wondering if you are still running your vdsl-line on your bbox2 or have you moved to the Fritz, and I just read in one of these comments about planned future changes in bbox2 firmware. Could you be more specific on this?
I have not moved to a Fritz!Box yet because the current model (7390) is hard to get at. AVM seems to deliver to the German ISPs in priority.
With regard to the BBox2 not being able to work it bridge mode, it seems the latest firmware revision solves the issue. It appears as: “Runtime Code Version 60I11U-60I01U” in the GUI, compiled on 26/1/2010. Firmware upgrades are generally performed when resetting the box, through the little switch on the back, between the connectors.
To set fixed IP addresses through DHCP based on the MAC address:
Go to “Advanced Settings”. In the “Network Interfaces” menu, double-click on the “Lan Bridge”. On the next screen, double-click on “IP Address Distribution”. Below right, there is a button called “Connection list”, where you can define static entries based on MAC addresses.
To deactivate the VoIP part, go to “Advanced Settings”. In the “Network Interfaces” menu, double-click on the “Wan eth1.20 VoIP”. On the next screen, click on “Disable”. Beware though that this will also disable the remote management and automatic firmware updates. There is no real reason to turn it off, though. If you do not use it, it will not consume any bandwidth.
This BBox2 really needs a user manual …
Hope this helps
Dear Patrick !
First of all my congratulations for the clear and concise way you deal with all those topics – it’s a pleasure to read !
I am personally struggling with the B-Box 2 I received 2 days ago from Belgacom.
It connected from itself as claimed by Belgacom but I am puzzled at not finding (or being able to activate) what I expected.
I was accustomed to configuring my LAN manually (without the help of DHCP) with my previous Netgear DG834GT modem-router’s LAN-IP SetUp interface (on the base of the MAC-address).
Does this feature exist on the B-Box 2 and if yes where is it to be found and how can I activate it ?
I would like also to deactivate completely the VOIP feature.
Is it possible and how can I achieve that ?
Thanks in advance for your help !
Have a good week-end.
Jacques GERARD
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
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).
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 10.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.
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
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.
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
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.
@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.
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?
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?
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.
Great effort. Thank you. I will have a look at that over the next weeks.
I have managed to compile some busybox and other stuff from the openwrt toolchain here:
http://www.zoobab.com/bbox2
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.
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
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.
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…