数分後、「DHCPの提案を受け取りませんでした!」というメッセージが届きました。これはサーバー上の私のdhcp.confです。
#
# Sample configuration file for ISC dhcpd for Debian
#
# Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as
# configuration file instead of this file.
#
#
# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;
# option definitions common to all supported networks...
option domain-name "example.org";
option domain-name-servers 192.168.1.60;
default-lease-time 600;
max-lease-time 7200;
# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
authoritative;
# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;
# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.
#subnet 10.152.187.0 netmask 255.255.255.0 {
#}
# This is a very basic subnet declaration.
#subnet 10.254.239.0 netmask 255.255.255.224 {
# range 10.254.239.10 10.254.239.20;
# option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
#}
# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.
#subnet 10.254.239.32 netmask 255.255.255.0 {
# range dynamic-bootp 10.254.239.40 10.254.239.60;
# option broadcast-address 10.254.239.31;
# option routers rtr-239-32-1.example.org;
#}
# A slightly different configuration for an internal subnet.
subnet 192.168.1.60 netmask 255.255.255.0 {
range 192.168.1.30 192.168.1.120;
# option domain-name-servers ns1.internal.example.org;
# option domain-name "internal.example.org";
# option subnet-mask 255.255.255.224;
option routers 192.168.1.60;
# option broadcast-address 10.5.5.31;
# default-lease-time 600;
# max-lease-time 7200;
filename="ubuntu/install/netboot/pxelinux.0";
}
# Hosts which require special configuration options can be listed in
# host statements. If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.
#host passacaglia {
# hardware ethernet 0:0:c0:5d:bd:95;
# filename "vmunix.passacaglia";
# server-name "toccata.fugue.com";
#}
# Fixed IP addresses can also be specified for hosts. These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP. Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
# hardware ethernet 08:00:07:26:c0:a5;
# fixed-address fantasia.fugue.com;
#}
# You can declare a class of clients and then do address allocation
# based on that. The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.
#class "foo" {
# match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
#}
#shared-network 224-29 {
# subnet 10.17.224.0 netmask 255.255.255.0 {
# option routers rtr-224.example.org;
# }
# subnet 10.0.29.0 netmask 255.255.255.0 {
# option routers rtr-29.example.org;
# }
# pool {
# allow members of "foo";
# range 10.17.224.10 10.17.224.250;
# }
# pool {
# deny members of "foo";
# range 10.0.29.10 10.0.29.230;
# }
#}
サーバー ifconfig:
eno1 Link encap:Ethernet HWaddr a0:48:1c:16:ab:19
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:254 errors:0 dropped:0 overruns:0 frame:0
TX packets:574 errors:1 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:73982 (73.9 KB) TX bytes:93643 (93.6 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:6001 errors:0 dropped:0 overruns:0 frame:0
TX packets:6001 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:499008 (499.0 KB) TX bytes:499008 (499.0 KB)
wlo1 Link encap:Ethernet HWaddr 70:18:8b:cc:41:09
inet addr:192.168.1.60 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::2074:6e2b:49be:277c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:64333 errors:0 dropped:0 overruns:0 frame:0
TX packets:54185 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:63862865 (63.8 MB) TX bytes:10043170 (10.0 MB)
クライアント ifconfig:
eth0 Link encap:Ethernet HWaddr 1c:75:08:f5:7e:62
inet6 addr: fe80::1e75:8ff:fef5:7e62/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:173 errors:0 dropped:0 overruns:0 frame:0
TX packets:246 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:36691 (36.6 KB) TX bytes:49110 (49.1 KB)
Interrupt:16
lo Link encap:Локальная петля (Loopback)
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:297 errors:0 dropped:0 overruns:0 frame:0
TX packets:297 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:28316 (28.3 KB) TX bytes:28316 (28.3 KB)
wlan0 Link encap:Ethernet HWaddr 88:9f:fa:19:76:c7
inet addr:192.168.1.45 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::8a9f:faff:fe19:76c7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1004 errors:0 dropped:0 overruns:0 frame:0
TX packets:197 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:130953 (130.9 KB) TX bytes:25928 (25.9 KB)
機能させるには何を変更する必要がありますか?
イーサネット経由で接続されたPSコンピュータ
ベストアンサー1
私が見たエラー(一部見落とされた可能性があります):
- イーサネットには割り当てられたIPアドレスはありません。
dhcp.conf
代わりにWLANインターフェイスのアドレス範囲を使用してください。- サブネット記述はネットマスクで0に設定されていません(サブネットは192.168.1でなければなりません)。0マスク 255.255.255.0 を含む)
- 割り当てられた範囲はDHCPサーバーのIPアドレスと重複します。
- PXEが必要かどうかはわかりませんが、
allow booting;
回線が痛くはallow bootp;
ありませんdhcp.conf
。 - ネームサーバーオプションは実際にDNSを提供しない限り機能しませんが(おそらくそうではありません)、PXEはDNSを要求しないため問題ありません。
だから:
- たとえば、WLANとは異なるプライベートサブネットを選択します
192.168.22.0
。 - 割り当てられたDHCPアドレス
192.168.22.30
に移動しましょう。192.168.22.120
- DHCPサーバーのアドレスは、選択したとおりに外部アドレスでなければなりません
192.168.22.1
。 - このアドレスをに割り当て
eno1
ますip addr add 192.168.22.1/24 dev eno1
。 - 変更して
dhcp.conf
再起動してくださいdhcpd
。
それからもう一度やり直してください。