Wifi issues PC related

[mbohets]

Hi,

Regularly (a few times a day) I no longer have network wifi connectivity when using KDE neon on an HP elitebook laptop.
I use a low latency kernel because I use midi musical instruments
Any ideas on what could cause this and how to solve it ?

I have a dual boot W7 - KDE Neon, and I never experience this on W7 (I dont use it very often though)
At the same time other devices connected to the lan are working fine (I can watch youtube on my tv and my daughter has no problems on her laptop), so it is not a router problem.

I cannot ping my router anymore
marc@HPT:~$ ping -i 1 192.168.1.1
connect: Network is unreachable

when I look at the network with ifconfig, I see that my IPv4 IP address has gone and I only have an IPv6 address.

wlo1 Link encap:Ethernet HWaddr 6c:88:14:ab:aa:70
inet6 addr: fe80::6e88:14ff:feab:aa70/64 Scope:Link
inet6 addr: 2a02:1811:1412:1100:6e88:14ff:feab:aa70/64 Scope:Global
inet6 addr: 2a02:1811:1412:1100:3ca3:cc0a:9605:a4eb/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:55936 errors:0 dropped:0 overruns:0 frame:0
TX packets:28141 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:49888625 (49.8 MB) TX bytes:5147411 (5.1 MB)

When I disconnect and reconnect wifi using the network icon in the system tray, everything works normal again

wlo1 Link encap:Ethernet HWaddr 6c:88:14:ab:aa:70
inet addr:192.168.1.247 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::11d2:3d67:ef41:ed9a/64 Scope:Link
inet6 addr: 2a02:1811:1412:1100:c40a:696d:eb7b:4f03/64 Scope:Global
inet6 addr: 2a02:1811:1412:1100:3ca3:cc0a:9605:a4eb/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:165743 errors:0 dropped:0 overruns:0 frame:0
TX packets:87374 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:211369670 (211.3 MB) TX bytes:11164765 (11.1 MB)

marc@HPT:~$ ping -i 1 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.68 ms

lshw output
*-pci:4
description: PCI bridge
product: 7 Series/C210 Series Chipset Family PCI Express Root Port 4
vendor: Intel Corporation
physical id: 1c.3
bus info: pci@0000:00:1c.3
version: c4
width: 32 bits
clock: 33MHz
capabilities: pci normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:29 memory:d4000000-d40fffff
*-network
description: Wireless interface
product: Centrino Advanced-N 6205 [Taylor Peak]
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:25:00.0
logical name: wlo1
version: 34
serial: 6c:88:14:ab:aa:70
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=4.13.0-37-lowlatency firmware=18.168.6.1 ip=192.168.1.247 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:35 memory:d4000000-d4001fff

[vinnywright]

try turning IPv6 off in network manager , click the network icon in the system tray , in the top right is an icon for the conection settings ,click it it should open with the current network selected click the IPv6 tab and in the "method" dropdown select "ignored" ,,,,see if this helps .

VINNY

[mbohets]

Thx for the tip, but it does not work, I did this some weeks ago.
I now removed the low latency kernel to see if that helps

Your post got me thinking however.
when looking at ifconfig, it seems that the ignore setting does not switch off IPv6 because ifconfig shows that my wifi has an IPv6 address.
--> I-ll have to google around a bit to see how I can switch it off effectively.

[wizard10000]

Thx for the tip, but it does not work, I did this some weeks ago.
--> I-ll have to google around a bit to see how I can switch it off effectively.

Hint: /etc/sysctl.conf -

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

[mbohets]

Thx, I'll try this the next time my WiFi is blocked.

As of removing the real-time kernel, I did not experience the problem anymore.

[mbohets]

Today I experienced the issue again, but only partially, most sites remained accessible, only some were not.
With the normal kernel, It occurs much less than with the real time kernel, where it happened regularly and all connectivity was gone.

I now put the commands in /etc/sysctl.conf --> I'll see what happens.