Internet loss on host after running intensive app (e.g. expo-cli, create-react-app servers, etc)
up vote
0
down vote
favorite
I'm having a bit of a problem and I'm having a really hard time of looking up info on the web.
The problem
When running network-intensive applications from WSL, after a while Windows 10 loses internet connectivity. Restarting LxssManager service restores internet connectivity.
This happens most often when using expo cli. It sometimes also happened with create-react-app server, but recently I haven't had problems with that.
What I've tried
- pinging 8.8.8.8 (sometimes works, sometimes errors with
Network Unreachable. Even when it works, Windows still doesn't have internet) - Disabling IPv6
- Disabling power saving on the WiFi adapter
- Running script from cmder (as opposed to the integrated terminal of VsCode)
- Running script from WSL Bash
- Switching from wireless to ethernet (same problem)
- Updating/rolling back all network drivers
- Reinstalling WSL, node and related packages
- Reinstalling Windows
Environment
- Dell Latitude E5570 with Intel Dual Band Wireless AC 8260
- Windows 10 version 1809 build 17763.55 (also happened with the previous update)
- WSL Ubuntu installed from store
- Node.JS versions 8 through 11 (tested on all versions and same behaviour on all)
I don't know if this is an issue with WSL or an issue with my laptop / drivers / config, so I thought it's best to post here before posting an issue on GitHub.
node.js networking windows-10 expo windows-subsystem-for-linux
edited Nov 11 at 14:00
halfer
14.2k758106
asked Nov 11 at 13:33
Bogdan Marius Calapod
11
add a comment |
up vote
0
down vote
favorite
I'm having a bit of a problem and I'm having a really hard time of looking up info on the web.
The problem
When running network-intensive applications from WSL, after a while Windows 10 loses internet connectivity. Restarting LxssManager service restores internet connectivity.
This happens most often when using expo cli. It sometimes also happened with create-react-app server, but recently I haven't had problems with that.
What I've tried
- pinging 8.8.8.8 (sometimes works, sometimes errors with
Network Unreachable. Even when it works, Windows still doesn't have internet) - Disabling IPv6
- Disabling power saving on the WiFi adapter
- Running script from cmder (as opposed to the integrated terminal of VsCode)
- Running script from WSL Bash
- Switching from wireless to ethernet (same problem)
- Updating/rolling back all network drivers
- Reinstalling WSL, node and related packages
- Reinstalling Windows
Environment
- Dell Latitude E5570 with Intel Dual Band Wireless AC 8260
- Windows 10 version 1809 build 17763.55 (also happened with the previous update)
- WSL Ubuntu installed from store
- Node.JS versions 8 through 11 (tested on all versions and same behaviour on all)
I don't know if this is an issue with WSL or an issue with my laptop / drivers / config, so I thought it's best to post here before posting an issue on GitHub.
node.js networking windows-10 expo windows-subsystem-for-linux
edited Nov 11 at 14:00
halfer
14.2k758106
asked Nov 11 at 13:33
Bogdan Marius Calapod
11
Can you provide the steps to reporduce this error? What's your windows 10 build number? This issue can't be solved with one Q&A. You've to make an issue in GitHub/WSL or GitHub/expo-cli repository.
– Biswapriyo
Nov 12 at 3:51
Well, the error simply appears when runningexpo cliafter a couple of minutes. My build number is17763.55, as I've mentioned in the Environment section. I've also posted in theexpo-clirepo, but no one replied there - I'll post to the WSL repo as well.
– Bogdan Marius Calapod
Nov 13 at 9:03
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm having a bit of a problem and I'm having a really hard time of looking up info on the web.
The problem
When running network-intensive applications from WSL, after a while Windows 10 loses internet connectivity. Restarting LxssManager service restores internet connectivity.
This happens most often when using expo cli. It sometimes also happened with create-react-app server, but recently I haven't had problems with that.
What I've tried
- pinging 8.8.8.8 (sometimes works, sometimes errors with
Network Unreachable. Even when it works, Windows still doesn't have internet) - Disabling IPv6
- Disabling power saving on the WiFi adapter
- Running script from cmder (as opposed to the integrated terminal of VsCode)
- Running script from WSL Bash
- Switching from wireless to ethernet (same problem)
- Updating/rolling back all network drivers
- Reinstalling WSL, node and related packages
- Reinstalling Windows
Environment
- Dell Latitude E5570 with Intel Dual Band Wireless AC 8260
- Windows 10 version 1809 build 17763.55 (also happened with the previous update)
- WSL Ubuntu installed from store
- Node.JS versions 8 through 11 (tested on all versions and same behaviour on all)
I don't know if this is an issue with WSL or an issue with my laptop / drivers / config, so I thought it's best to post here before posting an issue on GitHub.
node.js networking windows-10 expo windows-subsystem-for-linux
edited Nov 11 at 14:00
halfer
14.2k758106
asked Nov 11 at 13:33
Bogdan Marius Calapod
11
I'm having a bit of a problem and I'm having a really hard time of looking up info on the web.
The problem
When running network-intensive applications from WSL, after a while Windows 10 loses internet connectivity. Restarting LxssManager service restores internet connectivity.
This happens most often when using expo cli. It sometimes also happened with create-react-app server, but recently I haven't had problems with that.
What I've tried
- pinging 8.8.8.8 (sometimes works, sometimes errors with
Network Unreachable. Even when it works, Windows still doesn't have internet) - Disabling IPv6
- Disabling power saving on the WiFi adapter
- Running script from cmder (as opposed to the integrated terminal of VsCode)
- Running script from WSL Bash
- Switching from wireless to ethernet (same problem)
- Updating/rolling back all network drivers
- Reinstalling WSL, node and related packages
- Reinstalling Windows
Environment
- Dell Latitude E5570 with Intel Dual Band Wireless AC 8260
- Windows 10 version 1809 build 17763.55 (also happened with the previous update)
- WSL Ubuntu installed from store
- Node.JS versions 8 through 11 (tested on all versions and same behaviour on all)
I don't know if this is an issue with WSL or an issue with my laptop / drivers / config, so I thought it's best to post here before posting an issue on GitHub.
node.js networking windows-10 expo windows-subsystem-for-linux
node.js networking windows-10 expo windows-subsystem-for-linux
edited Nov 11 at 14:00
halfer
14.2k758106
asked Nov 11 at 13:33
Bogdan Marius Calapod
11
edited Nov 11 at 14:00
halfer
14.2k758106
asked Nov 11 at 13:33
Bogdan Marius Calapod
11
edited Nov 11 at 14:00
halfer
14.2k758106
edited Nov 11 at 14:00
halfer
14.2k758106
edited Nov 11 at 14:00
halfer
14.2k758106
14.2k758106
asked Nov 11 at 13:33
Bogdan Marius Calapod
11
asked Nov 11 at 13:33
Bogdan Marius Calapod
11
asked Nov 11 at 13:33
Bogdan Marius Calapod
11
11
Can you provide the steps to reporduce this error? What's your windows 10 build number? This issue can't be solved with one Q&A. You've to make an issue in GitHub/WSL or GitHub/expo-cli repository.
– Biswapriyo
Nov 12 at 3:51
Well, the error simply appears when runningexpo cliafter a couple of minutes. My build number is17763.55, as I've mentioned in the Environment section. I've also posted in theexpo-clirepo, but no one replied there - I'll post to the WSL repo as well.
– Bogdan Marius Calapod
Nov 13 at 9:03
add a comment |
Can you provide the steps to reporduce this error? What's your windows 10 build number? This issue can't be solved with one Q&A. You've to make an issue in GitHub/WSL or GitHub/expo-cli repository.
– Biswapriyo
Nov 12 at 3:51
Well, the error simply appears when runningexpo cliafter a couple of minutes. My build number is17763.55, as I've mentioned in the Environment section. I've also posted in theexpo-clirepo, but no one replied there - I'll post to the WSL repo as well.
– Bogdan Marius Calapod
Nov 13 at 9:03
Can you provide the steps to reporduce this error? What's your windows 10 build number? This issue can't be solved with one Q&A. You've to make an issue in GitHub/WSL or GitHub/expo-cli repository.
– Biswapriyo
Nov 12 at 3:51
Can you provide the steps to reporduce this error? What's your windows 10 build number? This issue can't be solved with one Q&A. You've to make an issue in GitHub/WSL or GitHub/expo-cli repository.
– Biswapriyo
Nov 12 at 3:51
Well, the error simply appears when running
expo cli after a couple of minutes. My build number is 17763.55, as I've mentioned in the Environment section. I've also posted in the expo-cli repo, but no one replied there - I'll post to the WSL repo as well.– Bogdan Marius Calapod
Nov 13 at 9:03
Well, the error simply appears when running
expo cli after a couple of minutes. My build number is 17763.55, as I've mentioned in the Environment section. I've also posted in the expo-cli repo, but no one replied there - I'll post to the WSL repo as well.– Bogdan Marius Calapod
Nov 13 at 9:03
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53249259%2finternet-loss-on-host-after-running-intensive-app-e-g-expo-cli-create-react-a%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Can you provide the steps to reporduce this error? What's your windows 10 build number? This issue can't be solved with one Q&A. You've to make an issue in GitHub/WSL or GitHub/expo-cli repository.
– Biswapriyo
Nov 12 at 3:51
Well, the error simply appears when running
expo cliafter a couple of minutes. My build number is17763.55, as I've mentioned in the Environment section. I've also posted in theexpo-clirepo, but no one replied there - I'll post to the WSL repo as well.– Bogdan Marius Calapod
Nov 13 at 9:03