forum.lissyara.su

Код: Выделить всё

# STB-0.1.1-beta (Simple Traffic Billing)
ext_if="fxp0"
int_if="em0"
vpn_if="{ tun0, tun1, tun2, tun3, tun4, tun5, tun6, tun7, tun8, tun9 }"
ext_add="XX.19X.2X5.XX"

# tables for STB
table <int_if> persist { em0 }
table <passip> persist file "/var/stb/etc/pass.ip"
table <bogons> const { 10.0.0.0/8, 172.0.0.0/12, 192.168.0.0/16, 127.0.0.0/8 }
services="{ 21, 22, 25, 53, 80, 110, 123 }"

scrub in all
set skip on lo0

nat on $ext_if from $int_if:network to any -> ($ext_if)
#nat on $ext_if from <passip> to any -> ($ext_if)
rdr proto tcp from $int_if to port 21 -> 127.0.0.1 port 8021

#pass in all
#pass out all

#block private networks
block in on $ext_if from <bogons> to any
block out on $ext_if from any to <bogons>

block out on $ext_if from <int_if> to any

#allow all on internal interface
pass in on $int_if proto {tcp, udp} from any to any
pass out on $int_if proto {tcp, udp} from any to any

#pass valid service's on external interface
pass in on $ext_if proto {tcp, udp} from $ext_add to any port $services
pass out on $ext_if proto {tcp, udp} from $ext_add to any port $services

# allow vpn connection
pass on $ext_if proto tcp from any to $ext_add port 1723

# allow gre
pass on $ext_if proto gre from any to any

# allow
pass on $vpn_if from any to any

# allow cvsup
pass out on $ext_if proto tcp from $ext_add to any port 5999

Код: Выделить всё

// $FreeBSD: src/etc/namedb/named.conf,v 1.21.2.1 2005/09/10 08:27:27 dougb Exp
$
//
// Refer to the named.conf(5) and named(8) man pages, and the documentation
// in /usr/share/doc/bind9 for more details.
//
// If you are going to set up an authoritative server, make sure you
// understand the hairy details of how DNS works.  Even with
// simple mistakes, you can break connectivity for affected parties,
// or cause huge amounts of useless Internet traffic.

options {
        directory       "/etc/namedb";
        pid-file        "/var/run/named/pid";
        dump-file       "/var/dump/named_dump.db";
        statistics-file "/var/stats/named.stats";

// If named is being used only as a local resolver, this is a safe default.
// For named to be accessible to the network, comment this option, specify
// the proper IP address, or delete this option.
//      listen-on       { 127.0.0.1; };

// If you have IPv6 enabled on this system, uncomment this option for
// use as a local resolver.  To give access to the network, specify
// an IPv6 address, or the keyword "any".
//      listen-on-v6    { ::1; };

// In addition to the "forwarders" clause, you can force your name
// server to never initiate queries of its own, but always ask its
// forwarders only, by enabling the following line:
//
//      forward only;

// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below.  This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.

        forwarders {
                212.34.33.1; 212.34.32.39;
        };

        /*
         * If there is a firewall between you and nameservers you want
         * to talk to, you might need to uncomment the query-source
         * directive below.  Previous versions of BIND always asked
         * questions using port 53, but BIND versions 8 and later
         * use a pseudo-random unprivileged UDP port by default.
         */
        // query-source address * port 53;
};

// If you enable a local name server, don't forget to enter 127.0.0.1
// first in your /etc/resolv.conf so this server will be queried.
// Also, make sure to enable it in /etc/rc.conf.

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

zone "0.0.127.IN-ADDR.ARPA" {
        type master;
        file "master/localhost.rev";
};

// RFC 3152
zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA"
{
        type master;
        file "master/localhost-v6.rev";
};

// NB: Do not use the IP addresses below, they are faked, and only
// serve demonstration/documentation purposes!
//
// Example slave zone config entries.  It can be convenient to become
// a slave at least for the zone your own domain is in.  Ask
// your network administrator for the IP address of the responsible
// primary.
//
// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
// (This is named after the first bytes of the IP address, in reverse
// order, with ".IN-ADDR.ARPA" appended.)
//
// Before starting to set up a primary zone, make sure you fully
// understand how DNS and BIND works.  There are sometimes
// non-obvious pitfalls.  Setting up a slave zone is simpler.
//
// NB: Don't blindly enable the examples below. :-)  Use actual names
// and addresses instead.