Lubuntu 18.04 Bionic Is possible auto reconnect when wifi disconnect?

aug7744 · January 28, 2021, 9:13pm

Hello thanks for read my topic.
Lubuntu 18.04 Bionic 32 bits.
Problems in wifi signal drop connection extremely.

Is possible configure Bionic 18.04 when dropping wifi connection automatically reconnect to previous wifi connection ?
When dropping connection is displayed an window to reconnect in wrong moments when typing text.

Thanks very much for your reply.

wxl · January 28, 2021, 9:51pm

We need to know what card you have (preferably with PCI ID), the kernel driver you’re using, which modules are available, and any telling log entries. See the instructions shown before you post.

aug7744 · January 31, 2021, 11:52pm

lspci
03:03.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)

kernel driver ipw2200

Kernel Modules

-Loaded Modules-
michael_mic : Michael MIC
lib80211_crypt_tkip : lib80211 crypt: TKIP
libarc4
ccm : Counter with CBC MAC
lib80211_crypt_ccmp : Host AP crypt: CCMP
dell_laptop : Dell laptop driver
ledtrig_audio : LED trigger for audio mute control
gpio_ich : GPIO interface for Intel ICH series
dell_smbios : Common functions for kernel modules using Dell SMBIOS
dell_wmi_descriptor : Dell WMI descriptor driver
dcdbas : Dell Systems Management Base Driver (version 5.6.0-3.3)
dell_smm_hwmon : Dell laptop SMM BIOS hwmon driver
ipw2200 : Intel(R) PRO/Wireless 2200/2915 Network Driver
serio_raw : Raw serio driver
snd_intel8x0 : Intel 82801AA,82901AB,i810,i820,i830,i840,i845,MX440; SiS 7012; Ali 5455
libipw : 802.11 data/management/control stack
pcmcia : PCMCIA Driver Services
joydev : Joystick device interfaces
input_leds : Input -> LEDs Bridge
snd_ac97_codec : Universal interface for Audio Codec '97
yenta_socket
lib80211 : common routines for IEEE802.11 drivers
ac97_bus
pcmcia_rsrc
lpc_ich : LPC interface for Intel ICH
snd_pcm : Midlevel PCM code for ALSA.
cfg80211 : wireless configuration support
pcmcia_core : Linux Kernel Card Services
ip6t_REJECT : Xtables: packet "rejection" target for IPv6
nf_reject_ipv6
mac_hid
snd_timer : ALSA timer interface
nf_log_ipv6 : Netfilter IPv6 packet logging
snd : Advanced Linux Sound Architecture driver for soundcards.
xt_hl : Xtables: Hoplimit/TTL field match
soundcore : Core sound module
ip6t_rt : Xtables: IPv6 Routing Header match
ipt_REJECT : Xtables: packet "rejection" target for IPv4
nf_reject_ipv4
nf_log_ipv4 : Netfilter IPv4 packet logging
nf_log_common
xt_LOG : Xtables: IPv4/IPv6 packet logging
xt_limit : Xtables: rate-limit match
xt_tcpudp : Xtables: TCP, UDP and UDP-Lite match
xt_addrtype : Xtables: address type match
xt_conntrack : Xtables: connection tracking state match
ip6table_filter : ip6tables filter table
ip6_tables : IPv6 packet filter
nf_conntrack_netbios_ns : NetBIOS name service broadcast connection tracking helper
nf_conntrack_broadcast
nf_nat_ftp : ftp NAT helper
nf_nat
nf_conntrack_ftp : ftp connection tracking helper
nf_conntrack
nf_defrag_ipv6
sch_fq_codel
nf_defrag_ipv4
iptable_filter : iptables filter table
zram : Compressed RAM Block Device
bpfilter
parport_pc : PC-style parallel port driver
ppdev
lp
parport
ip_tables : IPv4 packet filter
x_tables : {ip,ip6,arp,eb}_tables backend module
autofs4
btrfs
xor
zstd_compress : Zstd Compressor
raid6_pq : RAID6 Q-syndrome calculations
libcrc32c : CRC32c (Castagnoli) calculations
nouveau : nVidia Riva/TNT/GeForce/Quadro/Tesla/Tegra K1+
hid_generic : HID generic driver
mxm_wmi : MXM WMI Driver
wmi : ACPI-WMI Mapping Driver
i2c_algo_bit : I2C-Bus bit-banging algorithm
ttm : TTM memory manager subsystem (for DRM device)
drm_kms_helper : DRM KMS helper
usbhid : USB HID core driver
syscopyarea : Generic copyarea (sys-to-sys)
hid
sysfillrect : Generic fill rectangle (sys-to-sys)
sysimgblt : 1-bit/8-bit to 1-32 bit color expansion (sys-to-sys)
fb_sys_fops : Generic file read (fb in system RAM)
pata_acpi : SCSI low-level driver for ATA in ACPI mode
firewire_ohci : Driver for PCI OHCI IEEE1394 controllers
sdhci_pci : Secure Digital Host Controller Interface PCI driver
drm : DRM shared core routines
ahci : AHCI SATA low-level driver
cqhci : Command Queue Host Controller Interface driver
psmouse : PS/2 mouse driver
firewire_core : Core IEEE1394 transaction logic
libahci : Common AHCI SATA low-level routines
sdhci : Secure Digital Host Controller Interface core driver
crc_itu_t : CRC ITU-T V.41 calculations
video : ACPI Video Driver

wxl · January 31, 2021, 11:57pm

You just provided none of this information I asked for.

Use lspci -nnk and provide ONLY the information related to the card.

aug7744 · February 1, 2021, 12:13am

03:03.0 Network controller [0280]: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection [8086:4220] (rev 05)
Subsystem: Intel Corporation Dell B130 laptop integrated WLAN [8086:2721]
Kernel driver in use: ipw2200
Kernel modules: ipw2200

wxl · February 1, 2021, 12:33am

Looking in your logs, do you find any references to network errors or better, that particular kernel module ipw2200? If so, let’s see them.

aug7744 · February 1, 2021, 1:18am

I not see any error.
Few months using Linux Lubuntu and not crashes how was with windows, thus if Lubuntu use errors logs where is the network log to post here ?
I only need figure if yes or not possible automatic reconnect when connection drop because weak signal.
When connection drop is displayed an window to press to reconnect. I want avoid it.

wxl · February 1, 2021, 7:04pm

It does automatically reconnect, unless something is wrong. It sounds like you don’t know where your logs are. Try journalctl.

aug7744 · February 1, 2021, 11:52pm

Thanks for your reply

The last log lines before connection drop are :

fev 01 20:07:19 A2 NetworkManager[717]: [1612220839.0779] device (wlp3s3): supplicant interface state: 4-way handshake
fev 01 20:07:20 A2 wpa_supplicant[716]: wlp3s3: CTRL-EVENT-DISCONNECTED bssid=1c:3b:f3:3c:22:c6 reason=0
fev 01 20:07:20 A2 NetworkManager[717]: [1612220840.0911] device (wlp3s3): supplicant interface state: completed → di
fev 01 20:07:20 A2 NetworkManager[717]: [1612220840.1913] device (wlp3s3): supplicant interface state: disconnected →
fev 01 20:07:20 A2 wpa_supplicant[716]: wlp3s3: Trying to associate with 1c:3b:f3:3c:22:c6 (SSID=‘Oliveira’ freq=2422 MHz)
fev 01 20:07:20 A2 wpa_supplicant[716]: wlp3s3: Association request to the driver failed
fev 01 20:07:20 A2 NetworkManager[717]: [1612220840.3980] device (wlp3s3): supplicant interface state: scanning → ass
fev 01 20:07:22 A2 wpa_supplicant[716]: wlp3s3: Associated with 1c:3b:f3:3c:22:c6
fev 01 20:07:22 A2 NetworkManager[717]: [1612220842.1300] device (wlp3s3): supplicant interface state: associating →
fev 01 20:07:22 A2 NetworkManager[717]: [1612220842.2220] device (wlp3s3): supplicant interface state: associated → 4
fev 01 20:07:22 A2 wpa_supplicant[716]: wlp3s3: WPA: Key negotiation completed with 1c:3b:f3:3c:22:c6 [PTK=CCMP GTK=TKIP]
fev 01 20:07:22 A2 wpa_supplicant[716]: wlp3s3: CTRL-EVENT-CONNECTED - Connection to 1c:3b:f3:3c:22:c6 completed [id=0 id_str=
fev 01 20:07:22 A2 wpa_supplicant[716]: bgscan simple: Failed to enable signal strength monitoring
fev 01 20:07:22 A2 NetworkManager[717]: [1612220842.2533] device (wlp3s3): supplicant interface state: 4-way handshake
…skipping…
fev 01 20:06:56 A2 NetworkManager[717]: [1612220816.4876] device (wlp3s3): supplicant interface state: 4-way handshake
fev 01 20:06:56 A2 NetworkManager[717]: [1612220816.4910] device (wlp3s3): Activation: (wifi) Stage 2 of 5 (Device Con
fev 01 20:06:56 A2 NetworkManager[717]: [1612220816.4938] device (wlp3s3): state change: config → ip-config (reason ’
fev 01 20:06:56 A2 NetworkManager[717]: [1612220816.5121] dhcp4 (wlp3s3): activation: beginning transaction (timeout i
fev 01 20:06:56 A2 NetworkManager[717]: [1612220816.5550] dhcp4 (wlp3s3): dhclient started with pid 3168
fev 01 20:06:56 A2 avahi-daemon[710]: Withdrawing address record for fe80::1690:2308:b3ce:525 on wlp3s3.
fev 01 20:06:56 A2 avahi-daemon[710]: Leaving mDNS multicast group on interface wlp3s3.IPv6 with address fe80::1690:2308:b3ce:
fev 01 20:06:56 A2 avahi-daemon[710]: Interface wlp3s3.IPv6 no longer relevant for mDNS.
fev 01 20:06:56 A2 avahi-daemon[710]: Joining mDNS multicast group on interface wlp3s3.IPv6 with address fe80::a036:a591:819b:
fev 01 20:06:56 A2 avahi-daemon[710]: New relevant interface wlp3s3.IPv6 for mDNS.
fev 01 20:06:56 A2 avahi-daemon[710]: Registering new address record for fe80::a036:a591:819b:612e on wlp3s3.*.
fev 01 20:06:56 A2 dhclient[3168]: DHCPREQUEST of 192.168.0.102 on wlp3s3 to 255.255.255.255 port 67 (xid=0x6bb539f4)
fev 01 20:06:58 A2 NetworkManager[717]: [1612220818.0513] dhcp6 (wlp3s3): activation: beginning transaction (timeout i
fev 01 20:06:58 A2 NetworkManager[717]: [1612220818.0670] dhcp6 (wlp3s3): dhclient started with pid 3178
fev 01 20:06:58 A2 dhclient[3178]: XMT: Solicit on wlp3s3, interval 1080ms.
fev 01 20:06:58 A2 dhclient[3178]: RCV: Advertise message on wlp3s3 from fe80::1e3b:f3ff:fe3c:22c6.
fev 01 20:06:59 A2 dhclient[3178]: XMT: Solicit on wlp3s3, interval 2250ms.
fev 01 20:06:59 A2 dhclient[3178]: RCV: Advertise message on wlp3s3 from fe80::1e3b:f3ff:fe3c:22c6.
fev 01 20:06:59 A2 dhclient[3168]: DHCPREQUEST of 192.168.0.102 on wlp3s3 to 255.255.255.255 port 67 (xid=0x6bb539f4)
fev 01 20:06:59 A2 dhclient[3168]: DHCPACK of 192.168.0.102 from 192.168.0.1
fev 01 20:06:59 A2 NetworkManager[717]: [1612220819.7406] dhcp4 (wlp3s3): address 192.168.0.102
fev 01 20:06:59 A2 NetworkManager[717]: [1612220819.7430] dhcp4 (wlp3s3): plen 24 (255.255.255.0)
fev 01 20:06:59 A2 NetworkManager[717]: [1612220819.7437] dhcp4 (wlp3s3): gateway 192.168.0.1
fev 01 20:06:59 A2 NetworkManager[717]: [1612220819.7444] dhcp4 (wlp3s3): lease time 86400
fev 01 20:06:59 A2 NetworkManager[717]: [1612220819.7445] dhcp4 (wlp3s3): nameserver ‘8.8.8.8’
fev 01 20:06:59 A2 NetworkManager[717]: [1612220819.7445] dhcp4 (wlp3s3): nameserver ‘8.8.4.4’
fev 01 20:06:59 A2 NetworkManager[717]: [1612220819.7446] dhcp4 (wlp3s3): state changed unknown → bound
fev 01 20:06:59 A2 NetworkManager[717]: [1612220819.7745] device (wlp3s3): state change: ip-config → ip-check (reason
fev 01 20:06:59 A2 NetworkManager[717]: [1612220819.7907] device (wlp3s3): state change: ip-check → secondaries (reas
fev 01 20:06:59 A2 NetworkManager[717]: [1612220819.7999] device (wlp3s3): state change: secondaries → activated (rea
fev 01 20:06:59 A2 NetworkManager[717]: [1612220819.8045] manager: NetworkManager state is now CONNECTED_SITE
fev 01 20:06:59 A2 dhclient[3168]: bound to 192.168.0.102 – renewal in 36610 seconds.
fev 01 20:06:59 A2 NetworkManager[717]: [1612220819.8408] device (wlp3s3): Activation: successful, device activated.
fev 01 20:06:59 A2 NetworkManager[717]: [1612220819.8686] manager: NetworkManager state is now CONNECTED_GLOBAL
fev 01 20:06:59 A2 dbus-daemon[712]: [system] Activating via systemd: service name=‘org.freedesktop.nm_dispatcher’ unit='dbus-
fev 01 20:06:59 A2 whoopsie[830]: [20:06:59] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/9
fev 01 20:06:59 A2 whoopsie[830]: [20:06:59] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/9
fev 01 20:06:59 A2 whoopsie[830]: [20:06:59] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/9
fev 01 20:06:59 A2 whoopsie[830]: [20:06:59] online
fev 01 20:06:59 A2 systemd[1]: Starting Network Manager Script Dispatcher Service…
fev 01 20:06:59 A2 dbus-daemon[712]: [system] Successfully activated service ‘org.freedesktop.nm_dispatcher’
fev 01 20:06:59 A2 systemd[1]: Started Network Manager Script Dispatcher Service.
fev 01 20:06:59 A2 nm-dispatcher[3191]: req:1 ‘connectivity-change’: new request (1 scripts)
fev 01 20:06:59 A2 nm-dispatcher[3191]: req:1 ‘connectivity-change’: start running ordered scripts…
fev 01 20:07:01 A2 dhclient[3178]: XMT: Solicit on wlp3s3, interval 4590ms.
fev 01 20:07:01 A2 dhclient[3178]: RCV: Advertise message on wlp3s3 from fe80::1e3b:f3ff:fe3c:22c6.
fev 01 20:07:06 A2 dhclient[3178]: XMT: Solicit on wlp3s3, interval 9100ms.
fev 01 20:07:06 A2 dhclient[3178]: RCV: Advertise message on wlp3s3 from fe80::1e3b:f3ff:fe3c:22c6.
fev 01 20:07:15 A2 dhclient[3178]: XMT: Solicit on wlp3s3, interval 18850ms.
fev 01 20:07:15 A2 wpa_supplicant[716]: wlp3s3: CTRL-EVENT-DISCONNECTED bssid=1c:3b:f3:3c:22:c6 reason=0

wxl · February 2, 2021, 12:13am

Anything specific to the driver? Try journalctl -t ipw2200.

aug7744 · February 2, 2021, 12:20am

I am an new Linux user and long time windows user and need post here an truth … Linux is much more simple to configure and manage than windows and the only details more hard in Linux is some configuration are more detailed than windows thus using more commands, even thus Linux is much less time to configure.
I has regrets not had tested Linux much time before

running “journalctl -t ipw2200”
– Logs begin at Fri 2020-10-23 14:08:11 -03, end at Mon 2021-02-01 21:13:30 -03. –
– No entries –

is being displayed using wlp3s3
if using journalctl -t wlp3s3
– Logs begin at Fri 2020-10-23 14:08:11 -03, end at Mon 2021-02-01 21:21:45 -03. –
– No entries –

wxl · February 2, 2021, 1:25am

You will find there’s one problem with Linux, which actually isn’t a problem in Linux at all: many hardware manufacturers never ensure compatibility with the Linux kernel, don’t support it, and make their software proprietary and closed source so no one can figure out how to get it working. Despite that, kernel developers have often reverse engineered perfectly suitable solutions to the problem.

And then there’s the other problem: supporting old hardware. Windows is TERRIBLE at this whereas Linux is pretty good. Even still, eventually, drivers stop being maintained often when the manufacturer’s support for that hardware stops. Your card is pretty darn old and you can see quite clearly that it’s no longer maintained, so that’s not something in your favor.

That said, we’re kind of grasping in the dark here. What I can tell you is your problem is not specific to Lubuntu, but really all Ubuntu versions and is likely just as applicable to Debian and probably any other Linux distro using the same kernel. That said, you may not want to limit your inquiry to just here.

Most documents online insist on installing the firmware. If ls /lib/firmware/ipw2200* returns results, you should be fine there.

You should use dmesg -H and look through for any lines related to your card or the driver. Go through it extremely slowly and carefully. Any errors there might be helpful. DO NOT look for the sorts of information you posted above. We’re trying to figure out with this how the driver and firmware loaded and if any errors were produced.

This is about the most complete document I could find. Outside of a potential solution to WPA problems (which I would presume are issues establishing a connection, but who knows), there is a link to this which suggests that some access points are problematic with these cards, so that might be your problem. Possible solutions to this problem are:

As Intel suggests, turn off power management with ipwconfig wlp3s3 power off. This is likely the right solution.
Upgrade the firmware in your Access Point but that’s probably not easy.
Disable 802.11g and only use 802.11b, but that seems questionable in my mind.
Forcing a rate reduction with ipwconfig wlp3s3 rate 1M but that’s probably not ideal.

Beyond that, all I can say is good luck.

aug7744 · February 2, 2021, 1:53am

“You will find there’s one problem with Linux, which actually isn’t a problem in Linux at all”
Exactly.

“And then there’s the other problem: supporting old hardware. Windows is TERRIBLE at this whereas Linux is pretty good.”
THANKS FOR POST ABOUT IT !
I am an advanced windows user since 9X to 10 and some details in windows are an extreme mess mainly system folders.
is much detail to say here about for me how has worst details in windows being how NTFS trash the disk, registry size and etc.
Linux use text configurations and windows use huge registry files using more process and more time to startup.
Linux software install is much better than windows.
Much more others details are better and even Nvidia not having the same driver support for Linux how does for windows I see Vulkan running much better than in same machine using windows.
WINE in future versions running very well W10 softwares will be amazing.

Not was simple to figure the Linux distro for me.
Lubuntu was my choice because remember using windows with winreducer-ex.

In moment trying to understand how BTRFS works because configuring FSTAB and trying fixing the error “cache and super generation don’t match, space cache will be invalidated” using “BTRFS check --readonly --force --clear-space-cache v1” had damaged an disk partition at point to be not recovered even using --readonly.

I need more time also for ZFS in my little knownledge looks being better and less problems to recover than BTRFS, but look how use much RAM being an detail much avoided in Lubuntu.
The only detail that need in Linux is about write back for disk partitions thus how I had used in windows with Primocache.
Today Primocahe is possibly the best tool for windows 10. Is possible create write back buffer using defer write thus avoiding multiples repeated files writes on HDD and SDD.
In 10 hours using an 256 MB write cache buffer for system partition only less of 300 MB was really flushed on disk being not using primocache will be more of 2 GB repeated same files being writed on disk.
I has configured for BTRFS partition in fstab commit=3600, but look how not is exactly having defer write to flush data to disk. Linux is writing much data in system partition even not writing any user data. I need to configure how avoid repeated writes on disk.

“What I can tell you is your problem is not specific to Lubuntu, but really all Ubuntu versions and is likely just as applicable to Debian and probably any other Linux distro using the same kernel.”
Since begin I had posted trying to figure if is an configuration or setting using Lubuntu configuration.

Thanks very much for your reply about the details above.
Now used `iwconfig wlp3s3 power off.
all details above about the wireless card not allow Bionic to reconnect when wifi signal drop ? not has any configuration about it ?

Have an nice week.

system · March 4, 2021, 1:53am

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.