The OpenNET Project / Index page

[ новости /+++ | форум | теги | ]

форумы  помощь  поиск  регистрация  майллист  ВХОД  слежка  RSS
"dhcpd раздает адреса из неверного диапазона "
Вариант для распечатки Архивированная нить - только для чтения! 
Пред. тема | След. тема 
Форумы OpenNET: Виртуальная конференция (Public)
Изначальное сообщение [Проследить за развитием треда]

"dhcpd раздает адреса из неверного диапазона "
Сообщение от arruah emailИскать по авторуВ закладки(??) on 23-Окт-04, 07:36  (MSK)
бьюсь над сабжем.
в основном не моут получить тот ай пи который ему задан в конфиге, те машины которые наиболее удалены от сервера, сеть к примеру через два свитча и один хаб. Но адрес все таки они получают ! Так почему они получают не тот который я им сказал а тот, который из свободного диапазона ?

Привожу конфиг.
###############################################
# Подсети                                     #
###############################################
option netbios-name-servers 192.168.2.1;
option netbios-node-type 8;

subnet  80.241.0.138 netmask 255.255.255.254 {
        }
subnet  192.168.0.0 netmask 255.255.0.0 {
        range 192.168.2.200 192.168.2.254;
        option routers 192.168.2.100;
        option subnet-mask 255.255.255.0;
        }
###############################################
# four                                        #
###############################################
host mon1       {
                hardware ethernet 00:50:70:44:27:6B;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.3;
                }
host mon2       {
                hardware ethernet 00:50:70:44:29:3b;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.4;
                }
host mon3       {
                hardware ethernet 00:50:70:44:25:33;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.5;
                }
host kadr       {
                hardware ethernet 48:54:e8:21:42:40;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.6;
                }
host laptop     {
                hardware ethernet 48:54:e8:21:42:40;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.7;
                }
host buh1       {
                hardware ethernet 00:00:E8:DA:87:47;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.8;
                }
host buh2       {
                hardware ethernet 00:0C:76:85:0E:E9;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.9;
                }
host buh3       {
                hardware ethernet 00:00:E8:DA:81:07;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.10;
                }
host buh4       {
                hardware ethernet 00:0C:76:85:0E:F1;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.11;
                }
host otd1       {
                hardware ethernet 00:00:21:C3:81:B1;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.12;
                }
host otd2       {
                hardware ethernet 00:80:48:27:32:13;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.13;
                }
host zamvr      {
                hardware ethernet 00:00:21:64:3F:43;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.14;
                }
host rumo       {
                hardware ethernet 00:00:1C:02:0A:55;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.15;
                }
host przav      {
                hardware ethernet 00:80:48:27:32:35;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.16;
                }
host zavuch     {
                hardware ethernet 00:80:48:21:9f:93;
                option subnet-mask 255.255.255.0;
                fixed-address 192host dispetcher {
                hardware ethernet 00:80:48:27:5A:AF;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.18;
                }
host prdir      {
                hardware ethernet 00:C0:DF:23:7B:65;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.19;
                }
host director   {
                hardware ethernet 00:0C:76:85:10:45;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.20;
                }
host otd3       {
                hardware ethernet 00:80:48:27:5A:B2;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.21;
                }
host zamur      {
                hardware ethernet 48:54:E8:21:3F:E4;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.22;
                }
host zavpr      {
                hardware ethernet 00:00:21:D0:51:9A;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.23;
                }
host zotd       {
                hardware ethernet 00:00:21:C0:31:DD;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.24;
                }
host school     {
                hardware ethernet 00:c0:df:23:7b:1b;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.25;
                }
host slibhost1  {
                hardware ethernet 00:00:E8:65:91:E7;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.26;
                }
host slib01     {
                hardware ethernet 00:00:E8:65:94:24;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.27;
                }
host slib02     {
                hardware ethernet 00:AA:00:69:CB:15;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.28;
                }
host slib03     {
                hardware ethernet 00:00:21:64:2C:1E;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.29;
                }
host slib04     {
                hardware ethernet 00:00:21:64:2C:20;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.30;
                }
host slib05     {
                hardware ethernet 00:A0:C9:18:1E:70;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.31;
                }
host slib06     {
                hardware ethernet 00:40:33:27:B4:CB;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.32;
                }
host slib07     {
                hardware ethernet 00:AA:00:AD:6A:5C;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.33;
                }
host a4091      {
                hardware ethernet 00:C0:DF:23:7E:4A;
                option subnet-mask 255.255.255.0;
                fixed-address 192.168.2.34;
                }
#################################################
# kafedra                                       #
#################################################
host a503 {
          hardware ethernet 00:00:21:CC:46:01;
          option subnet-mask 255.255.255.0;
          fixed-address 192.168.2.40;
          }
host a504 {
          hardware ethernet 00:00:E8:DA:CC:F6;
          option subnet-mask 255.255.255.0;
          fixed-address 192.168.2.41;
          }
host a505 {
          hardware ethernet 00:00:E8:65:93:EF;
          option subnet-mask 255.255.255.0;
          fixed-address 192.168.2.42;
          }
host a508 {
          hardware ethernet 00:00:E8:DA:C8:42;
          option subnet-mask 255.255.255.0;
          fixed-address 192.168.2.43;
          }
host a509 {
          hardware ethernet 00:00:21:D2:30:3A;
          option subnet-mask 255.255.255.0;
          fixed-address 192.168.2.44;
          }
host a603 {
          hardware ethernet 00:00:E8:DA:CC:F6;
          option subnet-mask 255.255.255.0;
          fixed-address 192.168.2.45;
          }
host a604 {
          hardware ethernet 00:80:48:21:63:D6;
          option subnet-mask 255.255.255.0;
          fixed-address 192.168.2.46;
          }
host a608 {
          hardware ethernet 00:80:48:27:5A:B1;
          option subnet-mask 255.255.255.0;
          fixed-address 192.168.2.47;
          }
host a609 {
          hardware ethernet 00:00:21:D2:5E:B8;
          option subnet-mask 255.255.255.0;
          fixed-address 192.168.2.48;
          }
host a704 {
          hardware ethernet 00:00:21:C0:31:DA;
          option subnet-mask 255.255.255.0;
          fixed-address 192.168.2.49;
          }
host a707 {
          hardware ethernet 00:00:21:C0:31:DB;
          option subnet-mask 255.255.255.0;
          fixed-address 192.168.2.50;
          }
host a708 {
          hardware ethernet 00:00:E8:65:90:53;
          option subnet-mask 255.255.255.0;
          fixed-address 192.168.2.51;
          }
host a804 {
          hardware ethernet 00:00:21:C0:31:F5;
          option subnet-mask 255.255.255.0;
          fixed-address 192.168.2.52;
          }
host a807 {
          hardware ethernet 00:C0:DF:23:7E:C0;
          option subnet-mask 255.255.255.0;
          fixed-address 192.168.2.53;
          }
host a808 {
          hardware ethernet 00:80:48:27:5B:6C;
          option subnet-mask 255.255.255.0;
          fixed-address 192.168.2.54;
          }
host fizra {
          hardware ethernet 00:80:48:27:32:30;
          option subnet-mask 255.255.255.0;
          fixed-address 192.168.2.55;
          }
#аудитории

host a502   {
            hardware ethernet 00:80:48:27:32:3D;
            option subnet-mask 255.255.255.0;
            fixed-address 192.168.2.60;
            }
host a510   {
            option subnet-mask 255.255.255.0;
            hardware ethernet 00:80:48:27:32:28;
            fixed-address 192.168.2.61;
host a602   {
            hardware ethernet 00:00:21:cd:f5:50;
            option subnet-mask 255.255.255.0;
            fixed-address 192.168.2.62;
            }
host a606   {
            hardware ethernet 00:80:48:27:32:18;
            option subnet-mask 255.255.255.0;
            fixed-address 192.168.2.64;
            }
host a607   {
            hardware ethernet 00:80:48:27:5A:A6;
            option subnet-mask 255.255.255.0;
            fixed-address 192.168.2.65;
            }
host a610   {
            option subnet-mask 255.255.255.0;
            hardware ethernet 00:80:48:27:32:26;
            fixed-address 192.168.2.66;
            }
host a701   {
            hardware ethernet 00:80:48:27:39:35;
            option subnet-mask 255.255.255.0;
            fixed-address 192.168.2.67;
            }
host a702   {
            hardware ethernet 00:80:48:27:46:90;
            option subnet-mask 255.255.255.0;
            fixed-address 192.168.2.68;
            }
host a703   {
            hardware ethernet 00:80:48:27:32:21;
            option subnet-mask 255.255.255.0;
            fixed-address 192.168.2.69;
            }
host a706   {
            hardware ethernet 00:c0:df:23:7a:9e;
            option subnet-mask 255.255.255.0;
            fixed-address 192.168.2.71;
            }
host a709   {
            hardware ethernet 00:80:48:27:32:29;
            option subnet-mask 255.255.255.0;
            fixed-add            }
host a710   {
            hardware ethernet 00:00:E8:65:90:47;
            option subnet-mask 255.255.255.0;
            fixed-address 192.168.2.73;
            }
host a802   {
            hardware ethernet 00:00:E8:65:91:6F;
            option subnet-mask 255.255.255.0;
            fixed-address 192.168.2.74;
            }
host a806   {
            hardware ethernet 00:80:48:27:46:A7;
            option subnet-mask 255.255.255.0;
            fixed-address 192.168.2.75;
            }
host a810   {
            hardware ethernet 00:80:48:27:5A:AE;
            option subnet-mask 255.255.255.0;
            fixed-address 192.168.2.76;
            }
####################################################
# classes                                          #
####################################################
host s1801 {
           hardware ethernet 00:30:1B:33:96:EF;
           option subnet-mask 255.255.255.0;
           fixed-address 192.168.5.2;
           }

Заранее спасибо за ответ.

  Рекомендовать в FAQ | Cообщить модератору | Наверх

 Оглавление

Индекс форумов | Темы | Пред. тема | След. тема
Сообщения по теме

1. "dhcpd раздает адреса из неверного диапазона "
Сообщение от Мутабор Искать по авторуВ закладки(ok) on 23-Окт-04, 08:27  (MSK)
Даю наводку:
А что говорит arp -a?
  Рекомендовать в FAQ | Cообщить модератору | Наверх

2. "dhcpd раздает адреса из неверного диапазона "
Сообщение от arruah emailИскать по авторуВ закладки(??) on 23-Окт-04, 12:32  (MSK)
>Даю наводку:
>А что говорит arp -a?

mon2.sfek.kz (192.168.2.4) at 00:50:70:44:29:3B [ether] on eth0
? (192.168.5.37) at 00:00:21:CC:46:05 [ether] on eth0
argyn.sfek.kz (192.168.2.1) at 00:90:27:1D:8F:F0 [ether] on eth0
tobykty.sfek.kz (192.168.2.2) at 00:E0:4C:AB:1A:D9 [ether] on eth0
(192.168.2.42) at 00:00:E8:65:93:EF [ether] on eth0
a703.sfek.kz (192.168.2.64) at 00:80:48:27:32:18 [ether] on eth0
buh2.sfek.kz (192.168.2.9) at 00:0C:76:85:0E:E9 [ether] on eth0
a709.sfek.kz (192.168.2.67) at 00:80:48:27:39:35 [ether] on eth0
FinColl-Semipalatinsk.relcom.kz (80.241.0.137) at 00:FF:01:C5:DA:F0 [ether] on sbni0
? (192.168.5.40) at 00:00:21:D2:30:2F [ether] on eth0
(192.168.2.47) at 00:80:48:27:5A:B1 [ether] on eth0
buh4.sfek.kz (192.168.2.11) at 00:0C:76:85:0E:F1 [ether] on eth0
? (192.168.5.52) at 00:00:B4:5A:AB:E5 [ether] on eth0
a502.sfek.kz (192.168.2.50) at 00:00:21:C0:31:DB [ether] on eth0
school.sfek.kz (192.168.2.21) at 00:80:48:27:5A:B2 [ether] on eth0
a510.sfek.kz (192.168.2.55) at 00:80:48:27:32:30 [ether] on eth0
? (192.168.5.49) at 00:C0:DF:23:7B:3E [ether] on eth0
zavuch.sfek.kz (192.168.2.17) at 00:80:48:21:9F:93 [ether] on eth0
? (192.168.5.51) at 00:C0:DF:23:7A:5A [ether] on eth0
przav.sfek.kz (192.168.2.16) at 00:80:48:27:32:35 [ether] on eth0
FinCollege-subnet2-side2.relcom.kz (80.241.0.186) at <incomplete> on eth0
(192.168.2.227) at 00:00:E8:65:90:44 [ether] on eth0
(192.168.2.229) at 00:00:E8:65:94:2A [ether] on eth0
? (192.168.5.28) at 00:00:1C:B0:E5:EA [ether] on eth0
? (192.168.5.31) at 00:00:21:D4:52:C5 [ether] on eth0

  Рекомендовать в FAQ | Cообщить модератору | Наверх

3. "dhcpd раздает адреса из неверного диапазона "
Сообщение от arruah emailИскать по авторуВ закладки(??) on 23-Окт-04, 12:40  (MSK)
Если ты про то что не совпадает мак адресс указанный в конфиге dhcpd и реальный прошитый в карте, то это исключено проверял по нескольку раз, все совпадает.
  Рекомендовать в FAQ | Cообщить модератору | Наверх

4. "dhcpd раздает адреса из неверного диапазона "
Сообщение от Дмитрий Ю. Карпов emailИскать по авторуВ закладки on 23-Окт-04, 14:31  (MSK)
Я не понял, с какими машинами у тебя траблы - в ARP адреса из динамического диапазона имеют машины, чьи MAC-адреса не прописаны в dhcpd.conf.

Кроме того, твоим прописанным машинам не будет выдаваться роутер - лучше помести описания машин внутрь описания подсетИ (заодно и маску можно будет прописать один раз).

  Рекомендовать в FAQ | Cообщить модератору | Наверх


Удалить

Индекс форумов | Темы | Пред. тема | След. тема
Пожалуйста, прежде чем написать сообщение, ознакомьтесь с данными рекомендациями.




Партнёры:
PostgresPro
Inferno Solutions
Hosting by Hoster.ru
Хостинг:

Закладки на сайте
Проследить за страницей
Created 1996-2024 by Maxim Chirkov
Добавить, Поддержать, Вебмастеру