/etc/init.d/network restart required after manually setup of wireguard

I use wireguard across other OS and so have a custom setup script to do things like redundant DNS resolution of the server endpoint.

After running my script the wireguard tunnel is estabilished but I cant ping the endpoints.

I assume it's the firewall, since without making any change to any /etc/config/* files, but just by issuing a /etc/init.d/network restart, wireguard becomes fully functional.

Same if I execute /sbin/netifd. (while it is already running, yes).

What changes can this be doing? I was unable to see any differences with iptables -L or fw3 print.


A compare of the before and after snapshot of the firewall will answer your question.
The problem with connectivity could also have to do with improper routing, which gets fixed after you restart the network service.

Yes, that's exactly what I want to do. I just don't know how. How can i check routing beside "ip route" and firewall beside with iptables or fw3?

iptables-save or ip6tables-save for the firewall and ip -4 ro li tab all ip -6 ro li tab all