PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : ISC DHCPd gibt den standartgateway nicht weiter...



crazy-sonic
03.12.07, 22:10
Hallo leute.

Hab mir die Finger wund gesucht aber nichts gefunden.
Habe mir einen Server gebastelt mit Suse 9.2 und 2 netzwekkarten.

Folgendes Problem stellt sich hier:

Ich habe halt den suse 9.2 server auf dem ISC DHCPd 3.0.1 Läuft...
der client windoof XP PRO der vom DHCP IPadresse , DNS-Server , StandartGateway und WINS. funzt auch alles prima, bis auf die sache mit dem standartgateway. Alle werte werden übermittelt bis auf Stand.Gate. die aber
korrekt auf dem server eingetragen sind.

Meine Systeminfo:
Server:
Mainboard: Via Epia CN1000 Grafik LAN(eth0) Sound usw on Board.
RAM: 512MB DDR 2 elixir
Festplatte: 60GB 2,5" Toshiba
2te: eth1 LAN-Karte 3COM

Beriebssys.:
suse Linux 9.2
ISC DHCPd 3.0.1
WEBMIN 1.3.8.0 zur Konfiguration

Die interne LanKarte ist die Onboardkarte ip:192.168.0.1

DHCPd.conf:
option routers 192.168.0.1;
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#


default-lease-time 600;
max-lease-time 7200;

# if you do not use dynamical DNS updates:
#
# this statement is needed by dhcpd-3 needs at least this statement.
# you have to delete it for dhcpd-2, because it does not know it.
#
# if you want to use dynamical DNS updates, you should first read
ddns-update-style none;


# 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.


# This is a very basic subnet declaration.


# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.



# 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.


# 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

# 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";
}

subnet 192.168.0.0 netmask 255.255.255.0 {
max-lease-time 31104000;
default-lease-time 2592000;
authoritative;
allow client-updates;
ddns-updates on;
option dhcp-server-identifier 192.168.0.1;
option broadcast-address 255.255.255.0;
option domain-name-servers 192.168.0.1;
option subnet-mask 255.255.255.0;
option routers 192.168.0.1;
range 192.168.0.10 192.168.0.100;
}
# Laptop kabel
host crazy-laptop {
option broadcast-address 192.168.0.0;
option domain-name-servers 192.168.0.1;
option subnet-mask 255.255.255.0;
option host-name "muffdi";
option routers 192.168.0.1;
hardware ethernet 00:16:36:C2:EE:1E;
fixed-address 192.168.0.10;
}


ich hoffe ihr könnt mir helfen ... bin verzweifelt...

mfG: Crazy-Sonic

$kuLL
04.12.07, 12:20
class "foo" {
match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
}

subnet 192.168.0.0 netmask 255.255.255.0 {
max-lease-time 31104000;
default-lease-time 2592000;
authoritative;
allow client-updates;
ddns-updates on;
option dhcp-server-identifier 192.168.0.1;
option broadcast-address 255.255.255.0;
option domain-name-servers 192.168.0.1;
option subnet-mask 255.255.255.0;
option routers 192.168.0.1;
range 192.168.0.10 192.168.0.100;
}
# Laptop kabel
host crazy-laptop {
option broadcast-address 192.168.0.0;
option domain-name-servers 192.168.0.1;
option subnet-mask 255.255.255.0;
option host-name "muffdi";
option routers 192.168.0.1;
hardware ethernet 00:16:36:C2:EE:1E;
fixed-address 192.168.0.10;
}
Die Broadcast für das 0er Netz wäre 192.168.0.255. Es gibt auch kein Grund in der Host Section alle Informationen nochmal redundant anzugeben.

host crazy-laptop {
hardware ethernet 00:16:36:C2:EE:1E;
fixed-address 192.168.0.10;
}
Das sollte ausreichen. Was die beiden unterschiedlichen Hostnamen sollen, weiß ich auch nicht. Hast du die Config selber erstellt?

crazy-sonic
04.12.07, 12:55
Super hat alles geklappt, die fehler kamen durch das viele hin und her mit den Configs...


Besten Dank Crazy-Sonic :ugly: