Results 1 to 6 of 6

Thread: DHCP server don't assign IP adresses

  1. #1

    Default DHCP server don't assign IP adresses

    Hello everyone,

    Just to introduce the situation, i have to say that i'm not used to work on network things as i'm actually a software developper, but the guy that put everything in place left and was never replaced, i juste have the basics.

    So here i am ...

    As said in the title i have an issue today with my DHCP server, which doesn't give IP to any machine (virtual or physical) connected to it.

    This issue appeared after we had a big power outage in my office, but used to work well before that.

    The dhcp server is set on a SLES 15 SP1 distribution on a dell server, my VMs were also set on this machine using Virtual Machine Manager.

    Most of machines IP's on the network are set statically in the dhcp server configuration, but even like that they don't get any IP.

    All the VM are connected by a bridge on my network.

    When i read the result of an "ipconfig" in a windows VM i can see that the DNS suffix is set correctly at "tfa" but i get an IP like 169.254.12.149 ... which is not my subnet.
    The result of "ipconfig /renew" give me a error : Impossible to reach your DHCP server.

    Here is my dhcpd.conf file :

    Code:
    option domain-name "tfa";option domain-name-servers 192.168.100.11, 192.168.100.12;
    ddns-update-style none;
    default-lease-time 14400;
    subnet 192.168.100.0 netmask 255.255.255.0 {
      range 192.168.100.200 192.168.100.250;
      default-lease-time 14400;
      max-lease-time 172800;
      host GATE {
        fixed-address 192.168.100.100;
        hardware ethernet 52:54:00:B3:A7:9A;
      }
      host SUSY {
        fixed-address 192.168.100.102;
        hardware ethernet 04:0E:3C:C1:2C:49;
      }
      host SUZE {
        fixed-address 192.168.100.101;
        hardware ethernet 04:0E:3C:C1:2E:3F;
      }
      host PROJ {
        fixed-address 192.168.100.122;
        hardware ethernet 52:54:00:99:BE:24;
      }
      host OPEN {
        fixed-address 192.168.100.123;
        hardware ethernet 52:54:00:04:D3:26;
      }
      host COMP {
        fixed-address 192.168.100.111;
        hardware ethernet 52:54:00:08:67:B9;
      }
      host CONX {
        fixed-address 192.168.100.112;
        hardware ethernet 52:54:00:F0:E2:60;
      }
      host DEVL {
        fixed-address 192.168.100.121;
        hardware ethernet 52:54:00:C2:3B:60;
      }
      host WIMP {
        fixed-address 192.168.100.113;
        hardware ethernet 52:54:00:B9:9B:D1;
      }
      host WIND {
        fixed-address 192.168.100.114;
        hardware ethernet 52:54:00:66:97:5B;
      }
      host WPC1 {
        fixed-address 192.168.100.131;
        hardware ethernet 52:54:00:85:DA:DC;
      }
      host WPC2 {
        fixed-address 192.168.100.132;
        hardware ethernet 52:54:00:98:EA:03;
      }
      host WPC3 {
        fixed-address 192.168.100.133;
        hardware ethernet 52:54:00:86:12:B1;
      }
      host WPC4 {
        fixed-address 192.168.100.134;
        hardware ethernet 52:54:00:6a:14:c5;
      }
      host CONA {
        fixed-address 192.168.100.113;
        hardware ethernet 52:54:00:ae:91:54;
      }
      host CONB {
        fixed-address 192.168.100.114;
        hardware ethernet 52:54:00:3a:44:3a;
      }
    }
    If it can help i have some screenshot of the network settings and the dhcp settings on yast.

    Thanks in advance for your help.

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    28,902

    Default Re: DHCP server don't assign IP adresses

    Quote Originally Posted by yaco View Post

    The dhcp server is set on a SLES 15 SP1 distribution on a dell server, ........
    Sorry that you missed this, but these are the openSUSE forums, not the SLES/SLED forums. They are at http://forums.suse.com/ (same username/password as here).
    Henk van Velden

  3. #3
    Join Date
    Sep 2012
    Posts
    6,639

    Default Re: DHCP server don't assign IP adresses

    Quote Originally Posted by hcvv View Post
    (same username/password as here).
    That's wrong. SUSE forums are using Okta user database now while these forums are using different backend.

  4. #4
    Join Date
    May 2012
    Location
    Finland
    Posts
    2,160

    Default Re: DHCP server don't assign IP adresses

    Quote Originally Posted by yaco View Post
    If it can help i have some screenshot of the network settings and the dhcp settings on yast.
    Since SLE and openSUSE are literally the same nowadays, I'm gonna give you a hand no matter what you're running (run all commands as root or with sudo)

    1. Make sure all network devices are up and they have expected IP addresses and that the interfaces are up:
    Code:
    ip a
    2. Make sure the DHCP server is actually running :-)
    Code:
    systemctl status dhcpd
    3. Check dhcpd error logs for anything that might hint as to what the problem is;
    Code:
    journalctl -u dhcpd -b
    .: miuku @ #opensuse @ irc.libera.chat

  5. #5
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    28,902

    Default Re: DHCP server don't assign IP adresses

    Quote Originally Posted by arvidjaar View Post
    That's wrong. SUSE forums are using Okta user database now while these forums are using different backend.
    Thanks for the update.
    Henk van Velden

  6. #6

    Default Re: DHCP server don't assign IP adresses

    Thanks for your answer.

    Quote Originally Posted by Miuku View Post
    1. Make sure all network devices are up and they have expected IP addresses and that the interfaces are up:
    Code:
    ip a
    I tried this on the server and on one of the machine, on both all the interfaces are UP.
    On the server the only interface with an IP is "ptf1", which is the DHCP server selected interface.
    On my VMs, i have 2 interface on two different subnet.
    When i do this command eth0 which is suppose to be connected to my dhcp server does not seem to request anything (i only have the fake IP v6 address), and on eth1 i have a correct IP v4 address coming from on external dhcp server.
    But when i do a "ifstatus eth0", i can see "leases : ipv4 dhcp requesting", so i suppose the interface is actually doing something.

    Quote Originally Posted by Miuku View Post
    2. Make sure the DHCP server is actually running :-)
    Code:
    systemctl status dhcpd
    This i tried multiple time and it's starting correctly.

    Quote Originally Posted by Miuku View Post
    3. Check dhcpd error logs for anything that might hint as to what the problem is;
    Code:
    journalctl -u dhcpd -b
    Same, No error, just a warning "Host declarations are global. They are not limited to the scope you declared them in."



    I don't know what to do next i tried to see if "ifup" or "ifdown" can help but i get nothing new.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •