On Tue, 16 Mar 2004 16:49:20 -0600, Michael Satterwhite wrote: > <Booting from CD. Main goal was to test the wireless network setup in > installation. I have a Linksys WPC11V3 card which should talk to a Linksys > BEFW11S4. It was not able to pull an IP address from the router, but I've > seen this happen before. I gave it a static IP address - which I actually > prefer. It would be nice if this were an opton in the installer.
Here's how it all works: At the default priority, netcfg will NOT ask a question about your wireless ESSID. It will do the equivalent of 'iwconfig wlan0 essid any' and then run the DHCP client. If that fails, you should be asked for a static IP, and this is obviously where you got. But the reason the validity of your network connectivity was never checked was because the netinst images do not require you to configure the network to install the base system. By the way, I have, however, fixed a problem where the WEP key-setting question was never asked, if that was the reason why you could not configure the network successfully.. > After the reboot, I was informed that I did not have an internet > connection, so the wireless setup did not work. It would have been nice > if I had been informed of this much earlier in the installation - > possibly at the point that it was configuring the network. For all > intents and purposes, everything I did after that point - most of what > was done - was wasted time. I really don't know how we can test to see that your connection to the network is functioning, especially if you have specified an IP address by yourself. (Perhaps 'ping <gateway>', but I don't think busybox has a ping utility.) Or we could try to download a Release file or a random file from a Debian server if we knew that it was an internet connection (hm, and how do we do that?) -- Joshua Kwan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
