You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed when I run inn fetch <interface> that communication between the two associated peers doesn't work until I run inn fetch <interface> on both peers. That's a little cumbersome and would be nice to handle that automatically via the innernet-server.
The text was updated successfully, but these errors were encountered:
Unfortunately there's no way to remotely trigger an inn fetch on other peers from the server, since there's no push mechanism (clients poll the server, by default, every 60 seconds). You can always override the frequency with systemctl edit though, we do that often.
I'm going to rename this issue to "Add server push functionality" since I think that's what you're asking for here, where clients would establish a long-running connection with the server and receive pushed state updates instead of polling for them.
mcginty
changed the title
Adding association should run inn fetch on affected endpoints
Add server push functionality
Apr 16, 2021
I've noticed when I run
inn fetch <interface>
that communication between the two associated peers doesn't work until I runinn fetch <interface>
on both peers. That's a little cumbersome and would be nice to handle that automatically via theinnernet-server
.The text was updated successfully, but these errors were encountered: