Knoppix fails to obtain an IP via DHCP from the ADSL Router.

[baldyeti]

> If the noapic boot option does not work (as I think it may not do), do you have any other ideas of what it could be?

I think I remember reading (on the knoppix or mepis dev-list) about the relative merits of pump and other dhcp client implementations, and some users having better luck with one rather than the other. Maybe you're just being unlucky with pump...

You could try the following (as root):
kill the background "pump" process
check if "ifconfig" reports eth0; otherwise "ifconfig eth0 up"
pump -i eth0

> (P.s - what script file do I edit for the noapic? I may have only tried it with the bootCD!)[/quote]
Try again from CD to see it works before bothering to make it permanent

[user unknown]

For 'noapic', if you boot via lilo, you edit /etc/lilo.conf, and instert
append='noapic' to your linux-section.

Why don't you like static-settings?
I prefer static ones over dynamic.
It's more stable, more reliable, I don't need to look for my own IP, because it's allways the same.

And I can use /etc/hosts to specify my own hosts.
How do you get the other IPs when working with dhcp, to use ssh or ftp in your own network?

[drekidd]

ahh.. thanks User unknown - saved me some time there

To be honest I have always used DHCP even though the leases rarely expire and get re-used! The point for me is that I am (like most others) using Knoppix to learn Linux in a familiar Intel environment, and under windows all 3 of my workstations can get DHCP address's. I even have a wireless access point setup on 192.168.200.253 and it allows attached clients to request DHCP through it, to 192.168.200.254 which is the nets default gw.
DHCP is reliable and automated, so if I want to change the address's of all wireless clients and all local clients on the edge, I just change the DHCP settings and scope and they all change!

If it works in Windows, I want it to work in Knoppix/linux or at least know why it doesnt work! It's not like I'm trying to get Netbios or some other quirky thing to work, DHCP is not windows specific/reliant...

To answer the SSH/FTP question - I use NAT and filters on the Router to push FTP/HTTP requests to local IP address's - keeps things transparent

Thanks for your help U_UK..

[user unknown]

I don't know NAT - perhaps it's the point.

My question is: I have a /etc/host:
192.168.4.2 desktop
192.168.4.3 laptop

To make a filetransfer, I start ftpd on the desktop, and
ftp desktop
on the laptop.

When I use dhcp (and NAT?) the laptop will find the desktop too?
How?

[drekidd]

I don't know NAT - perhaps it's the point.

My question is: I have a /etc/host:
192.168.4.2 desktop
192.168.4.3 laptop

To make a filetransfer, I start ftpd on the desktop, and
ftp desktop
on the laptop.

When I use dhcp (and NAT?) the laptop will find the desktop too?
How?

Thanks for the reply Unknown.

..You seem to be talking about LAN-side DNS name resolution (resolving the name 'desktop' to an IP address) using the static hosts mechanism.. this is bit off-topic re: my LAN-side DHCP client issue with Knoppix.
My N.A.T (In-fact should've been P.A.T!) is a side-issue and not related to DHCP within the LAN - it is not affecting the clients ability to obtain an IP address.

PM me and I'll discuss, but I think we should leave this thread in the direction of working out why DHCP is not working in Knoppix (with my config/instance) when it works on the same machine when booting into Windows..

noapic
Also, I tried putting the 'noapic' option into my lilo.conf - no joy unfortunately ;(

Syslog [tail]
I ran syslog whilst running

pump -i eth0

after killing any pump instances in memory, and this is the common output:

Aug 17 22:38:49 Knoppix pumpd[811]: PUMP: sending discover
Aug 17 22:38:49 Knoppix pumpd[811]: reject: xid: 0x41332561 <--> 0x536b10f1
Aug 17 22:38:49 Knoppix pumpd[1054]: starting at (uptime 0 days, 0:07:22) Tue Aug 17 22:38:49 2004 (I restarted eth0 here as it keeps going down)
Aug 17 22:38:49 Knoppix pumpd[1054]: PUMP: sending discover
Aug 17 22:38:49 Knoppix pumpd[1054]: reject: xid: 0x37254133 <--> 0x536b1048

Thanks again everyone who has and may contribute to this thread

[user unknown]

drekidd:

apic: perhaps "noapic apic=off" will work.

I would prefer discuss the question of 'why use dhcp in the lan' public, so more people might tell their thoughts. I'll open a new thread and try to cite my question.

[drekidd]

Sure thing U_Unknown.. post/pm the thread link..
(Im not being difficult, just trying not to digress!)

Thanks again man..

p.s - Do you know what the 'noapic' option ommits from the h/w detection??
The cheat-codes doc doesnt say much!

p.p.s - I'm gonna try the DHCP request from another DHCP server today..

[tearinghairout]

OK drekidd/tearinghairout2

This is a long shot, but the best I could come up with.

A bit of extended googling with 'dhcp reject xid' seems to suggest that the xid is something generated by the client (in this case pump) - that it presumably sends to the server in each request, and the server sends back in the response - so that it (the client) can keep track of which responses belong to which requests.
Apparently the client is supposed to generate the xid in such a way that no two values are ever used one after the other.

Now maybe (and this is complete guessing) your Knoppix dhcp client (pump) is basing the xid on the mac address (or part thereof) and since the same network card, with the same mac address is used in dual booting computer, it looks to your dhcp server that two different clients are trying to use the same xid, hence the reject message in your dmesg.

What if you try doing a complete reset of everything? Power down your dual boot computer, power down your nat/router/dhcp thingy, unplug the power cables from the wall, put them back in their original boxes, put the boxes outside your front door for a while, perhaps move houses, maybe think about emigrating. Then plug it all back in and boot Knoppix first (without booting XP).
Alternatively, try the DHCP request from another DHCP server today..

Please let us know how it goes - I love a challenge.
THO

[drekidd]

LOL!!!! Yeah, I like it!!

You are right - a router (or switch, workstation etc.) will store an ARP entry, which is a record of your IP/MAC translation (Layer 2 to Layer 3 translation). In my Routers ARP cache I will see an entry.. so I actually did this before creating this thread:

• released my ip in windows.
  unplugged network cable.
  shutdown.
  shut down Router (clear ARP cache)
  Start router (no reference to PC or IP in the router)
  Start laptop - boot into linux
  watched ARP cache - entry for Linux client appears but occassionally

disappears depending on time and my attempts.

Tried pump -i eth0 etc. - no joy.

However, I like the sound of emigrating!!

I will try the other DHCP server here at work before I go home in a minute... edge of the seat stuff

Thanks T.H.Out..

[drekidd]

UPDATE!

Ok, so today I have my work laptop (Thinkpad T40) with me. The Laptop with the aforementioned HD install of Knoppix is at home (IBM Thinkpad T30).

I had tried the CD version of knoppix on my two laptops and my Windows 2000 PC. none of them currently obtain IP address's from my ADSL Router.
The 2000 pc did once me thinks, but not anymore.

So anyway, before emmigrating (!) I tried the CD version of Knoppix on my laptop at work. plugged my PC into the corporate network which uses DHCP and knoppix booted with an IP and Im now writing thjs damn message using Mozilla in Knoppix!!

So.. it seems it could be the DHCP of my Router versus my corporate switch on Linux (works in Windows remember!).. Hmm... gonna require some sniffing of some kind to work out if there are differences in DHCP options or something..

Anyway, this thread is not over!!
1) it might not be my router (Stop laughing!),
2) we/I need to know what it is that causes this.. I think I've seen others mention this in their threads...
3) My Router works fine in Windows.. so it could be the Router being crap or Linux having specific requirements..

Later peeps - Im tireddddddddd

://DK