🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: pl.comp.os.linux.debian
Article #29882

dlaczage nie dziala u mnie DHCP ?

#29882
From: Rafal
Date: Thu, 10 Aug 2006 10:54
115 lines
4941 bytes
na starym serwersze DHCP dziala mi bez zastrzezen,
na nowy serwer Proliant DL380 przekopiowalem wiernie zawartosc pliku 
dhcp.conf
i utworzylem dhcpd.leases
odpalam dhcpd i sie uruchamia bez bledow
wylaczylem calkiem firewalla aby nie przeszkadzal
---------------------------------------
ale stacje robocze nie maja przydzielanego IP
co jest nie tak ?
---------------------------------------
w pliku /var/log/messages powtarza sie:
Aug 10 12:41:58 wichura dhcpd: DHCPDISCOVER from 00:04:76:e6:7b:c1 via eth2
Aug 10 12:41:59 wichura dhcpd: DHCPOFFER on 192.168.193.254 to 
00:04:76:e6:7b:c1 via eth2
---------------------------------------
z dokumentacji doczytalem ze przy DHCP zachodza operacje:
DHCPDISCOVER, DHCPOFFER, DHCPREQUEST, DHCPACK
ale tych dwoch ostatnich nie widac w /var/log/messages
---------------------------------------
gdy zapuscilem tcpdump to pokazal przykladowo:
10:35:20.594939 IP (tos 0x0, ttl  60, id 0, offset 0, flags [none], proto:
UDP (17), length: 576) 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 00:04:76:0e:9e:fd, length: 548, xid:0x76182488, flags: [none]
(0x0000)
          Client Ethernet Address: 00:04:76:0e:9e:fd [|bootp]
10:35:20.595750 IP (tos 0x10, ttl  16, id 0, offset 0, flags [none], proto:
UDP (17), length: 328) 192.168.193.14.bootps > 192.168.193.1.bootpc:
BOOTP/DHCP, Reply, length: 300, xid:0x76182488, flags: [none] (0x0000)
          Your IP: 192.168.193.1
          Client Ethernet Address: 00:04:76:0e:9e:fd
          sname "192.168.19"[|bootp]


wymienialem juz kable i nie pomoglo

prosze o rade co zle ustawilem



---------------------------------------
# moj skrocony plik dhcpd.conf:
ddns-update-style ad-hoc;
default-lease-time 43200;
max-lease-time 259200;
subnet 192.168.193.0 netmask 255.255.255.0
{
    option subnet-mask 255.255.255.0;
    option broadcast-address 192.168.193.255;
    range 192.168.193.11 192.168.193.200;
    host ws001
    {
        hardware ethernet 00:04:76:0E:9E:FD;
        fixed-address 192.168.193.1;
        #option host-name "ws001";
        server-name "192.168.193.14";
        option root-path "/opt/ltsp/i386";
        filename "lts/vmlinuz-2.4.24-ltsp-4";
    }
}

---------------------------------------





ustawienia programow na starym i nowym serwerze ustawilem podobnie,
moze mam zle ustawione karte sieciowa ?
jak ktos sie na tym zna to prosze o pomoc


stary serwer:
---------------
[root@server2 rc]# /usr/sbin/ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 24
        Transceiver: internal
        Auto-negotiation: on
        Current message level: 0x00000001 (1)
        Link detected: yes


nowy serwer:
-----------------
[root@wichura rc]# /usr/sbin/ethtool eth0
Settings for eth0:
        Supported ports: [ MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: g
        Wake-on: d
        Current message level: 0x000000ff (255)
        Link detected: yes
Technical Details
Message-ID: <ebf390$eam$1@atlantis.news.tpi.pl>
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!newsfeed.gazeta.pl!news.nask.pl!news.nask.org.pl!newsfeed.tpinternet.pl!nemesis.news.tpi.pl!atlantis.news.tpi.pl!news.tpi.pl!not-for-mail

Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!newsfeed.gazeta.pl!news.nask.pl!news.nask.org.pl!newsfeed.tpinternet.pl!nemesis.news.tpi.pl!atlantis.news.tpi.pl!news.tpi.pl!not-for-mail
From: "Rafal" <rcU5UNT0@pulsarsc.com.pl>
Newsgroups: pl.comp.os.linux.debian
Subject: dlaczage nie dziala u mnie DHCP ?
Date: Thu, 10 Aug 2006 12:54:00 +0200
Organization: tp.internet - http://www.tpi.pl/
Lines: 123
Message-ID: <ebf390$eam$1@atlantis.news.tpi.pl>
NNTP-Posting-Host: akm86.internetdsl.tpnet.pl
X-Trace: atlantis.news.tpi.pl 1155207264 14678 83.17.16.86 (10 Aug 2006 10:54:24 GMT)
X-Complaints-To: usenet@tpi.pl
NNTP-Posting-Date: Thu, 10 Aug 2006 10:54:24 +0000 (UTC)
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-RFC2646: Format=Flowed; Original
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit