Merlin 380.59 Wireless Log not showing IP and Name for HP printer

[dvohwinkel]

I don't know if this existed before.. it may have.

I have a HP 276dw printer (using wireless N) with a hard-coded IP address (to get around the bug where the printer will crash if it has to query for it's ip address from an ASUS router) that is also listed in "Manually Assigned IP around the DHCP list". The IP and Name fields on the Wireless Log page are blank. All other devices have all fields listed.

It is showing it's MAC RSSI Rx / Tx Rate Connected Flags.. just not IP and Name.

I am talking about under Advanced Settings->System Log->Wireless Log.

Another interesting point is that it shows up fine on the "Network Map".

Regards

-dvohwinkel

 

[bluepoint]

I don't know if this existed before.. it may have.

I have a HP 276dw printer (using wireless N) with a hard-coded IP address (to get around the bug where the printer will crash if it has to query for it's ip address from an ASUS router) that is also listed in "Manually Assigned IP around the DHCP list". The IP and Name fields on the Wireless Log page are blank. All other devices have all fields listed.

It is showing it's MAC RSSI Rx / Tx Rate Connected Flags.. just not IP and Name.

I am talking about under Advanced Settings->System Log->Wireless Log.

Another interesting point is that it shows up fine on the "Network Map".

Regards

-dvohwinkel

Give it a little time when it renew the IP it'll recognize the name hopefully.

 

[dvohwinkel]

Give it a little time when it renew the IP it'll recognize the name hopefully.

Will it renew the ip thought? The ip is hard-coded/manual on the printer. I guess I'm a little surprised because it has the MAC and it is one of the entries that I put in the manual DHCP.

 

[bluepoint]

Will it renew the ip thought? The ip is hard-coded/manual on the printer. I guess I'm a little surprised because it has the MAC and it is one of the entries that I put in the manual DHCP.

Ooops, if it's hard coded then it won't renew. If this is the case the ip is outside of the DHCP pool? Try to use the DHCP reservation to assign the printer's IP and put in the name.

 

[dvohwinkel]

Ooops, if it's hard coded then it won't renew. If this is the case the ip is outside of the DHCP pool? Try to use the DHCP reservation to assign the printer's IP and put in the name.

Right. I do have it also as a DHCP reservation, so it should know from there what it's name and ip is.. and yet it is blank on that log page.

 

[bluepoint]

Right. I do have it also as a DHCP reservation, so it should know from there what it's name and ip is.. and yet it is blank on that log page.

Wait, you have the printer assigned a static IP and at the same time reserved an IP?

 

[dvohwinkel]

Wait, you have the printer assigned a static IP and at the same time reserved an IP?

Yes but the values are the same. There is a known bug with some HP printers and Asus routers.. if you have the printer query the DHCP server for an ip address it will cause the printer to crash. (It drove me nuts figuring out what was going on).. the fix is to hardcode(manually add) the ip address on the printer.. the problem with doing that is that I am also using DHCP in the env.. and I don't want that ip address to be used for something else.. so I also put the same ip, hostname, and MAC into the DHCP reservation so that no one else will try and grab it.

As long as they are all the same I don't see why that would be an issue.. but I could try and remove the DHCP reservation and see if the problem goes away.

 

[dvohwinkel]

Yes but the values are the same. There is a known bug with some HP printers and Asus routers.. if you have the printer query the DHCP server for an ip address it will cause the printer to crash. (It drove me nuts figuring out what was going on).. the fix is to hardcode(manually add) the ip address on the printer.. the problem with doing that is that I am also using DHCP in the env.. and I don't want that ip address to be used for something else.. so I also put the same ip, hostname, and MAC into the DHCP reservation so that no one else will try and grab it.

As long as they are all the same I don't see why that would be an issue.. but I could try and remove the DHCP reservation and see if the problem goes away.

I removed it from the DHCP reservations and rebooted.. no difference. Now I will try and make another wireless device ip and hostname hardcoded on the device and see if it also disappears.

 

[bluepoint]

the problem with doing that is that I am also using DHCP in the env.. and I don't want that ip address to be used for something else.. so I also put the same ip, hostname, and MAC into the DHCP reservation so that no one else will try and grab it.

As long as they are all the same I don't see why that would be an issue.. but I could try and remove the DHCP reservation and see if the problem goes away.

Assigning static IP manually to the printer then reserving the same IP in the DHCP is not a normal thing to do. You have to use one setup but not both, it could cause some problem not only the name but in the DHCP itself. If you wanted to assign static IP's manually, change the DHCP scope to start with .10 leaving .2 to .9 for your statics. This way you will not have IP conflicts with the dynamic DHCP assignments(reserve or not).

 

[ColinTaylor]

Having looked at the source code I can see that the Wireless Log page just uses /var/lib/misc/dnsmasq.leases to determine the host name rather than querying DNS. Obviously with a static assignment on the printer there is no lease created, hence the missing name. The Network Map function is much more sophisticated.

Assigning static IP manually to the printer then reserving the same IP in the DHCP is not a normal thing to do. You have to use one setup but not both, it could cause some problem not only the name but in the DHCP itself.

Actually, that's a perfectly valid thing to do. Although I admit it can be confusing. You're just using dnsmasq to reserve that IP address so that it isn't used by another device and to assign it a host name on the router.

 

[dvohwinkel]

Having looked at the source code I can see that the Wireless Log page just uses /var/lib/misc/dnsmasq.leases to determine the host name rather than querying DNS. Obviously with a static assignment on the printer there is no lease created, hence the missing name. The Network Map function is much more sophisticated.

I changed an ipod-touch to be manual and not DHCP and it's hostname and ip address disappeared on the log page just like for the printer. I think that verifies what you found in the source code. I guess I should look into how to report a bug/logic error.

Thanks

-dvohwinkel

 

[dvohwinkel]

Having looked at the source code I can see that the Wireless Log page just uses /var/lib/misc/dnsmasq.leases to determine the host name rather than querying DNS. Obviously with a static assignment on the printer there is no lease created, hence the missing name. The Network Map function is much more sophisticated.


Actually, that's a perfectly valid

I changed an ipod-touch to be manual and not DHCP and it's hostname and ip address disappeared on the log page just like for the printer. I think that verifies what you found in the source code. I guess I should look into how to report a bug/logic error.

It's odd because the printer and ipod-touch ip address are there one minute and then go missing the next. Are they also getting the ip address from the lease? (though if it was it should always be missing in my example where I manually set their addresses)

 

[ColinTaylor]

It's odd because the printer and ipod-touch ip address are there one minute and then go missing the next. Are they also getting the ip address from the lease? (though if it was it should always be missing in my example where I manually set their addresses)

No, the IP addresses don't come from the lease file. As far as I can tell it relies upon the ARP values in /proc/net/arp

Here's the code:

/* Obtain mac + IP list */
arplist = read_whole_file("/proc/net/arp");
/* Obtain lease list - we still need the arp list for
   cases where a device uses a static IP rather than DHCP */
leaselist = read_whole_file("/var/lib/misc/dnsmasq.leases");

 

[bluepoint]

You're just using dnsmasq to reserve that IP address so that it isn't used by another device and to assign it a host name on the router.

It's kind of defeating the purpose. Once an IP is reserved no one else will use it, there is no need to assign a static IP not unless the HP printer still crashes when using reservation.

And to the OP, what you're seeing is consistent with my experience. A static assigned client will not show the name whether it's a bug I don't know.

 

[ColinTaylor]

It's kind of defeating the purpose. Once an IP is reserved no one else will use it, there is no need to assign a static IP not unless the HP printer still crashes when using reservation.

But that's the point isn't it. He can't use DHCP because his printer crashes when he does.

So given that he has to statically set it on the printer, it makes sense to also reserve that IP on the router so that no one else gets assigned it. Plus, it tells the router what the printers host name is. Without doing that the routers DNS would not know the printers name.

But, yes you are correct, by preference it is much better to set everything up in DHCP and leave it at that. Unfortunately that's not an option in this case.

 

[dvohwinkel]

But that's the point isn't it. He can't use DHCP because his printer crashes when he does.

So given that he has to statically set it on the printer, it makes sense to also reserve that IP on the router so that no one else gets assigned it. Plus, it tells the router what the printers host name is. Without doing that the routers DNS would not know the printers name.

But, yes you are correct, by preference it is much better to set everything up in DHCP and leave it at that. Unfortunately that's not an option in this case.

Ideally ASUS and HP would work together to figure out why querying for an ip address crashes some of their printers(I never realized you could crash a printer.. I guess that is the beauty of having an LCD touchpad on the front..) and I would use only DHCP in my env.

 

[bluepoint]

But that's the point isn't it. He can't use DHCP because his printer crashes when he does.

His post wasn't clear if reserving IP also crashes the printer. My understanding is, the printer crash when the IP is dynamically assigned. Maybe, the OP can confirm?

 

[dvohwinkel]

His post wasn't clear if reserving IP also crashes the printer. My understanding is, the printer crash when the IP is dynamically assigned. Maybe, the OP can confirm?

Sorry for not being clear. It doesn't matter if the IP address is reserved or not. If the printer has to query the router for it's ip address, I get a crash. The only way around it is to manually set the ip address on the printer so that the printer does not query the router for it. Here is another example of this issue. http://h30434.www3.hp.com/t5/Inkjet...rashes-when-connected-to-network/td-p/4756279

 

[RMerlin]

If you haven't done so yet, disable all non-DHCP methods on your printer (such as BOOTP).

 

[dvohwinkel]

If you haven't done so yet, disable all non-DHCP methods on your printer (such as BOOTP).

I couldn't find where to disable bootp.. but I disabled Bonjour, SNMP, WINS, SLP, LPD, Port 9100 tcp printing, LLMNR, Microsoft Web Services, Syslog, DHCPV4(BOOTP?) and/or DHCPV6, HP Wireless Direct, and AirPrint. I disabled everything that was disable-able. Still the moment I changed the ip address setting from manual to automatic it crashes.