| Age | Commit message (Collapse) | Author |
|---|
|
Replace logging.getLogger with custom get_logger.
Remove some unneeded dependencies and reorder other.
|
|
Before this commit, the backend used plain pyzmq bindings for communicating
with the frontend. This implements the txzmq twisted-powered bindings instead.
Closes: #6360
|
|
|
|
... on them, to user-writeable only.
I think we could consider ipc for the curve-case too, at least for the
platforms that support them.
|
|
Use global flag for ZMQ_HAS_CURVE.
Closes #6646
|
|
|
|
Fix typo for signal disconnection.
The backend is the one who always creates the certificates. Either if it
is run separately or in a process in the same app as the frontend.
|
|
Add the 'check_online' method to check whether the backend is accessible
or not.
Reduce the wait for running threads timeout on quit.
Add retry feature to the backend requests send.
|
|
Closes: #4035
This falls in the "quick" workaround category.
A proper state machine that extends the four basic connection states
is hence needed. We have to accomodate design to have a
connection-oriented state machine in the backend (I would favor a
twisted protocol for this), and a more lightweight one that conducts
the gui-level changes (ie, change the actions / buttons / labels
accordingly).
Since this "cancel" functionality has been long postponed, I chose
to do one more ugly hack here, that is, show and hide dance with a
button that just calls the bitmask-root to kill the vpn process. It
should work well enough until we get to the reorganization needed for a
clean process control for eip.
|
|
Send a 'ping' request every 2 secs to ensure that the backend is
running.
Use polling instead of recv on the backend_proxy. This was already
implemented for the signaler.
|
|
|
|
|
|
|
|
|
