Hi Guys,
I loaded Opnsense onto a PC. It was working. Then I moved house.
When I turn on the PC it boots into Opnsense. It stops at Login/password.
Is this OK???
I cannot remember my password or log in. I tried root/admin root/opnsense.
My gut says that I do not need this unless I want to change the setting.
At the moment I need the internet as my modem is not working.
Any king person?
Dan
OPNsense starts working without logging in. But if your location changed your internet config might have changed, too.
Consider reinstall with an existing backup.
How do I do that?
Do you have a backup?
If yes -> Reinstall according to setup manual and throw in the backup when asked for
If no -> You may want to think about your approach and use different hardware to read out the hard disk with a matching filesystem driver and download the configuration in /conf/config.xml
If you had your credentials, you could download it in the webgui. But I guess that's not an option. Well, you wouldn't have to reinstall then.
Thanks guys.
I reinstalled the programme and now have issues. The 2 videos I downloaded are confusing.
My programme says WAN em0 and Lan em1. The video says Lan em0 and Wan em01.
I have 2 network RJ45 in the PC and not sure which is which. I have tried both and still cannot connect to the OPNSense PC.
I now have NO modem as it stopped working.
So I am a little screwed.
Don't use arbitrary videos made by prople who frequently have no clue about the product. The documentation is right here:
https://docs.opnsense.org/
With a newly installed OPNsense LAN is always the first interface. Just boot the system and plug your PC into one port. If you get an IP address in the 192.168.1.0/24 network and you can reach the firewall at 192.168.1.1, the port is the correct one. If you don't and you cannot, use the other port.
Once you have that connection and you can login to the UI you can proceed to configure the Internet uplink (WAN).
Hi Patrick.
Thank you.
But my screeen says WAN is O and LAN is 1. I have tried to plug the network cable into both and cannot connect to the Opnsense PC?
I am totally lost
After a fresh installation LAN is always 0. Did you change anything after installation?
No I kept all the defaults
I tried to put a photo, but it woudl nto take
Did you import the old configuration by any chance?
No - I reinstalled.
I used the OPN PC and tried to change Wan to em1
Now it is V4 DHCP 100.68.12.81/19
But I lost LAN???
If you perform a fresh installation LAN will be on the first interface at 192.168.1.1 - always.
There's something else we are missing in this discussion that is hard to diagnose via a forum. I don't have an idea.
Perhaps:
- perform another fresh installation
- don't connect it to any network
- don't perform any interface assignments on the console, don't touch, just let it boot on its own
- plug PC directly into one port, then if necessary the second
The OPNsense must be reachable at 192.168.1.1 - unless that works with the 4 steps outlined above any other action is useless.
Hi Patrick – thank you
I re-installed again, and I got LAN 0 192.168.1.1
I do not understand "plus PC Directly into one port, then second....
I connected the OPN-PC to the network via switch and ethernet. Tired both ports on the OPN-PC, but it could not be reached.
Ran Network Diagnostics
The default gateway is not available
Device is not responding.
Plug your PC into one port of your OPNsense. If that does not work (PC gets an address and you can ping 192.168.1.1), use the other port. Don't use a switch, don't connect to network. Cable one end in PC, one end in OPNsense.
I do not have a cord long enough. - I found a long cord
C:\Users\X299-UD4-144>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Ran Network Diagnostics
The default gateway is not available
Device is not responding.
C:\Users\X299-UD4-144>ping 192.168.1.1
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.144: Destination host unreachable.
Reply from 192.168.1.144: Destination host unreachable.
Reply from 192.168.1.144: Destination host unreachable.
Reply from 192.168.1.144: Destination host unreachable.
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Ethernet 2 doesn't have a valid IP configuration
Bring the OPNsense system to your desk?
What's the IP address of your PC?
What is 192.168.1.144?
Is there another router in your network? This is why it is so important to only use a straight cable connection at first. We need to make sure you identified the LAN port, OPNsense is handing out IP addresses via DHCP, and you can connect to the UI. Then you can add more "infrastructure".
I do not know.
It used to be 192.168.144.
But the properties are blank. When I put in the above IP windows says there is a clash. But I put it in anyway.
No change
Don't change anything. Leave your PC at "automatic". Connect OPNsense with a cable without a switch.
All the results above are without a switch.
None of this makes sense. What is this PC connected to? What are these networks?
Connect your PC to OPNsense with a cable and don't connect anything else. Neither to your PC nor to OPNsense. Your PC will acquire an IP address in the 192.168.1.0/24 network. You will be able to reach the UI at 192.168.1.1.
If you don't do as told when I try to help you how am I supposed to help?
Hi Patrick – Thanks.
I have done what you have asked. There are 2 pc's 1 ethernet cable and no connection to 192.168.1.1
I even used my IP Scanner and there is no 192.168.1.1. It used to work....
But.....
From where does the PC get the 100.69 address? This is a CGNAT address, so that looks like you connected your PC directly to your Internet uplink. The OPNsense should go between the PC and the Internet.
Newly installed OPNsense, PC with a single network interface configured as DHCP/"automatic", PC connected to OPNsense with a cable, no other network connection to anything, power on OPNsense, power on PC, PC will be able to reach OPNsense.
If it isn't, the cable is broken, the network interface in OPNsense is broken, or the network interface in the PC is broken.
Hi Patrick – Thank you.
I do not have a modem (one between the internet modem and the network) – it broke today. Hence my need to get OPNSense working.
I have as you correctly noted, connect my PC directly to the NBN Modem – it needs another modem/router to work – that has broken.
When I have done the connection to the OPN-PC I have taken the cords from the modem out. So, there has been NO modem when I have tested. I have to re-connect the modem to communicate to you.
Initially I connected the OPN-PC to the modem, but then I took the modem out of the connection.
Cable it OK, as this is the one I am using to connect my PC to the internet (via the switched.).
Any ideas. I know you are far more intelligent than I and this is too hard for me.
So you have a crapton of other devices in that network that you just "forgot" to mention with a single word. Great.
- power off everyhing
- plug one port of OPNsense into switch
- power on switch and OPNsense - don't power on ISP modem
- when OPNsense is booted, power on PC
- does it get an IP address? can it ping 192.168.1.1?
- if not:
- power down everything
- use the other network port on OPNsense
- power up switch and OPNsense - don't power on ISP modem
- when OPNsense is booted, power on PC
This must work with one of the two OPNsense ports. This one is your LAN port. The cable from that goes into the switch. After identifying the LAN port connect the other one to the ISP modem.
Never connect the ISP modem to your switch.
ISP Modem --- WAN OPNsense LAN --- Switch ---> one or more PCs.
Sorry I lost my internet.
I manually changed my ip address to 192.168.1.100 and was able to connect to 192.168.1.1.
I made some changed (as per the video) into Opensense. I powered on/off the PC and now I cannot connect or Ping to the OPN-PC.
My IP address keeps going to 100.68.12.130.
I have no idea.
I have discovered that the OPN-PC has 3 RJ45 ports – I connected it into the original.. Previously the new Network Card worked. Now I am not sure. I connected the ethernet cable to the old one and I managed to connecte after changing the IP address.
Now it does not work.
DHCP is not enable for Ethernet 2??? – this is new???
When did I tell you to manually set your IP address?
Don't connect anything but OPNsense WAN to the ISP modem. Don't make any changes to OPNsense. It must work out of the box. If you change things according to "the video", I'm out. Go ask the author of that video.
Fresh installation - OPNsense booted and not connected to anything. PC booted and not connected to anything. Plug cable in PC, plug other end into each OPNsense port in turn. The one which gives your PC an IP address and lets you connect to 192.168.1.1 is the LAN port. Simple as that. Don't connect any other device, don't change any settings. For chrissake!
Hi Patrick – Thank you.
I really do not know what to say.
The only way I got to connect to the OPN-PC was to change my IP address. – nothing so far worked.
I live in far western NSW (1,300 km from Sydney), PC support is non-existent.
My modem broke and I thought (since it used to work) I would connect the OPN-PC. It did not.
I cannot get another modem (and I would rather get the OPN-PC working) for a least a week. Meaning my work has stopped.
I will re-load the programme again tomorrow. Too late now I will have to go to bed.
Not sure where you are located, but there seem to me very few OPN- people in Australia.
Thanks for the help. Hope (crossing fingers) we can get this fixed.
I find open source, only for the experts. While it promised the world, it is very hard.
Talk soon.
Hi...
Disconnected all hardware, no internet connection. It is 5:37am and I have been up since 4am
Powered off/on both PC's
Re-installed OPN again.
2 PC's #1 is main PC #2 OPN-PC
These PC's are connected with each other and to nothing else.
192.168.1.1
No Connection.
Windows Diagnostics: Ethernet 2 doesn't have a valid IP configuration.
Ping – transmit failed. General failure.
Ethernet 2 Status – Ipv4 169.254.219.94, subnet 255.255.0.0
Reset Ethernet 2 – same result no valid IP configuration.
I have done all you have asked. All other hardware is off and not connected.
I will have to connect my PC to the internet to communicate.
Attempt 1 IPv4 169.254.94 – sorry did not write all the numbers down.
Attempt 2 IPv4 169.219.94 – sorry did not write all the number down.
Attempt 3 IPv4 192.169.1.100
Attempt 3 seems to work.
I will re-boot main PC and see
Seems that the dual network card in OPN-PC is faulty – I will take out and re-instal.
Moved network card and OPN-PC rebooted?? Seems like the dual card is faulty in this PC.
Moved to 4 locations and tested both holes – Not a valid IP configuration. IP 169.254.219.94. 3 showed lights 1 did not (the longer slots no light)
Have to take the dog for a walk, or it gets too hot.
suggestion: take photos (assuming you have a mobile phone) and add them and try to draw what connects to what. Importantly, include the ISP equipment.
Quote from: foxint on April 16, 2024, 02:55:44 PM
(...)
My modem broke and I thought (since it used to work) I would connect the OPN-PC. It did not.
(...)
You mentioned 'NBN' previously.
If your NBN
modem broke, you lost all Internet until NBN replace it, with or without OPNsense.
If your ISP-provided router broke, OPNsense can replace it.
As per @cookiemonster's suggestion, if it's the router, you should take some pictures of your equipment to provide more clarity.
Thank you.
ISP modem is broken.
The set up is 2 PC and they are connected to each other with 1 ethernet cable.
It used to work...but not now. But as I said I can connect to the OPN-PC via its network hole. The new (that used to work) dual network card appears NOT to be working.
Perhaps as we try and fix. I just use the one port that works and set up a static IP for my main PC?? How is that done?
perhaps some clarity is useful.
A connection that requires a modem. A modem is hardware that establishes a connection with the ISP using credentials. OPN can not do that in software.
I think you are saying you moved house and you had a PC with two NICs for OPN and that used to work and now it doesn't but whether in both places or just the new one, you had a modem and now you don't (it broke).
If all this is correct, and your ISP connection requires a modem, you will not be able to get out to the open internet with only OPN. There is no software in OPN that can replace a physical modem.
Take pictures, and will be easier to confirm or you'll be left without hairs.
Thank you.
I have OPS-PC with its original Network socket – is this a NIC??? It is Rj45. I put in another Network card with 2 holes. This was working and so was the internet and the network. Now the card does not work. I have a few spares....but I have a success but no idea is this is good or bad
I have been able to connect to the OPS-PC via the cord into the original RJ45 socket.
I logged on to OPNSense and left all the defaults. Is this good or not?
I cannot have internet and the OPS-PC connected. So I have to disconnect the OPS-PC and connect to the internet to get help from you guys.
What should my next move be?
Perhaps the dual network card sockets should be connected to my NBN modem??
I keep having to reinstall the internet connection.....
hjh
hkh
The green cable looks like an RJ45 cable, so in the PC that is a NIC. So that matches what you are saying.
That is one part of the chain only though. I was hoping for pictures of the various pieces of hardware.
Find out from your ISP, do you need a modem? Not all connections require one. Which type of modem and what are their credentials used and required.
Quick look https://www.nbnco.com.au/learn/device-compatibility/vdsl2-modems . Is this your provider? You can see they have different requirements depending on connection/broadband product taken.
You need to be clear on what you have and need before you can figure out what needs to be done. Draw it in your mind:
ISP terminating device on the wall --> modem? --> OPN WAN --> OPN LAN -->
One more time: If you need a modem and don't have one, it will never "work".
Deducing from their screenshots I suspect the "modem" that broke was in fact a router and that further the remaining ISP device delivers a CGNAT address via DHCP.
The problem seemed to be that whenever they connected all of the devices (remaining "modem", OPNsense and PC) at the same time the PC would get an address in the 100.69 range from the ISP device and not be able to communicate with OPNsense. Of course not.
That's why I insisted to connect only OPNsense LAN (or each port in turn until it is evident which one that is) and the PC and nothing else.
But they refused to follow that line so I have no clue what is really happening, just like everybody else, obviously.
yes, I was curious when I saw an external CGNAT ip. Assumed due to house move/service change.
No idea without more and more informative info.
Hi guys.
Thank you all for your help. It has been great.
To answer one of your questions, I have the NBN (fibre to the kerb). I have a white box with 3 lights in the house that is connected with wires to the NBN, into which I plugged in another box Netcommwirelss NF4V that was then connected to a switch and to the various PCs in the system.
As the modem/router or whatever the Netcommwireless box is, would no longer display/transmit the internet, I have now put a PC with Opnsense in its place.
I have managed to get it to work on minimal settings. Just set up 5 static IP addresses, sort of. My main PC should be XXX.XXX. X.144, but it is now 100. So, I have no idea what happened. 144 is nowhere in the network.
I would like to set up some protection, I think that is a Firewall and a VPN. But as I researched this on the internet, it total confused me.
My system is only me, so no vLan (not sure what that is used for) and I just need an idiot's step-by-step guide to basic set up.
I also used the old Netcommwireless thing as a Wi-Fi hub/accesspoint/bridge/thing and it seems to work. Please do not ask me to repeat the operation.
I have the internet and I can see all my PCs on the network.
Thanks.... Still would like to pursue protections whatever they are for small guy.
A newly installed OPNsense comes with all the protection you need enabled by default for a small home network. Unless you actively mess up the configuration.
Also why do you care about the IP addresses of your client systems? They will get one from OPNsense via DHCP. There is no need to assign static addresses.
Hi Patrick
Thank you.
I have static IP addresses because I synchronise my data each night. So, they need constant addresses – so I thought. I also use Tight VNC to control the PC's as they are headless with no monitors, keyboards and mice. They sit in another room.
I am still worried that my main PC that should have a 144 IP is now 100????
I hope I did not mess up the installation.
Good to have some functionality back. FYI, there is not a single modem/router for sale in the whole town. So Opnsense was my only option. All the relevant shops no loner sell these items. I told you I live in Shitsville far from the back of beyond.
You can navigate to Services > DHCPv4 > Leases, check the IP addresses of your client systems, and by clicking on the small "+" on the right hand side assign a static IP address to your PCs.
Note that static assignments must be outside the dynamic range. You can check the dynamic range (IIRC it starts at .100) at Services > DHCPv4 > LAN.
So e.g. give your PCs addresses .11, .12, etc.
.1 is used by OPNsense already, so don't start at .1.
The fact that your PC used to be .144 and is now .100 does not matter, but if you need static entries, they must be smaller numbers than the start of the dynamic range. It's just numbers, every router/firewall product comes with different defaults.
Hi Patrick,
Thank you again. I am glad you and the other guys are here to guide me.
I am a little confused.
I think my IP range is 192.168.1.1 to 192.168.1.254.
1. 192.168.1.144 is in my mind within the range, so why did it not take?
2. 192.168.1.20 is my old NetcomNF4V, but it remains on 192.168.20.1 – not an issue, but I did try and change the IP from within the Netcom interface, but it did not work. I thought that Opnsense could fix, but not.
It would be nice to have the IP's as previously intended.
really?
this cant be real can it... troll much?
If you define the range from .10 to .245 you cannot have fixed reservations inside that range. So if you insist on using .144 for one PC then
- change the range to e.g. .200 - .254
- create a static entry with .144 and your PC's MAC address
Hi Patrick
That is very confusing.
"If you define the range from .10 to .245 you cannot have fixed reservations inside that range. So if you insist on using .144 for one PC then"
As I wrote previously I "thought my IP range was 192.168.1.1 to 192.168.1.254."
Is this the same as you saying ".10 to .245?
Surely 144 is within the .1 to .254 range. I have 7 items in the 100 to 124 range. Surely 144 is not too far away and within 10 – 254.
So if 144 is not in the 1 – 245 range, and I cannot logically understand, then what is the biggest number in the 1 - 245 range, if it is not 245?
Sorry for being stupid. I am just looking at the numbers??
In this picture that you postet the range is defined as .10 to .245:
(https://forum.opnsense.org/index.php?action=dlattach;topic=40018.0;attach=34484;image)
This range is used for dynamic assignments within the 192.168.1.0/24 network. That network has got addresses from .1 to .254 - correct. And repeating myself the range above is the dynamic pool. So static assignments must be in ranges .2 to .9 and .246 to .254, respectively because static and dynamic addresses must not overlap.
Hi Patrick,
I am not understanding.
Tell it to me as if I am a 5-year old.
Is the range is 192.168.1.1 to 192.168.1.245 – I am not even sure this is correct.
So what is the range (in whole numbers as the abbreviations are doing my head in) I have to work in. Bearing in mind I have devices from 192.168.1.100 to 192.168.124.
I cannot understand .2 to .9 and .246 to .254. That is 8 if you include the .2 and the .9 and that is 9 if you include the ..246 and .254. This seems very restrictive. And there is no mention of my devices between 192.168.1.100 to 192.168.124.
I am a student of the humanities and not a computer scientist.
Your network is 192.168.1.0/24.
That means you can use addresses from 192.168.1.1 to 192.168.1.254.
OPNsense has 192.168.1.1 so client devices are limited to .2 to .254.
With me so far?
Now there is a mechanism named DHCP that hands out addresses to client devices. This service has two different ways to pick an IP address for a device that asks for one.
- a static assignmen - "this device identified by this MAC adddress always gets this IP address"
- a dynamic pool - "whenever a device asks for an address pick a free one from some defined range"
If you look at your screen shot you see next to the word "Range" that the range is defined as .10 to .245.
This is something you can set.
Whenever some device ask for an address it will get a more or less random one somewhere from .10 to .245.
But you want to set a static assignment for a particular PC to .144, right?
With the range defined as above this is not possible. Because static assignments must be outside the dynamic range. This is a property of the DHCP server in OPNsense. You cannot use any address from .10 to .245 for static assignments.
That leaves .2 to .9 and .246 to .254 as free for static assignments.
If you want to use .144 for a static assignment you must redefine the dynamic range ("Range" setting in the screen shot) to not include .144.
How you do that is up to you.
Hi Patrick,
While I really appreciate what you are saying, I am not understanding it at all. Especially with the abbreviated numbers.
You lost me on line 3.
Can we limit our discussion to static IP assignment.
To confirm (I think I may/possibly/may not understand):
1. The scope or range of IP addresses is from 192.168.1.1 to 192.168.1.254. Meaning in my confused mind is 255 possible IP addresses including 192.168.1.1 through and including 192.168.1.254.
2. If I my understanding in (1) is correct there are 255 possible IP addresses within that range.
3. Then why is 192.168.1.144 outside this range?
4. 192.168.1.124 is a static IP address that works with one of my PC's.
5. If 192.168.124 works what is the largest number than works in the scope/range as defined in (1). My dim-witted brain says 192.168.1.144 is within this range – why not.
6. What is the largest number I can assign as an IP address within the range in (1). In my experience I have reached 192.168.1.124.... can I go to 192.168.1.125 or more?
I do not understand: "That leaves .2 to .9 and .246 to .254 as free for static assignments." If we can work through 1 – 6, do I need to know what "That leaves .2 to .9 and .246 to .254 as free for static assignments" means. As I said I am confused by not using the complete number. As I said I am not sure we need to go here yet.
In summary I did not understand a word of what you wrote.
Please look at that screenshot.
It reads:
Available Range: 192.168.1.1-192.168.1.254
You are correct. These are all addresses you can use in your network.
Below that line there is another entry:
Range: from 192.168.1.10 to 192.168.1.245
This is the range that DHCP will actually use to hand out IP addresses. It won't hand out anything < 10 or anything > 245. This is called the "pool" or "dynamic range".
Now if you want to have any PC configured with a static assignment that static assignment must lie outside this dynamic pool. Because you give e.g. .144 to your PC then some day you plug some other device into your network, that requests an address, DHCP thinks "hey, I have not yet handed out .144, so here you go" - any you end up with duplicate addresses.
It is your duty as the administrator to say, e.g.
- this PC will get .144
- that PC will get .145
- all devices where I don't care will get anything from e.g. .10 to .140
You must make sure that the last range does not include the two statically defined PCs above. There's nothing "technical" about that - you have to manually manage your IP addresses. Two devices must not have the same address. So if .144 is assigned to PC 1 you cannot have .144 as part of the dynamic pool, too.
Another try. Not taking anything away from Patrick's explanation.
- Network is 192.168.1.0/24 - that makes it WHOLE range from 1 to 255. Typically first and last taken up i.e. 1 and 255.
- You define your DHCP DYNAMIC pool now: say from 100 to 200. A range carved out of the WHOLE.
That means static leases must not be overlapping with between 100 to 200.
Therefore your static leases can be issued between 2 and 99; and 201 and 254.
- To be precise on that above: dynamic from 192.168.1.100 to 192.168.1.200.
Statics: from 192.168.1.2 to from 192.168.1.99 AND from from 192.168.1.201 to from 192.168.1.254
Hi Patrick and Cookiemonster.
Thank you.
I am still confused.
There are 2 ranges:
1. 192.168.1.1 to 192.168.1.254 and
2. A subset of the above 192.168.1.10 to 192.168.1.254.
The Dynamis range is #2 192.168.1.10 to 192.168.1.254.
Patrick said: "Now if you want to have any PC configured with a static assignment that static assignment must lie outside this dynamic pool".
Then, and I do not understand, why do I have static IP addresses within the Dynamic Range, is the Dynamic Range is off limits for static IP addresses.
I have:
192.168.1.105
192.168.1.105
192.168.1.115
192.168.1.118 and
192.168.1.124
All of which are in the Dynamic Range, that is not supposed to happen.
But why? This is in contradiction to your words.
See why I get confused.
These are not static. These are dynamic. They can change.
You plug in any device. DHCP will hand out any IP address from the dynamic range. You switch off the device. You switch it on a couple of days later. It will get another address from the dynamic pool.
If you manually set any address as static you must do this so that this static address is not inside the dynamic range.
If you don't, any new device you plug in or power on might get that same address from the dynamic pool that you already defined as static for a different device.
If you did not define any static addresses then everything will just work.
But you said you wanted to assign .144 statically to a particular PC. That's why I mentioned that you must not do that as long as the dynamic range also covers .144 or any time another device might get that same address.
Hi Patrick,
Thank you.
You are doing a super job at confusing me.
I will add a photo of my "static IP's" in OPNsense and I will add a photo of the actual IP address all but 144 that has changed to 100 have the static IP address that I assigned.
Mais pourquoi ??? But WHY ?? In one sentence you say that 192.1681.1 to 192.168.1.254 are NOT available for static IP, yet I have them
You are doing my head in...
You have all these static IPs. Fine.
You also have a dynamic range from .10 to .245. Still with me?
If you bring in two hundred new devices without static reservations, DHCPd will eventually hand out one of your static IPs to one of these new devices. Because the dynamic range includes your static IPs. DHCPd does not manage that for you. You tell it to use any address from .10 to .245 for dynamic assignments and it will happily do that no matter what you also defined statically. It is old school "do as I tell you" software, not "try to think for me" software.
We are just advising you that you
might end up with duplicate IP address assignments if you do not manually take care that the dynamic range and the static assignments do not overlap.
Repeating: everything is fine. You can do all you did. Your network is fine at the moment.
It just so might happen one day that you connect a device and it will get an IP address that you already assigned as "static" to another device. And then some things won't work anymore. At least for the two devices in question.
QuoteIn one sentence you say that 192.1681.1 to 192.168.1.254 are NOT available for static IP, yet I have them
I said that .10 to .245 are not available for static assignments. Of course all addresses must lie in the .1 to .254 range. But the dynamic pool (.10 to .245) and the static assignments must not overlap.
The fact that the software does let you enter these does not change the fact! DHCPd does not do a consistency check! It lets you configure whatever you want even if it might breaks things. That's why we are repeatedly warning you not to configure your settings that way. You must manually ensure that the static assignments are outside the dynamic range. You must do this. DHCPd neither checks nor cares and will start to hand out duplicate addresses because you configured it that way.
I Partick,
Thank you.
But I DO NOT UNDERSTAND.
You still have not explained why ALL my static IP's have been OK and one (144) and been reassigned to 100) and NO other device in my network is on 100.
It might happen in the future that some new device will get the same IP as one of your existing static entries. It just might happen. Because the dynamic pool for unknown devices overlaps with your static entries.
Hi Patrick,
Thank you.
My apologies for not understanding.
But you have not said this, but can I understand THAT:
In my configuration - The labelling under Servies: DHCPv4: [LAN] (as I have attached):
Enable tick
Deny unknow clients no tick
Ignore Client UID no tick
Subnet 192.168.1.0
Subnet mask
Available range 192.168.10. – 192.168.1.254
Range
From to
192.167.1.10 192.167.1.245
Does RANGE mean pool of CASUAL IP's that can be allocated?
Do I have to reduce range to say 192.168.1.10 to 192.168.1.100 so I can have static IP's above 192.168.1.100?
YES! How many times did I write that "Range" is a dynamic pool of addresses? And that your static allocations must lie outside of that pool?