Kali network keeps dropping/dying
Running Kali 2.0 on VMWare Fusion 10.1.1 on MacBook Pro laptop running macOS 10.13.6. I'm running the newtwork from VMWare in the NAT mode. I was able to connect to the internet, had an IPV4 address via ifconfig and basically happy.
Now, my network "drops/dies". I lose my IPV4 address, i.e. no longer get an IPV4 address via ifconfig. Can't ping anything on the outside or use FireFox. From within Kali my network icon disappears from the top right. At the host level I'm still able to work and connect normally.
The only thing I've been able to do to resolve my issue is revert to an older snapshot. After I revert to the snapshot I'm able to work normally for a period of time, 15 minutes to a couple of hours and then my problem appears again and I lose connectivity.
Does anyone have any ideas?
networking kali-linux debian
migrated from security.stackexchange.com Dec 3 at 21:05
This question came from our site for information security professionals.
add a comment |
Running Kali 2.0 on VMWare Fusion 10.1.1 on MacBook Pro laptop running macOS 10.13.6. I'm running the newtwork from VMWare in the NAT mode. I was able to connect to the internet, had an IPV4 address via ifconfig and basically happy.
Now, my network "drops/dies". I lose my IPV4 address, i.e. no longer get an IPV4 address via ifconfig. Can't ping anything on the outside or use FireFox. From within Kali my network icon disappears from the top right. At the host level I'm still able to work and connect normally.
The only thing I've been able to do to resolve my issue is revert to an older snapshot. After I revert to the snapshot I'm able to work normally for a period of time, 15 minutes to a couple of hours and then my problem appears again and I lose connectivity.
Does anyone have any ideas?
networking kali-linux debian
migrated from security.stackexchange.com Dec 3 at 21:05
This question came from our site for information security professionals.
1
Although Kali has a lot of security tools, it is just a Linux distribution. So, this is a Linux networking question and not a security question.
– schroeder
Dec 3 at 21:04
add a comment |
Running Kali 2.0 on VMWare Fusion 10.1.1 on MacBook Pro laptop running macOS 10.13.6. I'm running the newtwork from VMWare in the NAT mode. I was able to connect to the internet, had an IPV4 address via ifconfig and basically happy.
Now, my network "drops/dies". I lose my IPV4 address, i.e. no longer get an IPV4 address via ifconfig. Can't ping anything on the outside or use FireFox. From within Kali my network icon disappears from the top right. At the host level I'm still able to work and connect normally.
The only thing I've been able to do to resolve my issue is revert to an older snapshot. After I revert to the snapshot I'm able to work normally for a period of time, 15 minutes to a couple of hours and then my problem appears again and I lose connectivity.
Does anyone have any ideas?
networking kali-linux debian
Running Kali 2.0 on VMWare Fusion 10.1.1 on MacBook Pro laptop running macOS 10.13.6. I'm running the newtwork from VMWare in the NAT mode. I was able to connect to the internet, had an IPV4 address via ifconfig and basically happy.
Now, my network "drops/dies". I lose my IPV4 address, i.e. no longer get an IPV4 address via ifconfig. Can't ping anything on the outside or use FireFox. From within Kali my network icon disappears from the top right. At the host level I'm still able to work and connect normally.
The only thing I've been able to do to resolve my issue is revert to an older snapshot. After I revert to the snapshot I'm able to work normally for a period of time, 15 minutes to a couple of hours and then my problem appears again and I lose connectivity.
Does anyone have any ideas?
networking kali-linux debian
networking kali-linux debian
asked Dec 3 at 20:59
5lb Bass
migrated from security.stackexchange.com Dec 3 at 21:05
This question came from our site for information security professionals.
migrated from security.stackexchange.com Dec 3 at 21:05
This question came from our site for information security professionals.
1
Although Kali has a lot of security tools, it is just a Linux distribution. So, this is a Linux networking question and not a security question.
– schroeder
Dec 3 at 21:04
add a comment |
1
Although Kali has a lot of security tools, it is just a Linux distribution. So, this is a Linux networking question and not a security question.
– schroeder
Dec 3 at 21:04
1
1
Although Kali has a lot of security tools, it is just a Linux distribution. So, this is a Linux networking question and not a security question.
– schroeder
Dec 3 at 21:04
Although Kali has a lot of security tools, it is just a Linux distribution. So, this is a Linux networking question and not a security question.
– schroeder
Dec 3 at 21:04
add a comment |
1 Answer
1
active
oldest
votes
In Kali, your network stack is managed by a Network Manager (that doesn't conform to ifconfig commands). So what's happening is that when you make your ifconfig changes, they are overwritten the next time NetworkManager checks to make sure it's config is represented.
You have at least two options:
- Kill NetworkManager after each boot so that when you use ifconfig, the ip/subnetmask will stay
- Use the GUI NetworkManager to manage the interface(s)
Either way will work, possibly others, but I use the previous two methods a lot because of this problem.
answered Dec 3 at 21:34
thepip3r
26115
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2fsuperuser.com%2fquestions%2f1380522%2fkali-network-keeps-dropping-dying%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
In Kali, your network stack is managed by a Network Manager (that doesn't conform to ifconfig commands). So what's happening is that when you make your ifconfig changes, they are overwritten the next time NetworkManager checks to make sure it's config is represented.
You have at least two options:
- Kill NetworkManager after each boot so that when you use ifconfig, the ip/subnetmask will stay
- Use the GUI NetworkManager to manage the interface(s)
Either way will work, possibly others, but I use the previous two methods a lot because of this problem.
answered Dec 3 at 21:34
thepip3r
26115
add a comment |
In Kali, your network stack is managed by a Network Manager (that doesn't conform to ifconfig commands). So what's happening is that when you make your ifconfig changes, they are overwritten the next time NetworkManager checks to make sure it's config is represented.
You have at least two options:
- Kill NetworkManager after each boot so that when you use ifconfig, the ip/subnetmask will stay
- Use the GUI NetworkManager to manage the interface(s)
Either way will work, possibly others, but I use the previous two methods a lot because of this problem.
answered Dec 3 at 21:34
thepip3r
26115
add a comment |
In Kali, your network stack is managed by a Network Manager (that doesn't conform to ifconfig commands). So what's happening is that when you make your ifconfig changes, they are overwritten the next time NetworkManager checks to make sure it's config is represented.
You have at least two options:
- Kill NetworkManager after each boot so that when you use ifconfig, the ip/subnetmask will stay
- Use the GUI NetworkManager to manage the interface(s)
Either way will work, possibly others, but I use the previous two methods a lot because of this problem.
answered Dec 3 at 21:34
thepip3r
26115
In Kali, your network stack is managed by a Network Manager (that doesn't conform to ifconfig commands). So what's happening is that when you make your ifconfig changes, they are overwritten the next time NetworkManager checks to make sure it's config is represented.
You have at least two options:
- Kill NetworkManager after each boot so that when you use ifconfig, the ip/subnetmask will stay
- Use the GUI NetworkManager to manage the interface(s)
Either way will work, possibly others, but I use the previous two methods a lot because of this problem.
answered Dec 3 at 21:34
thepip3r
26115
answered Dec 3 at 21:34
thepip3r
26115
answered Dec 3 at 21:34
thepip3r
26115
answered Dec 3 at 21:34
thepip3r
26115
26115
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1380522%2fkali-network-keeps-dropping-dying%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
1
Although Kali has a lot of security tools, it is just a Linux distribution. So, this is a Linux networking question and not a security question.
– schroeder
Dec 3 at 21:04