[Debian] DHCP Server.

itsgreen · Jul 18, 2014

Hey,

ich fange grade an, mich mit dem isc-dhcp-server zu beschäftigen.

Ich stelle mir das ganze so vor:
MOD: Bilder bitte immer als Anhang. Danke!

Leider bekomme ich noch nicht das gewünste Ergebnis.

Ich bin bereits soweit, das mein Server die IP Adressen an die PCs vergibt.
Jetzt haben die PCs die hinter meinem Server sind aber noch kein Internetzugang.

Ich Poste hier mal alle Configs, Meldungen und Außgaben, die relevant sind.

Ich hoffe, jemand kann mir dabei helfen.

File: /etc/default/isc-dhcp-server

Code:

# Defaults for dhcp initscript
# sourced by /etc/init.d/dhcp
# installed at /etc/default/isc-dhcp-server by the maintainer scripts

#
# This is a POSIX shell fragment
#

# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
#       Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACES="eth1"

File: /etc/dhcp/dhcp.conf

Code:

#
# Sample configuration file for ISC dhcpd for Debian
#
#

# 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 "my.network";
option domain-name-servers 8.8.8.8, 8.8.4.4;

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.224 {
#  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 10.5.5.0 netmask 255.255.255.224 {
#  range 10.5.5.26 10.5.5.30;
#  option domain-name-servers ns1.internal.example.org;
#  option domain-name "internal.example.org";
#  option routers 10.5.5.1;
#  option broadcast-address 10.5.5.31;
#  default-lease-time 600;
#  max-lease-time 7200;
#}
# 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;
#  }
#}

subnet 192.168.1.0 netmask 255.255.255.0 {
  range 192.168.1.20 192.168.1.80;
  option routers 192.168.1.1;
}

File: /etc/network/interfaces

Code:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo eth1
iface lo inet loopback

# The primary network interface
allow-hotplug eth0

iface eth0 inet dhcp

iface eth1 inet static
     address 192.168.1.1
     netmask 255.255.0.0
     gateway 192.168.1.66
     #bridge_ports eth0

up route add -net 192.168.1.1 netmask 255.255.255.0 gw 192.168.178.1
down route del -net 192.168.1.1 netmask 255.255.255.0 gw 192.168.178.1

Command: route -n

Code:

Ziel            Router          Genmask         Flags Metric Ref    Use Iface
192.168.178.0   0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth1
0.0.0.0         192.168.178.1   0.0.0.0         UG    0      0        0 eth0
0.0.0.0         192.168.1.66    0.0.0.0         UG    0      0        0 eth1

Command: ifconfig

Code:

root@Server:~# ifconfig -a
eth0      Link encap:Ethernet  Hardware Adresse 00:19:66:b7:08:88
          inet Adresse:192.168.178.39  Bcast:192.168.178.255  Maske:255.255.255.0
          inet6-Adresse: fe80::219:66ff:feb7:888/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX packets:651 errors:0 dropped:0 overruns:0 frame:0
          TX packets:424 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:60763 (59.3 KiB)  TX bytes:55436 (54.1 KiB)
          Interrupt:22 Basisadresse:0xb000
 
eth1      Link encap:Ethernet  Hardware Adresse 00:1c:f0:d5:37:52
          inet Adresse:192.168.1.1  Bcast:192.168.255.255  Maske:255.255.0.0
          inet6-Adresse: fe80::21c:f0ff:fed5:3752/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX packets:143 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:14331 (13.9 KiB)  TX bytes:762 (762.0 B)
          Interrupt:22 Basisadresse:0xb800
 
lo        Link encap:Lokale Schleife
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:16436  Metrik:1
          RX packets:14 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0
          RX bytes:2696 (2.6 KiB)  TX bytes:2696 (2.6 KiB)

Könnt ihr mir sagen, was fehlt? Was habe ich übersehen?

lieben Gruß
itsgreen

Firewire2002 · Jul 19, 2014

Ist Forwarding auf dem Server überhaupt aktiviert?
Kennt die Fritzbox die Route in das 2. Subnetz mit Server als Gateway? Alternativ NAT auf dem Server vom Subnetz Richtung Fritzbox konfiguriert?

[Debian] DHCP Server.

itsgreen

New Member

Attachments

Firewire2002

Registered User

We value your privacy