PalDiaray schrieb:
... Aber ich habe immernoch keine Ahnung wie das Problem entstanden ist.
Wenn Du z. Zt. keinen dhcp-Client auf deinem Server hast oder der dhcp-Client auf deinem Server nicht richtig konfiguriert ist, dann kannst Du z. B. mit dem tool nmap prüfen/testen, ob dein Server z. Zt. Zugang bzw. eine funktionierende Verbindung zu einem DHCP-Server hat bzw. herstellen kann. Z. B. mit:
sudo tcpdump -c 100 -vvveni <Interface> portrange 67-68
(Interface anpassen und ohne spitze Klammern).
Danach ausführen:
sudo nmap --script broadcast-dhcp-discover
Siehe nach dem Ausführen von nmap, die Ausgaben von tcpdump und die von nmap.
Hier ein Beispiel für solche Ausgaben:
:~$ sudo tcpdump -c 100 -vvveni wlan1 portrange 67-68
tcpdump: listening on wlan1, link-type EN10MB (Ethernet), capture size 262144 bytes
09:37:03.479783 ##:##:##:17:62:b4 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 355: (tos 0x0, ttl 64, id 55989, offset 0, flags [DF], proto UDP (17), length 341)
192.168.178.22.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from de:ad:c0:de:ca:fe, length 313, xid 0xfa921924, Flags [Broadcast] (0x8000)
Client-Ethernet-Address de:ad:c0:de:ca:fe
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
Parameter-Request Option 55, length 61:
Subnet-Mask, Time-Zone, Default-Gateway, Time-Server
IEN-Name-Server, Domain-Name-Server, LOG, CS
LPR-Server, IM, RL, Hostname
BS, DP, Domain-Name, SS
RP, EP, IPF, SRT
PF, RSZ, TTL, MTU-Timeout
MTU-Table, MTU, LSN, BR
MD, MS, Router-Discovery, RSA
Static-Route, UT, AT, IE
TT, KI, KG, YD
YS, NTP, Vendor-Option, Netbios-Name-Server
WDD, Netbios-Node, Netbios-Scope, XFS
XDM, Requested-IP, Lease-Time, OO
DHCP-Message, Server-ID, Parameter-Request, MSG
MSZ, RN, RB, Vendor-Class
Client-ID
Lease-Time Option 51, length 4: 1
END Option 255, length 0
09:37:04.496144 c0:25:06:##:##:## > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 590: (tos 0x0, ttl 64, id 55989, offset 0, flags [none], proto UDP (17), length 576)
192.168.178.1.67 > 255.255.255.255.68: [udp sum ok] BOOTP/DHCP, Reply, length 548, xid 0xfa921924, Flags [Broadcast] (0x8000)
Your-IP 192.168.178.43
Server-IP 192.168.178.1
Client-Ethernet-Address de:ad:c0:de:ca:fe
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Offer
Server-ID Option 54, length 4: 192.168.178.1
Lease-Time Option 51, length 4: 432000
RN Option 58, length 4: 216000
RB Option 59, length 4: 378000
Subnet-Mask Option 1, length 4: 255.255.255.0
Default-Gateway Option 3, length 4: 192.168.178.1
Domain-Name-Server Option 6, length 4: 192.168.178.1
Domain-Name Option 15, length 9: "fritz.box"
BR Option 28, length 4: 192.168.178.255
NTP Option 42, length 4: 192.168.178.1
END Option 255, length 0
PAD Option 0, length 0, occurs 239
^C
2 packets captured
2 packets received by filter
0 packets dropped by kernel
:~$ sudo nmap --script broadcast-dhcp-discover
Starting Nmap 6.40 ( http://nmap.org ) at 2020-01-07 09:37 CET
Pre-scan script results:
| broadcast-dhcp-discover:
| IP Offered: 192.168.178.43
| DHCP Message Type: DHCPOFFER
| Server Identifier: 192.168.178.1
| IP Address Lease Time: 5 days, 0:00:00
| Renewal Time Value: 2 days, 12:00:00
| Rebinding Time Value: 4 days, 9:00:00
| Subnet Mask: 255.255.255.0
| Router: 192.168.178.1
| Domain Name Server: 192.168.178.1
| Domain Name: fritz.box
| Broadcast Address: 192.168.178.255
|_ NTP Servers: 192.168.178.1
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 1.45 seconds