Kali Linux VM, Network related commands gets no response after having been in sleep for a long time [on hold]
I am having a problem with my Kali Linux virtual machine: when it enters sleep for an extended period of time (few hours) once it wakes up, any network related commands (iwconfig, arp -a, ifconfig, or simply accessing the Internet on a browser) are unresponsive. When the command is performed in the terminal, it gets stuck like such

and the browser simply won't load any webpage.
I am also unable to interact with the network manager, when I click on "turn off" the interface closes as it would normally do but nothing happens.
The VM is running on Oracle Virtual box, the version of Kali 2018.3 and the host machine is a Windows 10 operating system. I Have made sure the VM has enough RAM, processing power etc.
kali-linux
put on hold as off-topic by roaima, msp9011, nwildner, Anthony Geoghegan, Mr Shunz Mar 25 at 15:58
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – roaima, msp9011, nwildner, Anthony Geoghegan, Mr Shunz
If this question can be reworded to fit the rules in the help center, please edit the question.
|
show 1 more comment
I am having a problem with my Kali Linux virtual machine: when it enters sleep for an extended period of time (few hours) once it wakes up, any network related commands (iwconfig, arp -a, ifconfig, or simply accessing the Internet on a browser) are unresponsive. When the command is performed in the terminal, it gets stuck like such

and the browser simply won't load any webpage.
I am also unable to interact with the network manager, when I click on "turn off" the interface closes as it would normally do but nothing happens.
The VM is running on Oracle Virtual box, the version of Kali 2018.3 and the host machine is a Windows 10 operating system. I Have made sure the VM has enough RAM, processing power etc.
kali-linux
put on hold as off-topic by roaima, msp9011, nwildner, Anthony Geoghegan, Mr Shunz Mar 25 at 15:58
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – roaima, msp9011, nwildner, Anthony Geoghegan, Mr Shunz
If this question can be reworded to fit the rules in the help center, please edit the question.
1
Hello matkiller333. What have you tried? What interfaces are you expecting? What, if anything, is in the log files?
– roaima
Mar 5 at 8:32
Hi Roaima, The problem is that I'm expecting any result really, but normally I would receive info about: eth0, lo, wlan0 As for what I have tried, I simply tried to reboot, launch an apt-get update and looked up my problem online but with no relevant results Thanks
– matkiller333
Mar 5 at 16:32
Doesdmesggive any relevant results?
– roaima
Mar 5 at 16:50
I will have to wait until the issue comes up again though, I'll keep you updated is there anything I should test when it happens again?
– matkiller333
Mar 5 at 16:54
Another thing to check is the clock: is it correct, or is it still showing the time when you put the VM to sleep?
– Mark
Mar 5 at 19:47
|
show 1 more comment
I am having a problem with my Kali Linux virtual machine: when it enters sleep for an extended period of time (few hours) once it wakes up, any network related commands (iwconfig, arp -a, ifconfig, or simply accessing the Internet on a browser) are unresponsive. When the command is performed in the terminal, it gets stuck like such

and the browser simply won't load any webpage.
I am also unable to interact with the network manager, when I click on "turn off" the interface closes as it would normally do but nothing happens.
The VM is running on Oracle Virtual box, the version of Kali 2018.3 and the host machine is a Windows 10 operating system. I Have made sure the VM has enough RAM, processing power etc.
kali-linux
I am having a problem with my Kali Linux virtual machine: when it enters sleep for an extended period of time (few hours) once it wakes up, any network related commands (iwconfig, arp -a, ifconfig, or simply accessing the Internet on a browser) are unresponsive. When the command is performed in the terminal, it gets stuck like such

and the browser simply won't load any webpage.
I am also unable to interact with the network manager, when I click on "turn off" the interface closes as it would normally do but nothing happens.
The VM is running on Oracle Virtual box, the version of Kali 2018.3 and the host machine is a Windows 10 operating system. I Have made sure the VM has enough RAM, processing power etc.
kali-linux
kali-linux
edited Mar 5 at 8:33
roaima
45.9k758124
45.9k758124
asked Mar 5 at 5:29
matkiller333matkiller333
1
1
put on hold as off-topic by roaima, msp9011, nwildner, Anthony Geoghegan, Mr Shunz Mar 25 at 15:58
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – roaima, msp9011, nwildner, Anthony Geoghegan, Mr Shunz
If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as off-topic by roaima, msp9011, nwildner, Anthony Geoghegan, Mr Shunz Mar 25 at 15:58
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – roaima, msp9011, nwildner, Anthony Geoghegan, Mr Shunz
If this question can be reworded to fit the rules in the help center, please edit the question.
1
Hello matkiller333. What have you tried? What interfaces are you expecting? What, if anything, is in the log files?
– roaima
Mar 5 at 8:32
Hi Roaima, The problem is that I'm expecting any result really, but normally I would receive info about: eth0, lo, wlan0 As for what I have tried, I simply tried to reboot, launch an apt-get update and looked up my problem online but with no relevant results Thanks
– matkiller333
Mar 5 at 16:32
Doesdmesggive any relevant results?
– roaima
Mar 5 at 16:50
I will have to wait until the issue comes up again though, I'll keep you updated is there anything I should test when it happens again?
– matkiller333
Mar 5 at 16:54
Another thing to check is the clock: is it correct, or is it still showing the time when you put the VM to sleep?
– Mark
Mar 5 at 19:47
|
show 1 more comment
1
Hello matkiller333. What have you tried? What interfaces are you expecting? What, if anything, is in the log files?
– roaima
Mar 5 at 8:32
Hi Roaima, The problem is that I'm expecting any result really, but normally I would receive info about: eth0, lo, wlan0 As for what I have tried, I simply tried to reboot, launch an apt-get update and looked up my problem online but with no relevant results Thanks
– matkiller333
Mar 5 at 16:32
Doesdmesggive any relevant results?
– roaima
Mar 5 at 16:50
I will have to wait until the issue comes up again though, I'll keep you updated is there anything I should test when it happens again?
– matkiller333
Mar 5 at 16:54
Another thing to check is the clock: is it correct, or is it still showing the time when you put the VM to sleep?
– Mark
Mar 5 at 19:47
1
1
Hello matkiller333. What have you tried? What interfaces are you expecting? What, if anything, is in the log files?
– roaima
Mar 5 at 8:32
Hello matkiller333. What have you tried? What interfaces are you expecting? What, if anything, is in the log files?
– roaima
Mar 5 at 8:32
Hi Roaima, The problem is that I'm expecting any result really, but normally I would receive info about: eth0, lo, wlan0 As for what I have tried, I simply tried to reboot, launch an apt-get update and looked up my problem online but with no relevant results Thanks
– matkiller333
Mar 5 at 16:32
Hi Roaima, The problem is that I'm expecting any result really, but normally I would receive info about: eth0, lo, wlan0 As for what I have tried, I simply tried to reboot, launch an apt-get update and looked up my problem online but with no relevant results Thanks
– matkiller333
Mar 5 at 16:32
Does
dmesg give any relevant results?– roaima
Mar 5 at 16:50
Does
dmesg give any relevant results?– roaima
Mar 5 at 16:50
I will have to wait until the issue comes up again though, I'll keep you updated is there anything I should test when it happens again?
– matkiller333
Mar 5 at 16:54
I will have to wait until the issue comes up again though, I'll keep you updated is there anything I should test when it happens again?
– matkiller333
Mar 5 at 16:54
Another thing to check is the clock: is it correct, or is it still showing the time when you put the VM to sleep?
– Mark
Mar 5 at 19:47
Another thing to check is the clock: is it correct, or is it still showing the time when you put the VM to sleep?
– Mark
Mar 5 at 19:47
|
show 1 more comment
0
active
oldest
votes
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
Hello matkiller333. What have you tried? What interfaces are you expecting? What, if anything, is in the log files?
– roaima
Mar 5 at 8:32
Hi Roaima, The problem is that I'm expecting any result really, but normally I would receive info about: eth0, lo, wlan0 As for what I have tried, I simply tried to reboot, launch an apt-get update and looked up my problem online but with no relevant results Thanks
– matkiller333
Mar 5 at 16:32
Does
dmesggive any relevant results?– roaima
Mar 5 at 16:50
I will have to wait until the issue comes up again though, I'll keep you updated is there anything I should test when it happens again?
– matkiller333
Mar 5 at 16:54
Another thing to check is the clock: is it correct, or is it still showing the time when you put the VM to sleep?
– Mark
Mar 5 at 19:47