Duet 2 Wifi, DHCP / DNS questions

Ernst Blofeld

I have two printers here with Duet 2 Wifi controllers. The router they are connecting to (an Orange France Flybox 4G router) is very limited, with no way to reserve DHCP IP addresses and no way to add entries to its local DNS server.

When the printers connect to the network they show up in the router's admin with blank IP addresses and their hostnames set to their MAC addresses. nmap from a linux machine on the same network shows the MAC address where the hostname should appear. Other devices connected to the network, such as the linux machine and an Android tablet show up correctly.

I can connect to the machines through the IP addresses that nmap discovers, but not through their names, presumably because the names are getting lost somewhere. Both printers have an M550 P"name" as the first line in their config.g.

Any ideas on how I can get these printers properly onto the network?

jay_s_uk

You could configure them with a static IP address using M552.
Make sure this is out of the range assigned by DHCP

Ernst Blofeld

I'm going to try that as an interim solution so I can at least find them without jumping through hoops, but any idea what could have happened to their names?

Veti

@Ernst-Blofeld said in Duet 2 Wifi, DHCP / DNS questions:

Orange France Flybox 4G router

this seems to be a tp-link mr200.

you can install openwrt on it and it becomes a powerful router.

https://openwrt.org/toh/tp-link/archer-mr200

Ernst Blofeld

@Veti said in Duet 2 Wifi, DHCP / DNS questions:

@Ernst-Blofeld said in Duet 2 Wifi, DHCP / DNS questions:

Orange France Flybox 4G router

this seems to be a tp-link mr200.

you can install openwrt on it and it becomes a powerful router.

https://openwrt.org/toh/tp-link/archer-mr200

Unfortunately it's not mine to do that to.

Ernst Blofeld

@jay_s_uk said in Duet 2 Wifi, DHCP / DNS questions:

You could configure them with a static IP address using M552.
Make sure this is out of the range assigned by DHCP

I have now done this using M587 in a macro to set the IP address. I might not be able to refer to them by name, but at least I can find them.

whosrdaddy

@Ernst-Blofeld You can always add the names to the hosts file of your local computer (assuming it's windows 10)

Ernst Blofeld

@whosrdaddy said in Duet 2 Wifi, DHCP / DNS questions:

@Ernst-Blofeld You can always add the names to the hosts file of your local computer (assuming it's windows 10)

Sure, but I'd prefer to know what I've done wrong - I must have done something wrong because every other device that is connected to this network works correctly.

whosrdaddy

well the Duet board supports mDns according to this page but it would be better if it would have DNS support built-in (ie register with an existing DNS server).
Did you try accessing the printer with it's mDNS name (ie <yourprintername>.local)?

Ernst Blofeld

@whosrdaddy said in Duet 2 Wifi, DHCP / DNS questions:

well the Duet board supports mDns according to this page but it would be better if it would have DNS support built-in (ie register with an existing DNS server).
Did you try accessing the printer with it's mDNS name (ie <yourprintername>.local)?

mDNS isn't supported by my Android tablet or the Linux version I'm running at the moment, but both of those machines manage to tell the router what their names are, so either I really don't know what I'm talking about, or something is missing or broken.

whosrdaddy

The problem is that the Duet has no real DNS support other than mDNS.
Did you know that there's an app for Android to discover Duets on the network?

Ernst Blofeld

@whosrdaddy said in Duet 2 Wifi, DHCP / DNS questions:

The problem is that the Duet has no real DNS support other than mDNS.

Is this a hardware limitation or something that could be fixed in a firmware update?

A Former User

@whosrdaddy said in Duet 2 Wifi, DHCP / DNS questions:

it would be better if it would have DNS support built-in (ie register with an existing DNS server).

That is usually the job of the DHCP server, not the DHCP client; but it does seem the Duets does not send the M550 name as part of the DHCP request, so that could be an improvement - however it would still be up to the DHCP server to register with a DNS server.