Unfortunately, the train has already left for me to intensively learn another language (in this case English). So far, Polish and Russian are pretty good for me. But now to my problem:
I've been using the eBlocker since the very beginning and haven't had any major problems so far. For a long time I had considered whether I should update to version 2.5.x. At the weekend I did it and got a lot of problems straight away.
I operate two interrelated networks. This means that network node 2 is split for 2 IP addresses and uses the resources of network 1 (explained simply). In order for network 2 to work, the node (router) has a fixed IP in network 1.
The eBlocker in network 1 manages the DNS and DHCP assignment, which has worked wonderfully so far. After the update, the eBlocker ignored all fixed IPs and simply assigned new IPs (from its group). These could no longer be changed, so I was forced to put the DNS control and DHCP assignment back on the router (so switch back to "external" in the eBlocker network).
Surely it couldn't have been? What went wrong?
There is no know issue regarding eBlocker's DHCP after the upgrade. eBlocker usually scans the network and reassigns the same IPs if DHCP is initially set up. After the 2.5 upgrade "fixed" assignments are taken over automatically from 2.4 in all cases tested.
Hint for a fix: After assigning an external DHCP have you tried to switch it back to eBlocker's DHCP (as this will scan the network anew)?
Generally I'm not sure about your particular setup from the description above. But if the above hint did not fix the issue you might want to check out this post in case you are using eBlocker's MAC address for some "magic" in your networks: https://eblocker.org/community/bugs-features/known-issue-ip-and-mac-address-change-after-eos-2-5-upgrade/
THX!