Wireless connectivity on PC boot up

I’m getting wireless connectivity problems between my PC and the BTHub3.
After booting the computer I find I have no connectivity at all. The message I receive when attempting to manually connect is ‘The settings saved on this computer for the network do not match the requirements of the network’
This hasn’t always been the case. The issue seems to have started within the last month. Normally connectivity would be made almost instantly. Frustratingly, I can instantly connect to other (unsecured) BT networks in the neighbourhood. Other local networks (secured and unsecured) even appear to have a stronger signal than that from my router, if the number of bars are to be believed.
I am using a Linksys wireless adapter. Settings for security are WPA2 Personal and Encryption type AES.
I have systematically tried
-          deleting and recreating profiles
-          re-entering passwords
-          rebooting the Hub
-          rebooting the PC
-          changing channels
-          changing the BT hub ( new hub, vanilla settings)
Nothing appears to make an impact. If I wait anything between half an hour to an hour eventually everything connects even if I have not touched a single setting. Usually I sit playing solitaire until I connect. So Settings appear to be an issue initially but this issue goes away ???
Initially I believed it was a PC/PC adapter issue. But I took a look at the connectivity on my Blackberry and also my Kindle – same issue. So I now believe that something is not set correctly in the router (or unbelievably two routers have failed).
But where to look – Suggestions?

If it supports PPPoE, and has a WAN port, or the facility to map one ot its LAN ports, then you could use it.
It may also be possible to use the device as a wireless access port.
I am moving this to the Infinity board, as you have an Infinity and not an ADSL connection.
There are some useful help pages here, for BT Broadband customers only, on my personal website.
BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

Similar Messages

IBook won't boot after broken wireless connection trying to update OS

Trying to help my kid with his iBook via telephone calls. He was updating the OS over a wireless connection, lost the signal which apparently froze the machine. When he rebooted it wouldn't go past the blue start-up screen with a spinning gear. He's used the install disk and disk repair, which said it repaired one volume but not a second one (not sure what that means). But no luck with rebooting back into his machine. He then tried to boot up in "safe mode" but that doesn't work; gets the blue screen and spinning gear again. He's got a lot of stuff on his hard drive and is understandably concerned about the best way to get the machine back to normal and still have the contents of the hard drive. Any suggestions? Thanks in advance for any help.

Really needs to fix that HD, if DU can't do it, try, If DiskWarrior can't fix it, you might try Data Rescue II...
http://www.alsoft.com/DiskWarrior/
http://www.prosofteng.com/products/data_rescue.php
(Has a Free Demo to see if it could or not, but you'll need another drive to recover to).
Or FileSalvage...
http://www.subrosasoft.com/OSXSoftware/index.php?%20mainpage=product_info&productsid=1
to recover what you can.
If the good partition is the boot partition, then Archive & Install
http://docs.info.apple.com/article.html?artnum=107120

I get wireless connection but my internet does not work on my ipad 2

I get wireless connection but my internet does not work on my ipad 2

Some things to try first:
1. Turn Off your iPad. Then turn Off (disconnect power cord for 30 seconds or longer) the wireless router & then back On. Now boot your iPad. Hopefully it will see the WiFi.
2. Go to Settings>Wi-Fi and turn Off. Then while at Settings>Wi-Fi, turn back On and chose a Network.
3. Change the channel on your wireless router (Auto or Channel 6 is best). Instructions at http://macintoshhowto.com/advanced/how-to-get-a-good-range-on-your-wireless-netw ork.html
4. Go into your router security settings and change from WEP to WPA with AES.
5. Renew IP Address: (especially if you are droping internet connection)
    •    Launch Settings app
    •    Tap on Wi-Fi
    •    Tap on the blue arrow of the Wi-Fi network that you connect to from the list
    •    In the window that opens, tap on the Renew Lease button
~~~~~~~~~~~~~~~~~~~~~~~~~
iOS 6 Wifi Problems/Fixes
Fix For iOS 6 WiFi Problems?
http://tabletcrunch.com/2012/09/27/fix-ios-6-wifi-problems/
Did iOS 6 Screw Your Wi-Fi? Here’s How to Fix It
http://gizmodo.com/5944761/does-ios-6-have-a-wi+fi-bug
How To Fix Wi-Fi Connectivity Issue After Upgrading To iOS 6
http://www.iphonehacks.com/2012/09/fix-wi-fi-connectivity-issue-after-upgrading- to-ios-6.html
iOS 6 iPad 3 wi-fi "connection fix" for netgear router
http://www.youtube.com/watch?v=XsWS4ha-dn0
Apple's iOS 6 Wi-Fi problems
http://www.zdnet.com/apples-ios-6-wi-fi-problems-linger-on-7000004799/
~~~~~~~~~~~~~~~~~~~~~~~
Look at iOS Troubleshooting Wi-Fi networks and connections http://support.apple.com/kb/TS1398
iPad: Issues connecting to Wi-Fi networks http://support.apple.com/kb/ts3304
WiFi Connecting/Troubleshooting http://www.apple.com/support/ipad/wifi/
How to Fix: My iPad Won't Connect to WiFi
http://ipad.about.com/od/iPad_Troubleshooting/ss/How-To-Fix-My-Ipad-Wont-Connect -To-Wi-Fi.htm
iOS: Connecting to the Internet http://support.apple.com/kb/HT1695
iOS: Recommended settings for Wi-Fi routers and access points http://support.apple.com/kb/HT4199
How to Quickly Fix iPad 3 Wi-Fi Reception Problems
http://osxdaily.com/2012/03/21/fix-new-ipad-3-wi-fi-reception-problems/
iPad Wi-Fi Problems: Comprehensive List of Fixes
http://appletoolbox.com/2010/04/ipad-wi-fi-problems-comprehensive-list-of-fixes/
Fix iPad Wifi Connection and Signal Issues http://www.youtube.com/watch?v=uwWtIG5jUxE
Fix Slow WiFi Issue https://discussions.apple.com/thread/2398063?start=60&tstart=0
How To Fix iPhone, iPad, iPod Touch Wi-Fi Connectivity Issue http://tinyurl.com/7nvxbmz
Unable to Connect After iOS Update - saw this solution on another post.
https://discussions.apple.com/thread/4010130
Note - When troubleshooting wifi connection problems, don't hold your iPad by hand. There have been a few reports that holding the iPad by hand, seems to attenuate the wifi signal.
~~~~~~~~~~~~~~~
If any of the above solutions work, please post back what solved your problem. It will help others with the same problem.
 Cheers, Tom

Having a problem with wireless connection. On my Windows XP 32 bit system and a 6510 printer, initi

On my Dell Latitude D620, Windows XP 32 bit system and my 6510 printer wireless connection (Linksys EA4500) , everything works fine after the computer is booted. After a period of time (usually overnight), I lose connection to the printer (the scanner icon with a red x is shown on my Windows task bar and I can't print. Ran Windows Fix and the HP fix programs. The only thing that solves it is to reboot the computer. A second symptom is that my IE8 stops connecting to the internet at the same time (gives a 'waiting for' response that never changes). Firefox still connects OK when this is happening. So I suspect the problem isn't with the printer, but with my Windows set up. It is a fresh XP SP3 install (hard drive crashed, but it happened before also). I reset IE, checked my proxy, no malware, happens with or without firewalls and security programs.
Hoping that someone else has run into this problem. Been all over Google, and the IE doesn't work / Firefox works is fairly common, but none of the fixes helps.

If you want you can reload Firefox 4.0 or the last "old" version is 3.6.16 and is available here:
http://www.mozilla.com/en-US/firefox/all-older.html
Just reinstall your choice of FF. The bookmarks are in a different directory and are NOT overwritten. Some of the Add-ons that worked in 3.6 DO NOT work with 4.0, pay attention and head any warnings when you start 4.0.
I had to disable extensions: Flashblock and WOT
Firefox SafeMode? - A troubleshooting mode.
1.You can open the Firefox 4.0 SafeMode by holding the Shft key when you use the Firefox desktop or Start menu shortcut.
To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before using the Firefox shortcut to open it again.
For more help, see this: http://support.mozilla.com/en-US/kb/troubleshooting+extensions+and+themes
Hope this helps you out.
Feedback is appreciated especially if this helps you out.

Kernel 2.6.27.7 & xorg 1.5.3 - Wireless connection died & weird dwm

i did a clean FTP install of arch x86_64 and i configured my wlan0 wireless card (its a TP-Link tl wn321g usb wifi card), when i did a pacman -Syu today, the connection got stablished but i could't browse or open any internet site, like there was no connection, the latest Syu updates the kernel i think 2.6.27.7 and the nvidia drivers, now the connection is giving me this error when i do a sudo /etc/rc.d/network restart
SIOCDELRT: No such process
and so my dwm session is working weird:
- some keybindings are not working
- the urxvt's are not maximized and exists in all tags
seems that the latest update broke them, am I the only one with this kind of problem, after these updates?
Edit: I see the other posts about the new xorg... so i think i must wait until this gets solved, but my real concern it's about my wireless connection, downgrading the kernel package did no effect
Last edited by leo2501 (2008-12-01 01:44:19)

it use the rt2500usb rt2x00 rt73usb and i try to do everything manually with the same results, i added wlan to rc.conf and all to connect automatically at boot, so it connects but i dont have connection, i mean with a iwconfig i see that the essid is correct and connected, but i can't access any internet

Wireless connection problems with iTunes

After installing iTunes for my PC(using Windows Vista if that matters). Directly after installing iTunes my wireless connection works. Once I start importing my music into iTunes I lose my wireless connection. I can still see the wireless networks but I can no longer connect to any of them.
Does anyone know whats causing this problem. Once I deleted iTunes from my computer my networks started working properly again after rebooting. I tried to download it again and the same thing happened yet again. After deleting agin I am still unable to connect to my wireless conection.

I just saw your post and I resolved this on mine for my wired connection. I'm willing to bet that the issue is the same for wireless. Here's what I found.
Issue:
During the installation, iTunes installs some network components related to mobile device support over ethernet(Apple Mobile Device Ethernet Service - netaapl.inf). At the same time, according the logs, the install process removed OEM18.inf. This almost exactly coincided with the time that I saw the network connection die (preceded it by a few seconds).
Basically, iTunes appears to be removing a required network component.
Resolution:
After installing iTunes and the network connection breaking, remove the network device from Device Manager and allow Windows to reinstall it automatically.
The following instructions are for Windows 7, but they are close enough to follow for other versions of Windows.
1. Click the Start button (Jewel in Vista and Win7).
2. Right-click Computer and click Manage in the menu that appears (type your password or click Yes if prompted).
3. On the left side of hte Computer Management window, click Device Manager.
4. Click the arrow (or plus sign) next to Network Adapters to expand that section.
5. Right-click your network adapter and click Uninstall in the menu that appears.
6. Click OK.
7. Reboot.
Windows should automatically detect and reinstall your network device on boot.

IMac and other Apple devices lose wireless connections

We have two Apple iMacs, a MacBook Pro, an iPad and iPad2 and they all intermittently lose their Wireless connection to my network. All of my PC's work just fine and stay connected. This is funny... the MacBook Pro booted to Windows 7 Pro stays connected, but the MacOS doesn't.
It appears to be a problem with DNS, because if you ping to a remote host, you get a response back. Also, if you put an IP address into Safari on the iMac and MacBook then a site will come online. However, the iPads just say "You are not connected" while in Safari. I have verified that I'm using the correct DNS addresses provided by my ISP, and I have a Windows Domain server running DHCP/DNS on the inside of my firewall.
We recently moved and were issued a new wireless router by our ISP. I was thinking that might be the problem, but then we don't have the problem with any of the Windows PCs. This router is manufactured by Arris. My other router was a Cisco that worked like a champ.
Turning off the Airport feature and turning it back on restores Web Browsing capability. Interestingly, if I have a remote desktop session running, it never gets disconnected even when the web stops working. Again, symptoms point to DNS issues.

If you feel it's DNS related then change the DNS setting to:
1. System preferences
2. Network
3. Click Advanced
4. Click DNS tab
5. Click + sign
6. Add 208.67.222.222
7. Click + sign
8. Add 208.67.220.220
9. Click OK.
10. Exit System Preferences

Wireless Connection Sometimes Requires A Reboot To Work

I have had this going on for about two months. My wireless connection will work fine for a while and then suddenly slow down and eventually drop out completely. A reboot is the only thing that brings it back, but the cycle always starts over again. I've posted a few logs here, but if there is something more someone needs please let me know. The Arch system is the only device on my network that is experiencing this issue. I've also tried adding options ath9k nohwcrypt=1 to /etc/modprobe.d/ath9k.conf. I thought this had worked until today when I booted up and eventually had the same issue. I am running the x86_x64 variant of Arch with kernel 3.18.4-1-ARCH #1. The position of all my equipment remains unchanged so I'm guessing either the card is dying or I have a bug. Any insight is appreciated. Thanks.
journalctl -u wlp2s0
Jan 30 09:16:08 GatewayNV79 kernel: ath9k 0000:02:00.0 wlp2s0: renamed from wlan0
Jan 30 09:16:13 GatewayNV79 netctl-auto[332]: Included profile 'wlp2s0-OpenWrt'
Jan 30 09:16:14 GatewayNV79 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Jan 30 09:16:15 GatewayNV79 wpa_actiond[389]: Starting wpa_actiond session for interface 'wlp2s0'
Jan 30 09:16:16 GatewayNV79 kernel: wlp2s0: authenticate with 00:03:7f:bf:a3:0f
Jan 30 09:16:17 GatewayNV79 kernel: wlp2s0: send auth to 00:03:7f:bf:a3:0f (try 1/3)
Jan 30 09:16:17 GatewayNV79 kernel: wlp2s0: authenticated
Jan 30 09:16:17 GatewayNV79 kernel: wlp2s0: associate with 00:03:7f:bf:a3:0f (try 1/3)
Jan 30 09:16:17 GatewayNV79 kernel: wlp2s0: RX AssocResp from 00:03:7f:bf:a3:0f (capab=0x411 status=0 aid=3)
Jan 30 09:16:17 GatewayNV79 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
Jan 30 09:16:17 GatewayNV79 kernel: wlp2s0: associated
Jan 30 09:16:18 GatewayNV79 ntpd[432]: unable to create socket on wlp2s0 (4) for fe80::721a:4ff:fee0:702f%3#123
Jan 30 09:16:18 GatewayNV79 wpa_actiond[389]: Interface 'wlp2s0' connected to network 'OpenWrt'
Jan 30 09:16:18 GatewayNV79 systemd-networkd[330]: wlp2s0 : gained carrier
Jan 30 09:16:18 GatewayNV79 ntpd[432]: 30 Jan 09:16:18 ntpd[432]: unable to create socket on wlp2s0 (4) for fe80::721a:4ff:fee0:702f%3#123
Jan 30 09:16:19 GatewayNV79 avahi-daemon[333]: Registering new address record for fe80::721a:4ff:fee0:702f on wlp2s0.*.
Jan 30 09:16:20 GatewayNV79 dhcpcd[759]: wlp2s0: IAID 04:e0:70:2f
Jan 30 09:16:20 GatewayNV79 avahi-daemon[333]: Registering new address record for fdeb:3a5d:7d34:0:721a:4ff:fee0:702f on wlp2s0.*.
Jan 30 09:16:20 GatewayNV79 avahi-daemon[333]: Withdrawing address record for fe80::721a:4ff:fee0:702f on wlp2s0.
Jan 30 09:16:21 GatewayNV79 dhcpcd[759]: wlp2s0: soliciting a DHCP lease
Jan 30 09:16:22 GatewayNV79 ntpd[432]: Listen normally on 5 wlp2s0 [fdeb:3a5d:7d34:0:721a:4ff:fee0:702f]:123
Jan 30 09:16:22 GatewayNV79 ntpd[432]: Listen normally on 6 wlp2s0 [fe80::721a:4ff:fee0:702f%3]:123
Jan 30 09:16:22 GatewayNV79 ntpd[432]: 30 Jan 09:16:22 ntpd[432]: Listen normally on 5 wlp2s0 [fdeb:3a5d:7d34:0:721a:4ff:fee0:702f]:123
Jan 30 09:16:22 GatewayNV79 ntpd[432]: 30 Jan 09:16:22 ntpd[432]: Listen normally on 6 wlp2s0 [fe80::721a:4ff:fee0:702f%3]:123
Jan 30 09:16:23 GatewayNV79 dhcpcd[759]: wlp2s0: offered 192.168.1.211 from 192.168.1.1
Jan 30 09:16:28 GatewayNV79 dhcpcd[759]: wlp2s0: leased 192.168.1.211 for 43200 seconds
Jan 30 09:16:28 GatewayNV79 dhcpcd[759]: wlp2s0: adding route to 192.168.1.0/24
Jan 30 09:16:28 GatewayNV79 dhcpcd[759]: wlp2s0: adding default route via 192.168.1.1
Jan 30 09:16:28 GatewayNV79 avahi-daemon[333]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.211.
Jan 30 09:16:28 GatewayNV79 avahi-daemon[333]: New relevant interface wlp2s0.IPv4 for mDNS.
Jan 30 09:16:28 GatewayNV79 avahi-daemon[333]: Registering new address record for 192.168.1.211 on wlp2s0.IPv4.
Jan 30 09:16:30 GatewayNV79 ntpd[432]: Listen normally on 7 wlp2s0 192.168.1.211:123
Jan 30 09:16:30 GatewayNV79 ntpd[432]: 30 Jan 09:16:30 ntpd[432]: Listen normally on 7 wlp2s0 192.168.1.211:123
Jan 30 09:16:30 GatewayNV79 ntpd[1346]: Listen normally on 3 wlp2s0 192.168.1.211:123
Jan 30 09:16:30 GatewayNV79 ntpd[1346]: Listen normally on 5 wlp2s0 [fdeb:3a5d:7d34:0:721a:4ff:fee0:702f]:123
Jan 30 09:16:30 GatewayNV79 ntpd[1346]: Listen normally on 6 wlp2s0 [fe80::721a:4ff:fee0:702f%3]:123
Jan 30 09:27:38 GatewayNV79 avahi-daemon[333]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.211.
Jan 30 09:27:39 GatewayNV79 wpa_actiond[389]: Interface 'wlp2s0' disconnected from network 'OpenWrt'
Jan 30 09:27:39 GatewayNV79 dhcpcd[942]: wlp2s0: removing interface
Jan 30 09:27:39 GatewayNV79 wpa_actiond[389]: Terminating wpa_actiond session for interface 'wlp2s0'
Jan 30 09:27:40 GatewayNV79 kernel: wlp2s0: deauthenticating from 00:03:7f:bf:a3:0f by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 30 09:28:11 GatewayNV79 kernel: ath9k 0000:02:00.0 wlp2s0: renamed from wlan0
Jan 30 09:28:15 GatewayNV79 netctl-auto[350]: Included profile 'wlp2s0-OpenWrt'
Jan 30 09:28:15 GatewayNV79 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Jan 30 09:28:16 GatewayNV79 wpa_actiond[720]: Starting wpa_actiond session for interface 'wlp2s0'
Jan 30 09:28:17 GatewayNV79 kernel: wlp2s0: authenticate with 00:03:7f:bf:a3:0f
Jan 30 09:28:17 GatewayNV79 kernel: wlp2s0: send auth to 00:03:7f:bf:a3:0f (try 1/3)
Jan 30 09:28:17 GatewayNV79 kernel: wlp2s0: authenticated
Jan 30 09:28:17 GatewayNV79 kernel: wlp2s0: associate with 00:03:7f:bf:a3:0f (try 1/3)
Jan 30 09:28:17 GatewayNV79 kernel: wlp2s0: RX AssocResp from 00:03:7f:bf:a3:0f (capab=0x411 status=0 aid=3)
Jan 30 09:28:17 GatewayNV79 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
Jan 30 09:28:17 GatewayNV79 kernel: wlp2s0: associated
Jan 30 09:28:17 GatewayNV79 wpa_actiond[720]: Interface 'wlp2s0' connected to network 'OpenWrt'
Jan 30 09:28:17 GatewayNV79 ntpd[726]: unable to create socket on wlp2s0 (4) for fe80::721a:4ff:fee0:702f%3#123
Jan 30 09:28:17 GatewayNV79 systemd-networkd[349]: wlp2s0 : gained carrier
Jan 30 09:28:17 GatewayNV79 ntpd[726]: 30 Jan 09:28:17 ntpd[726]: unable to create socket on wlp2s0 (4) for fe80::721a:4ff:fee0:702f%3#123
Jan 30 09:28:18 GatewayNV79 avahi-daemon[354]: Registering new address record for fe80::721a:4ff:fee0:702f on wlp2s0.*.
Jan 30 09:28:19 GatewayNV79 dhcpcd[767]: wlp2s0: IAID 04:e0:70:2f
Jan 30 09:28:19 GatewayNV79 dhcpcd[767]: wlp2s0: rebinding lease of 192.168.1.211
Jan 30 09:28:20 GatewayNV79 ntpd[726]: unable to create socket on wlp2s0 (5) for fdeb:3a5d:7d34:0:721a:4ff:fee0:702f#123
Jan 30 09:28:20 GatewayNV79 ntpd[726]: Listen normally on 6 wlp2s0 [fe80::721a:4ff:fee0:702f%3]:123
Jan 30 09:28:20 GatewayNV79 ntpd[726]: 30 Jan 09:28:20 ntpd[726]: unable to create socket on wlp2s0 (5) for fdeb:3a5d:7d34:0:721a:4ff:fee0:702f#123
Jan 30 09:28:20 GatewayNV79 ntpd[726]: 30 Jan 09:28:20 ntpd[726]: Listen normally on 6 wlp2s0 [fe80::721a:4ff:fee0:702f%3]:123
Jan 30 09:28:20 GatewayNV79 avahi-daemon[354]: Registering new address record for fdeb:3a5d:7d34:0:721a:4ff:fee0:702f on wlp2s0.*.
Jan 30 09:28:20 GatewayNV79 avahi-daemon[354]: Withdrawing address record for fe80::721a:4ff:fee0:702f on wlp2s0.
Jan 30 09:28:22 GatewayNV79 ntpd[726]: Listen normally on 7 wlp2s0 [fdeb:3a5d:7d34:0:721a:4ff:fee0:702f]:123
Jan 30 09:28:22 GatewayNV79 ntpd[726]: 30 Jan 09:28:22 ntpd[726]: Listen normally on 7 wlp2s0 [fdeb:3a5d:7d34:0:721a:4ff:fee0:702f]:123
Jan 30 09:28:24 GatewayNV79 dhcpcd[767]: wlp2s0: leased 192.168.1.211 for 43200 seconds
Jan 30 09:28:24 GatewayNV79 avahi-daemon[354]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.211.
Jan 30 09:28:24 GatewayNV79 avahi-daemon[354]: New relevant interface wlp2s0.IPv4 for mDNS.
Jan 30 09:28:24 GatewayNV79 dhcpcd[767]: wlp2s0: adding route to 192.168.1.0/24
Jan 30 09:28:24 GatewayNV79 dhcpcd[767]: wlp2s0: adding default route via 192.168.1.1
Jan 30 09:28:24 GatewayNV79 avahi-daemon[354]: Registering new address record for 192.168.1.211 on wlp2s0.IPv4.
Jan 30 09:28:26 GatewayNV79 ntpd[726]: Listen normally on 8 wlp2s0 192.168.1.211:123
Jan 30 09:28:26 GatewayNV79 ntpd[726]: 30 Jan 09:28:26 ntpd[726]: Listen normally on 8 wlp2s0 192.168.1.211:123
Jan 30 09:28:27 GatewayNV79 ntpd[871]: Listen normally on 3 wlp2s0 192.168.1.211:123
Jan 30 09:28:27 GatewayNV79 ntpd[871]: Listen normally on 5 wlp2s0 [fdeb:3a5d:7d34:0:721a:4ff:fee0:702f]:123
Jan 30 09:28:27 GatewayNV79 ntpd[871]: Listen normally on 6 wlp2s0 [fe80::721a:4ff:fee0:702f%3]:123
Jan 30 10:19:10 GatewayNV79 wpa_actiond[720]: Interface 'wlp2s0' lost connection to network 'OpenWrt'
Jan 30 10:19:10 GatewayNV79 avahi-daemon[354]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
Jan 30 10:19:10 GatewayNV79 avahi-daemon[354]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.211.
Jan 30 10:19:10 GatewayNV79 dhcpcd[850]: wlp2s0: arp if_readrawpacket: Network is down
Jan 30 10:19:10 GatewayNV79 systemd-networkd[349]: wlp2s0 : lost carrier
Jan 30 10:19:10 GatewayNV79 avahi-daemon[354]: Withdrawing address record for fdeb:3a5d:7d34:0:721a:4ff:fee0:702f on wlp2s0.
Jan 30 10:19:10 GatewayNV79 avahi-daemon[354]: Withdrawing address record for 192.168.1.211 on wlp2s0.
Jan 30 10:19:10 GatewayNV79 avahi-daemon[354]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.211.
Jan 30 10:19:10 GatewayNV79 avahi-daemon[354]: New relevant interface wlp2s0.IPv4 for mDNS.
Jan 30 10:19:10 GatewayNV79 avahi-daemon[354]: Registering new address record for 192.168.1.211 on wlp2s0.IPv4.
Jan 30 10:19:11 GatewayNV79 ntpd[871]: Deleting interface #3 wlp2s0, 192.168.1.211#123, interface stats: received=0, sent=0, dropped=0, active_time=3044 secs
Jan 30 10:19:11 GatewayNV79 ntpd[871]: Deleting interface #5 wlp2s0, fdeb:3a5d:7d34:0:721a:4ff:fee0:702f#123, interface stats: received=0, sent=0, dropped=0, active_time=3044 secs
Jan 30 10:19:11 GatewayNV79 ntpd[871]: Deleting interface #6 wlp2s0, fe80::721a:4ff:fee0:702f%3#123, interface stats: received=0, sent=0, dropped=0, active_time=3044 secs
Jan 30 10:19:40 GatewayNV79 wpa_actiond[720]: Interface 'wlp2s0' disconnected from network 'OpenWrt'
Jan 30 10:19:40 GatewayNV79 dhcpcd[850]: wlp2s0: removing interface
Jan 30 10:19:40 GatewayNV79 avahi-daemon[354]: Withdrawing address record for 192.168.1.211 on wlp2s0.
Jan 30 10:19:40 GatewayNV79 avahi-daemon[354]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.211.
Jan 30 10:19:40 GatewayNV79 avahi-daemon[354]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
iwconfig
wlp2s0 IEEE 802.11bgn ESSID:"OpenWrt"
Mode:Managed Frequency:2.462 GHz Access Point: 00:03:7F:BF:A3:0F
Bit Rate=117 Mb/s Tx-Power=16 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=69/70 Signal level=-41 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:164 Missed beacon:0
lo no wireless extensions.
enp1s0 no wireless extensions.
lsmod
lsmod
Module Size Used by
fuse 87410 3
ctr 12927 3
ccm 17534 3
uvcvideo 83143 0
videobuf2_vmalloc 12816 1 uvcvideo
videobuf2_memops 12519 1 videobuf2_vmalloc
videobuf2_core 39635 1 uvcvideo
v4l2_common 12995 1 videobuf2_core
videodev 135040 3 uvcvideo,v4l2_common,videobuf2_core
media 18365 2 uvcvideo,videodev
joydev 17063 0
mousedev 17272 0
arc4 12536 2
snd_hda_codec_hdmi 49263 1
snd_hda_codec_realtek 63196 1
snd_hda_codec_generic 63087 2 snd_hda_codec_realtek
ath9k 137724 0
ath9k_common 21746 1 ath9k
ath9k_hw 428656 2 ath9k_common,ath9k
iTCO_wdt 12831 0
ath 26067 3 ath9k_common,ath9k,ath9k_hw
snd_hda_intel 26387 4
coretemp 12820 0
snd_hda_controller 26938 1 snd_hda_intel
broadcom 17013 0
acer_wmi 17603 0
sparse_keymap 12818 1 acer_wmi
iTCO_vendor_support 12649 1 iTCO_wdt
led_class 12855 2 ath9k,acer_wmi
intel_powerclamp 17122 0
snd_hda_codec 112621 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
mac80211 608652 1 ath9k
kvm_intel 143295 0
mxm_wmi 12515 0
tg3 164580 0
snd_hwdep 17244 1 snd_hda_codec
kvm 426425 1 kvm_intel
ptp 17692 1 tg3
pps_core 17225 1 ptp
libphy 32315 2 tg3,broadcom
hwmon 12930 2 tg3,coretemp
intel_agp 17432 0
evdev 21544 16
cfg80211 453926 4 ath,ath9k_common,ath9k,mac80211
i915 946695 9
rfkill 18867 3 cfg80211,acer_wmi
drm_kms_helper 80985 1 i915
snd_pcm 88785 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
drm 263481 6 i915,drm_kms_helper
crc32c_intel 21809 0
intel_gtt 17848 2 i915,intel_agp
i2c_i801 16965 0
mac_hid 12633 0
mei_me 17941 0
mei 75336 1 mei_me
pcspkr 12595 0
psmouse 107442 0
intel_ips 17420 0
i2c_algo_bit 12744 1 i915
snd_timer 26614 1 snd_pcm
i2c_core 50152 7 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,v4l2_common,videodev
serio_raw 12849 0
snd 73436 16 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
soundcore 13031 2 snd,snd_hda_codec
lpc_ich 20768 0
shpchp 35210 0
video 18043 2 i915,acer_wmi
battery 17452 0
ac 12715 0
button 12953 1 i915
acpi_cpufreq 17218 1
processor 27777 1 acpi_cpufreq
wmi 17339 2 acer_wmi,mxm_wmi
sch_fq_codel 17343 10
pci_stub 12429 1
vboxpci 23139 0
vboxnetflt 27412 0
vboxnetadp 25443 0
vboxdrv 352524 3 vboxnetadp,vboxnetflt,vboxpci
sg 34865 0
ext4 510292 2
crc16 12343 1 ext4
mbcache 17171 1 ext4
jbd2 86379 1 ext4
sr_mod 21903 0
cdrom 47479 1 sr_mod
sd_mod 43575 3
uas 21817 0
usb_storage 60311 1 uas
hid_generic 12393 0
usbhid 48595 0
hid 106316 2 hid_generic,usbhid
atkbd 22254 0
libps2 12739 2 atkbd,psmouse
ahci 33248 2
libahci 27215 1 ahci
ehci_pci 12512 0
ehci_hcd 69939 1 ehci_pci
libata 181518 2 ahci,libahci
usbcore 199382 6 uas,uvcvideo,usb_storage,ehci_hcd,ehci_pci,usbhid
scsi_mod 147580 6 sg,uas,usb_storage,libata,sd_mod,sr_mod
usb_common 12561 1 usbcore
i8042 18002 2 acer_wmi,libps2
serio 18282 6 serio_raw,atkbd,i8042,psmouse
lspci
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 12)
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05)
01:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe (rev 01)
02:00.0 Network controller: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) (rev 01)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
ff:02.1 Host bridge: Intel Corporation 1st Generation Core Processor QPI Physical 0 (rev 02)
ff:02.2 Host bridge: Intel Corporation 1st Generation Core Processor Reserved (rev 02)
ff:02.3 Host bridge: Intel Corporation 1st Generation Core Processor Reserved (rev 02)
dmesg
[ 12.707801] ath: phy0: ASPM enabled: 0x42
[ 12.707807] ath: EEPROM regdomain: 0x65
[ 12.707809] ath: EEPROM indicates we should expect a direct regpair map
[ 12.707811] ath: Country alpha2 being used: 00
[ 12.707812] ath: Regpair used: 0x65
[ 12.790781] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 12.791136] ieee80211 phy0: Atheros AR9280 Rev:2 mem=0xffffc90010880000, irq=17
[ 12.841627] ath9k 0000:02:00.0 wlp2s0: renamed from wlan0
[ 12.858062] tg3 0000:01:00.0 enp1s0: renamed from eth0
[ 12.949786] mousedev: PS/2 mouse device common for all mice
[ 13.441384] ACPI: Battery Slot [BAT0] (battery present)
[ 13.886581] media: Linux media interface: v0.10
[ 13.914444] Linux video capture interface: v2.00
[ 13.979679] uvcvideo: Found UVC 1.00 device Video WebCam (064e:a103)
[ 13.996259] input: Video WebCam as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input17
[ 13.996373] usbcore: registered new interface driver uvcvideo
[ 13.996376] USB Video Class driver (1.1.1)
[ 14.580406] systemd-journald[150]: Received request to flush runtime journal from PID 1
[ 14.637675] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: data=ordered
[ 16.288680] intel ips 0000:00:1f.6: i915 driver attached, reenabling gpu turbo
[ 18.802102] tg3 0000:01:00.0: irq 28 for MSI/MSI-X
[ 18.823887] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[ 19.213570] tg3 0000:01:00.0 enp1s0: Link is down
[ 20.473582] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 21.806923] wlp2s0: authenticate with 00:03:7f:bf:a3:0f
[ 21.836003] wlp2s0: send auth to 00:03:7f:bf:a3:0f (try 1/3)
[ 21.838218] wlp2s0: authenticated
[ 21.839772] wlp2s0: associate with 00:03:7f:bf:a3:0f (try 1/3)
[ 21.844383] wlp2s0: RX AssocResp from 00:03:7f:bf:a3:0f (capab=0x411 status=0 aid=3)
[ 21.844517] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[ 21.844621] wlp2s0: associated
[ 67.298039] fuse init (API version 7.23)
[ 861.811760] perf interrupt took too long (2503 > 2495), lowering kernel.perf_event_max_sample_rate to 50100

you don't need to reboot go into the GTTY prompt ( ie ctl alt F2 - F7 ) then systemctl STOP ( xx current desktop manager ie lightdm kdm gdm etc ) an it will kill all current processes run wifi-menu as root or sudo with normal user an then reestablish connection that way or look on the arch wiki for NETCTL an read that or search google

Wireless connection not visible on Vista laptop using Time capsule

Change setup with Time capsule 1 TB, all MAC PC's work perfectly with wireless connection, except Vista laptop.
Vista discovers all other wireless connections except the one from Time capsule.
On advise from forum, changed Airport settings :
- Radio mode = 802/a - 802/g"
- Wireless security to "none"
Which other setting on Vista prevents at least discovering the wireless signal ?
Thanks for your support !
Pascal

I believe the problem has to do with some potential compatibility issue between the SP3 update and the currently installed Boot Camp drivers. Did you make sure that you (re)installed the latest Boot Camp drivers after you performed the SP3 update?
(ref: Apple Support: Installing Boot Camp drivers)
Also, the following firmware update may help as well: MacBook EFI Firmware Update 1.1

Wireless not working on boot

I have an older PC (so it's not moving much...), and I'm trying to set up wireless connection trough a USB wireless adapter (Ralink Technology, Corp. RT2501USB Wireless Adapter).
I have the correct drivers installed, and everything set up (doulbe checked of course).
The wireless setup during boot-time does not works, and prints the error message
Could not associate $1 - try increasing WIRELESS_TIMEOUT and check network is WEP or has no security
If I run iwgetid immeadiateley after login, I get the following output:
$ iwgetid wlan0 -ra
00:00:00:00:00:00
On the other hand, if I try a
sudo /etc/rc.d/network start
after I log in, it works flawlessley.
I've tried the following:
--> setting WIRELESS_TIMEOUT to 10 seconds, does not works (only after boot)
--> double checking the setup lines
--> reading the /etc/rc.d/network script, and executing the commands manually, it works
$ sudo /etc/rc.d/network stop
$ sudo iwconfig wlan0 essid BodorWLAN key s:wikey
$ sudo iwgetid wlan0 -ra
[the MAC-ADDRESS of wlan0, differring from 00:00:00:00:00:00]
--> stopping and starting the /etc/rc.d/network script, it works
--> editing /etc/rc.d/network to print out the used varialbes and more verbose error messages (I've restored it since then, so I cannot post the results, all seemed to be ok.)
/etc/config.d/wireless:
# Settings for wireless cards
# For each wireless interface declared in INTERFACES (in rc.conf), declare
# a wlan_${IF} variable that contains the arguments to be passed to
# iwconfig(8). Then list the original interface name in the
# WLAN_INTERFACES array.
#wlan_eth0="eth0 mode managed essid default"
#WLAN_INTERFACES=(eth0)
/etc/rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="hu_HU.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Budapest"
KEYMAP="hu"
CONSOLEFONT="lat2-16.psfu.gz"
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="curly-desktop"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
wlan0="dhcp"
wlan_wlan0="wlan0 essid BodorWLAN key s:wikey"
INTERFACES=(eth0 wlan0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng dbus hal network openntpd netfs crond alsa)
Note: I modified sensitive information (passwd, stb.)
I'm running out of ideas, since the network script appears to be working always except at boot time.
Last edited by dragonfi (2010-06-11 15:44:52)

Activating the usb hooks in the ramdisk did not done the job, as the network demon only runs late in boottime (maybe I'm just being imprecise, i'm meaning the part, where it already entered the final runlevel).
On the other hand, I did tracked down the problem, and I beliveve it's some kind of desing-flaw in the wireless USB utility. (Or I'm just not aware of a certain feature in it.)
I modified /etc/rc.d/network to resend the iwconfig to the device after the 2 second sleep, and it seems to work sometimes.
/etc/rc.d/network: (added lines in wi_up())
#!/bin/bash
. /etc/rc.conf
. /etc/rc.d/functions
# wireless settings
[ -f /etc/conf.d/wireless ] && . /etc/conf.d/wireless
# ethernet bonding settings
[ -f /etc/conf.d/bonding ] && . /etc/conf.d/bonding
# bridge settings
[ -f /etc/conf.d/bridges ] && . /etc/conf.d/bridges
# dhcpcd settings
[ -f /etc/conf.d/dhcpcd ] && . /etc/conf.d/dhcpcd
ifup()
if [ "$1" = "" ]; then
echo "usage: $0 ifup <interface_name>"
return 1
fi
eval ifcfg="\$${1}"
# Get the name of the interface from the first token in the string
if [ "$ifcfg" = "dhcp" ]; then
ifname="$1"
else
ifname=${ifcfg%% *}
fi
/sbin/ifconfig $ifname up
wi_up $1 || return 1
if [ "$ifcfg" = "dhcp" ]; then
# remove the .pid file if it exists
/bin/rm -f /var/run/dhcpcd-${1}.pid >/dev/null 2>&1
/bin/rm -f /var/run/dhcpcd-${1}.cache >/dev/null 2>&1
/sbin/dhcpcd $DHCPCD_ARGS ${1}
else
/sbin/ifconfig $ifcfg
fi
return $?
wi_up()
eval iwcfg="\$wlan_${1}"
[ "$iwcfg" = "" ] && return 0
/usr/sbin/iwconfig $iwcfg
[[ -z "$WIRELESS_TIMEOUT" ]] && WIRELESS_TIMEOUT=2
sleep $WIRELESS_TIMEOUT
#added line below because wlan0 does not play nice..
/usr/sbin/iwconfig $iwcfg
bssid=`iwgetid $1 -ra`
if [[ "$bssid" = "00:00:00:00:00:00" ]]; then
printhl "Could not associate $1 - try increasing WIRELESS_TIMEOUT and check network is WEP or has no security"
return 1
fi
return 0
ifdown()
if [ "$1" = "" ]; then
echo "usage: $0 ifdown <interface_name>"
return 1
fi
eval ifcfg="\$${1}"
if [ "$ifcfg" = "dhcp" ]; then
if [ -f /var/run/dhcpcd-${1}.pid ]; then
/bin/kill $(cat /var/run/dhcpcd-${1}.pid)
fi
fi
# Always bring the interface itself down
/sbin/ifconfig ${1} down >/dev/null 2>&1
return $?
iflist()
for ifline in ${INTERFACES[@]}; do
if [ "$ifline" = "${ifline#!}" ]; then
printf " $ifline:\t"
else
printf "$ifline:\t"
fi
eval real_ifline=\$${ifline#!}
echo $real_ifline
done
rtup()
if [ "$1" = "" ]; then
echo "usage: $0 rtup <route_name>"
return 1
fi
eval routecfg="\$${1}"
if grep -q :: <<< $routecfg; then
/sbin/route -A inet6 add $routecfg
else
/sbin/route add $routecfg
fi
return $?
rtdown()
if [ "$1" = "" ]; then
echo "usage: $0 rtdown <route_name>"
return 1
fi
eval routecfg="\$${1}"
if grep -q :: <<< $routecfg; then
/sbin/route -A inet6 del $routecfg
else
/sbin/route del $routecfg
fi
return $?
rtlist()
for rtline in ${ROUTES[@]}; do
if [ "$rtline" = "${rtline#!}" ]; then
printf " $rtline:\t"
else
printf "$rtline:\t"
fi
eval real_rtline=\$${rtline#!}
echo $real_rtline
done
bond_up()
for ifline in ${BOND_INTERFACES[@]}; do
if [ "$ifline" = "${ifline#!}" ]; then
eval bondcfg="\$bond_${ifline}"
if [ -n "${bondcfg}" ]; then
/sbin/ifenslave $ifline $bondcfg || error=1
fi
fi
done
bond_down()
for ifline in ${BOND_INTERFACES[@]}; do
if [ "$ifline" = "${ifline#!}" ]; then
eval bondcfg="\$bond_${ifline}"
/sbin/ifenslave -d $ifline $bondcfg || error=1
fi
done
bridge_up()
for br in ${BRIDGE_INTERFACES[@]}; do
if [ "$br" = "${br#!}" ]; then
# if the bridge already exists, remove it
if [ "$(/sbin/ifconfig $br 2>/dev/null)" ]; then
/sbin/ifconfig $br down
/usr/sbin/brctl delbr $br
fi
/usr/sbin/brctl addbr $br
eval brifs="\$bridge_${br}"
for brif in $brifs; do
if [ "$brif" = "${brif#!}" ]; then
for ifline in ${BOND_INTERFACES[@]}; do
if [ "$brif" = "$ifline" ] && [ "$ifline" = "${ifline#!}" ]; then
ifup $ifline
eval bondcfg="\$bond_${ifline}"
/sbin/ifenslave $ifline $bondcfg || error=1
unset bond_${ifline}
fi
done
/usr/sbin/brctl addif $br $brif || error=1
fi
done
fi
done
bridge_down()
for br in ${BRIDGE_INTERFACES[@]}; do
if [ "$br" = "${br#!}" ]; then
/usr/sbin/brctl delbr $br
fi
done
case "$1" in
start)
if ! ck_daemon network; then
echo "Network is already running. Try 'network restart'"
exit
fi
stat_busy "Starting Network"
error=0
# bring up bridge interfaces
bridge_up
# bring up ethernet interfaces
for ifline in ${INTERFACES[@]}; do
if [ "$ifline" = "${ifline#!}" ]; then
ifup $ifline || error=1
fi
done
# bring up bond interfaces
bond_up
# bring up routes
for rtline in "${ROUTES[@]}"; do
if [ "$rtline" = "${rtline#!}" ]; then
rtup $rtline || error=1
fi
done
if [ $error -eq 0 ]; then
add_daemon network
stat_done
else
stat_fail
fi
stop)
#if ck_daemon network; then
# echo "Network is not running. Try 'network start'"
# exit
#fi
stat_busy "Stopping Network"
rm_daemon network
error=0
for rtline in "${ROUTES[@]}"; do
if [ "$rtline" = "${rtline#!}" ]; then
rtdown $rtline || error=1
fi
done
# bring down bond interfaces
bond_down
for ifline in ${INTERFACES[@]}; do
if [ "$ifline" = "${ifline#!}" ]; then
ifdown $ifline || error=1
fi
done
# bring down bridge interfaces
bridge_down
if [ $error -eq 0 ]; then
stat_done
else
stat_fail
fi
restart)
$0 stop
/bin/sleep 2
$0 start
ifup|ifdown|iflist|rtup|rtdown|rtlist)
$1 $2
echo "usage: $0 {start|stop|restart}"
echo " $0 {ifup|ifdown|iflist|rtup|rtdown|rtlist}"
esac
# vim: set ts=2 noet:
I wrote a sript and chnaged network to this script in my rc.conf, it appears to be working now.
/etc/rc.d/myscript:
#!/bin/bash
. /etc/rc.conf
. /etc/rc.d/functions
ifup()
/sbin/ifconfig wlan0 up
/usr/sbin/iwconfig wlan0 essid BodorWLAN key s:admin
sleep 2
/usr/sbin/iwconfig wlan0 essid BodorWLAN key s:admin
dhcpcd wlan0
return $?
ifdown()
if [ -f /var/run/dhcpcd-wlan0.pid ]; then
/bin/kill $(cat /var/run/dhcpcd-wlan0.pid)
fi
/sbin/ifconfig wlan0 down >/dev/null 2>&1
return $?
case "$1" in
start)
stat_busy "Starting Network"
ifup
stat_done
restart)
stat_busy "Restarting Network"
ifdown
ifup
stat_done
stop)
stat_busy "Stopping Network"
ifdown
stat_done
echo "usage: $0 {start|stop|restart}"
esac
My only question now is that how could I achieve the same solution in a more elegant way, I'm a bit confused, because the above script does the exact same stuff that my modified /etc/rc.d/network would supposed to be doing.
Last edited by dragonfi (2010-06-12 19:27:38)

Dear Steve, will anything be done about this wireless connectivity issue?

This is no fun whatsoever....
I am telling you - browsing interenet on iMac is no fun, seriously.
I prepared a quick research for you:
http://discussions.apple.com/thread.jspa?threadID=830426
http://discussions.apple.com/thread.jspa?threadID=834613
http://discussions.apple.com/thread.jspa?threadID=831111
http://discussions.apple.com/thread.jspa?threadID=829204 (I like this one best)
http://discussions.apple.com/thread.jspa?threadID=827632
http://discussions.apple.com/thread.jspa?threadID=833593 (although marked as solved - doesn't seem to be true in my and many others' cases)
http://discussions.apple.com/thread.jspa?threadID=838501
http://discussions.apple.com/thread.jspa?threadID=822703
http://discussions.apple.com/thread.jspa?threadID=826128
People, help me in refining this list - did I leave something out?
P.S. I was thinking lately, why, after spending so much money, should I spend several days already, in agregate, trying to understand the issue and how it should be resolved? Have I not paid for not having such problems?

Here is a lot more:
http://www.macintouch.com/readerreports/wirelessnetworking/topic4035.html
Highly interesting is the post of J.Exby which i reproduce here:
For months I've not been alone in holding to the notion that the airport client software on Mac OS X 10.4.x has been problematic and unstable in certain (noisy, crowded, channel overlapped) wireless environments. Issues littered around the Internet Mac forums include problems of networks appearing, then disappearing. This is a difficult problem to pin down, given the difficulty of reproducing the conditions that might cause wireless network dropouts.
A major symptom of the problem was seeing the constant messages of:
"An error occurred joining the AirPort network" (Try Again) (Cancel)
when attempting to connect to a wireless network, despite that network being seen, having correct security settings, etc.
Various temporary fixes/ideas floated around the mac community have included:
- reseting pram, nvram and PMU
- installing 10.4 from scratch, instead of 10.3 to 10.4 upgrade process
- Repairing permissions, run Combo updaters, etc
- putting system to sleep or reboot for temporary connection fix
- applying AirPort 2005-001 patch (or not)
- upgrading (or downgrading!) AirPort basestation firmware
- changing AirPort channels
- enabled (or disabling) Interference Robustness
- disabling Bluetooth and BT peripherals
- removing WEP/WPA passwords out of Keychain
- running Keychain First Aid on user/login keychains
- buying new AirPort extreme cards
- replacing AirPort base stations with other vendor hardware, etc.
With the stability of our Windows XP clients now (after driver updates) and the change from Apple base stations to Belkin Wireless Pre-N Router having no appreciable benefit for our Mac notebooks, the OS X AirPort client software suspicions only grew.
During troubleshooting I always have
Applications--->Utilities--->Console
and
iStumbler (96)
running, and I watch output as wireless scans are performed.
From the Terminal I also run:
/System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport -s
and usually see constant
AirPortScanner WirelessScan error -2013261821 airpInternalErr
messages.
After two days of testing (and fixing?) I am even more convinced there are bugs in the powerpc 10.4.x AirPort Extreme Framework!
This is what I found:
Environment at our office:
- wireless Network A (802.11g channel 1, WPA personal)
- wireless Network B (802.11b channel 6, WEP 40bit ascii)
- wireless Network C (802.11g channel 11, WPA personal)
(WAR-marching around our office exterior shows at least 12 outside wireless networks found at various signal strengths!)
Test systems used:
- iBook G4 (10.3.x and 10.4.5)
- Powerbook G4 (10.4.5)
- Intel iMac (10.4.5)
Primary symptom on iBook: networks not displaying long enough under the AirPort icon/menu (or Internet Connect) to connect to ANY network reliably! Perhaps connect to Network A intermittently, never even see Network C.
iStumbler showing some networks respond to poll, then immediately stagnate/disappear.
Primary symptom on Powerbook: stable connections to Network C most times, difficulty "switching" to Network B or A once moving closer to source. Usually stable "seeing" networks via AirPort menu icon, but still have occasional dropouts (due to fluctuating signal strength or interference?).
Primary symptom on Intel iMac: NO PROBLEMS! Can connect to (and steadily "see") all valid Networks A, B, C !
iStumbler constantly polls all available networks, with no dropouts.
Steps taken:
1. Wipe iBook hard drive, install 10.3 from dvd. AirPort signals unreliable.
1a. Perform all 10.3.x Software updates, Repair Permissions, reboot. AirPort still unreliable.
2. Reset PRAM, nvram, PMU. no improvements.
3. Reseat AirPort Extreme card, ensure antenna is firmly plugged in. AirPort still unreliable.
4. Wipe iBook, install 10.4.3 "fresh" from Full retail version DVD. AirPort still unreliable.
4a. Perform all 10.4.5 Software (combo) updates, Repair Permissions, reboot. AirPort still unreliable.
5. Hold down the Option key, and click on the AirPort icon in the menu bar.
select About AirPort...
pay particular attention to each system showing:
iBook: AirPort Framework 421.13.0
powerbook: AirPort Framework 421.13.0
intel iMac: AirPort Framework 426.1.0
Aha! A big difference with the AirPort Framework component version on the Intel iMac!
6. So, using the Terminal let's get this newer Apple80211.framework onto the iBook.
First on the intel iMac:
cd /System/Library/PrivateFrameworks
sudo tar cf ~/intelApple80211frame.tar Apple80211.framework
Copy this intelApple80211frame.tar file onto a USB thumb drive, CDR, iPod, scp, etc. to copy it onto the iBook (home directory).
7. With the tar file copied into the home area on the iBook, turn off iBook's AirPort via the menubar icon.
Now launch Terminal and:
mkdir backup-framework
cd /System/Library/PrivateFrameworks
sudo mv Apple80211.framework ~/backup-framework/
sudo tar xvpf ~/intelApple80211frame.tar
Launch Disk Utility, Repair Permissions on boot drive.
Reboot iBook.
8. Turn Airport on via the menubar icon.
iBook now has HUGE improvements in wireless connectivity! It can "see" all Networks A, B, C reliably and can connect to any of them when in range (having enough signal strength). Switching between networks is successful 90% of the time. Occasional message of:
"An error occurred joining the AirPort network (Try Again) (Cancel)"
usually works after clicking (Try Again), whereas before Try Again almost always failed.
I am unsure how this newer Apple80211.framework will affect future Software Updates on the iBook, but frankly I could care less now that it's able to access all of our wireless networks!
I am unsure if this is the magic-bullet solution for a majority of people, but I'm stunned that Apple appears to be providing new and improved Apple80211.framework software with the intel iMacs, but many of us have been fighting AirPort problems on PowerPC platforms for months!
Come on Apple, OS X 10.4.5 should contain the SAME software component versions for ALL CPU platforms!
Source: http://www.macintouch.com/readerreports/wirelessnetworking/topic4035.html

Mad: Can't get wireless work either on boot or after resume: 3945ABG

lspci | grep Wireless
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
/etc/rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="America/Detroit"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="myhost"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp"
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#gateway="default gw 192.168.0.1"
#ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
NETWORKS=(hw)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng net-profiles alsa hal)
/etc/network.d/hw
CONNECTION="wireless"
DESCRIPTION="A simple WEP encrypted wireless connection"
INTERFACE="wlan0"
SECURITY="wep"
ESSID="blablabla"
KEY="blablabla"
IP="dhcp"
This set of configuration dosen't get connected to internet. The wirless indication light is on but not blinking.
I can manually bring it up by using
sudo netcfg hw
The other problem, which I guess is very common to linux users, is the wireless isn't waked up after resume from suspend. In my case, it can't be waked up even if I use the manual method. This is more important than to get it work on boot because I usually put my computer to sleep instead of power down when I am not using it.
I am trying Arch Linux on my old laptop, if it works well, I'll put it into my work desktop.

Ramses de Norre wrote:
Can you post the output of
dmesg|grep iwl
this might be the same bug as a lot of people are having and which should be resolved in linux 2.6.32.3, which is currently in testing.
dmesg|grep iwl
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
iwl3945: Copyright(c) 2003-2009 Intel Corporation
iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwl3945 0000:03:00.0: setting latency timer to 64
iwl3945 0000:03:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
iwl3945 0000:03:00.0: Detected Intel Wireless WiFi Link 3945ABG
iwl3945 0000:03:00.0: irq 28 for MSI/MSI-X
phy0: Selected rate control algorithm 'iwl-3945-rs'
iwl3945 0000:03:00.0: firmware: requesting iwlwifi-3945-2.ucode
iwl3945 0000:03:00.0: loaded firmware version 15.32.2.9
Registered led device: iwl-phy0::radio
Registered led device: iwl-phy0::assoc
Registered led device: iwl-phy0::RX
Registered led device: iwl-phy0::TX

Have successfully installed windows 7 but can't get wireless connection?

Hi There,
I have just installed a Windows 7 Partition using Boot Camp on my partner's iMac and it works fine but can't connect to the wireless connection? On the mac side it connects without problem? Can anyone advise???

I used boot camp to create partition then installed brand new home users windows 7 I backed it up to an external hard drive before installing. Her iMac connects to her sky router without problems? Which is why I can't understand why, when we switch to windows in doesn't find any networks? Hope this helps
Regards

Ethernet default over wireless connection.

when I boot up I want my network to default to the ethernet which is connected to the Dynadock U3.0 before the wireless in the Lenovo x220 laptop. The ethernet is much faster. is there any way I can have this occur automatically - rather than me having to shut off the wireless connection? any ideas?

Mount the TC disk manually.
In Finder use Go, Connect to server.
Type in the following.
AFP://TCname.local (TCname is the actual network name of the TC. I strongly recommend you use SMB names.. ie short, no spaces and pure alphanumeric)
Find out the Network version of the TC name if you don't want to comply to the above rule. The best way is to discover it via netstat scan.
Open network utility.
Locate your TC on it.. since my TC is correctly named it shows up as tcgen4.local
I then type in AFP://tcgen4.local
Then the computer can discover the TC and it will ask for a password. The default is public
Type in whatever you changed it to or public.
The TC disk should now be mounted.
If this fails.. reset the TC to factory and start over. Name it correctly.. all short names, no spaces and pure alphanumeric will be a lot lot easier.
Then manually force the mounting.

Wireless connection not restored immediately after sleep

Hi,
Since I have updated to Mavericks (OS X 10.9.1), my wireless connection doesn't restore automatically anymore after sleep.
This recently also started to happen when I boot my computer. I always have to click the wifi icon, select my network and then it still says "can't connect to network".
When I click the wifi icon and select my network a second time, it works.
I have tried setting the order of network services (WiFi first, then Bluetooth and finally Thunderbolt bridge), deleting my saved home network and adding it again, deleting all other saved wireless networks.
What can I do to fix this?
Thank you.

Test after taking each of the following steps that you haven't already tried. Back up all data before making any changes.
1. Make sure the network is on the preferred list by following these instructions. It's important to read the article carefully, as it's the starting point for any further efforts to solve the problem. If you skip any of the steps, the problem may not be solved. Make sure the box marked
Remember networks this computer has joined
is checked.
2. Follow the instructions in this support article under the heading "Symptom: The network connection drops unexpectedly."
3. Make a note of all your settings for Wi-Fi in the Network preference pane, then delete the connection from the connection list and recreate it with the same settings. You do this by clicking the plus-sign icon below the connection list, and selecting Wi-Fi as the interface in the sheet that opens. Select Join other network from the Network Name menu, then select your network. Enter the password when prompted and save it in the keychain.
4. From the Location menu at the top of the Network preference pane, select Edit Locations. A sheet will drop down. Click the plus-sign button to create a new location. Give it any name you want. In the new location, set up the Wi-Fi service with the same settings you used before. Click Apply and test.
5. Launch the Keychain Access application. Search for and delete all AirPort network password items that refer to the network. Make a note of the password first.
6. Repair permissions on the startup volume.
7. Turn off Bluetooth and test.
8. Reset the System Management Controller.
9. Reset the PRAM.
10. Reinstall OS X.

Wireless connectivity on PC boot up

Similar Messages

Maybe you are looking for