Bbox- proximus Belgium - static IP
Solved
juniel75 Posted messages 26 Status Member -
Hello everyone,
I'll try to keep it as simple as possible and then I'll provide more details later ...
I have a bbox-3 and I'm trying to link a MAC address to an IP address for Wi-Fi cameras using a Raspberry Pi.
The problem is that the bbox-3 refuses; every time I try to add a MAC address, it returns to the Bbox homepage.
My question is, is it possible to connect another router just behind the bbox to manage the IP addresses since the bbox won't?
No point in thinking about customer support; they don't even respond.
The reason for my request is that the servers and applications managing the forwarding of these cameras are abandoned ... no more server, no more support.
So to avoid throwing away 9 cameras, I installed a Raspberry Pi and integrated the 9 cameras. It works very well, but if the cameras are reset, the IPs change and the cameras are no longer accessible, requiring me to re-enter the IPs.
In the picture, the page of my router where you need to enter the data ... if you have any advice or other ideas, I’m all ears.
Thank you
Have a good weekend
jb
6 answers
-
Hello,
why don't you install a DHCP server on the Raspi?
You can configure static leases there.
https://raspberrytips.fr/serveur-dhcp-raspberry-pi/
And disable the one from the box to avoid conflicts.
And there you go ....
But gosh, those line spaces are so annoying!! -
Thank you for this clear, effective, and detailed response!!
-
yg_be Posted messages 23437 Registration date Status Contributor Last intervention Ambassadeur 1 588
Hello,
The DHCP configuration page of the box seems strangely empty. Maybe we should start by restoring the original configuration?
-
I agree.. Let's see what the original configuration looks like and then give the DHCP server an address range because at the moment we can't see anything..
Further down it seems that you can assign fixed IPs associated with a MAC address... -
-
As I feared, the reset created another problem... No more internet access.
Where can I find the passwords? The information on the back of the box is only for the wifi and router...
After much searching, I found the sacred document with the identifiers (2014).
Thank you for your dedication to everyone.
I noticed that all the information has reappeared, so I think it's okay. Thank you.
Hello,
Is it possible to connect another router right behind the Bbox to manage the IP addresses since the Bbox doesn't want to?
Yes, there is the "generic" way where you place your own router in cascade with the one provided by the ISP.
There are generally two ways to configure the second router:
- With its NAT mode enabled: in this case, the LAN network of the second router will be unknown to the Bbox, which can cause issues when trying to communicate devices from the Bbox LAN to the second router's LAN (easy solution: put everything on the second router's LAN). If you plan to create port forwarding, you'll need to configure the "chain" of forwarding on both routers.
- Without NAT mode: you would then need to configure a static route on the Bbox, but this allows you to set up port forwarding only once (on the Bbox).
In both cases, the Bbox is involved in the routing.
Otherwise, although the Proximus Bbox does not offer bridge mode, it allows for "PPPoE passthrough".
Your personal router, connected to the Bbox's LAN, can directly authenticate to the Proximus network with your PPP credentials. Your personal router will receive its own public IPv4 on its "pppoe" interface, its IPv6, as well as an IPv6 prefix in /56. No configuration will be required on the Bbox (neither bridge mode nor port forwarding).
The difference with a "bridge mode" as offered by other ISPs is that the Bbox's LAN remains functional. Your personal router will always have an IP in this LAN, which it will receive via the Bbox's DHCP. However, this does not prevent your personal router from providing its own DHCP service for its LAN. Nevertheless, care must be taken to ensure that the Bbox's DHCP does not alter the default route of your custom router (which must route its traffic through its PPP connection and not through the Bbox).
Your cameras need to have a static IP on your network. The MAC address gives you permission, but the IP address gives you the target of the camera.
The static IP of a device is determined by the device itself; it can either be fixed or assigned by the DHCP server.
On the DHCP server, you might be able to block an IP for a MAC address; check in the box if that's possible.
For the public IP, you can use a service like "No-IP," which has a free option, I believe. This allows you to automatically retrieve the public IP with each change (if there is one, of course).Thanks for the info, it's definitely a router since I have about ten connected sockets, a Raspberry Pi, 3 PCs, and connected light bulbs...
I'm going to perform a reset tonight and we'll see tomorrow the extent of the damage...
Have a good evening and thank you for your advice.
Ju
-
