On Sun, May 16, 2004 at 04:17:33PM +0100, Martin Michlmayr wrote: > > netgear wlan card was detected and driver was loaded, i could not see or > > select the ESSID of the network it connected to, but was only asked for > > a WEP key. This is correct behavior. It is supposed to select an ESSID by itself the first time. However, in netcfg 0.63, you must Go Back and Configure the network again (with the lower debconf priority) if you would like to configure your ESSID. In the new one, when DHCP fails, you are offered a chance to reconfigure your wireless network, at which point you may set the ESSID explicitly. > > since there is no dhcp on the net, dhcp failed; the installer did > > not offer me the manual config instead, but tried to access the debian > > mirror. back in the main menu, typing in the ip address the interface > > was not configured. switched to the console and configured it by hand. I'm dumbfounded at this one. I think this may be due to the horrible UI misunderstanding that is netcfg/dhcp_retry (see #244901, already fixed in trunk.) Basically, if you hit No in netcfg 0.63, it should go to static network configuration. This has been replaced by a descriptive menu in trunk, as you may have seen already. > > after rebooting the wlan interface moved from eth1 to eth2 since the > > firewire interface was found and used as eth1. > > Are you sure firewire took up eth1 and not your Realtek Ethernet chip? > (or is that eth0, I guess?). Why would firewire appear as an eth > device? Is that some kind of firewire ethernet? That happens even in Windows XP. :| Could we use nameif? -- Joshua Kwan
Attachment:
signature.asc
Description: Digital signature