DHCPOFFER not being accepted
-
I just lost an HP OfficeJet 9025 on my wired network the other day. Same symptoms I see the request and offer in the logs but the officejet never gets an IP. Moved to wireless and all is good. No changes to my network recently that I know of. I thought it must have been a rouge DHCP server but Fing can’t find it.
Now I have a wired Linux box doing the same thing.
Really weird. Never experienced this before.
-
@elliott32224 said in DHCPOFFER not being accepted:
but there is no setting for that.
There is one 'setting' that will do the job : jto be sure : remove it from the network during tests to be sure.
@cwagz said in DHCPOFFER not being accepted:
I see the request and offer in the logs but the officejet never gets an IP
It sends a DHCPDISCOVER so it can communicate with pfSense.
pfSense sends DHCPOFFER : Looks like it never received that DHCPOFFER because it's sending a DHCPDISCOVER again.When you do not use the Wifi of that printer, what becomes the IP after a while ? You can print the actual network settings I presume by pressing (a combination of) buttons on the printer.
Maybe not a second DHCP but a broken signal path in the switch (interchange all the ports to find out), a cable (swap chamge them all) or, worstc ase, the NIC in the printer has a 'broken' input (so it receives nothing).
-
@gertjan The printer has always had a static IP assigned in pfSense. When my wife informed me that the printer was no longer working we went through and rebooted everything. I then noticed that the printer had a 169.X.X.X address. I checked everything and even rebooted my main switch. I tried manually configuring the printer to it's static IP address but it would not communicate. I could not get to it's webpage or ping it. I noticed the requests and offers listed over and over again in the pfSense log.
I then unplugged the network cable and the printer auto switched to WiFi and picked up a random address assigned by the pfSense DHCP. Now I could go to it's webpage and ping it. I went into pfSense and updated the printers static IP assignment to the new MAC and rebooted the printer. Now it came back up with its original static IP that it has always had and we were able to print without problem with no changes on the client computers.
Tonight I went to boot my kids computer via a linux flash drive as I normally have it mine ETH using RaveOS overnight. The computer has a static IP assigned by pfSense and was working fine all day in Windows 10. I get into Linux and no IP. I set a static IP and nothing. This time I do not see log entries in pfsense. I then booted this same computer straight back to Win 10 and it picks up its normal static IP no problem.
This machine was picking up an IP from pfsense just yesterday with the same RaveOS flash drive configuration.
I have rebooted my Netgear GS724Tv4 several times now. I can't remember the last time I rebooted it. Probably when I installed it in the rack.
I just find it really strange that someone else seemed to have the same problem.
My network consists of:
APU2 running pfSense
Netgear GS724Tv4 - pretty much default settings
3x Netgear WAC510 in access point mode managed via Insight
3 groups of 2 piholes that manage my kids internet content restrictions and YouTube accessI have had this configuration for a long time and never experienced anything like this. I assumed it was another DHCP server or an IP conflict but I am out of ideas now.
The only other thing I can think of is that my switch has gone bad or it is actually the HP 9025 causing the problem since that just seems like a crazy coincidence here.
Netgate 6100 MAX
-
@cwagz said in DHCPOFFER not being accepted:
The printer has always had a static IP assigned in pfSense.
Wait .....
The printer has TWO network interfaces.
The WIFI interface has been shut down.
The wired NIC is set to static IP settings : this means the printer is not using a "DHCP client" to obtain an IP (and network mask, and gateway, and DNS). It "Static" or "DHCP", not both.So this line :
DHCPOFFER on 192.168.4.246 to 34:e1XXvia em1can not come from your printer, but some other device.
Is "34:e1XX" your printer ?
@cwagz said in DHCPOFFER not being accepted:
I then noticed that the printer had a 169.X.X.X address.
169.x.x.x is special.
The 169.x.x.x. is auto assigned by the DHCP client in a device when it does not obtain a valid lease with xx time.
On of the side effect of "169.x.x.x" is : "you can't communincate with it".
So, this printer with a static IP setup has no static IP setup.No need to access the GUI interface of the printer (a Ethernet connection must exist to be able to do this !) : use the buttons on the printer to print the printers settings. You can do so when the printer is connected to nothing, except the power.
What are the defaults 'after power on' network settings ?
@cwagz said in DHCPOFFER not being accepted:
or it is actually the HP 9025 causing the problem
The options are still opens ;)
-
@gertjan my printer was always set to DHCP. I had a static DHCP reservation in pfsense for it for the wired MAC. A few day ago it stopped getting an IP and was showing the 169 address. While troubleshooting I went into the printer menu and tried to statically assign the printers normal reserved address. The printer would still not work. I set the printer back to DHCP and pulled the Ethernet cable. This causes the printer to turn on its WiFi interface and request an address. This request was successful via pfsense dhcp.
I then altered the static reservation in pfsense so the wireless MAC would be assigned the correct address so my client computers would still print seamlessly. This all worked out and has been fine since. The printer is still successfully using DHCP over WiFi.
Now I have a pc that worked until today and now only gets DHCP when in windows? In Linux DhCP is not working and if I assign a static ip in Linux it still does not work. It worked yesterday.
It is like my switch is blocking the traffic. Or pfsense is somehow blocking the device. Like some kind of security setting since maybe it looks like a different device with the same MAC once I boot to Linux.
I really don’t know where to start.
I was going to update the switch firmware and factory reset it.
-
@cwagz said in DHCPOFFER not being accepted:
my printer was always set to DHCP. I had a static DHCP reservation
Oops.
Static reservation .... I was reading - no : understanding that you meant : a static IP setup.
That's ok : a static DHCP reservation on pfSense is the best option. That's what I'm using for all my 'server' type of devices.@cwagz said in DHCPOFFER not being accepted:
..... The printer is still successfully using DHCP over WiFi.
Ok, I guess the printer's Ethernet NIC is bad. But, you have the Wifi, a very valid "Plan B" solution.
@cwagz said in DHCPOFFER not being accepted:
Now I have a pc that worked until today and now only gets DHCP when in windows? In Linux DhCP is not working ....
Is this a dual boot system ?
The fact that the NIC emits a DHCP discover when Windows boots, and not when booted with Linux, means : that the issue is not the NIC.
I'm 99 % sure it's a DHCP client setting - or somewhat lower then that.
Check the "dmseg" log and see if the network device is found ans assigned a driver name like "em0" during boot.
When you use "ifconfig" what do you see ? -
I updated my Netgear GS724TV4 to the latest firmware and factory reset it. All of these weird issues are now gone. The switch must have lost it's mind at some point last week. Linux was configured fine on the dual boot machine it just wasn't able to get past the switch for some reason.
My printer is able to connect via the wired connection now as well.
-
@cwagz Did you ever get this fixed? I have not.
-
@elliott32224 said in DHCPOFFER not being accepted:
@cwagz Did you ever get this fixed? I have not.
I have not had further issues since updating my switch firmware. I do wonder if it had something to do with the HP Printer.
-
@cwagz Thanks.
-
@gertjan Well, problem has been solved. My set up involved 2 unmanaged switches. The eero connected to the first switch to provide internet access to wired devices. The error: I had two cables from the first switch connecting to the second switch. When I found this to be the case, unplugging one immediately fixed the problem.
