Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
bitmask-vpn
bitmask-vpn
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 154
    • Issues 154
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • leap
  • bitmask-vpnbitmask-vpn
  • Issues
  • #337

Closed
Open
Created Aug 18, 2020 by Kali Kaneko@kaliOwner0 of 2 tasks completed0/2 tasks

Give feedback about current exit gateway / egress ip

A first step on the gateway selection would be to display the gateway we're using as exit.

  • we should parse the CONNECTED event and store that information CONNECTED: 212.83.143.67
  • we could cross-check with info fetched from the platform's geoip service (or an external service), see comment below.

An inconvenience I see is that the first method gives us an event (that can get outdated if things go wrong), while the second case can help us verify repeatedly that the egress ip is the expected.

Edited Aug 25, 2020 by Kali Kaneko
Assignee
Assign to
Desktop 0.21.2
Milestone
Desktop 0.21.2
Assign milestone
Time tracking
None
Due date
None