There is no event-driven script associated with a wireless client connecting to the router. The best you can do is create a process that continuously pings/scans/polls the device until it becomes active.
It sounds like it would go into an infinite boot loop anyway if the client couldn't connect (e.g. was turned off, damaged or removed).I can't do that because my script is for restarting the router if it doesn't connect with the wireless client so a ping condition will put it in an infinite loop.
It sounds like it would go into an infinite boot loop anyway if the client couldn't connect (e.g. was turned off, damaged or removed).
What is the objective here? What is the interaction between the router and the smart plug that requires you to reboot the router? Can you not just restart the wireless instead?Yes, there's still a risk for that but the wireless client is a Smart Plug switched on 24/7/365 so there's almost a zero chance that the client will turn off.
What is the objective here?
Could you not exploit the dnsmasqHey guys I want to run a scripts AFTER a wireless client is connected to the router on reboot so what user script will be appropriate for it? I tested with wan-start but it seems it runs way too early.
dhcp-script=
Could you not exploit the dnsmasq
so you could detect @boot the fact that a specifc MAC has been assigned an IP address?Code:dhcp-script=
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!