Wireless
Bill Davidsen
davidsen at tmr.com
Wed Dec 1 13:46:52 UTC 2010
Antonio Olivares wrote:
>> Check your
>
>> /etc/resolv.conf
>>
>> Are you on DHCP or on static IP address?
>> DHCP usually overwrites /etc/resolv.conf.
>>
>> --
>> users mailing list
>> users at lists.fedoraproject.org
>> To unsubscribe or change subscription options:
>> https://admin.fedoraproject.org/mailman/listinfo/users
>> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>
> @JD
> yes, I have checked /etc/resolv.conf and it contains 192.168.1.1 which is what
> is in windows it matches.
>
> @Bill
> Yes I see two to three bars and it(networkmanager) tells me that I am connected,
> yet I cannot surf the net or add updates. I got it working once, but now I
> can't anymore :(,
>
If you have a connect to your access point, then time to ping the AP and be sure
packets are going. Then look at your routing with
netstat -rn
and see if the default route is through the AP. Note that you still might have a
problem with the connect between the AP and the net, if the AP isn't configured
correctly.
Should see something like this:
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.41.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.41.100 0.0.0.0 UG 0 0 0 eth0
One step at a time...
> I read up on
>
> http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch13_:_Linux_Wireless_Networking
>
>
> and I tried iwconfig as root:
>
> [olivares at quadcore ~]$ su -
> Password:
> [root at quadcore ~]# iwconfig
> lo no wireless extensions.
>
> eth0 no wireless extensions.
>
> eth1 no wireless extensions.
>
> wlan0 IEEE 802.11bg ESSID:"DirtyAL-Server-Wireless"
> Mode:Managed Frequency:2.412 GHz Access Point: C0:3F:0E:1C:B5:EC
> Bit Rate=24 Mb/s Tx-Power=27 dBm
> Retry long limit:7 RTS thr:off Fragment thr:off
> Encryption key:off
> Power Management:off
> Link Quality=34/70 Signal level=-76 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> virbr0 no wireless extensions.
>
> [root at quadcore ~]#
>
> Nov 27 11:13:58 quadcore NetworkManager[1333]:<info> (wlan0): canceled DHCP
> transaction, DHCP client pid 2302
> Nov 27 11:13:58 quadcore dnsmasq[1786]: reading /etc/resolv.conf
> Nov 27 11:13:58 quadcore dnsmasq[1786]: using nameserver 192.168.1.1#53
> Nov 27 11:13:58 quadcore avahi-daemon[1353]: Withdrawing address record for
> 192.168.1.7 on wlan0.
> Nov 27 11:13:58 quadcore avahi-daemon[1353]: Leaving mDNS multicast group on
> interface wlan0.IPv4 with address 192.168.1.7.
> Nov 27 11:13:58 quadcore avahi-daemon[1353]: Interface wlan0.IPv4 no longer
> relevant for mDNS.
> Nov 27 11:13:58 quadcore NetworkManager[1333]:<info> Updating /etc/hosts with
> new system hostname
> Nov 27 11:13:58 quadcore nm-dispatcher.action: nm_dispatcher_action: Invalid
> connection: '(null)' / 'connection setting not found' invalid: 1
> Nov 27 11:14:14 quadcore NetworkManager[1333]: ifcfg-rh: removed
> /etc/sysconfig/network-scripts/ifcfg-Auto_DirtyAL-Server-Wireless.
> Nov 27 11:14:14 quadcore NetworkManager[1333]: ifcfg-rh: removed
> /etc/sysconfig/network-scripts/ifcfg-Auto_DirtyAL-Server-Wireless.
>
> [root at quadcore ~]#
>
> I removed the connection and tried to reconnect it again, and I see
>
>
> scanning
> Nov 27 11:32:16 quadcore NetworkManager[1333]:<info> (wlan0): supplicant
> connection state: scanning -> associating
> Nov 27 11:32:17 quadcore NetworkManager[1333]:<info> (wlan0): supplicant
> connection state: associating -> associated
> Nov 27 11:32:18 quadcore NetworkManager[1333]:<info> (wlan0): supplicant
> connection state: associated -> 4-way handshake
> Nov 27 11:32:18 quadcore NetworkManager[1333]:<info> (wlan0): supplicant
> connection state: 4-way handshake -> group handshake
> Nov 27 11:32:18 quadcore NetworkManager[1333]:<info> (wlan0): supplicant
> connection state: group handshake -> completed
> Nov 27 11:32:18 quadcore NetworkManager[1333]:<info> Activation
> (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to
> wireless network 'DirtyAL-Server-Wireless'.
> Nov 27 11:32:18 quadcore NetworkManager[1333]:<info> Activation (wlan0) Stage 3
> of 5 (IP Configure Start) scheduled.
> Nov 27 11:32:18 quadcore NetworkManager[1333]:<info> Activation (wlan0) Stage 3
> of 5 (IP Configure Start) started...
> Nov 27 11:32:18 quadcore NetworkManager[1333]:<info> (wlan0): device state
> change: 5 -> 7 (reason 0)
> Nov 27 11:32:18 quadcore NetworkManager[1333]:<info> Activation (wlan0)
> Beginning DHCPv4 transaction (timeout in 45 seconds)
> Nov 27 11:32:18 quadcore NetworkManager[1333]:<info> dhclient started with pid
> 32183
> Nov 27 11:32:18 quadcore NetworkManager[1333]:<info> Activation (wlan0) Stage 3
> of 5 (IP Configure Start) complete.
> Nov 27 11:32:18 quadcore dhclient[32183]: Internet Systems Consortium DHCP
> Client 4.2.0
> Nov 27 11:32:18 quadcore dhclient[32183]: Copyright 2004-2010 Internet Systems
> Consortium.
> Nov 27 11:32:18 quadcore dhclient[32183]: All rights reserved.
> Nov 27 11:32:18 quadcore dhclient[32183]: For info, please visit
> https://www.isc.org/software/dhcp/
> Nov 27 11:32:18 quadcore dhclient[32183]:
> Nov 27 11:32:18 quadcore NetworkManager[1333]:<info> (wlan0): DHCPv4 state
> changed nbi -> preinit
> Nov 27 11:32:18 quadcore dhclient[32183]: Listening on
> LPF/wlan0/00:15:af:28:dc:7c
> Nov 27 11:32:18 quadcore dhclient[32183]: Sending on
> LPF/wlan0/00:15:af:28:dc:7c
> Nov 27 11:32:18 quadcore dhclient[32183]: Sending on Socket/fallback
> Nov 27 11:32:18 quadcore dhclient[32183]: DHCPREQUEST on wlan0 to
> 255.255.255.255 port 67
> Nov 27 11:32:21 quadcore dhclient[32183]: DHCPREQUEST on wlan0 to
> 255.255.255.255 port 67
> Nov 27 11:32:21 quadcore dhclient[32183]: DHCPACK from 192.168.1.1
> Nov 27 11:32:21 quadcore dhclient[32183]: bound to 192.168.1.7 -- renewal in
> 36950 seconds.
> Nov 27 11:32:21 quadcore NetworkManager[1333]:<info> (wlan0): DHCPv4 state
> changed preinit -> reboot
> Nov 27 11:32:21 quadcore NetworkManager[1333]:<info> Activation (wlan0) Stage 4
> of 5 (IP4 Configure Get) scheduled...
> Nov 27 11:32:21 quadcore NetworkManager[1333]:<info> Activation (wlan0) Stage 4
> of 5 (IP4 Configure Get) started...
> Nov 27 11:32:21 quadcore NetworkManager[1333]:<info> address 192.168.1.7
> Nov 27 11:32:21 quadcore NetworkManager[1333]:<info> prefix 24
> (255.255.255.0)
> Nov 27 11:32:21 quadcore NetworkManager[1333]:<info> gateway 192.168.1.1
> Nov 27 11:32:21 quadcore NetworkManager[1333]:<info> nameserver '192.168.1.1'
> Nov 27 11:32:21 quadcore NetworkManager[1333]:<info> Activation (wlan0) Stage 5
> of 5 (IP Configure Commit) scheduled...
> Nov 27 11:32:21 quadcore NetworkManager[1333]:<info> Activation (wlan0) Stage 4
> of 5 (IP4 Configure Get) complete.
> Nov 27 11:32:21 quadcore NetworkManager[1333]:<info> Activation (wlan0) Stage 5
> of 5 (IP Configure Commit) started...
> Nov 27 11:32:21 quadcore avahi-daemon[1353]: Joining mDNS multicast group on
> interface wlan0.IPv4 with address 192.168.1.7.
> Nov 27 11:32:21 quadcore avahi-daemon[1353]: New relevant interface wlan0.IPv4
> for mDNS.
> Nov 27 11:32:21 quadcore avahi-daemon[1353]: Registering new address record for
> 192.168.1.7 on wlan0.IPv4.
> Nov 27 11:32:22 quadcore NetworkManager[1333]:<info> (wlan0): device state
> change: 7 -> 8 (reason 0)
> Nov 27 11:32:22 quadcore NetworkManager[1333]:<info> Policy set 'Auto
> DirtyAL-Server-Wireless' (wlan0) as default for IPv4 routing and DNS.
> Nov 27 11:32:22 quadcore NetworkManager[1333]:<info> Updating /etc/hosts with
> new system hostname
> Nov 27 11:32:22 quadcore NetworkManager[1333]:<info> Activation (wlan0)
> successful, device activated.
> Nov 27 11:32:22 quadcore NetworkManager[1333]:<info> Activation (wlan0) Stage 5
> of 5 (IP Configure Commit) complete.
> Nov 27 11:32:22 quadcore nm-dispatcher.action: nm_dispatcher_action: Invalid
> connection: '(null)' / 'connection setting not found' invalid: 1
>
>
> This line worries me:
> Nov 27 11:13:58 quadcore nm-dispatcher.action: nm_dispatcher_action: Invalid
> connection: '(null)' / 'connection setting not found' invalid: 1
> also found above
>
> I checked wpa_supplicant and I ran
> # service wpa_supplicant start
> # chkconfig wpa_supplicant on
>
> and like I have posted NM puts up two/three bars that I am connected, but I
> can't browse or surf.
>
> Thanks for any tips/advice in this thread.
>
> I did not respond to the previous messages because I reinstalled Fedora 14 on
> this machine to see if I could connect like I did the first time, but now I
> can't :(
>
> Will check up above error with google 'null' .
>
> Regards,
>
> Antonio
>
>
>
--
Bill Davidsen <davidsen at tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
More information about the users
mailing list