[opensuse] permanently leased wireless DHCP IP address not always assigned/in range
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. If I set it to the desired static IP address, it "takes", but manually specifing nameserver/router doesn't. Doing this rebooting and going back to DHCP and rebooting several times will often produce the desired results of the wireless nic getting its permanantly leased, DHCP-assigned IP address. Note, that when the IP addressed is assigned within the specified DHCP range, it is always the correct one - the one the notebook was initially assigned. But often the wireless, and only the wireless, gets an address outside of the range. TIA, ds -- Dennis E. Slice Department of Anthropology University of Vienna ======================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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. -- kai - theperfectreign@yahoo.com www.perfectreign.com || www.4thedadz.com www.filesite.org || www.donutmonster.com closing the doors that surround me so no one will ever penetrate complete my retreat just to wait for the day that never comes, so I will laugh alone -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Does your wireless router have the ability to set its essid. On my router I set the essid and I instruct my wireless network cards to attach to that essid. I use wep encryption and I have on average about 9 wifi networks in range. John -- Registered Linux User 263680, get counted at http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Yes, and the problem seems to have been solved. The reason I couldn't find the place to specify the ESSID in Yast2 was because it only appears after you accept the changes to the network card configuration, which I was reluctant to mess with since it was working. To recap: Problem:DHCP not assigning IP addresses within the designated range. Cause: Another wireless network was interfering. Soln: 1) Set wireless hub to unique ESSID. 2) Set network card (on 2nd page after accepting card changes) to use specified ESSID. Thanks to all. -ds John Pierce wrote:
Does your wireless router have the ability to set its essid. On my router I set the essid and I instruct my wireless network cards to attach to that essid. I use wep encryption and I have on average about 9 wifi networks in range.
John
-- Dennis E. Slice Department of Anthropology University of Vienna ======================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Dennis E. Slice -
John Pierce -
Kai Ponte