Question

1

My wi-fi auto connect after very long time (about 5 minutes)

rated 0 times [ 1] [ 0] / answers: 1 / hits: 1687 / 2 Years ago, sat, april 23, 2022, 8:56:21

Every time I start my computer I have to press twice F12 in order to deactivate and reactivate WI FI, and just after that my connection starts (in a few seconds). Is it a way to make it start automatically?
Complementary info: If I don’t press twice F12, it takes about 5 minutes to auto-connect - as I just discovered
Complementary info: It seems that it was an illusion the fact that pressing twice F12 shorten the connection time. Now every time I have to wait about 5 minutes.

[From OP]

[  336.774812] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

[  336.775300] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

[  338.236603] wlan0: authenticate with dc:02:8e:63:b9:10

[  338.244241] wlan0: send auth to dc:02:8e:63:b9:10 (try 1/3)

[  338.245846] wlan0: authenticated

[  338.247641] wlan0: associate with dc:02:8e:63:b9:10 (try 1/3)

[  338.250925] wlan0: RX AssocResp from dc:02:8e:63:b9:10 (capab=0x411 status=0 aid=1)

[  338.251034] wlan0: associated

[  338.251059] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

[ 2592.514180] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

[ 2696.299008] wlan0: authenticate with dc:02:8e:63:b9:10

[ 2696.308971] wlan0: send auth to dc:02:8e:63:b9:10 (try 1/3)

[ 2696.319632] wlan0: authenticated

[ 2696.320512] wlan0: associate with dc:02:8e:63:b9:10 (try 1/3)

[ 2696.328968] wlan0: RX AssocResp from dc:02:8e:63:b9:10 (capab=0x411 status=0 aid=1)

[ 2696.329083] wlan0: associated

[ 2696.329161] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

itutejagua

Add To Favorites

Follow

Total Points: 89

Total Questions: 124

Total Answers: 113

Location: British Indian Ocean Territory

Member since Sun, Feb 13, 2022

2 Years ago

answered 2 Years ago listeerrated · Accepted Answer

This could be a workaround.

Create a Upstart file in the folder "/etc/init/startup-network-reset.conf".

The content should be:

description "Network restart at system startup"



start on (started network-interface

          or started network-manager

          or started networking)

stop on runlevel [!2345]



script

  sudo -u root service network-manager restart

end script

Perhaps an delay before restarting with sleep should be added.

For further details to the Upstart functions look at this page: http://upstart.ubuntu.com/cookbook/