I thought it could be a different wifi network as I was writing my initial message.
After a bit of checking, it seems that may be the problem. "iwconfig eth1" flip flops between two ESSID networks with different "Access Point" addresses (though I have "Serve as Access Point" disabled on mine) and two different signal levels. I wouldn't have thought the seniors around me would be so technically sophisticated, but I do recall one of my neighbors a few yards away is a retired corporate programmer. So, what to do? I don't see anything obvious in the Yast2 setup to tell the network card to look only for a specific ESSID or MAC address or whatever. I only allow connections by specific MAC addresses on my network. Maybe I should turn off my network and use his to do something naughty. ;-> -ds Kai Ponte wrote: > On Tuesday 23 January 2007 05:20, Dennis E. Slice wrote: >> Here's an annoying problem that I can usually address by fiddling and a >> random number of reboots, but maybe someone here has a real answer. I >> have searched the archives, but didn't recognized the problem in any of >> the listings. >> >> SUSE 10.0 >> Notebook: IBM T41 with IBM wireless and wired nics >> Desktops: >> Dell GX240 with ethernet hard card (SUSE 10.0) >> older Dell Dimension (Windows 2000) >> Networked printer: Lexmark >> Hub: Belkin 802.11b wireless >> >> Problem: I need to ping, NFS, Samba, ssh, sftp, etc. all the various >> systems on the network and access the internets. >> >> I have set up the Belkin box for DHCP with "Forever" IP leasing. >> >> This works for the hard-wired cards - systems always get the same IP >> address, and often for the wireless. But frequently, the notebook >> wireless card gets assigned an IP outside of the specified range. >> > <snip> > > Is it getting assigned a number on your network or could it be picking up > another wifi network? > > I used to have this happen with regularity, before I setup 10.1 with kwallet > handling the WPA key. > > On a very rare occasion, my laptop will still get assigned a number not > leased > previously 192.168.0.101). I simply reboot the laptop and the router. I had > found rebooting the laptop didn't do it. Also, for some reason, I needed to > have the Wintendo computer (192.168.0.100) up first. My other SUSE desktop > (192.168.0.102) usually is okay. > > Soon, the Win2K computer will be put to pasture and be replaced with a new > linux machine. -- Dennis E. Slice Department of Anthropology University of Vienna ======================================================== -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
