What do you mean by “messing everything up”?
When it comes to manually setting IP addresses, you consciously choose them within the network area, but outside the area intended for automatic assignment, so you can then see directly from the IP address whether it is a fixed one or automatically assigned IP address and the two IP address allocation mechanisms are guaranteed never to get in each other’s way.
Here’s another example:
If you use the default value for the automatic allocation range of 192.168.1.100 to 192.168.1.254, then you only select IP addresses between 192.168.1.2 to 192.168.1.99 for the manual IP fixations.
In general, you can still say that manual fixes only really help if you want to access a web GUI of a single device using the address, or if you want to establish an explicit network connection in your own network via the IP address of a single device , otherwise fixing IP addresses is simply “waste of time” from a LAN technical point of view.
Hobby-Nerd ohne wirtschaftliche Abhängigkeiten zur Swisscom
Hello
my DHCP range in the IB2 box is defined from 5 to 50.
From 100 onwards, all IP addresses are fixed addresses (heating control, house control, car, etc. -> all with their own GUI)
Now it happens that the IB2 box “changes” the range for the fixed addresses to 100-254.
For whatever reason. It also happens that addresses are assigned twice.
e.g. the 100 for my NAS and the heating.
What is the reason?
Greetings Mainzelmann
In general, it shouldn’t happen that the DHCP range is changed automatically.
The IB2 is just not that fresh anymore and it may well be that it has “a corner off”…
Maybe a hardware reset and then setting it up again is enough - and if you do that, just pay attention to the next note:
On the other hand, leave the default DHCP range where it is and assign the fixed IP addresses in the range from 2 (10) to 99 - as suggested by colleague Werner…. 😉
….keep on rockin'
@Mainzelmann wrote:
Hello
my DHCP range in the IB2 box is defined from 5 to 50.
From 100 onwards, all IP addresses are fixed addresses (heating control, house control, car, etc. -> all with their own GUI)
I designed it similarly to you, but placed the fixed IPs underneath. 😉 For me, the advantages actually outweigh the advantages of using “langenhostname.fritz.box” or in your case “fixername.local”.
Now it happens that the IB2 box “changes” the range for the fixed addresses to 100-254.
My hypothesis (hipshot): The internal memory has a crack, which is discovered using checksum algorithms. In this case, the software’s reaction would be to start over with the default values.
However, I would expect that other user settings would be thrown overboard. But I don’t know of any specific case with your IB2. Everything is very vague and empty…
Whatever. It also happens that addresses are assigned twice.
e.g. the 100 for my NAS and the heating.
This might be a stupid question: Are you talking about dynamically assigned addresses? Not the fixed ones, right? Both would be fatal:
- The fact that the DHCP in the router assigns addresses twice would be a software error. And that is rather unthinkable with such well-aged meat (IB2).
- No protocol prevents them from being manually / mistakenly configured twice on different devices. It would then be more of a coincidence which IP gives the answer.
- This also applies if the manually entered IP (.100 for the NAS) would collide with the first device assigned by the DHCP (.100 heater). Neither DHCP (router) nor NAS (fixed IP) can detect the collision of the two addresses.
Sorry if these are banal examples. It is difficult to gauge the network knowledge of a forum participant from the outside.
Äs Greetings
Android
👽
In order to have as few problems as possible, I would leave the IP settings of the IB as they come by default. Important: leave the DHCP area as written by @WalterB. And place the fixed IPs that you assign to the devices outside of this “Swisscom standard”; for example between 192.168.1.10 and 192.168.1.99.
If you assign fixed IPs to the devices that are in the standard DHCP range of the router, you will almost inevitably have IP conflicts after such a router failure, because then the DHCP clients “have to” occupy addresses that are already used by others Devices are assigned static IPs. The IB knows nothing about these statically assigned addresses on the individual devices and takes no account of them.
From my point of view, such a total failure of an IB is extraordinary anyway. It’s probably shot and I would look for a replacement (IB3).
Then I would think about the benefits of statically assigning an IP address directly on the device. In my experience, none anymore. For some time now, I have been using the router’s ability to assign a device a permanently assigned IP for devices that need a fixed IP (of course also outside the DHCP range). The router then takes over the assignment of the fixed IP addresses and no longer the end devices, which then remain on DHCP. This has the advantage that in the event of a failure like the one you describe, there will no longer be any IP conflicts in the network (with all the tedious consequences such as network failure…).
Dear community
At the urging of Swisscom support, I was persuaded to switch/purchase IB3.
Problem still exists:
- I laboriously assigned all the fixed IP addresses in the range 100 to 250 (and yes, I have more than 100 fixed IP addresses 🙂
- If I had to assign new fixed IP addresses to all devices, I would be busy for a few days…
- DHCP range set to 5-90…….and after three restarts all devices in the DHCP range above 100 could be found again……grrrrrrrr……
Where does this auto come from? Change?
Greetings Mainzelmann
No one will probably be able to give you a definitive answer.
But the fact is:
- You don’t have an everyday usage scenario
- The Internet boxes are known to sometimes have a bit of trouble with very large networks with a lot of participants
- You ignored the repeated advice to leave the standard DHCP area where it is and to place the area with the fixed addresses outside of this area
….keep on rockin'
As in December 2023, I would still strongly advise against trying to connect directly to the network of an Internet box with over 100 clients.
I consider the risk that you will come up against not completely transparent limits of the maximum number of WLAN clients per WLAN band and the limits of the possibilities of the DHCP server of the Swisscom Internet boxes to be too great.
My recommendation for a really large network is always to cascade at least one other broadband router behind an Internet access router and, at the same time, to distribute the clients across at least two or more different networks in an organizationally sensible manner.
Hobby-Nerd ohne wirtschaftliche Abhängigkeiten zur Swisscom
@WalterB wrote:
Yes, didn’t you create a backup of the Internet-Box 2 on your PC and then install it on the Internet-Box 3?
Logo, but unfortunately it couldn’t be played on the IB 😞
@POGO 1104 wrote:
I don’t think anyone will be able to give you a definitive answer.
But the fact is:
……
- You ignored the repeated advice to leave the standard DHCP range where it is and to put the range with the fixed addresses outside of this range
No, that has grown historically and everything worked out perfectly at the IB1. I only had problems with the IB2
and all addresses were already distributed in the range above 100.
@WalterB wrote:
I’ve had the area at the bottom of the picture for many years and haven’t had any problems.
Ooooh man….would I go through the trouble of moving all of this…..there’s a KNX attached to it, Sonos, Homeassistant, several NAS, etc….
The question is, does it really MUST be so with so many fixed IPs? 🤔
People often underestimate the fact that a lot of things actually work very well. with DHCP.
Fixed IPs for active network devices: SmartSwitches, APs, NAS, routers, HomeAutom. Gateways yes.
Remaining, stupid clients all via DHCP
….keep on rockin'
@POGO 1104 wrote:
The question is, does it really MUST be so with so many fixed IPs? 🤔
People often underestimate the fact that a lot of things actually work very well. with DHCP.
Fixed IPs for active network devices: SmartSwitches, APs, NAS, routers, HomeAutom. Gateways yes.
Remaining, stupid clients all via DHCP
Correctly:
DHCP: iPads, iPhones, laptops, macbooks…….we have 15 of them
fixed IPs: TVs, several NAS, heating, solar inverters, solar batteries, wall boxes, whirlpool, pool system (pump, heating, countercurrent, etc.), sauna -> (fixed IP, since everything is via KNX and Homeassistant as well various wall tablets are running) With DHCP there would be a huge “Knorz”, various switches for IP cams…etc……
There are a “few” devices in the hut 🙂
@Mainzelmann wrote:
@POGO 1104 wrote:
The question is, does it really MUST be so with so many fixed IPs? 🤔
People often underestimate the fact that a lot of things actually work very well. with DHCP.
Fixed IPs for active network devices: SmartSwitches, APs, NAS, routers, HomeAutom. Gateways yes.
Remaining, stupid clients all via DHCP
fixed IPs: TVs,🙂
Why TV’s?
How/where do you assign the fixed IPs?
On the devices themselves or via assignment in the router?
….keep on rockin'