My DHCP settings are being lost every few hours

I have KNOPPIX 4.0 installation to my hard drive, and I choose the
"Debian" install option. This box is on my home network along with other
computers running Debian stable, Win2000 and OSX Panther. All but my
KNOPPIX box get DHCP from a wired Linksys router (BEFSR41) and function
normally. I am a newbie, so the information below may be insufficient to
solve the problem, but here goes...

My router is serving IPs between 192.168.1.100 and 1.150. But, the
KNOPPIX box thinks it is 192.168.1.15 and has no gateway. To fix this,
I've been manually entering these lines, and it works - I can ping and
resolve, as well a browse the web in an X session.

route add default gw 192.168.1.1
ifconfig eth1 192.168.1.104

However, every hour or so, it loses my settings and the network, too.
Results of 'ifconfig' and 'route' are below. How can I turn off the DHCP
settings and keep static IPs, or fix it so that it's a normal DHCP client?

Thanks in advance, and suggestions on which manuals to RTFM will be
appreciated.

Eric Saylor
Interconnection
Volunteer Coordinator
http://computers.interconnection.org
<(E-Mail Removed)>



sh-3.00$ ifconfig
eth1 Link encap:Ethernet HWaddr 00:B00:98:48:6A
inet addr:192.168.1.15 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::2b0:d0ff:fe98:486a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:435034 errors:0 dropped:0 overruns:1 frame:0
TX packets:242192 errors:0 dropped:0 overruns:0 carrier:0
collisions:453 txqueuelen:1000
RX bytes:412298934 (393.1 MiB) TX bytes:56429215 (53.8 MiB)
Interrupt:5 Base address:0xec00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:10647 errors:0 dropped:0 overruns:0 frame:0
TX packets:10647 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:926719 (904.9 KiB) TX bytes:926719 (904.9 KiB)



sh-3.00$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
default 192.168.1.254 0.0.0.0 UG 0 0 0 eth1



sh-3.00$ cat /etc/resolv.conf
nameserver 192.168.1.1



sh-3.00$ cat /etc/hosts
127.0.0.1 knoppix localhost

On 11/20/05 16:20, Eric wrote:
> I have KNOPPIX 4.0 installation to my hard drive, and I choose the
> "Debian" install option. This box is on my home network along with other
> computers running Debian stable, Win2000 and OSX Panther. All but my
> KNOPPIX box get DHCP from a wired Linksys router (BEFSR41) and function
> normally. I am a newbie, so the information below may be insufficient to
> solve the problem, but here goes...
>
> My router is serving IPs between 192.168.1.100 and 1.150. But, the
> KNOPPIX box thinks it is 192.168.1.15 and has no gateway. To fix this,
> I've been manually entering these lines, and it works - I can ping and
> resolve, as well a browse the web in an X session.
>
>

How do you get the IP? Is dhcp client properly configured?

Ciao
Giovanni
--
A computer is like an air conditioner,
it stops working when you open Windows.
Registered Linux user #337974 <http://counter.li.org/>

Giovanni wrote:
> On 11/20/05 16:20, Eric wrote:
>
>> I have KNOPPIX 4.0 installation to my hard drive, and I choose the
>> "Debian" install option. This box is on my home network along with other
>> computers running Debian stable, Win2000 and OSX Panther. All but my
>> KNOPPIX box get DHCP from a wired Linksys router (BEFSR41) and function
>> normally. I am a newbie, so the information below may be insufficient to
>> solve the problem, but here goes...
>>
>> My router is serving IPs between 192.168.1.100 and 1.150. But, the
>> KNOPPIX box thinks it is 192.168.1.15 and has no gateway. To fix this,
>> I've been manually entering these lines, and it works - I can ping and
>> resolve, as well a browse the web in an X session.
>>
>>
>
> How do you get the IP? Is dhcp client properly configured?
>
> Ciao
> Giovanni

I don't know why the box is calling itself 192.168.1.15. I am
"supposedly" receiving DHCP information from the router, but not what
the router is configured to broadcast. Like I said, three other
machines, including a LINUX box, are playing nicely with the router. As
for configuring the KNOPPIX box DHCP client, I haven't a clue how to do
that. 'man dhcp" fails, and 'man dhcpd' is all server information.

Eric

Eric wrote:

> Giovanni wrote:
>
>> On 11/20/05 16:20, Eric wrote:
>>
>>> I have KNOPPIX 4.0 installation to my hard drive, and I choose the
>>> "Debian" install option. This box is on my home network along with other
>>> computers running Debian stable, Win2000 and OSX Panther. All but my
>>> KNOPPIX box get DHCP from a wired Linksys router (BEFSR41) and function
>>> normally. I am a newbie, so the information below may be insufficient to
>>> solve the problem, but here goes...
>>>
>>> My router is serving IPs between 192.168.1.100 and 1.150. But, the
>>> KNOPPIX box thinks it is 192.168.1.15 and has no gateway. To fix this,
>>> I've been manually entering these lines, and it works - I can ping
>>> and resolve, as well a browse the web in an X session.
>>>
>>>
>>
>> How do you get the IP? Is dhcp client properly configured?
>>
>> Ciao
>> Giovanni
>
>
> I don't know why the box is calling itself 192.168.1.15. I am
> "supposedly" receiving DHCP information from the router, but not what
> the router is configured to broadcast. Like I said, three other
> machines, including a LINUX box, are playing nicely with the router. As
> for configuring the KNOPPIX box DHCP client, I haven't a clue how to do
> that. 'man dhcp" fails, and 'man dhcpd' is all server information.
>
> Eric
>
>
>
Probably one of those other machines also has a DHCP server running.

--
The e-mail address in our reply-to line is reversed in an attempt to
minimize spam. Our true address is of the form che...@prodigy.net.

On 11/21/05 00:40, Eric wrote:

> I don't know why the box is calling itself 192.168.1.15. I am
> "supposedly" receiving DHCP information from the router, but not what
> the router is configured to broadcast. Like I said, three other
> machines, including a LINUX box, are playing nicely with the router. As
> for configuring the KNOPPIX box DHCP client, I haven't a clue how to do
> that. 'man dhcp" fails, and 'man dhcpd' is all server information.

$ man dhcpcd

Ciao
Giovanni
--
A computer is like an air conditioner,
it stops working when you open Windows.
Registered Linux user #337974 <http://counter.li.org/>

Giovanni wrote:
> On 11/21/05 00:40, Eric wrote:
>
>> I don't know why the box is calling itself 192.168.1.15. I am
>> "supposedly" receiving DHCP information from the router, but not what
>> the router is configured to broadcast. Like I said, three other
>> machines, including a LINUX box, are playing nicely with the router.
>> As for configuring the KNOPPIX box DHCP client, I haven't a clue how
>> to do that. 'man dhcp" fails, and 'man dhcpd' is all server information.
>
>
> $ man dhcpcd
>
> Ciao
> Giovanni

That man page is not there, surprisingly, but the problem is solved.
There was a rogue DHCP server running on the Debian box. I commented out
the /etc/dhcpd.conf file and killed the process. There have been no more
hijacked IP addresses. Incidentally, the range of assigned IPs on the
rogue server was 192.168.1.10 to 1.20.

Thank you.

Eric

In article <(E-Mail Removed)> ,
Eric <(E-Mail Removed)> wrote:
:
:I don't know why the box is calling itself 192.168.1.15. I am
:"supposedly" receiving DHCP information from the router, but not what
:the router is configured to broadcast. Like I said, three other
:machines, including a LINUX box, are playing nicely with the router. As
:for configuring the KNOPPIX box DHCP client, I haven't a clue how to do
:that. 'man dhcp" fails, and 'man dhcpd' is all server information.

What you want is "man dhclient" and "man dhclient.conf".

FYI, "man -k dhcp" would have given you several suggestions.

--
Bob Nichols AT comcast.net I am "RNichols42"