Community discussions

MikroTik App
 
p3ter
just joined
Topic Author
Posts: 19
Joined: Fri Jul 16, 2021 3:17 pm

Why so hard to give friendly name to a client?

Mon Dec 20, 2021 4:52 pm

In most Routers/Firewalls/HotSpots I have used, there is some very simple & consistent method of giving a friendly/memorable name to a client, which is used throughout the interface. Usually it works by treating the 'Hostname' field as a multi-purpose field that would contain in the worst case a Mac Address (if the client does not set a host name), otherwise the HostName , but where the field contents can be overwritten with a friendly name identifying the host in a language I understand a little better than hexadecimal...

As a RouterOS newbie I really struggle with the lack of a consistent approach to this - for example in DHCP Server I can add a 'Comment' to give a friendly name to a client, but that comment remains local to only the DHCP window - if I navigte to 'Kid Control' I lose my DHCP assigned comment, but here, (in Kid Control) instead of 'Active Hostname' I have 'Name' - and here I can override that name into a friendly name (which will not appear anywhere else in RouterOS...)

If I open My Mikrotik Home app and navigate to 'Clients', I see a MAC address if the client did not supply a Hostname - and again here I need to navigate to 'Edit device Details', and rename the device with my friendly name...

Open Dude Server... Here we go again - no friendly name, and another need to rename the client.

...and so on... I actually found myself writing down MAC addresses with a pen and paper... and I can barely read my own writing...

If RouterOS can't be consistent about this, at least it would be helpful if 'DCHP Client Comment' could be 'Global' - and an available column anywhere I see the MAC address assoicated with that client, seen EVERYWHERE in all RouterOS windows, apps etc.
 
holvoetn
Forum Guru
Forum Guru
Posts: 5321
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: Why so hard to give friendly name to a client?

Mon Dec 20, 2021 4:58 pm

Your DNS server is responsible for providing that name, I would think ?
IP / DNS / Static would be the place to look IF your router is also acting as your DNS server.
 
tdw
Forum Guru
Forum Guru
Posts: 1841
Joined: Sat May 05, 2018 11:55 am

Re: Why so hard to give friendly name to a client?

Mon Dec 20, 2021 5:13 pm

DNS only applies to IP, there is no equivalent database/mapping for name to MAC address.

The hostname which appears in the DHCP server leases list is provided by the client in the DHCP request, so may be anything and is not guaranteed to be unique.
 
kalamaja
Member Candidate
Member Candidate
Posts: 112
Joined: Wed May 23, 2018 3:13 pm

Re: Why so hard to give friendly name to a client?

Mon Dec 20, 2021 5:35 pm

With iOS15 came the Private Wi-Fi Address feature that uses different MAC-address for every Wi-Fi network, AND also doesn't send device's name to DHCP-server anymore. So. it's much harder now to keep eye on new devices in DHCP-Server -> Leases. And if you switch off Private Wi-Fi Address feature in Settings -> Wi-Fi -> networkname (to see device's name again in DHCP-server), then this network will have a text "Privacy Warning" under the network's name in Wi-Fi netoworks list. User won't like it and will switchi Private Wi-Fi Address on again.
 
p3ter
just joined
Topic Author
Posts: 19
Joined: Fri Jul 16, 2021 3:17 pm

Re: Why so hard to give friendly name to a client?

Mon Dec 20, 2021 6:49 pm

Thanks, but none of those responses really get close to the core issue. This is a home network but with many (60+) Devices. All mobile devices have been set to use hardware MAC, and all devices have Static DCHP Leases. I have even gone one step further, with a script that sends me an Email every time an unknown device receives an IP Address: (DHCP Server -> DHCP -> Scripts)
# Based on https://forum.mikrotik.com/viewtopic.php?t=153641

:local recipient "email@address.com"
/ip dhcp-server lease
:if (($leaseBound=1) && ([/ip dhcp-server lease find where dynamic mac-address=$leaseActMAC]!="")) do {
	:do {
		:tool e-mail send to=$recipient subject="DHCP Address Alert [MAC: $leaseActMAC]" body="The following device received an Dynamic IP address:
		Mac: $leaseActMAC
		Ip: $leaseActIP,
		Host: $lease-hostname,
		Bound: $leaseBound"
		:log info "Sent Dynamic IP alert for MAC $leaseActMAC, $leaseActIP, $lease-hostname"
	} on-error={:log error "Failed to send alert email to $recipient"}
}}
...so I have very good control over what is on my network, and I have added a 'Comment' identifying each device - but the only place I can make use of that comment is on the 'DHCP Server' -> 'Leases' Tab. Anywhere else, and I am back to the lottery of IP Addresses, MAC Addresses, & Host Names (if the device was kind enough to provide a host name) I have no way to reliably see the clients with a 'friendly name' across the entire Mikrotik experience. There are different methods per app and per window to 'name' a client - and none of those methods are consistently used across the various interfaces.

Compare that for example to my TP Link Omada Controller - I simply click 'Name' (A name which has been derived from the client Host Name if supplied, or the MAC Address) then rename it to whatever I want. Now that friendly name is seen wherever I see that client across the entire interface, alongside MAC Address and IP Address.

I do not believe there is currently any RouterOS equivalent method of giving a client a 'friendly name' that is used globally across all windows and apps.
 
User avatar
Amm0
Forum Guru
Forum Guru
Posts: 3169
Joined: Sun May 01, 2016 7:12 pm
Location: California

Re: Why so hard to give friendly name to a client?

Mon Dec 20, 2021 7:17 pm

Thanks, but none of those responses really get close to the core issue. This is a home network but with many (60+) Devices. All mobile devices have been set to use hardware MAC, and all devices have Static DCHP Leases. I have even gone one step further, with a script that sends me an Email every time an unknown device receives an IP Address: (DHCP Server -> DHCP -> Scripts)

I do not believe there is currently any RouterOS equivalent method of giving a client a 'friendly name' that is used globally across all windows and apps.
I'd imagine not, but several workarounds.

Since you have static DHCP lease entries, you can use the "address-list" option as the unique name field. It populate IP>Firewall>Address List with the same with IP address (but no MAC there)., but you'd have at least a list of names (and then use those names in firewall rules to restrict to the user level using a friendly name). The "Address List" can be used as column in winbox to proximate a name. Only side-effect is you have a few unused Address Lists in IP>Firewall>AddressLists.

Alternatively you could try new User Manager in V7 at somepoint, and then use RADIUS to auth your users. A bit overkill for a typical home, but your whitelisting your clients already, 60 devices, etc... That give you even more ability to set a "name", and likely add another measure of control.
 
p3ter
just joined
Topic Author
Posts: 19
Joined: Fri Jul 16, 2021 3:17 pm

Re: Why so hard to give friendly name to a client?

Tue Dec 21, 2021 11:01 am

DNS only applies to IP, there is no equivalent database/mapping for name to MAC address.
This is what I am looking for - a global 'MAC address --> friendly name' label that can be seen wherever that MAC Address is displayed.

Since you have static DHCP lease entries, you can use the "address-list" option as the unique name field.
Thanks - this is useful, I have added the 'Address List' column to DHCP Server, but guess what, you can't add it anywhere else, like Kid Control, Mikrotik Home App, and it is not visible in log entries, etc. I guess there is simply an acceptance in the RouterOS community that you must take multiple additional steps to translate an IP Address / MAC Address back into an understandable "Johns Mobile" or "The PC in the Conference Room"

Alternatively you could try new User Manager in V7 at somepoint, and then use RADIUS to auth your users. A bit overkill for a typical home, but your whitelisting your clients already, 60 devices, etc... That give you even more ability to set a "name", and likely add another measure of control.
But would that name be visible everywhere I see the corresponding IP/MAC? I suspect not...
 
D892220
just joined
Posts: 1
Joined: Mon May 16, 2022 8:19 pm

Re: Why so hard to give friendly name to a client?

Thu May 19, 2022 2:14 pm

Fully agree

As i am a newbie it took for me at least an hour to figure out which MAC address / IP i need to block under KID control. Generally since i have like 20 devices connected it is difficult to track under different Router OS functions (DHCP Pool,etc.) the devices as there is no global "friendly name" possibility to add. And what seemed to be strange that i.e mobile phone internal MAC address after connecting to router was getting a different MAC... my only option to recognize what is what was to switch OFF/ON devices and look for what disappears/pops up in the list of connected devices.

Hope to have this centralized in some future update.
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 11967
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: Why so hard to give friendly name to a client?

Thu May 19, 2022 2:43 pm

[...] And what seemed to be strange that i.e mobile phone internal MAC address after connecting to router was getting a different MAC... [...]
No, this is exactly how things are designed to work.
It does not depend on MikroTik.
 
User avatar
anav
Forum Guru
Forum Guru
Posts: 18958
Joined: Sun Feb 18, 2018 11:28 pm
Location: Nova Scotia, Canada
Contact:

Re: Why so hard to give friendly name to a client?

Thu May 19, 2022 3:05 pm

Excellent request, I submitted it as an idea for consideration at the MT support site.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: Why so hard to give friendly name to a client?

Thu May 19, 2022 4:16 pm

It is true that MikroTik is a bit lacking in this, in other home routers there is an integration between DHCP and DNS, so any device getting an address via DHCP will automatically get a DNS forward and reverse entry with e.g. the name hostname.local (when you are lucky you can configure the .local part to something else).
It is possible to do this with MikroTik routers, but it requires scripting. And that is a bit hard to do for the newbie user, unless they can find some good-quality ready-made script to do it.
It could be a solution when MikroTik provides ready scripts for such purposes so you only need to connect them to the DHCP service.

Also, some home routers have an internal MAC address to name table, not as a DNS service, but as part of the DHCP service (similar to DHCP static entries in RouterOS) and refer to devices under this name everwhere in the user interface. RouterOS does not offer that, and it is hard to add that using scripts as you cannot add a custom column to data tables. It would have to be done via comments, and dynamic entries (like Kid Control devices that have been automatically found) cannot have comments.
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 11967
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: Why so hard to give friendly name to a client?

Thu May 19, 2022 6:31 pm

Someone should be asked to (re)do this script... :roll:

Joke apart, is impossible to have it: empty hosts or duplicate names...
Real examples of duplicate device names among different MAC:
Redmi7A-Redmi-A
Galaxy-A6
Galaxy-A3-2017
C530-IP
and other problems...
like number at the start:
16173WL82191696
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: Why so hard to give friendly name to a client?

Thu May 19, 2022 8:58 pm

It is not guaranteed that the name is unique (e.g. you may have multiple Galaxy-A6 names) but it can be solved by adding some suffix when it is a duplicate.
At least when you see a Galaxy-A6 and a Galaxy-A6-97-8a-03 (say those are the last 3 bytes of the MAC) you know that these are the kids' telephones, and you do not have to look at all the other devices when you want to restrict them.
And as said, some other home routers do have this. It isn't impossible.

One could claim that MikroTik isn't a home router, and in the past that was true, but several recent additions (both the RouterOS and the product line) show that MikroTik's intention is to take a part of that market.
So it could be useful to add this kind of features.

But first fix BGP!
 
User avatar
anav
Forum Guru
Forum Guru
Posts: 18958
Joined: Sun Feb 18, 2018 11:28 pm
Location: Nova Scotia, Canada
Contact:

Re: Why so hard to give friendly name to a client?

Thu May 19, 2022 9:21 pm

BGP, boring geek problem? Big Giant Pita?
I like the idea of the name thingy first LOL......
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 11967
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: Why so hard to give friendly name to a client?

Thu May 19, 2022 9:34 pm

BGP
Best Gateway Protocol :lol:
 
kevinds
Long time Member
Long time Member
Posts: 575
Joined: Wed Jan 14, 2015 8:41 am

Re: Why so hard to give friendly name to a client?

Mon May 23, 2022 9:05 pm

In most Routers/Firewalls/HotSpots I have used, there is some very simple & consistent method of giving a friendly/memorable name to a client,

As a RouterOS newbie I really struggle with the lack of a consistent approach to this - for example in DHCP Server I can add a 'Comment' to give a friendly name to a client, but that comment remains local to only the DHCP window - if I navigte to 'Kid Control' I lose my DHCP assigned comment, but here, (in Kid Control) instead of 'Active Hostname' I have 'Name' - and here I can override that name into a friendly name (which will not appear anywhere else in RouterOS...)

If I open My Mikrotik Home app and navigate to 'Clients', I see a MAC address if the client did not supply a Hostname - and again here I need to navigate to 'Edit device Details', and rename the device with my friendly name...

Open Dude Server... Here we go again - no friendly name, and another need to rename the client.
Isn't the answer to this to set the Hostname on the client?

"Active Hostname" means the hostname that the client is announcing for itself.

Kid Control is based on MAC address for a reason, everything else is just 'fluff' to help you see things a bit easier..

If you need to write your hostname and MAC address down to keep track of them, arrange your Winbox windows to keep your DHCP server comments visible or just copy and paste into notepad..
 
User avatar
anav
Forum Guru
Forum Guru
Posts: 18958
Joined: Sun Feb 18, 2018 11:28 pm
Location: Nova Scotia, Canada
Contact:

Re: Why so hard to give friendly name to a client?

Mon May 23, 2022 10:33 pm

since when does one have control over hostname? The admin has control over the router only, not the settings on the devices.
 
User avatar
k6ccc
Forum Guru
Forum Guru
Posts: 1490
Joined: Fri May 13, 2016 12:01 am
Location: Glendora, CA, USA (near Los Angeles)
Contact:

Re: Why so hard to give friendly name to a client?

Mon May 23, 2022 10:39 pm

Isn't the answer to this to set the Hostname on the client?
Except that for many devices, you have no control over that - Especially IoT devices. For example:
Of my five Amazon Echo devices, one shows a Host Name of "amazon-" followed by 9 hex digits that are not the MAC. The other four have no Host Name.
Of my four Techin outlets, they all have a Host Name of "ESP_" followed by the last 6 digits of the MAC.
Of my four Wyze outdoor switches, all four have a Host Name of "Wyze Outdoor Plug"
Of my 14 currently connected Wyze V2 cameras, none have a Host Name
Of my 13 currently connected Wyze V3 cameras, all have a Host Name of "WyzeCam"
My Garmin GPS has a Host Name of "rogue"
My one window air conditioner that has WiFi does not show a Host Name.

Most of the computers, and phones have a Host Name that reflects what is configured in the device.
This is all reported on the DHCP server leases listing of my RB4011 router.
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 11967
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: Why so hard to give friendly name to a client?

Mon May 23, 2022 10:43 pm

My Garmin GPS has a Host Name of "rogue"
Oh.......
My Garmin DriveSmart76 is called.... "koala"!!! :shock:
 
User avatar
k6ccc
Forum Guru
Forum Guru
Posts: 1490
Joined: Fri May 13, 2016 12:01 am
Location: Glendora, CA, USA (near Los Angeles)
Contact:

Re: Why so hard to give friendly name to a client?

Mon May 23, 2022 10:57 pm

My Garmin GPS has a Host Name of "rogue"
Oh.......
My Garmin DriveSmart76 is called.... "koala"!!! :shock:
Mine is a DriveSmart65. I do like the GPS and the ability to update it via WiFi. It's fast enough that by the time I back into driveway, the GPS has connected to the WiFi, connected to my NTP server (not sure why a GPS needs to check in with an NTP server), and it has checked in with the Garmin servers to determine if there is an update.
 
kraal
Member Candidate
Member Candidate
Posts: 142
Joined: Tue Jan 19, 2021 10:24 pm

Re: Why so hard to give friendly name to a client?

Mon May 23, 2022 10:58 pm

Isn't the answer to this to set the Hostname on the client?

Well if you can tell me how to do it:
  • on Android devices (for instance phones, tv boxes, media players) or other devices which ignore the hostname for DHCP I'll be happy to apply your solution.
  • on devices we are not managing

Even on a small scale where I can manage the hostname by myself I'm facing issues: the hostname is set on most of the devices at home, what I see in DHCP leases is what the device producer wants me to see, not what I need... For instance, to only name a few:

  • All Huawei phones have an "active hostname" such as: HUAWEI_<model>-<uid>
  • TVBox: android-<uid>
  • Media player: android-<uid>
  • TP-Link AP: <manually_set_hostname>-<MAC address>

And there is no way to change this...
So "no", "setting the hostname" doesn't always work.
That's why other tools allow to add a system-wide friendly name (for instance Omada SDN Controller).

Would it be intersting to be able to have system-wide device identifiers (for instance friendly names for MAC address) ? definitively yes.
Would it be intersting to be able to use them everywhere (including logs) ? definitively yes.
Would it help with readability and analysis ? definitively yes.
Would it help with productivity ? definitively yes
Could it be replaced with a "notepad approach" ? to some extent yes
Would itbe as efficient ? definitively not...

RouterOS does not allow to do it for some reason I am not aware of.
My feeling is that it is due to the fact that RouterOS is built on top of a patchwork of tools/libs and that Mikrotik can't add such a feature easily. (for instance iptables for the firewall, how can they modify logs without modifying iptables' source code ?)
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: Why so hard to give friendly name to a client?

Tue May 24, 2022 11:10 am

Well if you can tell me how to do it:
  • on Android devices (for instance phones, tv boxes, media players) or other devices which ignore the hostname for DHCP I'll be happy to apply your solution.
On many Android devices you cannot set it, but on phones of the past ~7 years you can actually set the device name in the settings menu.
E.g. on Samsung phones the device type is in that field (like "Galaxy A41") but you can edit it, and it will be used as the DHCP hostname (with spaces substituted by dashes).

But indeed, it is often not possible.
Actually, when you have a static DHCP entry and set the hostname in there, the device would normally copy that into its hostname.
But that is not so useful when you do not have the information to begin with.

But it isn't what the question initially was about anyway. What RouterOS lacks is a convenient mechanism to keep track of MAC addresses (and IP addresses) throughout the router configuration. That could be placed on the feature request list, at some appropriate priority.
 
User avatar
Amm0
Forum Guru
Forum Guru
Posts: 3169
Joined: Sun May 01, 2016 7:12 pm
Location: California

Re: Why so hard to give friendly name to a client?

Fri May 27, 2022 5:24 pm

But it isn't what the question initially was about anyway. What RouterOS lacks is a convenient mechanism to keep track of MAC addresses (and IP addresses) throughout the router configuration. That could be placed on the feature request list, at some appropriate priority.
Totally agree. The OP wasn't wrong. A "client" manifest itself in a lot of places: Wi-Fi registration, DHCP lease, ARP cache, L2 firewall, VPN interfaces, etc., etc. But there isn't a good view "all connect devices" & certainly no way to "name" them. While creating static DHCP reservations can help with a device name, problem that device name doesn't appear elsewhere. And, yeah a lot of ISP routers have a "device list" with a edit button for a name, so OP's request isn't crazy.

Even some "tooltips" in Winbox that "resolved" a MAC address to the DHCP name be useful, similar to how hostname sometimes shows up as yellow box when hovering on IP address.
 
p3ter
just joined
Topic Author
Posts: 19
Joined: Fri Jul 16, 2021 3:17 pm

Re: Why so hard to give friendly name to a client?

Sat May 28, 2022 12:14 am

In RouterOS it seems that if a DHCP client supplies a hostname ('RFC 2131 "sname" (Server host name)), then 'Active Host Name' = sname, but if the client does not supply sname, then Active Host Name' = NULL. All we need is to treat 'Active Host Name' as a User editable field, and additionally treat it's display contents with a ranking (so it is never null), like:
  1. If Active Hostname not set manually and sname = NULL then Active Host Name = MAC Address
  2. If Active Hostname not set manually and sname NOT NULL then Active Host Name = sname
  3. If Active Hostname set manually then Active Host Name = user defined hostname.
...then use this Active Host Name consistently anywhere a client MAC Address can be seen...
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: Why so hard to give friendly name to a client?

Sat May 28, 2022 10:13 am

Yes, that would be part of the solution. Additionally, something must be done to make that selected hostname always unique (so when more than one host on the network has the same name, something unique is appended to it).
Also in routers that do this it is customary to put these hostnames in DNS under some .local zone, and to do that the hostname sometimes has to be edited (e.g. because it contains spaces).
When this is done for DNS, it is better when that same edited hostname appears everywhere.
All in all, it is not a trivial operation. But it can be done.

In some other home routers, the unique identifier of a host is the MAC address, and this can then also be used in firewall rules. So when you want to allow some traffic to/from a particular host, or to "forward a port" to some host, you can reference that host by its MAC address (which is what you effectively do when you select it from the list of locally known hosts), and the proper firewall rule is made with the actual IP address of that host.
In RouterOS you need to make the DHCP entry fixed and then you can either use that fixed address or link it to an address list, but it is a more involved operation.
 
User avatar
thanpolas
just joined
Posts: 13
Joined: Wed May 11, 2022 9:22 pm
Location: Greece
Contact:

Re: Why so hard to give friendly name to a client?

Tue Sep 20, 2022 10:51 am

Fully agree with the OPs sentiment.

I need a sensible way to label, tag, track and manage the clients of my network.

It's just too laborious to have to work through and hack it with the means available by Mikrotik OS.

This feature is badly needed, will immensely improve QoL, security and UX.
 
poseo9wsw
newbie
Posts: 48
Joined: Thu Feb 02, 2023 6:41 pm

Re: Why so hard to give friendly name to a client?

Sun Feb 12, 2023 11:48 pm

I found this thread looking for a fix... I am also surprised there is not one. The "Active Host Name" should either:

Be editable

Or

Provide a column the user can edit themselves

I'm a home gamer new to this, but there surely is a way around this isn't there? The suggestions so far are not so appealing.

I need a simple way to LABEL everything on my network. Asking this to be a client job is impossible. You can't expect the client to provide this every time, so intervention is necessary.
 
irfan44
just joined
Posts: 21
Joined: Fri Apr 07, 2023 6:26 pm

Re: Why so hard to give friendly name to a client?

Sat Apr 22, 2023 4:01 pm

I am also in a fix due to in-editable host names. Its a disaster referring to the list everytime you have to find a particular client.
ROS must include in future updates as an option if a lazy person like me wants to use it.
 
User avatar
pothi
newbie
Posts: 46
Joined: Fri Sep 14, 2018 7:48 pm
Location: Srivilliputhur, Tamil Nadu, India
Contact:

Re: Why so hard to give friendly name to a client?

Sat Jul 15, 2023 2:01 pm

+1 for a friendly name that can be used across Router OS.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: Why so hard to give friendly name to a client?

Sat Jul 15, 2023 4:03 pm

Well it seems that work is progressing a little on this. E.g. now you can see the hostname and connection port in the ARP table (and DHCP leases).

It is also possible to assign an address list to a static DHCP entry and it will put the assigned address in the address list, e.g. for use in the firewall.
But there is still a lot that could be improved.
 
Rox169
Member
Member
Posts: 432
Joined: Sat Sep 04, 2021 1:47 am

Re: Why so hard to give friendly name to a client?

Sat Jul 15, 2023 4:58 pm

+1 for a friendly name that can be used across Router OS
 
User avatar
SecOps7
just joined
Posts: 2
Joined: Tue Feb 14, 2023 4:07 pm

Re: Why so hard to give friendly name to a client?

Tue Nov 14, 2023 1:49 pm

+1 for custom DHCP host names. :D
 
User avatar
woland
Member Candidate
Member Candidate
Posts: 258
Joined: Mon Aug 16, 2021 4:49 pm

Re: Why so hard to give friendly name to a client?

Tue Nov 14, 2023 4:19 pm

+1 makes life easier + other vendors have it already
 
frengo
just joined
Posts: 20
Joined: Fri Jan 20, 2023 12:17 pm

Re: Why so hard to give friendly name to a client?

Mon Jan 22, 2024 9:16 pm

Well it seems that work is progressing a little on this. E.g. now you can see the hostname and connection port in the ARP table (and DHCP leases).

It is also possible to assign an address list to a static DHCP entry and it will put the assigned address in the address list, e.g. for use in the firewall.
But there is still a lot that could be improved.
Any news on the topic? Does the aforementioned message make it clear that a non-expert user like me could finally name the various connected clients?
If so, what is the procedure in detail?

Thanks in advance
 
pe1chl
Forum Guru
Forum Guru
Posts: 10183
Joined: Mon Jun 08, 2015 12:09 pm

Re: Why so hard to give friendly name to a client?

Mon Jan 22, 2024 9:35 pm

I don't think there is further progress than what is written above...

Who is online

Users browsing this forum: Bing [Bot], robertkjonesjr, UkRainUa and 45 guests