dhcp proxy und firewall

Post Reply
Message
Author
yool

dhcp proxy und firewall

#1 Post by yool »

hilfe verzweiflung droht! seit tagen plagt mich folgendes prob:
der suse 8.1 funzt (sollte) als proxy-dhcp-samba-router server mit firewall (suse2) laufen.
kabelmodem an einer netzwerkkarte hub an der anderen netzkarte. kabelmodem bekommt per dhcp die ip (läuft)

status: proxy läuft auf dem server und surfen ist mögl. dhcp ip vergabe geht (nicht) mehr. anbei die beiden files named und dhcp.conf vielleicht findet ja jemand raus wiso das das ned geht. falls mehr infos benötigt bitte melden. wär echt froh wenn jemand rat wüsste

# dhcpd.conf
#
# a minimal /etc/dhcpd.conf example

# 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.
ddns-update-style none;

# this subnet is served by us
authoritative;

# declare the lease times (the time after which a client will renew its lease)
default-lease-time 600; # 10 minutes
max-lease-time 7200; # 2 hours

# let's give the local domain a name
# (which should correlate to your name server configuration)
option domain-name "kosmos.all";

# this assumes that your dhcp server is also the router for the subnet
option routers 192.168.1.2;

# clients shall use this host as nameserver, too
option domain-name-servers 192.168.1.2;
option netbios-name-servers 192.168.1.2;

# this can explicitely be specified
option broadcast-address 192.168.1.255;

# these addresses will be given out dynamically
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.20 192.168.1.200;
# options may also be put here if they are not global
}



options {

# The directory statement defines the name server's
# working directory

directory "/var/named";

# The forwarders record contains a list of servers to
# which queries should be forwarded. Enable this line and
# modify the IP-address to your provider's name server.
# Up to three servers may be listed.

forwarders { 192.168.1.1;
194.25.2.129; };

# Enable the next entry to prefer usage of the name
# server declared in the forwarders section.

#forward first;

# The listen-on record contains a list of local network
# interfaces to listen on. Optionally the port can be
# specified. Default is to listen on all interfaces found
# on your system. The default port is 53.

#listen-on port 53 { 127.0.0.1; };

# The next statement may be needed if a firewall stands
# between the local server and the internet.

#query-source address * port 53;

# The allow-query record contains a list of networks or
# IP-addresses to accept and deny queries from. The
# default is to allow queries from all hosts.

allow-query { 127.0/16; 192.168.1/24; };

# The cleaning-interval statement defines the time interval
# in minutes for periodic cleaning. Default is 60 minutes.
# By default, all actions are logged to /var/log/messages.

cleaning-interval 120;

# Name server statistics will be logged to /var/log/messages
# every <statistics-interval> minutes. Default is 60 minutes.
# A value of 0 disables this feature.

statistics-interval 0;

# If notify is set to yes (default), notify messages are
# sent to other name servers when the the zone data is
# changed. Instead of setting a global 'notify' statement
# in the 'options' section, a separate 'notify' can be
# added to each zone definition.

notify no;
};

# The following three zone definitions don't need any modification.
# The first one defines localhost while the second defines the
# reverse lookup for localhost. The last zone "." is the
# definition of the root name servers.

zone "localhost" in {
type master;
file "localhost.zone";
};

zone "0.0.127.in-addr.arpa" in {
type master;
file "127.0.0.zone";
};

zone "." in {
type hint;
file "root.hint";
};

# You can insert further zone records for your own domains below.


zone "kosmos.all" in {
type master;
file "privat.zone";
};

zone "1.168.192.in-addr.arpa" in {
type master;
file "tavirp.zone";
};

D. Ynamicip

Re: dhcp proxy und firewall

#2 Post by D. Ynamicip »

Läuft er denn wirklich, der dhcpd? Was steht denn nach einem
rcdhcpd restart
in /var/log/messages ?

Post Reply