Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection to 76.76.21.21 on startup #895

Closed
pscsys opened this issue Nov 4, 2021 · 2 comments
Closed

Connection to 76.76.21.21 on startup #895

pscsys opened this issue Nov 4, 2021 · 2 comments

Comments

@pscsys
Copy link

pscsys commented Nov 4, 2021

Installed vscodium on Fedora following https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo

Now everytime it's being run it sends few packets (I don't want) to 76.76.21.21:443

Is it legit traffic for one of the components or something I should worry about?

Haven't installed any extensions yet.

Whois of the IP shows:

OrgName: Vercel, Inc
OrgId: ZEITI
Address: 340 S LEMON AVE #4133
City: Walnut
StateProv: CA
PostalCode: 91789
Country: US
RegDate: 2020-03-26
Updated: 2020-06-05
Comment: https://vercel.com
Ref: https://rdap.arin.net/registry/entity/ZEITI

Some traffic from tcpdump:

listening on enp0s3, link-type EN10MB (Ethernet), snapshot length 262144 bytes
08:59:33.145917 IP fedm4t3.39368 > 76.76.21.21.https: Flags [S], seq 286426010, win 64240, options [mss 1460,sackOK,TS val 1674302099 ecr 0,nop,wscale 7], length 0
08:59:33.170969 IP 76.76.21.21.https > fedm4t3.39368: Flags [S.], seq 3265934393, ack 286426011, win 14480, options [mss 1360,wscale 7,nop,sackOK,nop,nop], length 0
08:59:33.171020 IP fedm4t3.39368 > 76.76.21.21.https: Flags [.], ack 1, win 502, length 0
08:59:33.171266 IP fedm4t3.39368 > 76.76.21.21.https: Flags [P.], seq 1:518, ack 1, win 502, length 517
08:59:33.198198 IP 76.76.21.21.https > fedm4t3.39368: Flags [.], ack 518, win 1968, length 0
08:59:33.239369 IP 76.76.21.21.https > fedm4t3.39368: Flags [.], seq 1:2921, ack 518, win 1968, length 2920
08:59:33.239395 IP fedm4t3.39368 > 76.76.21.21.https: Flags [.], ack 2921, win 496, length 0
08:59:33.239838 IP 76.76.21.21.https > fedm4t3.39368: Flags [P.], seq 2921:4097, ack 518, win 1968, length 1176
08:59:33.239854 IP fedm4t3.39368 > 76.76.21.21.https: Flags [.], ack 4097, win 501, length 0
08:59:33.239928 IP 76.76.21.21.https > fedm4t3.39368: Flags [P.], seq 4097:5088, ack 518, win 1968, length 991
08:59:33.239951 IP fedm4t3.39368 > 76.76.21.21.https: Flags [.], ack 5088, win 501, length 0
08:59:33.264297 IP 76.76.21.21.https > fedm4t3.39368: Flags [P.], seq 4097:5088, ack 518, win 1968, length 991
....

@daiyam
Copy link
Member

daiyam commented Nov 4, 2021

I thinks it's the update process.
You will need to deactivate it with "update.mode": "none" in your settings.

@pscsys
Copy link
Author

pscsys commented Nov 4, 2021

Although I don't know which part causes the connection, that did the trick, thanks for the input.

@pscsys pscsys closed this as completed Nov 4, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants