WRT54GS v4.0 wireless connection doesn't work... Edit: Resolved

My Linksys WRT54gs v4 router will no longer conncect wirelessly to my laptop running Win XP. I tried making sure the name and everything matches in the Wireless Network Connections window. It shows up as linksys_SES_38313 but never connects. It just says "waiting for network to be ready...". It worked fine before, until I installed ZoneAlarm firewall on my other main computer (not the laptop). I uninstalled the firewall but still nothing. I think the ZA messed something up but I have no idea what. I'm now running Outpost firewall.
If someone can please help me get this working again, I'd be very grateful. If you need any more info about my setup or router settings, etc. just let me know.
Thanks,
Mike
Message Edited by mlmar490 on 06-23-2007 02:06 PM
Message Edited by mlmar490 on 06-25-2007 12:48 AM

Wow, thank you! Your advice worked!!! I can't believe it took two minutes to fix!
I really appreciate your help!
-Mike

Similar Messages

Wireless connection doesn't work - G770

Hi there,
I have a problem with my brand new G770 - I can't use wireless connection. After first run my home wifi AP wasn't found, so I set manual connection to it. It didn't solve the problem. So I did a lot of Googling and discovering, that Lenovo has realy often problems with wifi. I tried reinstaling drivers, disabling and uninstalling lenovo energy saver. Trying Fn + F5 showed me information, that wireless device isn't turned on, or something like that... I was so desperate, that I reinstalled windows. But it didn't help. Does enybody some hint to resolve my problem? Thanks!
Previous system: W7 home 64b, Now: W7 prof 32b, devices: Atheros 8152/8158, Broadcom 802.11n (latest drivers)
Solved!
Go to Solution.

From Lenovo G770 Userguide V1.0 (English).pdf
"on select models" ???
Z.
The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc. The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

Wireless connection doesn't work

Please bear with me, this is the first time I have tried to use a wireless router, and the first time I've used Cable internet.
Info:
WRT54G
Dell 1395 WLAN g wireless card (came with Inspiron laptop)
XP
Comcast came to insall internet this afternoon. Everything works fine when internet cable is plugged into the PC, but once unplugged it cannot find a signal even though I have created a network.
Please advise.

Consider / Try:
Make sure channel is set to 1, 6, or 11 -- there is a reason for this: no overlapping signals
Make sure the printer and the router are at least three feet (about a meter) apart.
Try moving the printer or router -- even six or so inches may do it.
Routers function better higher from the ground - if you have a cabinet, place the router on top of it instead of inside.
Routers are NOT, repeat NOT equal. Even well known, newer routers -- in the "less expensive" category -- might be plagued with lack of features, slow speed, and poor (weak) antennas. Weak routers offer less performance: To give this type of router a chance to succeed, remove any objects that may reduce or block the signal: remove or move metal cabinets or appliances, large furniture, electronics (2.4 GHz). Do not expect a smaller, weaker, older router to send a strong signal through heavy walls, downstairs, or down the hallway from where the printer is located.
Check this interesting and useful post by our own HP Forum Expert Cloud_Strider:
My printer will not stay connected to the network
The settings may or may not apply directly to your case; the information illustrates wireless router connection points.
Help / Guidance:
Reconfiguring your printer
Troubleshooting Your Printer - Network
ePrint Help and Tips Page
Click the Kudos Star!
It is a great “Thank You” for the Author's efforts.
Kind Regards,
Dragon-Fur

Wired connection doesn't work if cable is not plugged in at boot time

Hey all,
I started using arch a few days ago and I simply love it, but I have a problem. The wired connection doesn't work if the cable is not plugged in at boot time, or if it was plugged in at boot time, then plugged out and in again. Switching it off and on again via the gui has the same effect. I am using NetworkManager with dhcpcd, NetworkManager is started via systemd, dhcpcd is not, I let NetworkManager do that. When I started investigating this problem there were some remnants of netctl, but now NetworkManager is the only networking-related service started at boot time. When the cable is plugged back in, NM-applet shows that it's connected, and an IP address is assigned, but the connection doesn't work.
Here's some information regarding the system:
It's a lenovo G50-70 laptop, it uses the r8169 driver for ethernet. (I dualboot it with windows 8.1, but arch is default and all this stuff happens also if i only use arch)
The router is a Linksys EA2700/N600
journalctl -u NetworkManager
aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> NetworkManager (version 0.9.10.1) is starting...
aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> WEXT support is enabled
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the NetworkMan
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/Bokros
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/1. vezetékes kapcsolat
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/UPC1838142
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> monitoring kernel firmware directory '/usr/lib/firmware'.
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.3/0000:02:00.0/iee
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC20
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> WiFi hardware radio set enabled
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> WWAN hardware radio set enabled
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wifi.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wwan.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-adsl.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WiFi enabled by radio killswitch; enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WWAN enabled by radio killswitch; enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WiMAX enabled by radio killswitch; enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Networking is enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): link connected
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): carrier is ON
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): carrier is OFF
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): new Ethernet device (driver: 'r8169' ifindex: 2)
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): exported as /org/freedesktop/NetworkManager/Devices/1
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
aug 26 19:14:36 arch_daboka systemd[1]: Started Network Manager.
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): preparing device
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): using nl80211 for WiFi device control
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): driver supports Access Point (AP) mode
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): exported as /org/freedesktop/NetworkManager/Devices/2
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): preparing device
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> use BlueZ version 5
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> wpa_supplicant started
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0) supports 4 scan SSIDs
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: starting -> ready
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: ready -> disconnected
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0) supports 4 scan SSIDs
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: disconnected -> inactive
aug 26 19:14:42 arch_daboka NetworkManager[527]: <info> startup complete
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Auto-activating connection 'Bokros'.
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) starting connection 'Bokros'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) scheduled...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) started...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTING
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) scheduled...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) complete.
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) starting...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0/wireless): connection 'Bokros' has security, and secrets exist. No new sec
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'ssid' value 'Bokros'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'scan_ssid' value '1'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'psk' value '<omitted>'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: set interface ap_scan to 1
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: inactive -> authenticating
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: authenticating -> associated
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: associated -> 4-way handshake
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: 4-way handshake -> completed
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireles
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) scheduled.
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) started...
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: config -> ip-config (reason 'none') [50 70 0]
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> dhcpcd started with pid 3599
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) complete.
aug 26 19:15:01 arch_daboka dhcpcd[3599]: version 6.4.3 starting
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: version 6.4.3 starting
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): DHCPv4 state changed nbi -> preinit
aug 26 19:15:01 arch_daboka dhcpcd[3599]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:01 arch_daboka dhcpcd[3599]: wlp2s0: IAID 65:59:c9:b5
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: IAID 65:59:c9:b5
aug 26 19:15:01 arch_daboka dhcpcd[3599]: wlp2s0: soliciting an IPv6 router
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: soliciting an IPv6 router
aug 26 19:15:02 arch_daboka dhcpcd[3599]: wlp2s0: rebinding lease of 192.168.1.137
aug 26 19:15:02 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: rebinding lease of 192.168.1.137
aug 26 19:15:07 arch_daboka dhcpcd[3599]: wlp2s0: leased 192.168.1.137 for 86400 seconds
aug 26 19:15:07 arch_daboka dhcpcd[3599]: wlp2s0: adding route to 192.168.1.0/24
aug 26 19:15:07 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: leased 192.168.1.137 for 86400 seconds
aug 26 19:15:07 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: adding route to 192.168.1.0/24
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): DHCPv4 state changed preinit -> reboot
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> address 192.168.1.137
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> plen 24 (255.255.255.0)
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> gateway 192.168.1.1
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> server identifier 192.168.1.1
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> lease time 86400
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> hostname 'arch_daboka'
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> nameserver '192.168.1.1'
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> domain name 'chello.hu'
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Commit) started...
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Commit) complete.
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_GLOBAL
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Policy set 'Bokros' (wlp2s0) as default for IPv4 routing and DNS.
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Writing DNS information to /usr/bin/resolvconf
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) successful, device activated.
aug 26 19:15:14 arch_daboka dhcpcd[3599]: wlp2s0: no IPv6 Routers available
aug 26 19:15:14 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: no IPv6 Routers available
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): link connected
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 4
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Auto-activating connection '1. vezetékes kapcsolat'.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) starting connection '1. vezetékes kapcsolat'
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) scheduled...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) started...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) scheduled...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) complete.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) starting...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: prepare -> config (reason 'none') [40 50 0]
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) successful.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) scheduled.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) complete.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) started...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: config -> ip-config (reason 'none') [50 70 0]
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> dhcpcd started with pid 4322
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) complete.
aug 26 19:15:34 arch_daboka dhcpcd[4322]: version 6.4.3 starting
aug 26 19:15:34 arch_daboka dhcpcd[4322]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: IAID 44:7f:89:66
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: version 6.4.3 starting
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: IAID 44:7f:89:66
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): DHCPv4 state changed nbi -> preinit
aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: soliciting an IPv6 router
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: soliciting an IPv6 router
aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: rebinding lease of 192.168.1.138
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: rebinding lease of 192.168.1.138
aug 26 19:15:39 arch_daboka dhcpcd[4322]: enp1s0: leased 192.168.1.138 for 86400 seconds
aug 26 19:15:39 arch_daboka dhcpcd[4322]: enp1s0: adding route to 192.168.1.0/24
aug 26 19:15:39 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: leased 192.168.1.138 for 86400 seconds
aug 26 19:15:39 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: adding route to 192.168.1.0/24
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): DHCPv4 state changed preinit -> reboot
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> address 192.168.1.138
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> plen 24 (255.255.255.0)
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> gateway 192.168.1.1
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> server identifier 192.168.1.1
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> lease time 86400
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> hostname 'arch_daboka'
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> nameserver '192.168.1.1'
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> domain name 'chello.hu'
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Commit) started...
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Commit) complete.
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_GLOBAL
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Policy set '1. vezetékes kapcsolat' (enp1s0) as default for IPv4 routing and DNS.
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Writing DNS information to /usr/bin/resolvconf
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) successful, device activated.
aug 26 19:15:47 arch_daboka dhcpcd[4322]: enp1s0: no IPv6 Routers available
aug 26 19:15:47 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: no IPv6 Routers available
ping -c 10 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=4.38 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=2.79 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=4.89 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=5.30 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.59 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.61 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=4.37 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=2.40 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=6.47 ms
--- 192.168.1.1 ping statistics ---
10 packets transmitted, 9 received, 10% packet loss, time 9014ms
rtt min/avg/max/mdev = 1.599/3.759/6.471/1.627 ms
ping -c 100 8.8.8.8 - it's not completely disconnected, but it's always 8 packets at once that are received
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=20 ttl=46 time=41.7 ms
64 bytes from 8.8.8.8: icmp_seq=21 ttl=46 time=40.0 ms
64 bytes from 8.8.8.8: icmp_seq=22 ttl=46 time=38.8 ms
64 bytes from 8.8.8.8: icmp_seq=23 ttl=46 time=39.3 ms
64 bytes from 8.8.8.8: icmp_seq=24 ttl=46 time=41.8 ms
64 bytes from 8.8.8.8: icmp_seq=25 ttl=46 time=38.4 ms
64 bytes from 8.8.8.8: icmp_seq=26 ttl=46 time=38.4 ms
64 bytes from 8.8.8.8: icmp_seq=27 ttl=46 time=38.0 ms
64 bytes from 8.8.8.8: icmp_seq=56 ttl=46 time=43.4 ms
64 bytes from 8.8.8.8: icmp_seq=57 ttl=46 time=49.8 ms
64 bytes from 8.8.8.8: icmp_seq=58 ttl=46 time=40.2 ms
64 bytes from 8.8.8.8: icmp_seq=59 ttl=46 time=44.3 ms
64 bytes from 8.8.8.8: icmp_seq=60 ttl=46 time=38.5 ms
64 bytes from 8.8.8.8: icmp_seq=61 ttl=46 time=43.4 ms
64 bytes from 8.8.8.8: icmp_seq=62 ttl=46 time=39.2 ms
64 bytes from 8.8.8.8: icmp_seq=63 ttl=46 time=40.5 ms
64 bytes from 8.8.8.8: icmp_seq=92 ttl=46 time=38.3 ms
64 bytes from 8.8.8.8: icmp_seq=93 ttl=46 time=43.7 ms
64 bytes from 8.8.8.8: icmp_seq=94 ttl=46 time=42.3 ms
64 bytes from 8.8.8.8: icmp_seq=95 ttl=46 time=46.6 ms
64 bytes from 8.8.8.8: icmp_seq=96 ttl=46 time=44.9 ms
64 bytes from 8.8.8.8: icmp_seq=97 ttl=46 time=42.9 ms
64 bytes from 8.8.8.8: icmp_seq=98 ttl=46 time=41.7 ms
64 bytes from 8.8.8.8: icmp_seq=99 ttl=46 time=37.8 ms
--- 8.8.8.8 ping statistics ---
100 packets transmitted, 24 received, 76% packet loss, time 99062ms
rtt min/avg/max/mdev = 37.886/41.455/49.829/3.000 ms
cat /etc/dhcpcd.conf - I tried clientid instead of duid and disabling IPv6, but neither of those helped.
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.
# Inform the DHCP server of our hostname for DDNS.
hostname
# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
duid
# Persist interface configuration when dhcpcd exits.
persistent
# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit
# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
# Some interface drivers reset when changing the MTU so disabled by default.
#option interface_mtu
# A ServerID is required by RFC2131.
require dhcp_server_identifier
# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private
# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname
#noipv4ll
#Disable IPv6
#noipv6rs
#noipv6
cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=keyfile
dhcp=dhcpcd
## Set static hostname
#[keyfile]
#hostname=foobar
## HTTP-based connectivity check
#[connectivity]
#uri=http://nmcheck.gnome.org/check_network_status.txt
I couldn't find anything else to append, but if there are other log or conf files or anything else, which would help solving the problem, I should put here, please tell me.

Try to use dhclient perhaps? Might I also suggest letting systemd deal with the dhcp issue and not NM. That may seem incongruous but it is possible NM is mis-handling the dhcp hand-off to the network card. I'm no guru but I got thinking about this when I saw this in your output:
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
It is very possible that I'm mis-interpreting this information so please take it with a boulder of salt.

Seems RTL8192EE wireless card doesn't work with Linux 3.19

Hi all, I just fresh installed ArchLinux on my new Thinkpad T450s. The installation has been smooth enough. I can use wifi-menu on ArchISO image (which is based on kernel 3.18.6) to get my wifi connected. Everything works great. But when I reboot into the new hard disk installation, the WiFi connection always fails.
I have tried to connect manually via wpa_supplicant and dhcpcd. It didn't show any error information like driver issue or so. The problem I can see is the link is really slow: too slow to get authenticated by router. At a small chance I can connect to the WiFi but then failed to get dhcpcd work. And at a really really small chance I can get an IP from the router but the ping latency to gateway is about seconds, so I cannot visit any service via this network.
This issue happens to Linux 3.19. I have tested on 3.19.2 in core and 3.19.3 in testing.
Is there any of you have the same issue, and is there a solution for this currently?
EDIT: typo
Last edited by sunng (2015-04-02 07:16:12)

fabiopicchi wrote:
For those using kernel 4.0, the problem is partially gone. The wireless connection doesn't randomly drops and you can always connect correctly but you can get really slow speed, and sometimes all packages are lost.
Installing this new version of the driver solves the problem:
sudo git clone http://github.com/lwfinger/rtlwifi_new.git
cd ./rtlwifi_new
sudo make
sudo make install
sudo modprobe -v rtl8192ee
Yes, rtlwifi_new works for me. I do hope this can be merged into mainline some day.

WRT54GS v7 loses wireless connectivity after 15 minutes or so

I just installed a WRT54GS v7 router to work with my cable modem. It has the latest firmware. The wireless connection seems to work for about 15 minutes or so at a time and then it stops working. I can't even get to 192.168.1.1. The only way to get it to work is unplug the router and plug it back in. Originally, I thought it was interference from my 2.8GHz cordless phone, so I unpluged it. But that still didn't fix the problem. What could be the problem? Thanks.

@mallinj
Hi,
Disconnect from Internet.
Uninstall from Your system audio drivers.
Resources:
Uninstalling Software in Windows 7
Uninstall or change a program in Windows 7
Restart Your system:
On boot press ' F8 ' and choose ' Safe mode '.
Go to Control Panel -> Devices Manager -> Network Cards
and find there Athero Wireless card. Click on it with right button of Your mouse and choose uninstall driver.
Restart Your system and this time start it in normally.
Install latest driver:
Atheros Wireless here (ver 8.0.0.238 for 32/64 bit Win7)
** Say thanks by clicking the "Thumb up" icon which is on the left. **
** Make it easier for other people to find solutions, by marking my answer with "Accept as Solution" if it solves your issue. **

HP P1102w Wireless Function Doesn't Work!

- I am tech savvy
- used search, google, etc.
- Mac OS X 10.8.3
- HP P1102w, driver 5.0
1. installed "HP LaserJet Full Feature Software and Driver"
2. watched http://youtu.be/c972ybZvZzo
3. after inputting my wireless information (SSID, password), I am redirected to a blank page with this url: http://localhost:5050/cgi-bin/ip_wireless_result.htm
The USB works, but the wireless feature doesn't work at all. Why does life have to be so hard? This is extremely frustrating.

I know that sometimes just pressing the wireless button one time can disable the wireless feature unless you are certain your wireless feature is completely broken. I suggest holding down the cancel button for five to ten seconds until the configuration page prints out and it will provide you with some information in the network section (for example: Wireless DISABLED) if it is not working.
Also, here is a link to the firmware update for this printer designed for your Mac - Version: 20130213. I know this printer can be confusing so here is a link with the User Guide for this model.
I would print that configuration page and try to update the firmware and see if that fixes this for you. Let me know if it works. If not, do you see anything in the network section of that page that prints out that says it has been disabled?
Don't forgot to say thanks by giving "Kudos" if I helped solve your problem.
When a solution is found please mark the post that solves your issue.
Every problem has a solution!

Apple Wireless Keyboard doesn't work in Vista Ultmate?

My Apple Wireless Keyboard doesn't work (not response) on Vista Ultmate but its works properly in Mac OS X 10.5.2...
Should I install the driver in Mac OS first or update the keyboard firmware?
Or install a driver for Windows Vista (I can't find any on web...)
Please kindly help! Thanks a lot.

this problem is fixed, but if anybody has an idea what happened, I would like to know.

Every app on my ipod (2nd gen) which requires wifi connection doesn't work although the wifi mark is on. i did try restarting my ipod, resetting network setting, disconnect from wifi and reconnected it but non of them worked.

every app on my ipod (2nd gen) which requires wifi connection doesn't work although the wifi mark is on. i did try restarting my ipod, resetting network setting, disconnect from wifi and reconnected it but non of them worked.

This may sound silly but try your date a time setting my ipod had the same problem and i had even checked the the date and time went all the way to the apple store for help and the genius guy just rest the date and time and it worked just fine.

The HP (USB connected) and Epson (wireless) printers keep losing their connection with my Mac mini. I have to physically disconnect the HP and then reconnect for the Mac to find it. Turning off the wireless Epson doesn't work. All software is updated.

My HP (USB connected) and Epson (wireless) printers keep losing their connection with my Mac mini. I have to physically disconnect the HP and then reconnect for the Mac to find it. Turning off the wireless Epson doesn't resolve anything. All software/drivers have been updated.

My HP (USB connected) and Epson (wireless) printers keep losing their connection with my Mac mini. I have to physically disconnect the HP and then reconnect for the Mac to find it. Turning off the wireless Epson doesn't resolve anything. All software/drivers have been updated.

Wireless Music doesn't work with new software

Hello-
I can't get my wireless music to work after I update the software to the latest version. The only one that will work is when I install it from the CD. But, I would like to use the most recent version of the software. As soon as I update, the Media Server won't launch on my computer. I am using a linksys WRT54G wireless router. If I check DHCP clients, the wireless music receiver is successfully getting an IP address. I have tried all of the things that linksys suggested (disable WEP, firewall, broadcast SSID, etc...) to no avail. Has anyone gotten the latest media server software to work with WRT54G? I have tried it on both my XP and W2K machine, with the same results (doesn't work).
Thanks,
Rich

Hi Jeremy
I have the similar problem, I've installed the software on my desktop, no error messages (apart from the certificate) and everything seems to be fine. After about 2 minutes the message appears that the network is not ready and consequently the media server is not running.
Without the server running I can't setup the Network and the entire system is not working. I could ping it but that was about it.
I've reset my router, renamed the SSID, tried with and without WEP, MAC, without firewall, opened a new account on my desktop with admin rights installed the software again into a new folder - result still not working, same error message.
To make really bad, I installed it on my laptop, same procedure and it works fine! So it seem that it has nothing to do with my wireless devices or configurations, there must be a problem while setting up the software on my desktop.
I really would appreciate your help a lot!

Cheers

Balz

Wireless Printing Doesn't Work

In February I had to purchase a Mac desktop computer due to the failure of my semi-old HP Windows computer. When we bought the Mac we also purchased a new printer since it would be cheap since we bought it with the computer. The printer is a HP Photosmart Plus B210a series model and so it has wireless printing. However, the only way to get the 'wireless printing' to work is if you first install the software. Seems good, right? No. After proceeding to turn off the printer like every normal person since you don' want to leave it on, everything goes wrong. If you turn the printer on at some time, the wireless printing won't work at all! Even if I disconnect and reconnect the WiFi to it and print the diagnostics page, where everything turns out normal EVERYTIME. This is quite thoroughly making me irate because to get the wireless printing to work again, you have to uninstall the software and reinstall it. I got so fed up with it the other night that I connected a USB cord to it, which totally defeats the purpose of the entire printer since it's suppose to be hi-tech for it's wireless printing and e-services ( which require WiFi). Can anyone please help me figure out how to have the printer continuously working so it doesn't just stop when I turn it off?
Solved!
Go to Solution.

By the fact that you desire the printer to be turned off, I would think that you probably shut off your computer and other devices as well? You do this every time you're done?
There are two schools of thought on this.
Turning it off:
- Reduces electrical usage versus leaving it on in low power or 'sleep mode'. In today's modern terms, you'll probably save about $40 a year.
- If you have a fan or cooling issue, such as you're in a tight space with no airflow, this can reduce heat and cause hardware to last longer.
- No one can access your machine or other devices when they are turned off. This prevents virus's from executing or running so long as the machine *remains* off.
Leaving it on:
- Allows programs to update automatically when you are not there, dramatically reducing the chances of getting a virus and also giving you the latest version of your software.
- Virus scans can be run *automatically* to fully scan your computer while your not there, making it unnessasary to do this when you're actually using the computer, and therefore speeding up the computer greatly.
- Instant-access to what you're doing, instead of having to wait for the machine and devices to turn on.
- If you're sharing files, folders, or printers, this makes them available on the network.
Computers and their accessory devices are designed to run 24/7, 365 days a year. They are also designed to be shut off every night, if that is your preference. However, I think the benefits of leaving things on greatly outweigh the benefits of turning things off. Again, however, it's a personal decision.
If you decide to turn your devices off after use, please spend the time at each session to download and make updates to your computer, especially WIndows Updates and anti-virus databases. Especially with the anti-virus updates, try not to access the internet until you have the latest anti-virus update installed.
I am a Bestbuy employee who volunteers on these boards on my own time. I am not paid for posting here, and you should understand that my opinions are exactly that - opinions. I do not represent Bestbuy in any way.
: Open Mailbox

WRT54G V8 Dropping wireless connection

Hello,
I have an issue with my Lynksys WRT54G V8 (firmware upgraded to V8.00.2). No problem whatsoever with wired connection, however, it appears to drop my wireless connection every 10 or so minutes. I appear to be able to connect to my neighbors unsecured connection with no problem however.   The only way I can figure out to reconnect is to power the device off and on again. Disabling and enable the wireless adapter on my laptop does nothing.
Here is what I have tried:
I have moved the device to be closer to my laptop (it is now approximately 6 inches away).
I have changed the channel to be 11 instead of default 6.
I have changed client lease time from 0 to 999
I have upgraded the firmware to 8.00.2
Verified that my SSID is unique
This is the 3rd wireless setup I have done (separate places, 1 office and 1 in my home and this one in my vacation home). This is the first time I have had any issues. It is the same laptop, I have the same model of cordless phone in my home as the vacation home.   The only thing I am not sure of is the firmware level of the other two devices. They are the same model.
Any suggestions before I return this device and buy another model?
Thank you

After a firmware upgrade, you must reset the router to factory defaults, then setup the router again from scratch. If you have not done this since the last firmware upgrade, please do this now, and see if it corrects your problem. If you saved a router configuration file, DO NOT use it.    If the above does not fix your problem, then read on:
There are many causes for poor wireless connections, and many solutions:
Set "SSID Broadcast" to "enabled". This will help your computer find and lock on to your router's signal.
Poor wireless connections are often caused by radio interference from other 2.4 GHz devices. This includes wireless phones, wireless baby monitors, microwave ovens, wireless mice and keyboards, wireless speakers, and your neighbor's wireless network. In rare cases, Bluetooth devices can interfere. Even some 5+ GHz phones also use the 2.4 Ghz band. Unplug these devices, and see if that corrects your problem.
In your router, try a different channel. There are 11 channels in the 2.4 GHz band. Usually channel 1, 6, or 11 works best. Check out your neighbors, and see what channel they are using. Because the channels overlap one another, try to stay at least +5 or -5 channels from your strongest neighbors. For example, if you have a strong neighbor on channel 9, try any channel 1 through 4.
Also, try to locate the router about 4 to 6 feet above the floor, in an open area. Do not locate it behind your monitor or near other computer equipment or speakers. The antenna should be vertical.
Also, in the computer, go to your wireless software, and go to "Preferred Networks" (sometimes called "Profiles" ). There are probably a few networks listed. Delete any network named "linksys". Also delete any network that you do not recognize, or that you no longer use. If your current network is not listed, enter its info (SSID, encryption (if any), and key (if any) ). Then select your current network and make it your default network, and set it to automatic login. You may need to go to "settings" to do this, or you may need to right click on your network and select "Properties" or "settings".
Also, you did not mention what type of encryption you were using. If you are using WPA2, or "WPA with AES" (= WPA2 ), then note that Windows XP requires a patch to run WPA2. Go to Microsoft Knowledge base, article ID=917021 and it will direct you to the patch.
Sadly, the patch is not part of the automatic Windows XP updates, so lots of people are missing the patch.
If the above does not fix your problem, download and install the latest driver for your wireless card.
If you continue to have trouble, try the following:
For wireless g routers, try setting the "Transmission Rate" to 54 Mbps. For wireless n routers, try setting the "n Transmission Rate" to 162 Mbps, and the (wireless g) "Transmission Rate" to 54 Mbps.
If you still have trouble, download and re-install the latest firmware for your router. After a firmware upgrade, you must reset the router to factory defaults, then setup the router again from scratch. If you saved a router configuration file, DO NOT use it.
Hope this helps.

Wireless mouse doesn't work after installing iTunes

New 30Gb iPod, installed iTunes v6 on 6-mos old HP laptop with docking station/wireless keyboard/mouse. All is well, updated iTunes with latest from web, loaded songs on iPod BUT now wireless mouse will not work. Reset mouse, works for a few clicks, then dies. Reset mouse again, few more clicks, then dies. Reboot without iPod connected, no iTunes up, still mouse only works for a couple clicks. Touchpad on laptop works, also so does wireless keyboard so I know transmitter is working (not battery problem). All worked fine until I started playing with options in iTunes today. I didn't uninstall iTunes yet, is that next step? Anyone else have this problem? Suggestions???

I'm pretty sure it's probably just your mouse/computer, however I would recommend uninstalling iTunes just to make sure though.

Apple wireless keyboard doesn't work in windows all of a sudden how to fix please?

Hi All,
Last night my apple wireless keyboard stop working in windows. It is working perfectly fine in the OS system though. I have checked control panel in Windows 7 and found out that under Device management "apple keyboard" has an issue there, I have tried to follow the steps windows suggest but it doesn't work...How can I fix this please? Thanks a lot

this problem is fixed, but if anybody has an idea what happened, I would like to know.

WRT54GS v4.0 wireless connection doesn't work... *Edit: Resolved*

Similar Messages

Maybe you are looking for

WRT54GS v4.0 wireless connection doesn't work... Edit: Resolved