Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Thank you Stoad for the answer.
Sadly the physical on/off switcher is ok, but I don't understand when you talk about the "wired NIC".
How can I disable that at boot? Sorry for that!
So, I try to use DHCP-4.2.5-P1 then Dynamic Ip's.
Now I can connect to Internet with ethernet, but wireless network still not working, and I really don't know hot to proceed.
I past my last configuration of:
"/etc/udev/rules.d/70-persistent-net.rules", "/etc/sysconfig/ifconfig.eth0", "/etc/sysconfig/ifconfig.wlan0",
"/etc/resolve.conf", "/etc/hosts".
Code:
root [ / ]# cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# net device tg3
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:18:8b:bf:d8:00", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# net device iwl3945
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:19:d2:6c:e7:5e", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
Code:
root [ / ]# cat /etc/sysconfig/ifconfig.eth0
ONBOOT="no"
IFACE="eth0"
SERVICE="dhclient"
DHCP_START=""
DHCP_STOP=""
# Set PRINTIP="yes" to have the script print
# the DHCP assigned IP address
PRINTIP="no"
# Set PRINTALL="yes" to print the DHCP assigned values for
# IP, SM, DG, and 1st NS. This requires PRINTIP="yes".
PRINTALL="no"
Code:
root [ / ]# cat /etc/sysconfig/ifconfig.wlan0
ONBOOT="yes"
IFACE="wlan0"
SERVICE="dhclient"
DHCP_START=""
DHCP_STOP=""
# Set PRINTIP="yes" to have the script print
# the DHCP assigned IP address
PRINTIP="no"
# Set PRINTALL="yes" to print the DHCP assigned values for
# IP, SM, DG, and 1st NS. This requires PRINTIP="yes".
PRINTALL="no"
Druna I've do the steps you said and I've got this problem when i run this command "/etc/rc.d/init.d/network start".
The output is:
Code:
root[ - ]# /etc/rc.d/init.d/network start
Bringing up the eth0 interface...
Adding IPv4 address 192.168.1.15 to the eth0 interface.. [ OK ]
Setting up the default gateway..RTNETLINK answers: Network is unreachable [ FAIL ]
******
Bringing up the wlan0 interface...
Adding IPv4 address 192.168.100.15 to the wlan0 interface.. [ OK ]
Setting up the default gateway..RTNETLINK answers: Network is unreachable [ FAIL ]
EDIT: I found this answer in "wiki.archlinux.org":
"RTNETLINK answers: Cannot assign requested address
If you get this error when trying to set an interface up, its most probably because you've got an invalid MAC adress. To set a working MAC, see MAC Address Spoofing."
I'm rather sure that this isn't a MAC address problem. This error is probably related to the GATEWAY=62.101.93.101 entries.
I might have overlooked something important: How do you connect to the outside world?
- Do you have a modem between your computer and your ISP? Or do you connect from your computer straight to the ISP? (please answer for both wired and wireless).
BTW: Can you post the output of the ifconfig -a and route command (just ignore the error message about RTNETLINK). This to make sure that the basic setup is correct and both devices are seen and can be activated.
When I was connected with eth0 i do the commands you said: "ping -c2 lfs", "ping -c2 lfs_wl", "ping -c2 www.linuxquestions.org", and there are the results:
Code:
root [ ~ ]# ping -c2 lfs
PING lfs.wired.home (192.168.1.15): 56 data bytes
64 bytes from 192.168.1.15: icmp_seq=0 ttl=64 time=0.095 ms
64 bytes from 192.168.1.15: icmp_seq=1 ttl=64 time=0.067 ms
--- lfs.wired.home ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.067/0.081/0.095/0.000 ms
root [ ~ ]# ping -c2 lfs_wl
PING lfs_wl.wireless.home (192.168.100.15): 56 data bytes
--- lfs_wl.wireless.home ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
root [ ~ ]# ping -c2 www.linuxquestions.org
PING www.linuxquestions.org (75.126.162.205): 56 data bytes
64 bytes from 75.126.162.205: icmp_seq=0 ttl=47 time=159.283 ms
64 bytes from 75.126.162.205: icmp_seq=1 ttl=47 time=157.094 ms
--- www.linuxquestions.org ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 157.094/158.189/159.283/1.095 ms
You fixed the gateway problem for eth0, which is now up and running.
I'm not sure why you changed the wlan ip address, leave it as suggested by me in post #19 (IP=192.168.100.15 / BROADCAST=192.168.100.255). Why, you might ask: Eth0 and wlan0 are 2 different devices, it would be wise to put them on different networks.
When using a static IP address you have to make sure that that IP address is also used in /etc/hosts (it doesn't seem to be so, looking at the # ping -c2 lfs_wl output (which points to 192.168.100.15).
Does your wireless also make use of the router to connect to the outside world? If not, then how? You might need a different gateway address or have to make use of dhcp (which I overlooked originally, sorry about that).
I know this is old; I found this thread when trying to set up iwl3945.
Quote:
I'm not sure how to fix the following:
root [ ~ ]# iwlist wlan0 scan
wlan0 interface doesn't support scanning
I had this same problem until recompiling my kernel with cfg80211:
Networking support --->
Wireless --->
cfg80211 - wireless configuration API: Y or M
cfg80211 wireless extensions compatibility: Y
Generic IEEE 802.11 Networking Stack (mac80211): Y or M
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.