ltsp server/client problem: no DHCPREQUEST after DHCPOFFER

ltsp server/client problem: no DHCPREQUEST after DHCPOFFER

Post by Pete » Mon, 28 Oct 2002 18:23:29



hi everyone

I tried to setup an ltsp-server and -client configuration. It doesn't
work. I have a SuSE 8.0 box which I updated via YOU.

I checked everything twice:

- the two machines are connected with eachother, I ping-ed each from
the otherone and it worked.
- I shut the firewall down
- tftp is running
- dhcpd is running
- I even tried the configuration with another PC (but the same
networking-card, because I only have that one...)

I now have three possible problem sources that I could think of:

- DHCP doesn't work the right way
- The networking-card is broken
- The routing doesn't work correctly

Could someone tell me where to dig deeper, what to try, what to do?

Thanks a lot, I appreciate any help

Peter

# /var/log/messages
Oct 18 11:04:21 arien dhcpd: Internet Software Consortium DHCP Server V3.0.1rc6
Oct 18 11:04:21 arien dhcpd: Copyright 1995-2001 Internet Software Consortium.
Oct 18 11:04:21 arien dhcpd: All rights reserved.
Oct 18 11:04:21 arien dhcpd: For info, please visit http://www.isc.org/products/DHCP
Oct 18 11:04:51 arien dhcpd: ip length 576 disagrees with bytes received 590.
Oct 18 11:04:51 arien dhcpd: accepting packet with data after udp payload.
Oct 18 11:04:51 arien dhcpd: DHCPDISCOVER from 00:05:5d:e5:23:9d via eth0
Oct 18 11:04:51 arien dhcpd: DHCPOFFER on 192.168.0.1 to 00:05:5d:e5:23:9d via eth0
<sleep>

# /etc/dhcpd.conf
ddns-update-style             none;
default-lease-time            21600;
max-lease-time                21600;
ignore unknown-clients;

option subnet-mask            255.255.255.0;
option broadcast-address      192.168.0.255;
option routers                192.168.0.254;
option domain-name-servers    192.168.0.254;
option domain-name            "arien.arda";
option root-path              "192.168.0.254:/opt/ltsp/i386";

option option-128 code 128 = string;
option option-129 code 129 = text;

shared-network WORKSTATIONS {
    subnet 192.168.0.0 netmask 255.255.255.0 {
     option routers 192.168.0.254;
    }

Quote:}

group   {
    use-host-decl-names       on;
    option log-servers        192.168.0.254;

    host ws001 {
        hardware ethernet     00:05:5D:E5:23:9D;
        fixed-address         192.168.0.1;
        filename              "/tftpboot/lts/vmlinuz-2.4.19-ltsp-1";
    }

Quote:}

 
 
 

ltsp server/client problem: no DHCPREQUEST after DHCPOFFER

Post by Michael Heimin » Mon, 28 Oct 2002 18:40:52



Quote:> hi everyone

> I tried to setup an ltsp-server and -client configuration. It
> doesn't work. I have a SuSE 8.0 box which I updated via YOU.
[..]
> # /etc/dhcpd.conf
> ddns-update-style             none;
> default-lease-time            21600;
> max-lease-time                21600;
> ignore unknown-clients;

Add here:
ddns-update-style            ad-hoc;

Enhance dhcpd debugging, if problems persist.

Good luck

Michael Heiming
--

figure it out

 
 
 

1. DHCPOFFER but no DHCPREQUEST

Hello

I've running an dhcp-server.
If I run dhcpcd -T on the same machine it seems to work fine. The protocol
DHCPDISCOVER, DHCPOFFER, (DHCPREQUEST, DHCPACK via interface),
(DHCPREQUEST, DHCPACK via ip addr) occur.

If I run dhcpcd -T on another machine which is routet via dhcrelay to the
dhcp-server it don't work.
The dhcp-server say DHCPDISCOVER, DHCPOFFER, I think 4 times. No
DHCPREQUEST occurs.

What ist there wrong?
--
Don't panic

2. pop3 for linux?

3. DHCPD Windows XP DHCPOFFER no DHCPREQUEST

4. linksys LNE100TX version 4 problem with syld.com netdriver package...

5. RedHat client sends DHCPDISCOVER, server hears and sends DHCPOFFER that doesn't reach client

6. Strange keyboard behaviour...

7. newbie - client not replying to DHCPOFFER

8. Arguments too long with du

9. LTSP Thin Client Configuration

10. Informix problems afters Y2K Solaris 2.5 patch

11. PXEbooting a netier sl1000/sl2000 into an LTSP Server

12. Connecting two machines:; Client only communicate with server when server continuously pings client.

13. Sex Change - Making Server as Client and Client as Server