1. 30 Dec, 2014 1 commit
  2. 26 Dec, 2014 3 commits
  3. 18 Dec, 2014 4 commits
  4. 17 Dec, 2014 3 commits
  5. 14 Nov, 2014 1 commit
  6. 03 Nov, 2014 2 commits
  7. 23 Oct, 2014 1 commit
  8. 22 Oct, 2014 1 commit
  9. 21 Oct, 2014 3 commits
  10. 20 Oct, 2014 1 commit
  11. 16 Oct, 2014 1 commit
  12. 09 Oct, 2014 6 commits
  13. 06 Oct, 2014 1 commit
  14. 03 Sep, 2014 1 commit
  15. 02 Sep, 2014 1 commit
  16. 26 Aug, 2014 1 commit
  17. 20 Aug, 2014 1 commit
    • Julien Muchembled's avatar
      Do not fail on unexpected 'route_up' notifications from OpenVPN clients · d7d7b425
      Julien Muchembled authored
      This fixes the following error:
      
        TypeError: unsupported operand type(s) for -: 'NoneType' and 'int'
        Traceback (most recent call last):
          File "/usr/sbin/re6stnet", line 438, in main
            tunnel_manager.handleTunnelEvent(read_pipe.readline())
          File "/usr/lib/python2.7/dist-packages/re6st/tunnel.py", line 389, in handleTunnelEvent
            m(*args)
          File "/usr/lib/python2.7/dist-packages/re6st/tunnel.py", line 412, in _ovpn_route_up
            self._connection_dict[prefix].connected()
          File "/usr/lib/python2.7/dist-packages/re6st/tunnel.py", line 76, in connected
            i = self._retry - 1
      
      What happened is probably that a route_up notification was received just before
      killing/recreating the connection for the same node, and then process twice
      the same OpenVPN notification: in this case, the first was for a previous
      connection and should have been ignored.
      d7d7b425
  18. 31 Jul, 2014 2 commits
  19. 29 Jul, 2014 2 commits
  20. 22 Jul, 2014 1 commit
  21. 18 Jul, 2014 2 commits
  22. 16 Jul, 2014 1 commit