Releases: mysteriumnetwork/node
0.11.2
Fixed bugs:
- Docker hub images are outdated #1270
0.11.2 (2019-08-13)
Implemented enhancements:
- Prepare docker image for ARM architecture #859
Closed issues:
- Show WG providers on Leaderboard too #1266
- Optimize DB queries #1253
- Add dashboard for Bounty Leaderboard #1209
- Update Leaderboard to monthly tracking #1208
- Transactor MVP #1120
Merged pull requests:
- Fix outdated docker images #1271 (tadaskay)
- Bump go-openvpn version #1269 (zolia)
- OpenVPN user subnet parameter #1264 (zolia)
- Bump up go-openvpn version #1262 (zolia)
- Correct debug level identifier #1261 (zolia)
- Wait for proposals in tests longer #1260 (zolia)
- Improve IP binding #1259 (zolia)
- Allow multiple close calls in tests #1258 (zolia)
- Tequilapi transactor endpoints #1234 (zolia)
* This Change Log was automatically generated by github_changelog_generator
0.11.1
Change Log
0.11.1 (2019-08-03)
Closed issues:
- Terms & conditions #1095
Merged pull requests:
* This Change Log was automatically generated by github_changelog_generator
0.11.0
Release highlights
User configuration file support
It is possible to customize startup options via <config-dir>/config.toml. On debian/raspbian installations, the location is usually /etc/mysterium-node/config.toml. 0.11.0 mystberry image ships with the following config.toml to serve whitelisted traffic by default:
[access-policy]
list = "mysterium"
Other:
mystwill now restart uponunattended-upgrade(overnight) to make sure the updated version is running- Added e-mail field support to Tequilapi for nodes participating in bounty program to enter their contact details
0.10.1
0.10.0
Release highlights
Built-in Web UI for Mysterium node
Web UI is accessible on port :4449.
- When the service is stopped the user can enter wallet address (for airdrops), referral code and select whitelist policy.
- When the service is running, the user can see statistics (sessions, the amount of transferred data).
Default credentials are myst:mystberry (it's possible to change them using the same Web UI).
Mysterium node discovery in the local network
To make it easier to access nodes running in local network (e.g. nodes on Raspberry Pi), they are automatically discovered using SSDP and Bonjour protocols. On Windows, the nodes should appear in This PC where double-clicking them would take you to the Web UI. On Mac OS, the node can be accessed using http://raspberrypi.local:4449 in your browser. Find out more about this feature
NAT hole punching improvements
While the easiest way to get Mysterium node running and serving traffic is to use UPnP (Learn how to setup UPnP on your router), we understand that it is not always possible to do so due to network router capabilities or security concerns. Hence we have implemented NAT traversal in node to work around the NAT and we are continuously fixing and improving its capabilities to provide a seamless node-runner experience.
Fixed automatic updates on mystberry (Raspberry PI image)
We have fixed the automated updates to stable versions on mystberry image so you can connect it and forget it. To have a seamless node-runner experience on Raspberry Pi, consider flashing the latest mystberry.zip. Learn more
Raspberry Sunrise
Raspberry auto updates and NAT fixes
- Start from TTL 2 for windows to be happy
- Protect session client ID map with lock while reading
- Autoupdates for myst on raspberry
- Run autoupdates only for stable releases
- Do not exit if pinger read fails
NAT hole punching fixes
- bootstrap now checks for presence of node before starting
- Move command flag to entrypoint
- Fix builder package build (gem install issues)
- Restore TTL for remote conn just after hole is punched
- Remove timeout from consumer pinger
Start provider natproxy session immediately after hole punch
Merge pull request #1065 from mysteriumnetwork/master Update 0.8 release with fixes