router side ifplugd

I was curious if anyone at Mikrotik has contemplated something like a router side ifplugd.

Basic theory of operation would go something like this: using the same kind daemon that runs ifplugd on clients, a router could be configured to monitor port media state changes. When a media state (link) was established the configuration for that ethernet port could be pulled from a central location (user manager?) with detailed configuration scripting.

Ideally, I would like to build simple 2 IP address subnets for designated ethernet ports that are only configured (or possibly enabled) when a user plugs in a device that brings the port up to a valid link established state. In my ideal scenario, the routing for this address space would depend payment status (route to a captive portal explaining how to pay in the event of no payment for the port or route to teh intrahwebs in the event that payment has been made for the port)

I’d also like to be able to configure the ports in bridges or modest subnets involving various configurations of one to many NAT, one to one NAT, static IP address and/or have DHCP service configured and running on the port.

so, what’s problem with DHCP?..

so, what’s problem with DHCP?..

DHCP doesn’t allow for the router side configuration of the port.

Specifically, there are things I want to do to the port and to the routing upon link establishment.

Plus, I’m just curious why ifplugd hasn’t been extended to the non-client side of the network equation (but I realize that both Router OS and linux are slow to add client oriented network features into embedded network equipment)

ifplugd offers some potentially powerful features to network configuration that would overcome some of the Router OS “scripting” limitations that are a direct consequence of not having full shell and system access.

routing? you can redistribute routes and default gw via DHCP. port? what you want to do to the port? O_o

Perhaps I was just being polite.

The primary reason I want a router side ifplugd is because Mirkotik’s hotspot implementation blows.