banIP starts too early during boot – how to delay until WAN is ready?

[Geri_S]

During boot, banIP tries to start before eth0 (WAN) is ready. Unfortunately, it remains disabled until I start it manually.

Is there a way to configure banIP so that it automatically starts as soon as the WAN is ready?

[frollic]

Restart it in /etc/rc.local, perhaps add a sleep 60 too ?

Or create a hotplug script: https://openwrt.org/docs/guide-user/base-system/hotplug#iface

[rexbinary]

Verify that 'Reload Trigger Interface' is set to 'WAN'. Also, you can add a Trigger Delay if needed. These are both under General Settings if using luci.

[Geri_S]

Thank you all!

I really appreciate your help and the useful suggestions. The reload trigger for wan was exactly what I needed!

[timur.davletshin]

I had the same problem. But my problem was with WAN6 which takes 2-4 second longer than WAN to bring up. Occasionally I had problems loading lists (banip reload is very fast, about 5-6 seconds for me) when WAN6 wasn't ready yet. So I used WAN6 as a trigger but later I decided to keep WAN as a trigger and add 15 seconds delay. So far so good.