1. 06 May, 2019 1 commit
    • Killian Lufau's avatar
      Remove old fix in ovpn-client · 24fea8cd
      Killian Lufau authored
      The fix to mark an interface as "up" and indicate its MTU was
      useful for machines with a single client, because OpenVPN would fail
      to configure them this way in OpenVPN 2.3. It has been fixed in 2.4
      so the fix has been removed.
      
      /reviewed-on !14
      24fea8cd
  2. 30 Dec, 2015 1 commit
  3. 07 Mar, 2015 1 commit
  4. 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
  5. 20 Nov, 2013 1 commit
  6. 11 Jun, 2013 1 commit
  7. 03 Sep, 2012 1 commit
  8. 31 Jul, 2012 1 commit
  9. 24 Jul, 2012 1 commit
  10. 19 Jul, 2012 1 commit
  11. 17 Jul, 2012 3 commits
  12. 16 Jul, 2012 1 commit