Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Gordon Newsgroups: comp.os.linux.networking Subject: Re: controlling the 'eth0' device that gets detect by ifconfig Date: 10 Aug 2012 06:13:18 GMT Lines: 27 Message-ID: References: X-Trace: individual.net GOUrRBbGMkBJ2Q2HO1UsbQjVpYUg9QvGn78whnM6bgXbkN5jY5yXc7X/3Uqvzd5Htw Cancel-Lock: sha1:ZHEXwlx9K3TuiKvWch8RdHUXRwk= User-Agent: slrn/pre1.0.0-18 (Linux) Xref: csiph.com comp.os.linux.networking:1575 On 2012-07-27, Jim Anderson wrote: > > I used to run Kubuntu linux and my network addresses would be detected > properly during startup. I have switched to crunchbang linux and my > network runs ok except on one PC the OS is not detecting the correct > port for eth0 and I don't know how to fix the problem. > > The network has two routers, one wireless and one wired using ethernet > ports. The wired router is connected to a DSL line so all of the wired > PCs should be directed to that router to connect to the world. > Unfortunately, the problem PC detects the wireless router for the > 'eth0' device. > > When I run the route command, the default address is 192.168.2.1, the > address of the wireless router, not 192.168.0.1, the address of the > wired router. If I disconnect the wireless router and reboot, then I > think it is detected the correct router, but when I run ifconfig, the > ethernet address is in inet6, not an inet4 address. > > If there a way to force the inet4 address of the wired router to be > detected? > Sure, make the address of your network card on the PC, static. Say 192.168.2.103, which is outside the DHCP range of the router. If you have only one LAN. Then as another poster has hinted at drop the second DHCP. Having two DCHPs battle it out is not really the way to go.