LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook
User Name
Password
Linux - Laptop and Netbook Having a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).

Notices


Reply
  Search this Thread
Old 04-29-2020, 11:03 PM   #1
llewellen
Member
 
Registered: Oct 2016
Location: Vancouver Island, Canada
Distribution: Crunchbang++ Openbox
Posts: 401

Rep: Reputation: Disabled
Internet Connection Dropped - Random, Intermittent


As the subject line says. No rhyme or reason that I can discern. The only app I'm using when this occurs is Waterfox browser with various tabs open.

All other people in my building use the same ISP and none that I have spoken to are experiencing this problem. When I go to Settings>Network it shows "Connected" even when it's not. Sometimes (not always) when I attempt to get to Settings it is slow to open and then shows a message "Contact your software provider". I have to shutdown or restart to re-establish a connection. Details below.

Manjaro Linux - Budgie DE (both with latest updates pushed out by Manjaro)
Dell Inspiron 7300 Series Laptop
Intel® Core™ i5-8250U CPU @ 1.60GHz × 8
Mesa Intel® UHD Graphics 620 (KBL GT2)

Coax connected to a Cisco DP3825 wifi router (supplied by my ISP)
No other devices connected to this router.
Wifi transferring data from my iPhone to my computer experiences no problems.

"inxi -Fxxxz" returns this:

Code:
[drew@dell-pc ~]$ inxi -Fxxxz
System:
  Host: dell-pc Kernel: 4.14.177-1-MANJARO x86_64 bits: 64 compiler: gcc 
  v: 9.3.0 Desktop: Budgie 10.5.1 info: budgie-panel wm: budgie-wm 
  dm: LightDM 1.30.0 Distro: Manjaro Linux 
Machine:
  Type: Laptop System: Dell product: Inspiron 7370 v: N/A serial: <filter> 
  Chassis: type: 10 serial: <filter> 
  Mobo: Dell model: 06KDFD v: A00 serial: <filter> UEFI: Dell v: 1.7.0 
  date: 01/31/2018 
Battery:
  ID-1: BAT0 charge: 33.7 Wh condition: 33.7/38.0 Wh (89%) volts: 12.5/11.4 
  model: SMP DELL 39DY56B type: Li-poly serial: <filter> status: Full 
CPU:
  Topology: Quad Core model: Intel Core i5-8250U bits: 64 type: MT MCP 
  arch: Kaby Lake rev: A L2 cache: 6144 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 28808 
  Speed: 800 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 801 2: 800 
  3: 800 4: 800 5: 800 6: 800 7: 800 8: 801 
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: Dell driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:5917 
  Display: x11 server: X.org 1.20.8 driver: intel unloaded: modesetting 
  alternate: fbdev,vesa compositor: budgie-wm resolution: <xdpyinfo missing> 
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.5 
  direct render: Yes 
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell 
  driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:9d71 
  Sound Server: ALSA v: k4.14.177-1-MANJARO 
Network:
  Device-1: Intel Wireless 7265 driver: iwlwifi v: kernel port: f040 
  bus ID: 01:00.0 chip ID: 8086:095a 
  IF: wlp1s0 state: up mac: <filter> 
  Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 
  bus ID: 2-3:2 chip ID: 0bda:8153 serial: <filter> 
  IF: enp0s20f0u3 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 238.47 GiB used: 61.87 GiB (25.9%) 
  ID-1: /dev/sda vendor: Toshiba model: KSG60ZMV256G M.2 2280 256GB 
  size: 238.47 GiB speed: 6.0 Gb/s serial: <filter> rev: 4101 scheme: GPT 
Partition:
  ID-1: / size: 224.77 GiB used: 61.87 GiB (27.5%) fs: ext4 dev: /dev/sda2 
  ID-2: swap-1 size: 8.80 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 
Sensors:
  System Temperatures: cpu: 44.0 C mobo: 43.0 C sodimm: 39.0 C 
  Fan Speeds (RPM): cpu: 0 
Info:
  Processes: 209 Uptime: 22m Memory: 7.54 GiB used: 1.20 GiB (15.9%) 
  Init: systemd v: 244 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.16 
  running in: gnome-terminal inxi: 3.0.37
Any clues, suggestions or further diagnostics? Thanks.
 
Old 04-29-2020, 11:45 PM   #2
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,855

Rep: Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149
Quote:
All other people in my building use the same ISP and none that I have spoken to are experiencing this problem.
1) Are you using NetworkManager to manage your wifi connectivity?

2) Some kind of shared network service with multiple APs? If so, it might be that roaming is occurring...
https://www.phoronix.com/scan.php?pa...oam-Aggressive

This archwiki page describes the unwanted symptoms that can occur with that...
https://wiki.archlinux.org/index.php..._packets_(WiFi)
...and how to inhibit it if that is the causing frequent disconnection...
Quote:
Alternatively, if roaming is not important, the periodic scanning behavior can be disabled by locking the BSSID of the access point in the WiFi connection profile.
An old blog on the subject (and what happens with bad drivers)
https://blogs.gnome.org/dcbw/2016/05...nd-wifi-scans/

Apologies if on the wrong track here.
 
Old 04-29-2020, 11:49 PM   #3
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,159

Rep: Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125Reputation: 4125
What do the logs say ?. RTL drivers are as flakey as hell - depends where Manjaro gets theirs from. I tend to look around on github but it's a bit of a crap-shoot. Sorry, was thinking wifi not cable - ignore that, I've never had a problem with RTL ethernet.

Last edited by syg00; 04-29-2020 at 11:52 PM. Reason: :doh:
 
Old 04-29-2020, 11:55 PM   #4
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,855

Rep: Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149
Quote:
Coax connected to a Cisco DP3825 wifi router (supplied by my ISP)
No other devices connected to this router.
Sorry, I missed this bit on my initial read.

Power management can sometimes cause issues like this. It can be inhibited if required...
https://wiki.archlinux.org/index.php...cards_(iwlwifi)
 
Old 04-30-2020, 01:09 AM   #5
llewellen
Member
 
Registered: Oct 2016
Location: Vancouver Island, Canada
Distribution: Crunchbang++ Openbox
Posts: 401

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ferrari View Post
Sorry, I missed this bit on my initial read.

Power management can sometimes cause issues like this. It can be inhibited if required...
https://wiki.archlinux.org/index.php...cards_(iwlwifi)
Thanks for the tip and the link. That article is more advanced than I am so it will take me some time to try to digest it. Undoubtedly, I will be back with more questions (and perhaps indigestion )
 
Old 04-30-2020, 02:03 AM   #6
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,855

Rep: Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149
Try the following:

Create /etc/modprobe.d/iwlwifi.conf with an editor (as root) with the following entry

Code:
options iwlwifi swcrypto=0 bt_coex_active=0 power_save=0
Save when done. It will take effect when you next reboot. (You could also just unload and reload the wifi driver, but I'll leave that as en exercise for you to research/learn.)

If that doesn't help with frequent disconnections, we'll need to investigate further.

One possibility is to watch the kernel messaging in a terminal while using your desktop. It will just run in the background...
Code:
dmesg -w|grep iwlwifi
...and when you are next disconnected, observe capture the output.
 
Old 04-30-2020, 09:37 AM   #7
llewellen
Member
 
Registered: Oct 2016
Location: Vancouver Island, Canada
Distribution: Crunchbang++ Openbox
Posts: 401

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ferrari View Post
Try the following:

Create /etc/modprobe.d/iwlwifi.conf with an editor (as root) with the following entry

Code:
options iwlwifi swcrypto=0 bt_coex_active=0 power_save=0
Save when done. It will take effect when you next reboot. (You could also just unload and reload the wifi driver, but I'll leave that as en exercise for you to research/learn.)

If that doesn't help with frequent disconnections, we'll need to investigate further.

One possibility is to watch the kernel messaging in a terminal while using your desktop. It will just run in the background...
Code:
dmesg -w|grep iwlwifi
...and when you are next disconnected, observe capture the output.
OK, thanks. I will try this later today and report back.
 
Old 04-30-2020, 08:42 PM   #8
llewellen
Member
 
Registered: Oct 2016
Location: Vancouver Island, Canada
Distribution: Crunchbang++ Openbox
Posts: 401

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ferrari View Post
Try the following:

Create /etc/modprobe.d/iwlwifi.conf with an editor (as root) with the following entry

Code:
options iwlwifi swcrypto=0 bt_coex_active=0 power_save=0
Save when done. It will take effect when you next reboot. (You could also just unload and reload the wifi driver, but I'll leave that as en exercise for you to research/learn.)

If that doesn't help with frequent disconnections, we'll need to investigate further.

One possibility is to watch the kernel messaging in a terminal while using your desktop. It will just run in the background...
Code:
dmesg -w|grep iwlwifi
...and when you are next disconnected, observe capture the output.
I already have the /etc/modprobe.d folder which contains one file: dell-smm-hwmon.conf, which contains this:

# This file must be at /etc/modprobe.d/
options dell-smm-hwmon restricted=0

Will run
Code:
dmesg -w|grep iwlwifi
and see what shows up the next time the connection drops.
 
Old 05-01-2020, 04:34 AM   #9
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,855

Rep: Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149
Quote:
I already have the /etc/modprobe.d folder which contains one file: dell-smm-hwmon.conf, which contains this:
That's irrelevant though. There could be any number of config files in the /etc/modprobe.d/ directory for different reasons. Create a custom configuration file with the entry that I mentioned already.
 
Old 05-01-2020, 09:27 PM   #10
llewellen
Member
 
Registered: Oct 2016
Location: Vancouver Island, Canada
Distribution: Crunchbang++ Openbox
Posts: 401

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ferrari View Post
That's irrelevant though. There could be any number of config files in the /etc/modprobe.d/ directory for different reasons. Create a custom configuration file with the entry that I mentioned already.
OK will do. In the meantime, this may be relevant. I just experienced a dropped connection. As has often (not always) happened with past drops when I attempted to go into Settings to check if the connection was enabled, the Settings window was very slow to open and then produced the attached saying that Network Manager is not running. There is then no way to check on the Network connection status. I have to Shutdown or Restart and when I do that I am met with a long series of Stop Job Running countdowns before the computer will actually shutdown or restart.
Attached Thumbnails
Click image for larger version

Name:	NetworkManager.png
Views:	13
Size:	41.2 KB
ID:	33144  
 
Old 05-01-2020, 09:56 PM   #11
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,855

Rep: Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149
Are you definitely using NetworkManager or some other network framework though?

Code:
sudo systemctl status network
Code:
sudo systemctl status NetworkManager
Code:
sudo systemctl status systemd-networkd.service
Quote:
There is then no way to check on the Network connection status. I have to Shutdown or Restart and when I do that I am met with a long series of Stop Job Running countdowns before the computer will actually shutdown or restart.
You could still examine/capture the kernel logging around this though (as I already explained).
 
Old 05-01-2020, 10:20 PM   #12
llewellen
Member
 
Registered: Oct 2016
Location: Vancouver Island, Canada
Distribution: Crunchbang++ Openbox
Posts: 401

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ferrari View Post
Are you definitely using NetworkManager or some other network framework though?

Code:
sudo systemctl status network
Code:
sudo systemctl status NetworkManager
Code:
sudo systemctl status systemd-networkd.service

You could still examine/capture the kernel logging around this though (as I already explained).
"sudo systemctl status network" returns this:

Code:
[drew@dell-pc ~]$ sudo systemctl status network
[sudo] password for drew: 
Unit network.service could not be found.
[drew@dell-pc ~]$
"sudo systemctl status NetworkManager" returns this:

Code:
[drew@dell-pc ~]$ sudo systemctl status NetworkManager
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; v>
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Fri 2020-05-01 19:19:24 PDT; 57min ago
       Docs: man:NetworkManager(8)
   Main PID: 604 (NetworkManager)
      Tasks: 3 (limit: 9198)
     Memory: 19.8M
     CGroup: /system.slice/NetworkManager.service
             └─604 /usr/bin/NetworkManager --no-daemon

May 01 20:13:37 dell-pc NetworkManager[604]: <info>  [1588389217.2467] dhcp4 (w>
May 01 20:13:37 dell-pc NetworkManager[604]: <info>  [1588389217.2467] dhcp4 (w>
May 01 20:13:37 dell-pc NetworkManager[604]: <info>  [1588389217.2467] dhcp4 (w>
May 01 20:13:37 dell-pc NetworkManager[604]: <info>  [1588389217.2467] dhcp4 (w>
May 01 20:13:37 dell-pc NetworkManager[604]: <info>  [1588389217.2468] dhcp4 (w>
May 01 20:13:37 dell-pc NetworkManager[604]: <info>  [1588389217.2468] dhcp4 (w>
May 01 20:13:37 dell-pc NetworkManager[604]: <info>  [1588389217.2516] device (>
May 01 20:13:37 dell-pc NetworkManager[604]: <info>  [1588389217.2535] device (>
May 01 20:13:37 dell-pc NetworkManager[604]: <info>  [1588389217.2537] device (>
May 01 20:13:37 dell-pc NetworkManager[604]: <info>  [1588389217.2768] device (>
lines 1-22/22 (END)
"sudo systemctl status systemd-networkd.service" returns this:

Code:
[drew@dell-pc ~]$ sudo systemctl status systemd-networkd.service
[sudo] password for drew: 
● systemd-networkd.service - Network Service
     Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; disabled>
     Active: inactive (dead)
       Docs: man:systemd-networkd.service(8)
lines 1-4/4 (END)
 
Old 05-01-2020, 11:03 PM   #13
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,855

Rep: Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149Reputation: 1149
That confirms that you're using NetworkManager. You could keep a watch on this service using
Code:
sudo journalctl -fu NetworkManager
Just leave it running in a terminal, and get on with your other tasks. When you next lose network connectivity observe the output, and post the pertinent logging here.
 
Old 05-01-2020, 11:08 PM   #14
llewellen
Member
 
Registered: Oct 2016
Location: Vancouver Island, Canada
Distribution: Crunchbang++ Openbox
Posts: 401

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ferrari View Post
That confirms that you're using NetworkManager. You could keep a watch on this service using
Code:
sudo journalctl -fu NetworkManager
Just leave it running in a terminal, and get on with your other tasks. When you next lose network connectivity observe the output, and post the pertinent logging here.
Will do. Thank you for sticking with me on this. I appreciate it.
 
Old 05-02-2020, 10:47 PM   #15
llewellen
Member
 
Registered: Oct 2016
Location: Vancouver Island, Canada
Distribution: Crunchbang++ Openbox
Posts: 401

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by llewellen View Post
Will do. Thank you for sticking with me on this. I appreciate it.
This had been happening several times today. There is a disconnect and then an automatic reconnection. Sorry for so much print out but its necessary to show what has been happening. This is just part of it to show one instance.

Code:
May 02 20:29:24 dell-pc NetworkManager[618]: <warn>  [1588476564.0207] sup-iface[0x55e69ab25110,wlp1s0]: connection disconnected (reason -3)
May 02 20:29:24 dell-pc NetworkManager[618]: <info>  [1588476564.0208] device (wlp1s0): supplicant interface state: completed -> disconnected
May 02 20:29:24 dell-pc NetworkManager[618]: <info>  [1588476564.0208] device (p2p-dev-wlp1s0): supplicant management interface state: completed -> disconnected
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.1696] policy: auto-activating connection '587839' (56a07dd8-486a-4e13-8592-db2076bd1142)
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.1701] device (wlp1s0): Activation: starting connection '587839' (56a07dd8-486a-4e13-8592-db2076bd1142)
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.1702] device (wlp1s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.1718] device (wlp1s0): set-hw-addr: reset MAC address to 74:E5:F9:39:A8:23 (preserve)
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.1745] device (wlp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.1747] device (wlp1s0): Activation: (wifi) access point '587839' has security, but secrets are required.
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.1747] device (wlp1s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.1846] device (wlp1s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.1849] device (wlp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.1852] device (wlp1s0): Activation: (wifi) connection '587839' has security, and secrets exist.  No new secrets needed.
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.1852] Config: added 'ssid' value '587839'
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.1852] Config: added 'scan_ssid' value '1'
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.1852] Config: added 'bgscan' value 'simple:30:-70:86400'
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.1852] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.1852] Config: added 'auth_alg' value 'OPEN'
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.1852] Config: added 'psk' value '<hidden>'
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.2513] device (wlp1s0): supplicant interface state: disconnected -> scanning
May 02 20:29:25 dell-pc NetworkManager[618]: <info>  [1588476565.2514] device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> scanning
May 02 20:29:26 dell-pc NetworkManager[618]: <info>  [1588476566.2956] device (wlp1s0): supplicant interface state: scanning -> authenticating
May 02 20:29:26 dell-pc NetworkManager[618]: <info>  [1588476566.2958] device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> authenticating
May 02 20:29:26 dell-pc NetworkManager[618]: <info>  [1588476566.2979] device (wlp1s0): supplicant interface state: authenticating -> associating
May 02 20:29:26 dell-pc NetworkManager[618]: <info>  [1588476566.2980] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> associating
May 02 20:29:26 dell-pc NetworkManager[618]: <info>  [1588476566.3078] device (wlp1s0): supplicant interface state: associating -> associated
May 02 20:29:26 dell-pc NetworkManager[618]: <info>  [1588476566.3079] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> associated
May 02 20:29:26 dell-pc NetworkManager[618]: <info>  [1588476566.3297] device (wlp1s0): supplicant interface state: associated -> 4-way handshake
May 02 20:29:26 dell-pc NetworkManager[618]: <info>  [1588476566.3297] device (p2p-dev-wlp1s0): supplicant management interface state: associated -> 4-way handshake
May 02 20:29:26 dell-pc NetworkManager[618]: <info>  [1588476566.3506] device (wlp1s0): supplicant interface state: 4-way handshake -> completed
May 02 20:29:26 dell-pc NetworkManager[618]: <info>  [1588476566.3506] device (wlp1s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "587839"
May 02 20:29:26 dell-pc NetworkManager[618]: <info>  [1588476566.3506] device (p2p-dev-wlp1s0): supplicant management interface state: 4-way handshake -> completed
May 02 20:29:26 dell-pc NetworkManager[618]: <info>  [1588476566.3508] device (wlp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
May 02 20:29:26 dell-pc NetworkManager[618]: <info>  [1588476566.3510] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3768] dhcp4 (wlp1s0): option dhcp_lease_time      => '3600'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3769] dhcp4 (wlp1s0): option domain_name_servers  => '64.59.160.15 64.59.161.69'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3769] dhcp4 (wlp1s0): option expiry               => '1588480168'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3770] dhcp4 (wlp1s0): option ip_address           => '192.168.0.11'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3770] dhcp4 (wlp1s0): option next_server          => '192.168.0.1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3770] dhcp4 (wlp1s0): option requested_broadcast_address => '1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3771] dhcp4 (wlp1s0): option requested_domain_name => '1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3771] dhcp4 (wlp1s0): option requested_domain_name_servers => '1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3772] dhcp4 (wlp1s0): option requested_domain_search => '1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3772] dhcp4 (wlp1s0): option requested_host_name  => '1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3772] dhcp4 (wlp1s0): option requested_interface_mtu => '1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3772] dhcp4 (wlp1s0): option requested_ms_classless_static_routes => '1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3772] dhcp4 (wlp1s0): option requested_nis_domain => '1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3772] dhcp4 (wlp1s0): option requested_nis_servers => '1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3772] dhcp4 (wlp1s0): option requested_ntp_servers => '1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3772] dhcp4 (wlp1s0): option requested_rfc3442_classless_static_routes => '1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3772] dhcp4 (wlp1s0): option requested_root_path  => '1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3772] dhcp4 (wlp1s0): option requested_routers    => '1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3772] dhcp4 (wlp1s0): option requested_static_routes => '1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3772] dhcp4 (wlp1s0): option requested_subnet_mask => '1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3773] dhcp4 (wlp1s0): option requested_time_offset => '1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3773] dhcp4 (wlp1s0): option requested_wpad       => '1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3773] dhcp4 (wlp1s0): option routers              => '192.168.0.1'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3773] dhcp4 (wlp1s0): option subnet_mask          => '255.255.255.0'
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3773] dhcp4 (wlp1s0): state changed unknown -> bound
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3798] device (wlp1s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3813] device (wlp1s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3815] device (wlp1s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
May 02 20:29:29 dell-pc NetworkManager[618]: <info>  [1588476569.3965] device (wlp1s0): Activation: successful, device activated.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Intermittent Internet Connection after Setting up load balancer phani96 Linux - Networking 1 02-25-2011 03:56 AM
Intermittent Internet connection Issues on Kubuntu creature124 Linux - Networking 2 02-01-2008 10:46 AM
Random loss of connectivity with dropped packets indicated - ? rylan76 Linux - Newbie 2 12-31-2006 03:58 AM
Intermittent Internet connection drops mlaverdiere Linux - Networking 2 08-21-2004 06:23 PM
silo overflow - internet connection dropped KaruppuSwamy.T *BSD 1 05-10-2004 10:51 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook

All times are GMT -5. The time now is 02:28 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration