Belgacom bbox 2 manual

De manual die bij de BBox-2 geleverd wordt is bijzonder schaars met informatie. Heb gezocht, zelfs Belgacom Self Care beschikt er niet over. Heeft een tijdje goed gewerkt, tot een stroomuitval van ong. DHCP op automatisch range van Van buitenuit evenmin toegang meer DynDNS is nochtans ingeschakeld maar weigert nog up te daten, uiteraard normaal, kan niet meer naar buiten.

Ok AVG geraakt niet meer buiten, wil niet meer updaten. Groot probleem. Since this firewall blocks incoming connections you may need open a port through it for certain games and applications. This process of opening a port is frequently called a port forward , since you are forwarding a port from the internet to your home network. While these steps might seem difficult at first, we will walk you through each step for your Belgacom B-Box2 router.

We think that forwarding a port should be easy. That's why we created Network Utilities. Our software does everything that you need to forward a port. Get Started Now! It is important to setup a static ip address in the device that you are forwarding a port to. This ensures that your ports will remain open even after your device reboots. Now we are going to login to your Belgacom B-Box2 router.

Your router has a web interface, so you will login to it using your web browser. It usually does not matter which browser you choose to use.

Open up your web browser and find the address bar. It should look something like this:. We will use readelf. Here we can use the toolchain or the standard of our linux.

At the end of the day ELF format is the same for all architectures: Quote. We will convert the binary kernel. Let's just say ELF headers are removed. Usaremos objcopy command of the toolchain: Code:.

Finally, we compress the kernel. Compression techniques can be used bzip2, gzip, lzma and lzo, and tell your mkimage. I have not tested other than gzip, and not know the capabilities that was compiled u-boot. Probably work, but you yourselves Smiley Code:. Well, we have the kernel binary, compressed, and also know the architecture and the load and entry points. We can run and create our uImage mkimage to stick it to the router. Now we can only install this uImage on the router.

It's pretty simple, but special care must be put in some things. First you have to climb the uImage. Unfortunately we have no network, so we have no choice but to use the old kermit. Also, take the opportunity to comment that I strongly recommend you use the putty as a terminal to connect to the router. Do not use the minicom. Not you wear the kermit own terminal at least as long as you send the file.

NOTE: Used to better the gkermit ckermit though you have installed on your system. The other distributions, you know how to do well. Once installed both programs, we create a configuration file for kermit, we call such kermit. Like this: Code:. The first direction would be the 0xBF0A usable then.

This implies that the kernel must be recorded in any direction that is a multiple of 0x although we will use 0xBF0A for reasons that will later , since you can not start writing in the middle of a sector.. Make use of the calculator. Consider the first address free, 0xBF0A, then:. You will not be. Back to our router. The first thing you have to do is delete the part of the flash that we use.

Once deleted, proceed to the last step. Copy the kernel to flash until now was in memory. Otherwise, do not compile. Warned you are. It should compile perfectly after hours and a half or 2 hours, depending on your connection speed and CPU , but I advise you to do this: Code:. Thus, the compilation will not be silent. A lot of compilation messages, downloads, etc will appear in your terminal, but in case of error-hopefully not-be easier to detect where. These files are: Two JFFS2 images 64k and k aligned and a squashfs image, a kernel "ghost" that we can delete with confidence, because we will use "our", the ImageBuilder, we will create images without having to recompile, and a file with the md5 of the above.

Also a directory with all the packages that you have chosen. Now we will install OpenWRT on your router. Technically, it should be done from the u-boot, but our attempts were wastelands. So we will do in a more unorthodox but functional prefect. This we see are the partitions on the flash. One for the boot, one for the kernel and the other to dedicate to our image, as you can see mtd2 matches. Well, let's copy the file-root. As you will see, when connected, the router will display messages recognizing the device as sda, and a partition if you have one , sda1.

We create a mount point and assemble: Code:. Easy, right?. Well, let's check that it worked. We will mount this partition, again creating a mount point before: Code:. You will see that there is a warning, nothing happens, you can ignore it. Go to the directory and see the contents: Code:.

If you get it, post it here, please. Well, from here, if you're an expert on OpenWRT do this you probably know better than me, but if not, this is how I did. For steps:. Recall that we have compiled the kernel separately. This step is not strictly necessary to boot, but I advise you to do.

This prevents a lot of errors in console. Also, if you do not even have lan, so we need a firewall? Again, this is not necessary to boot, but we will not delete messages from stderr in case there is a problem.