Hi, i have a hot spot setup that redirects to an external page redirected by login.html. There are a lot of valuable variables i can use to pass to my external page, but the one i am missing is the MAC of the router. I want to use this to identify the client. Currently I set the identity of the router to the MAC and pas Nasid (routers are assigned to clients by MAC) , but I was hoping there was another way.
why not use server’s IP address (“server-address” variable) instead of MAC address? if you replace the router, IP address won’t change, but MAC address will
Because I don’t know what that is until its shipped out and the customer plugs it in. I need something known when its shipped. If I have to replace the router, I can add the new MAC to their client profile before its shipped.
Hi, My hotspot is on an external website. Here are the form variables i am passing, including MAC. However, the value of mac is the connecting device, not the MAC of the router.
Thew wiki clearly states “MAC ADDRESS OF THE USER” not the router.
Air Stream Wireless

I completely get the fact that your hotspots are redirecting to a central website - and I completely understand that the $(mac) variable implies the hotspot client, not the hotspot server.
My original suggestion to use this variable was under the mistaken assumption that your hotspot service (like the walled garden website that you redirect everyone to) was running on a central hotspot server, thus the clients’ routers WOULD be the client MAC that connects to the hotspot.
Since you want the MAC of the hotspot host itself, then I deduced that you’re running hotspot service on every customer’s individual router, and from there, redirecting to the centralized walled garden login page, which must eventually redirect back to the login html on the local router to complete the login… or however it works. It doesn’t matter to this discussion.
You’re right that $(mac) means the hotspot client. I was simply agreeing that since I had misunderstood your topology, you cannot use $(mac)
Using the system id is probably the best solution available to you. If you want to template that part as well, then you could make your standard template configuration include a script scheduled to run at boot time which searches for the MAC address of the particular interface, and sets the system ID to be the same.