cvl

cvl

Member Since 12 years ago

Experience Points
8
follower
Lessons Completed
3
follow
Lessons Completed
227
stars
Best Reply Awards
0
repos

149 contributions in the last year

Pinned
Activity
Nov
22
1 week ago
Activity icon
issue

cvl issue mysteriumnetwork/node

cvl
cvl

[android] can't connect to any node on mainnet (weird errors)

Describe the bug Lots of errors with weird characters. App reinstalls don't help.

Logs mysterium-node.log

Environment (please complete the following information):

  • Node version: 1.0.0
  • OS: Android
Activity icon
issue

cvl issue mysteriumnetwork/node

cvl
cvl

[critical] testnet3 not working anymore

Describe the bug Can't connect to any provider both on Android and Mac. Can't register on Mac

Logs: mysterium-node-2.log mysterium-node-3.log mysterium-node.log

Environment (please complete the following information):

  • Node version: Various
  • OS: Mac, Android, WindowS
Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

[android] 1.0.0-rc1 could not create p2p channel during connect: p2p dialer failed: could not dial p2p channel: could not ping peer: too few connections were built

Describe the bug Trying to connect getting multiple errors including "could not create p2p channel during connect: p2p dialer failed: could not dial p2p channel: could not ping peer: too few connections were built"

Logs: mysterium-node.log

Environment (please complete the following information):

  • Node version: 1.0.0-rc1
  • OS: Android
cvl
cvl

Hmm, nothing's changed for years in the app.

It works fine for most providers though.

Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

Reopening questions regarding kill-switch/reconnect functionality

As per https://github.com/mysteriumnetwork/node/issues/3168

@soffokl

I can see that Android lib and mysterium-vpn-js has setDisableKillSwitch amongst connect options. It feels like kill switch should be enabled by default (unless I set "disable kill switch" to true). Is this something I should use?

As per your suggested implementation for Android:

  • Where is this config? I can't find it anywhere in Mysterium app, not in MobileNodeOptions (looked at 0.45.0).
  • How should I implement this in desktop app?
  • Is this a real kill-switch (i.e. can I market is a kill-switch) - as it sounds like it's a reconnect feature. In other words: if connection is dropped for any reason (node, wifi signal lost/reconnected whatever), would the traffic leak, or will the internet be disabled until user manually clicks Disconnect, or node reconnects to provider successfully?
  • What's the difference between setDisableKillSwitch? Would those two implementations conflict?
  • how would you suggest to test this (the easiest way if possible :) )?
  • is it possible to get a notification (e.g. status change or smth like that) once the connection is dropped, so I can notify user that something bad happened and he should Disconnect and Connect again.
Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

Give an option to enable LAN access when connected to VPN

As per https://github.com/mysteriumnetwork/node/issues/3792 Most VPN clients (all of them I have tried) enable users to access LAN when on VPN connection.

Currently, it's not possible to access LAN on Windows (works fine on Mac).

I'd suggest to have an option to enable LAN when on VPN connection.

Nov
21
2 weeks ago
Activity icon
issue

cvl issue mysteriumnetwork/node

cvl
cvl

[android] 1.0.0-rc1 could not create p2p channel during connect: p2p dialer failed: could not dial p2p channel: could not ping peer: too few connections were built

Describe the bug Trying to connect getting multiple errors including "could not create p2p channel during connect: p2p dialer failed: could not dial p2p channel: could not ping peer: too few connections were built"

Logs: mysterium-node.log

Environment (please complete the following information):

  • Node version: 1.0.0-rc1
  • OS: Android
Activity icon
issue

cvl issue mysteriumnetwork/node

cvl
cvl

[mac] 1.0.0-rc1 connection failure, connection drop & reconnect, no state update

Describe the bug Trying out 1.0.0-rc1 (worked fine with 1.0.0-rc0):

  • Connection fails to multiple providers
  • After finally connecting, I got connection drop after few seconds, connection state => Hold
  • After few seconds node logs produced "NATS: reconnected", and I can see that I have a german IP. Yet the connection state still stays at "Hold". Logs: mysterium-node.log

Environment (please complete the following information):

  • Node version: 1.0.0-rc1
  • OS: Mac
Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

Connection state not updated properly when no connection

Describe the bug

  • Turn off internet connection & try to connect -> state stays "Disconnected". Yet it actually attempts to connect.
  • Turn the connection back on, after a while it changes from Disconnected -> Connected.

Expected behavior Node should change the state to Connecting once the connecting attempt occurs.

Environment (please complete the following information):

  • Node version: 0.46.1
  • OS: Any
Nov
20
2 weeks ago
Activity icon
issue

cvl issue mysteriumnetwork/node

cvl
cvl

[android] sendto: operation not permitted, could not fetch fees

Describe the bug Can't get node running properly on Android. I can see multiple errors. Logs: mysterium-node.log

Environment (please complete the following information):

  • Node version: 0.68.1
  • OS: Android
Nov
14
3 weeks ago
Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

[android, bug] Can't access /proc/net/route

Describe the bug User sent diagnostics report, I can see many errors like write udp [::]:40992->239.255.255.250:1900: sendto: operation not permitted https://testnet2-location.mysterium.network/api/v1/location -> 64:ff9b::5fd8:cce8 error="failed to get default gateway: Can't access /proc/net/route

Logs: mysterium-node.log

Environment (please complete the following information):

  • Node version: 0.51.0
  • OS: Android
Nov
12
3 weeks ago
Activity icon
issue

cvl issue mysteriumnetwork/node

cvl
cvl

[android] node doesn't work, multiple errors (could not fetch fees, no contract code at given address)

Describe the bug Node doesn't work properly on Android, I can see multiple errors. Logs: mysterium-node.log

Environment (please complete the following information):

  • Node version: 0.68.1
  • OS: Android
Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

failed to connect to NATS servers when connected to mobile hotspot (0.47.1)

Describe the bug

  • Connect to mobile hostpot.
  • Run app.

Node doesn't start properly, hangs on "failed to connect to NATS servers".

Worked well before.

Logs: mysterium-node.log

Environment (please complete the following information):

  • Node version: 0.47.1
  • OS: Mac
Nov
9
3 weeks ago
Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

[windows, bug] user is blocked (?) after connecting once to a node.

Describe the bug User reports, that he can connect to a node once successfully, then on second attempt, he's cannot connect to it anymore. He can connect to another node once, then he can't connect to the same node anymore again. He suspect he's blocked by his ISP (t-mobile 4g lte home internet) - but I doubt it. Must be some weird bug. More feedback from user: "I was connected to Japan for about an hour, then my modem reset and whole house went offline. When everything came back up I could no longer connect to Japan. I then tried closing the app from system tray, opened it again and tried to connect again, then tried all options in the menu, data ip, residential, changed dns types as well and nothing. Put everything back to default and connected to Argentina which worked for about an hour and then I got booted and it wouldn't work anymore as well. "

Logs: mysterium-node.log

Environment (please complete the following information):

  • Node version: 0.51.0
  • OS: Windows 10
Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

[mac, bug] node frequently disconnect, multiple errors

Describe the bug User reports that node frequently disconnects when using BBC iPlayer. I can see many various errors in logs:

mysterium-node.log

Environment (please complete the following information):

  • Node version: 0.51.0
  • OS: Mac
Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

[windows, bug] can't access any website after connecting to any node

Describe the bug User reported he can't access any website when connected. He's tried many nodes.

Logs: mysterium-node.log

Environment (please complete the following information):

  • Node version: 0.51.0
  • OS: Windows
Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

[windows, bug] user "lost" his IP after disconnecting

Describe the bug User reports that after disconnecting he cannot resolve his local IP anymore. Restarting computer didn't help.

After 5 minutes and 2 restarts it came back to normal somehow.

Logs: mysterium-node.log

Environment (please complete the following information):

  • Node version: 0.51.0
  • OS: Windows
Activity icon
issue

cvl issue mysteriumnetwork/node

cvl
cvl

[android] can't connect to providers NATType:fail

Describe the bug Can't connect to any provider, getting various errors like NATType:fail

Logs: mysterium-node.log

Environment (please complete the following information):

  • Node version: 0.68.1
  • OS: Android
Nov
6
4 weeks ago
Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

[bug, linux app] app cannot be upgraded without removing app

Describe the bug

  • Download newer version installer (.deb)
  • Open it -> it shows "Remove" only. There's no "Install new version" or reinstall. So user is forced to first remove the app, then install again just to upgrade the app.

Environment (please complete the following information):

  • Node version: NA
  • OS: Ubuntu LTS
Nov
3
1 month ago
Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

[bug, linux app] app cannot be installed again after uninstall

Describe the bug

  • Install Mysterium app on Ubuntu

1st scenario:

  • Don't quit app, and try to remove it via installer.
  • Installer will show that app is removed, but in fact it's not, and tray icon is there, you can still open Mysterium app window via "Show Window".

2nd scenario:

  • Quit app, and try to remove it via installer.
  • Installer will show that app is removed, but myst_supervisor keeps running.
  • Try to install app again -> the app cannot get installed again: installer shows, that it installed, but there's no app to be found amongst apps.

Environment (please complete the following information):

  • OS: Ubuntu LTS
  • Desktop app version (if applicable): 3.9.0
Nov
2
1 month ago
Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

[android] no fees known for chain 0: redis: nil

Describe the bug Can't connect to any provider. Logs: mysterium-node.log

Environment (please complete the following information):

  • Node version: 0.66.2
  • OS: Android
cvl
cvl

No, no changes for months/years in the app.

Activity icon
issue

cvl issue mysteriumnetwork/node

cvl
cvl

[android] no fees known for chain 0: redis: nil

Describe the bug Can't connect to any provider. Logs: mysterium-node.log

Environment (please complete the following information):

  • Node version: 0.66.2
  • OS: Android
Oct
26
1 month ago
Activity icon
issue

cvl issue mysteriumnetwork/node

cvl
cvl

getting spammed with Returning default value launcher.ver

After upgrade to node 0.67.4, logs are getting spammed with the following: 2021-10-26T15:12:22.959 DBG source/config/config.go:224 > Returning default value launcher.ver:

Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

Smart (re)connect

There are 2 big tasks that are required for smart-reconnect:

1) a way to find a node for initial connection also known as smart-filters. 2) a real reconnect to a new node once we lost connection to the currently used.

Most of the work on the 1st part should be done on the discovery service:

  1. Discovery service should support an endpoint to provide an ordered list of suggested nodes by smart-filters.
  2. Discovery service should be able to build such ordered lists based on quality data: biggest bandwidth, lowest latency, lowest node load, etc.
  3. Node should support sending these smart-filter requests and be able to establish connections based on the ordered list.

The 2nd part of them is to finish proper reconnect once the connection is lost without leaking any traffic:

  1. We had an initial POC implementation for reconnecting, but it has a lot of problems which is not been solved.
  2. It's a platform-dependent solution, and most likely we will need to have platform-specific implementation. This requires additional research.

POC of reconnect was disabled by https://github.com/mysteriumnetwork/node/pull/3875 We need to resolve routing maintenance issue to make sure we can use: https://github.com/mysteriumnetwork/node/issues/3247

cvl
cvl

Do I understand correctly now, that for smart reconnect to work as expected (i.e. if connection is dropped, it should reconnect to the provider in the same country and IP type), then command connection up should be used in the first place instead of connection create? So in desktop app, instead of tequilapi.connectionCreate it would be tequilapi.up (when it's implemented)?

I have created a feature request to add smart reconnect to desktop and mobile apps https://github.com/mysteriumnetwork/node/issues/4149 as it's not possible to use this feature now in apps unless node code would be forked (if I understand correctly).

Oct
25
1 month ago
Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

Smart (re)connect

There are 2 big tasks that are required for smart-reconnect:

1) a way to find a node for initial connection also known as smart-filters. 2) a real reconnect to a new node once we lost connection to the currently used.

Most of the work on the 1st part should be done on the discovery service:

  1. Discovery service should support an endpoint to provide an ordered list of suggested nodes by smart-filters.
  2. Discovery service should be able to build such ordered lists based on quality data: biggest bandwidth, lowest latency, lowest node load, etc.
  3. Node should support sending these smart-filter requests and be able to establish connections based on the ordered list.

The 2nd part of them is to finish proper reconnect once the connection is lost without leaking any traffic:

  1. We had an initial POC implementation for reconnecting, but it has a lot of problems which is not been solved.
  2. It's a platform-dependent solution, and most likely we will need to have platform-specific implementation. This requires additional research.

POC of reconnect was disabled by https://github.com/mysteriumnetwork/node/pull/3875 We need to resolve routing maintenance issue to make sure we can use: https://github.com/mysteriumnetwork/node/issues/3247

cvl
cvl
  • Is there a way for desktop/mobile app to reconnect to the provider of the same country / IP type? Command line command for this is myst connection up --location-type=hosting --country=FI but how can I use this in the app?
  • If the myst connection up command is not called, will it reconnect to the same provider (I assume, that if provider goes down, hence reconnect, then the same provider won't be available), or to some random provider in global list of providers (i.e. some other country and IP type)?
  • When myst connection up command should be called, right after connection drop, or before connecting in the first place?
Activity icon
issue

cvl issue mysteriumnetwork/node

cvl
cvl

[windows] can't connect to any provider

Describe the bug Can't connect to any provider on Windows. Lots of errors, probably related to NAT punching?

Logs: mysterium-node.log

Environment (please complete the following information):

  • Node version: 0.66.4
  • OS: Windows
Activity icon
issue

cvl issue mysteriumnetwork/node

cvl
cvl

Smart (re)connect for desktop and mobile apps

As smart reconnect was implemented for command line clients (https://github.com/mysteriumnetwork/node/issues/3870), I'd suggest to implement it for desktop and mobile apps as well.

Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

Smart (re)connect

There are 2 big tasks that are required for smart-reconnect:

1) a way to find a node for initial connection also known as smart-filters. 2) a real reconnect to a new node once we lost connection to the currently used.

Most of the work on the 1st part should be done on the discovery service:

  1. Discovery service should support an endpoint to provide an ordered list of suggested nodes by smart-filters.
  2. Discovery service should be able to build such ordered lists based on quality data: biggest bandwidth, lowest latency, lowest node load, etc.
  3. Node should support sending these smart-filter requests and be able to establish connections based on the ordered list.

The 2nd part of them is to finish proper reconnect once the connection is lost without leaking any traffic:

  1. We had an initial POC implementation for reconnecting, but it has a lot of problems which is not been solved.
  2. It's a platform-dependent solution, and most likely we will need to have platform-specific implementation. This requires additional research.

POC of reconnect was disabled by https://github.com/mysteriumnetwork/node/pull/3875 We need to resolve routing maintenance issue to make sure we can use: https://github.com/mysteriumnetwork/node/issues/3247

cvl
cvl

Business as usual at Mysterium :)

Oct
23
1 month ago
Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

[bug] user can't connect to any node

Describe the bug User can't connect to any node - node is stuck in "connecting" state. Tried multiple restarts, reinstalls, with clearing configs etc. Nothing helped.

Logs: mysterium-node 36.log

Environment (please complete the following information):

  • Node version: 0.44.0
  • OS: Windows 10
Oct
19
1 month ago
Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

Smart (re)connect

There are 2 big tasks that are required for smart-reconnect:

1) a way to find a node for initial connection also known as smart-filters. 2) a real reconnect to a new node once we lost connection to the currently used.

Most of the work on the 1st part should be done on the discovery service:

  1. Discovery service should support an endpoint to provide an ordered list of suggested nodes by smart-filters.
  2. Discovery service should be able to build such ordered lists based on quality data: biggest bandwidth, lowest latency, lowest node load, etc.
  3. Node should support sending these smart-filter requests and be able to establish connections based on the ordered list.

The 2nd part of them is to finish proper reconnect once the connection is lost without leaking any traffic:

  1. We had an initial POC implementation for reconnecting, but it has a lot of problems which is not been solved.
  2. It's a platform-dependent solution, and most likely we will need to have platform-specific implementation. This requires additional research.

POC of reconnect was disabled by https://github.com/mysteriumnetwork/node/pull/3875 We need to resolve routing maintenance issue to make sure we can use: https://github.com/mysteriumnetwork/node/issues/3247

cvl
cvl

Hi.

How can I use this feature on desktop/mobile app? I want node to reconnect to a) the same country b) same location-type (i.e. residential/hosting).

Activity icon
issue

cvl issue comment mysteriumnetwork/node

cvl
cvl

[mac, urgent] connection drops constantly after migrating to 0.62.1, 0.66.2

Describe the bug Was working fine with 0.51.0.

Right after updating to 0.62.1, then 0.66.2, connection starts dropping very frequently to unusable levels.

Logs: mysterium-node.log

Environment (please complete the following information):

  • Node version: 0.66.2
  • OS: Mac
cvl
cvl

Any progress with this?