On Sunday 25 January 2004 10:12 pm, Glenn wrote: > On Sunday 25 January 2004 00:36, Marc Resnick wrote: > > My network, running on a linksys router, really hates my linux box. It > > uses no encryption, and has a DHCP server providing IP info for all of > > the connected boxes. The problem is, every time I boot linux, I have to > > reset the router by unplugging it then plugging it back in, kicking my > > whole family offline. Then I need to do a service network restart on > > linux, and then disable and enable the connection on another windoze box. > > I've downloaded a bunch of DHCP bugfixes and updates on mdk 9.2, and > > upgraded the firmware for my router. Anyone have a way around it? I'm on > > the verge of getting tech support from linksys, and I've had some nasty > > experiences with tech support.
There are a number of possibilities that might account for this behavior. First, the Linux box is set with a static IP address assigned that conflicts with one of the IP's that is being delegated by the linksys Router device. So, for example, the linux box is set to use 192.168.0.101 and the Router is trying to assign that address to one of the Windows boxen. When you start up, there is a conflict, when you restart the router, that removes the assigned IP addresses, restart linux claims that IP address from the router and then the other machines get other IP addresses. The solution here is to tell the router to start assigning addresses after the static one, thus start at 192.168.0.105 and leave the first few addresses for static assignments. Another possibility. You have set the router to assign a specific IP address to a MAC address that belongs to the network card in the LInux box. But the address assignments start at that address. So, the router gives the address to one of the windows boxen, then the Linux box tries to claim the address via MAC assignment, again there is a conflict with the restart resolving the conflict. This happens when you create a static assignment in the Linksys but then tell the router to start assigning addresses before or at the static assignment. I.E., I tell the router to assign 192.168.0.101 to MAC address AA-EB-16-02-DC, then tell it to start assigning addresses at 192.168.0.100. The first box on the net gets 100, the second 101, then the MAC address comes along and can't pick up 101 cause it has already been assigned. The solution here is the same as the first one, tell the router to start assigning addresses after the static ones, so start at 192.168.0.105 and leave the first few for static assignments. If you really want to troubleshoot this, we would need to know any static assignments in the router, where it starts assigning addresses and how each of the windows and linux boxen are configured. Another possible solution is to hard reset the Linksys router, clearing all of the configuration info from the device and then see if the problem goes away. If so, my guess would be a configuration conflict in the router. -- Bryan Phinney Software Test Engineer
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
