Am Mittwoch, 6. März 2013, 11:44:27 schrieb Pierre M.R.: > Ethan Oldale wrote: > > Hello > > > > I have recently finished installing LFS 7.2, and then onto BLFS 2013-02-23 > > > > I went up to chapter 3, and did the acl, attr, ca certs, iptables, and > > openssl parts from chapter 4. > > > > Then I went to the networking section and installed ISC DHCP client, > > wget, wireless tools, links and all required and recommended > > dependencies, except relating to X. > > > > Then I installed wpa_supplicant (and libnl beforehand) without dbus or qt. > > > > I rebooted, and wpa_supplicant seemed to start fine, and ip addr > > reported that wlan0 had an ip address, except I could not ping my > > wireless router or my modem, or ping a url or open a url with links. > > > > > > root [ ~ ]# ifdown wlan0 > > > > * ping dhclient on the wlan0 interface... [ OK ] > > > > * ping wpa_supplicant on the wlan0 interface... [ OK ] > > * Bringing down the wlan0 interface... [ OK ] > > > > root [ ~ ]# ifup wlan0 > > > > Bringing up the wlan0 interface... > > > > Starting wpa_supplicant on the wlan0 interface...[ 271.770568] > > > > b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07) > > [ 271.829215] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > > * [ OK ] > > > > Starting dhclient on the wlan0 interface...[ 280.634519] IPv6: > > ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready > > * [ OK ] > > root [ ~ ]# ip addr > > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN > > > > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > > inet 127.0.0.1/8 scope host lo > > inet6 ::1/128 scope host > > > > valid_lft forever preferred_lft forever > > > > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast > > state UP qlen 1000 > > > > link/ether 04:7d:7b:39:80:37 brd ff:ff:ff:ff:ff:ff > > inet 192.168.1.1/24 brd 192.168.1.255 scope global eth0 > > inet6 fe80::67d:7bff:fe39:8037/64 scope link > > > > valid_lft forever preferred_lft forever > > > > 4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP > > qlen 1000 > > > > link/ether 20:10:7a:2e:cc:ba brd ff:ff:ff:ff:ff:ff > > inet 192.168.1.65/24 brd 192.168.1.255 scope global wlan0 > > inet6 fe80::2210:7aff:fe2e:ccba/64 scope link > > > > valid_lft forever preferred_lft forever > > > > root [ ~ ]# [ 293.198603] cfg80211: Calling CRDA to update world > > regulatory domain > > ping [ 303.218491] kworker/u:0 (5) used greatest stack depth: 3496 > > bytes left > > 192.168.1.255 > > PING 192.168.1.255 (192.168.1.255): 48 data bytes > > [ 388.149868] cfg80211: Calling CRDA to update world regulatory domain > > [ 393.579256] cfg80211: Calling CRDA to update world regulatory domain > > ^Z > > [4]+ Stopped ping 192.168.1.255 > > root [ ~ ]# ping 192.168.1.254 > > PING 192.168.1.254 (192.168.1.254): 48 data bytes > > [ 435.134727] cfg80211: Calling CRDA to update world regulatory domain > > 60 bytes from 192.168.1.1: Destination Host Unreachable > > Vr HL TOS Len ID Flg off TTL Pro cks Src Dst Data > > > > 4 5 00 4c00 0000 0 0040 40 01 61b6 192.168.1.1 192.168.1.254 > > > > ^Z > > [5]+ Stopped ping 192.168.1.254 > > root [ ~ ]# [ 448.756344] cfg80211: Calling CRDA to update world > > regulatory domain > > > > > > Does anyone have any idea what might be causing this? > > > > Thanks, > > Ethan > > ip addr shows the wlan0 interface has the IP adress 192.168.1.65 given > by the router (is it also a modem ?). > The gateway and nameserver (written in /etc/resolv.conf) should be the > IP adress of the router. > If the router adress happens to be 192.168.1.1 there is a potential > conflict with eth0 interface IP address. > > Pierre
also check what "ip route show" lists when you have the wlan stuff active. -- Thomas -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
