- 27 Dec, 2019 3 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
This feature was mainly for laptops but users: - often don't care having the daemon running all the time; - may not want to use the 'main-interface' option because the interface that provides internet access is not always the same, e.g. wifi & wired; - may want other kinds of conditions, e.g. only specific wifi access points. So in practice, main-interface is currently only use to set up a DHCP server or provide IPv6 autoconfiguration. For such case, it is preferred to start/stop re6stnet like a normal service.
-
Julien Muchembled authored
-
- 11 Dec, 2019 2 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
-
- 08 Nov, 2019 1 commit
-
-
Julien Muchembled authored
This should fix strange bugs after running the demo for a long time, with certificate renewal happening every few minutes.
-
- 07 Nov, 2019 1 commit
-
-
Julien Muchembled authored
The previous commit, which adds --ipv6, has the issue that it does not check whether given IPs are valid. Since IPv4 & IPv6 use completely different address representation, --ip can be used for both.
-
- 06 Nov, 2019 1 commit
-
-
Julien Muchembled authored
When re6st attempts to use UPnP and IPv6 is enabled at the same time, the external IPv4 was published for IPv6 protocols. For example, machine6 in the demo had: 10.0.1.3,1194,tcp;10.0.1.3,1194,udp;10.0.1.3,1195,udp6 This caused re6stnet to crash (socket.gaierror) if GEOIP2_MMDB is set. With this commit, IPv4 & IPv6 are now processed independently.
-
- 31 Oct, 2019 2 commits
-
-
Killian Lufau authored
-
Julien Muchembled authored
-
- 22 Oct, 2019 1 commit
-
-
Julien Muchembled authored
/reviewed-on nexedi/re6stnet!21
-
- 04 Jul, 2019 1 commit
-
-
Killian Lufau authored
/reviewed-on nexedi/re6stnet!19
-
- 03 Jul, 2019 1 commit
-
-
Killian Lufau authored
The detection of the attribute `_private` was performed on a string object representing the name of the method instead of the method itself, leading to the registry allowing anyone to call private methods.
-
- 27 Jun, 2019 1 commit
-
-
Killian Lufau authored
The purpose is to check that HMAC prevents routes from being exchanged between the 2 networks. This happened when 2 nodes of 2 different re6st networks are in the same LAN, and it caused many issues. /reviewed-on !15
-
- 26 Jun, 2019 1 commit
-
-
Julien Muchembled authored
This reverts commit 24fea8cd. The client up hook is required when IPv4 is not enabled.
-
- 19 Jun, 2019 1 commit
-
-
Killian Lufau authored
HMAC is added in babel call to prevent babel communication between nodes of different re6st networks. This solves the problem of machines in different re6st networks but on the same LAN that exchange routes through babel. The key used to authenticate packets is randomly created on 16 bytes by the registry and sent to nodes when they fetch network parameters. This uses the WIP hmac branch of jech/babeld with Nexedi patches and the added possibility to not check HMAC in incoming packets for better HMAC integration on a HMAC-less network. /reviewed-on nexedi/re6stnet!18
-
- 18 Jun, 2019 1 commit
-
-
Killian Lufau authored
The received network parameter name can have a ':json' suffix that is not present in the class attribute of this parameter. This suffix was not removed and could cause attribute deletion to fail. /reviewed-on nexedi/re6stnet!20
-
- 12 Jun, 2019 1 commit
-
-
Julien Muchembled authored
In commit d7a4d73f, this was done only for the init.d script.
-
- 04 Jun, 2019 1 commit
-
-
Julien Muchembled authored
-
- 15 May, 2019 2 commits
-
-
Killian Lufau authored
/reviewed-on nexedi/re6stnet!11
-
Killian Lufau authored
argparse is error-prone in that `action='append'` starts from (a copy of) the given default when it adds values from command-line, rather than restarting from an empty list. For example, simply passing `--disable-proto udp` resulted in ['udp', 'udp6', 'udp'], which caused 'udp6' to remain disabled. /reviewed-on nexedi/re6stnet!17
-
- 09 May, 2019 1 commit
-
-
Killian Lufau authored
In commit 06974788, we increased the --link-mtu value as a temporary way to compensate the unexplained behaviour change of recent OpenVPN. This was partly due to encryption, which was enabled despite `--cipher none`. And it happens that the behaviour of --link-mtu only changed for the server, with a mysterious difference of 93 bytes. Hence the workaround to get identical tunnel MTU on both sides. /reviewed-on !13
-
- 06 May, 2019 1 commit
-
-
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 nexedi/re6stnet!14
-
- 03 May, 2019 1 commit
-
-
Killian Lufau authored
Passing `--cipher none` to OpenVPN is not enough anymore because clients and servers can still negotiate the algorithm to use for encryption (by default not empty). We pass the option `--ncp-disable` to disable cipher negotiation. /reviewed-on !12
-
- 29 Apr, 2019 1 commit
-
-
Killian Lufau authored
The behaviour of --link-mtu has changed and we increase the values to at least have interface MTU greater than IPv6 minimum. We'll see later to have even greater values in ovpn_link_mtu_dict (so that the resulting MTU is closer to what we had with 2.3) or review the whole MTU part completely.
-
- 10 Apr, 2019 1 commit
-
-
Killian Lufau authored
The main goal of this is to check if we should keep supporting older distributions. /reviewed-on !9
-
- 12 Mar, 2019 1 commit
-
-
Killian Lufau authored
See "./demo --help" for more information. /reviewed-on nexedi/re6stnet!8
-
- 21 Feb, 2019 1 commit
-
-
Killian Lufau authored
/reviewed-on nexedi/re6stnet!7
-
- 05 Feb, 2019 1 commit
-
-
Thomas Gambier authored
-
- 14 Dec, 2018 1 commit
-
-
Jérome Perrin authored
prevent this kind of errors when running openssl fail: ``` 10-12-2018 19:04:02 ERROR AttributeError: 'NoneType' object has no attribute 'splitlines' Traceback (most recent call last): File "/opt/re6st/eggs/re6stnet-0.513-py2.7.egg/re6st/cli/node.py", line 428, in main s(*args) File "/opt/re6st/eggs/re6stnet-0.513-py2.7.egg/re6st/utils.py", line 191, in select R[r]() File "/opt/re6st/eggs/re6stnet-0.513-py2.7.egg/re6st/tunnel.py", line 399, in handlePeerEvent True, crypto.FILETYPE_ASN1) File "/opt/re6st/eggs/re6stnet-0.513-py2.7.egg/re6st/x509.py", line 136, in loadVerify for x in err.splitlines(): ``` /reviewed-on nexedi/re6stnet!6
-
- 17 Oct, 2018 2 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
-
- 02 Oct, 2018 1 commit
-
-
Julien Muchembled authored
-
- 25 Sep, 2018 2 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
-
- 30 Aug, 2018 3 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
Ideally, babeld should not keep running when it can't set such routes. Currently, it only outputs an error message in its log.
-
Julien Muchembled authored
In SQLite, a string that only contains '0' chars evaluates to False.
-
- 09 Aug, 2018 1 commit
-
-
Julien Muchembled authored
-
- 07 Aug, 2018 1 commit
-
-
Julien Muchembled authored
We currently have issues with OpenVPN hook scripts that aren't always killed at exit. Such orphan processes prevent re6st from starting again (EADDRINUSE). We want to know if it's an OpenVPN that does not exit cleanly on TERM, or if it sometimes does not exit at all after 5s (then re6st sends a KILL signal and at that point we should indeed make sure that any subprocess is also KILLed).
-