Tag Info

Hot answers tagged

5

This is essentially Warwick's answer, just with step-by-step instructions. Create the following shell script in your home folder: check_inet.sh #!/bin/bash TMP_FILE=/tmp/inet_up # Edit this function if you want to do something besides reboot no_inet_action() { shutdown -r +1 'No internet.' } if ping -c5 google.com; then echo 1 > $TMP_FILE ...


4

One way would be to put an entry in root's cron that runs a script every 30 minutes. The script would test the WIFI connection, perhaps using ping, and write the result to a file in /tmp - 1 for connection exists, 0 if it doesn't. Subsequent iterations of the script would then check that file, and if it was 0, and the WIFI connection was still bad, run an ...


2

It seems that this has been a common request for at least the last five years, but progress is slow. You could always ditch Network Manager and manually control your Wi-Fi network by configuring wpa_supplicant to priorotise your network. Details here, but it seems a lot of work. It would also mean manually scanning for and configuring each new network you ...


2

Find out the interface name, by running iwconfig $ iwconfig eth0 no wireless extensions. lo no wireless extensions. wlan0 IEEE 802.11bgn ESSID:"EvanCarroll" Mode:Managed Frequency:2.437 GHz Access Point: D8:50:E6:44:B2:C8 Bit Rate=19.5 Mb/s Tx-Power=15 dBm Retry long limit:7 RTS thr:off ...


2

First see if the interface got a IP address, using ip addr show or ifconfig # ip addr show ... 3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:24:d7:ae:dc:64 brd ff:ff:ff:ff:ff:ff inet 10.0.0.8/24 brd 10.0.0.255 scope global dynamic wlp3s0 valid_lft 3596sec preferred_lft ...


1

The problem you are experiencing is because your system's hostname is changing. Originally your hostname was localhost, but after connecting it becomes localhost.localdomain. This can cause problems due to either of the following: 1. hostname resolution If the new hostname (localhost.localdomain) doesn't resolve properly, processes which use IP based ...


1

This bug is currently being investigated by the developers. It seems the outbound traffic may be being mis-accounted and assigned to the physical device (iwn0 or ath0, etc) instead of wlan0 try these two commands to confirm: netstat -I wlan0 -i 1 (shows only incoming traffic) netstat -I ath0 -i 1 (shows only outgoing traffic) See this thread: ...


1

I finally got my Wireless card working in Powerbook G4 Aluminum 1.25Ghz laptop running Debian 7.5.0 Wheezy. 1) go to /etc/apt/sources.list, add 'contrib' and 'non-free' behind every line ( it's an overkill but I don't know what I am doing ) Here is part of my file: deb cdrom:[Debian GNU/Linux 7.5.0 _Wheezy_ - Official powerpc DVD Binary-1 20140426-14:34]/ ...



Only top voted, non community-wiki answers of a minimum length are eligible