Помогите настроить nodeny

[uchenik]

как можно проверить,где смотреть

[VitalVas]

в ядро добавил диверт?

[stix]

можно просто убрать с начальных правил файрвола правила диверта.
если анлим тарифы, то считать ничего не нужно

в ядро добавляются следующие строки

Код:

options         IPFIREWALL
options         IPDIVERT
options         IPFIREWALL_FORWARD
options         DUMMYNET

файрвол, перенаправляемые сокеты, форвардинг, шейпинг

[uchenik]

Когда ядро компелировал добавил

options         IPFIREWALL
options         IPDIVERT
options         IPFIREWALL_FORWARD
options         DUMMYNET
device          pf


Если перекомпелировать ядро,весь биллинг ставить нужно заново?

[versus]

нет не надо, стукни ко мне в скайп versus.ua попробуем вылечить оперативным вмешательством

[uchenik]

Если пробую подгрузить командой модуль ipdivert.ko

[root@kommunar /home/elhan]# kldload ipdivert
kldload: can't load ipdivert: File exists
судя по всему он запущен.


Может причина в маршрутизаторе который стоит до биллинга,
стоит dir100 на котором поднят инет от прова по протоколу L2TP,а с него уже на биллинг.

[uchenik]

kernel configuration NODENY

Код:

#
# GENERIC -- Generic kernel configuration file for FreeBSD/i386
#
# For more information on this file, please read the handbook section on
# Kernel Configuration Files:
#
#    http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also available locally in /usr/share/doc/handbook
# if you've installed the doc distribution, otherwise always see the
# FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the
# latest information.
#
# An exhaustive list of options and more detailed explanations of the
# device lines is also present in the ../../conf/NOTES and NOTES files.
# If you are in doubt as to the purpose or necessity of a line, check first
# in NOTES.
#
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.474.2.22.2.1 2010/02/10 00:26:20 kensmith Exp $

cpu		I686_CPU
ident		NODENY

# To statically compile in device wiring instead of /boot/device.hints
#hints		"GENERIC.hints"		# Default places to look for devices.

makeoptions	DEBUG=-g		# Build kernel with gdb(1) debug symbols

options 	SCHED_ULE		# ULE scheduler
options 	PREEMPTION		# Enable kernel thread preemption
options 	INET			# InterNETworking
#options 	INET6			# IPv6 communications protocols
options 	SCTP			# Stream Control Transmission Protocol
options 	FFS			# Berkeley Fast Filesystem
options 	SOFTUPDATES		# Enable FFS soft updates support
options 	UFS_ACL			# Support for access control lists
options 	UFS_DIRHASH		# Improve performance on big directories
options 	UFS_GJOURNAL		# Enable gjournal-based UFS journaling
options 	MD_ROOT			# MD is a potential root device
options 	NFSCLIENT		# Network Filesystem Client
options 	NFSSERVER		# Network Filesystem Server
options 	NFSLOCKD		# Network Lock Manager
options 	NFS_ROOT		# NFS usable as /, requires NFSCLIENT
#options 	MSDOSFS			# MSDOS Filesystem
options 	CD9660			# ISO 9660 Filesystem
options 	PROCFS			# Process filesystem (requires PSEUDOFS)
options 	PSEUDOFS		# Pseudo-filesystem framework
options 	GEOM_PART_GPT		# GUID Partition Tables.
options 	GEOM_LABEL		# Provides labelization
options 	COMPAT_43TTY		# BSD 4.3 TTY compat [KEEP THIS!]
options 	COMPAT_FREEBSD4		# Compatible with FreeBSD4
options 	COMPAT_FREEBSD5		# Compatible with FreeBSD5
options 	COMPAT_FREEBSD6		# Compatible with FreeBSD6
options 	SCSI_DELAY=5000		# Delay (in ms) before probing SCSI
options 	KTRACE			# ktrace(1) support
options 	STACK			# stack(9) support
options 	SYSVSHM			# SYSV-style shared memory
options 	SYSVMSG			# SYSV-style message queues
options 	SYSVSEM			# SYSV-style semaphores
options 	P1003_1B_SEMAPHORES	# POSIX-style semaphores
options 	_KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions
options 	KBD_INSTALL_CDEV	# install a CDEV entry in /dev
options 	ADAPTIVE_GIANT		# Giant mutex is adaptive.
options 	STOP_NMI		# Stop CPUS using NMI instead of IPI
options 	AUDIT			# Security event auditing
#options 	KDTRACE_HOOKS		# Kernel DTrace hooks
options 	INCLUDE_CONFIG_FILE     # Include this file in kernel

# To make an SMP kernel, the next two lines are needed
options 	SMP			# Symmetric MultiProcessor Kernel
device		apic			# I/O APIC

# CPU frequency control
device		cpufreq

# Bus support.
device		eisa
device		pci

# Floppy drives
#device		fdc

# ATA and ATAPI devices
device		ata
device		atadisk		# ATA disk drives
device		ataraid		# ATA RAID drives
device		atapicd		# ATAPI CDROM drives
device		atapifd		# ATAPI floppy drives
device		atapist		# ATAPI tape drives
options 	ATA_STATIC_ID	# Static device numbering


# atkbdc0 controls both the keyboard and the PS/2 mouse
device		atkbdc		# AT keyboard controller
device		atkbd		# AT keyboard
device		psm		# PS/2 mouse

device		kbdmux		# keyboard multiplexer

device		vga		# VGA video card driver

device		splash		# Splash screen and screen saver support

# syscons is the default console driver, resembling an SCO console
device		sc

device		agp		# support several AGP chipsets

# Power management support (see NOTES for more options)
#device		apm
# Add suspend/resume support for the i8254.
device		pmtimer

# PCCARD (PCMCIA) support
# PCMCIA and cardbus bridge support
device		cbb		# cardbus (yenta) bridge
device		pccard		# PC Card (16-bit) bus
device		cardbus		# CardBus (32-bit) bus

# Serial (COM) ports
device		sio		# 8250, 16[45]50 based serial ports
device		uart		# Generic UART driver

# Parallel port
device		ppc
device		ppbus		# Parallel port bus (required)
device		lpt		# Printer
device		plip		# TCP/IP over parallel
device		ppi		# Parallel port interface device
#device		vpo		# Requires scbus and da

# If you've got a "dumb" serial or parallel PCI card that is
# supported by the puc(4) glue driver, uncomment the following
# line to enable it (connects to sio, uart and/or ppc drivers):
#device		puc

# PCI Ethernet NICs.
device		de		# DEC/Intel DC21x4x (``Tulip'')
device		em		# Intel PRO/1000 Gigabit Ethernet Family
device		igb		# Intel PRO/1000 PCIE Server Gigabit Family
device		ixgb		# Intel PRO/10GbE Ethernet Card
device		le		# AMD Am7900 LANCE and Am79C9xx PCnet
device		txp		# 3Com 3cR990 (``Typhoon'')
device		vx		# 3Com 3c590, 3c595 (``Vortex'')

# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
device		miibus		# MII bus support
device		age		# Attansic/Atheros L1 Gigabit Ethernet
device		alc		# Atheros AR8131/AR8132 Ethernet
device		ale		# Atheros AR8121/AR8113/AR8114 Ethernet
device		bce		# Broadcom BCM5706/BCM5708 Gigabit Ethernet
device		bfe		# Broadcom BCM440x 10/100 Ethernet
device		bge		# Broadcom BCM570xx Gigabit Ethernet
device		dc		# DEC/Intel 21143 and various workalikes
device		et		# Agere ET1310 10/100/Gigabit Ethernet
device		fxp		# Intel EtherExpress PRO/100B (82557, 82558)
device		jme		# JMicron JMC250 Gigabit/JMC260 Fast Ethernet
device		lge		# Level 1 LXT1001 gigabit Ethernet
device		msk		# Marvell/SysKonnect Yukon II Gigabit Ethernet
device		nfe		# nVidia nForce MCP on-board Ethernet
device		nge		# NatSemi DP83820 gigabit Ethernet
#device		nve		# nVidia nForce MCP on-board Ethernet Networking
device		pcn		# AMD Am79C97x PCI 10/100 (precedence over 'le')
device		re		# RealTek 8139C+/8169/8169S/8110S
device		rl		# RealTek 8129/8139
device		sf		# Adaptec AIC-6915 (``Starfire'')
device		sis		# Silicon Integrated Systems SiS 900/SiS 7016
device		sk		# SysKonnect SK-984x & SK-982x gigabit Ethernet
device		ste		# Sundance ST201 (D-Link DFE-550TX)
device		stge		# Sundance/Tamarack TC9021 gigabit Ethernet
device		ti		# Alteon Networks Tigon I/II gigabit Ethernet
device		tl		# Texas Instruments ThunderLAN
device		tx		# SMC EtherPower II (83c170 ``EPIC'')
device		vge		# VIA VT612x gigabit Ethernet
device		vr		# VIA Rhine, Rhine II
device		wb		# Winbond W89C840F
device		xl		# 3Com 3c90x (``Boomerang'', ``Cyclone'')


# Pseudo devices.
device		loop		# Network loopback
device		random		# Entropy device
device		ether		# Ethernet support
device		vlan		# 802.1Q VLAN support
device		sl		# Kernel SLIP
device		ppp		# Kernel PPP
device		tun		# Packet tunnel.
device		pty		# Pseudo-ttys (telnet etc)
device		md		# Memory "disks"
device		gif		# IPv6 and IPv4 tunneling
device		faith		# IPv6-to-IPv4 relaying (translation)
device		firmware	# firmware assist module

# The `bpf' device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
# Note that 'bpf' is required for DHCP.
device		bpf		# Berkeley packet filter

device          pf
device          pflog
device          pfsync
options         IPFIREWALL
options         IPDIVERT
options         IPFIREWALL_FORWARD
options         DUMMYNET
options         ALTQ_CBQ        # Class Bases Queuing (CBQ)
options         ALTQ_RED        # Random Early Detection (RED)
options         ALTQ_RIO        # RED In/Out
options         ALTQ_HFSC       # Hierarchical Packet Scheduler (HFSC)
options         ALTQ_PRIQ       # Priority Queuing (PRIQ)
options         ALTQ_NOPCC      # Required for SMP build

юзайте тег "Код"

[sl]

попробуй в rc.conf добавить pf_rules="/etc/pf.conf" (и проверь путь)

[uchenik]

вот мой конфиг

Код:

ifconfig_vr0="inet 192.168.0.102 netmask 255.255.255.0"
hostname="kommunar.local"
#local network
ifconfig_rl0="inet 10.0.0.1 netmask 255.255.255.0"
defaultrouter="192.168.0.2"
firewall_enable="YES"
fsck_y_enable="YES"
background_fsck="NO"
gateway_enable="YES"
mysql_enable="YES"
apache22_enable="YES"
pf_enable="YES"
pf_rules="/etc/pf.conf"
ipcad_enable="YES"
webmin_enable="YES"
nodeny_enable="YES"
nol2auth_enable="YES"
noserver_enable="YES"
dhcpd_enable="YES"                          # dhcpd enabled?
dhcpd_flags="-q"                            # command option(s)
#dhcpd_conf="/usr/local/nodeny/dhcpd.conf"   # configuration file
dhcpd_ifaces="rl0"                          # ethernet interface(s)
named_enable="YES"
nomake_enable="YES"

[uchenik]

Код:

[root@kommunar /home/elhan]# cat /etc/pf.conf
set limit states 128000
set optimization aggressive
nat pass on vr0 from 10.0.0.0/24 to any -> vr0

[ser970]

Код:

[root@kommunar /home/elhan]# cat /etc/pf.conf
set limit states 128000
set optimization aggressive
nat pass on vr0 from 10.0.0.0/24 to any -> vr0

какой днс на клиенте прописан?

несколько человек тоторые ко мне обращались пытались получить инет прописывая на клиента днс апи сервера
притом что там не настроен намед.

[uchenik]

Так на клиенте
днс 10.0.0.1

[ser970]

Так на клиенте
днс 10.0.0.1

и шлюз 10,0,0,1 - это сервер на котором стоит билинг правильно?
named поднят? думаю что нет.

пробуй так ping 8.8.8.8 
ответ должен быть
а так ping mail.ru  нет.

[uchenik]

Пинг от клиента есть

Код:

[root@kommunar /home/elhan]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=56 time=38.529 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=38.424 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=38.653 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=38.620 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=56 time=38.456 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=56 time=38.616 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=56 time=38.537 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=56 time=39.479 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=56 time=53.330 ms
^C
--- 8.8.8.8 ping statistics ---
9 packets transmitted, 9 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 38.424/40.294/53.330/4.619 ms
[root@kommunar /home/elhan]# ^C
[root@kommunar /home/elhan]# ping mail.ru
PING mail.ru (94.100.191.202): 56 data bytes
64 bytes from 94.100.191.202: icmp_seq=0 ttl=55 time=80.315 ms
64 bytes from 94.100.191.202: icmp_seq=1 ttl=55 time=78.655 ms
64 bytes from 94.100.191.202: icmp_seq=2 ttl=55 time=80.619 ms
64 bytes from 94.100.191.202: icmp_seq=3 ttl=55 time=80.629 ms
64 bytes from 94.100.191.202: icmp_seq=4 ttl=55 time=80.206 ms
64 bytes from 94.100.191.202: icmp_seq=5 ttl=55 time=80.384 ms
64 bytes from 94.100.191.202: icmp_seq=6 ttl=55 time=80.040 ms
^C
--- mail.ru ping statistics ---
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 78.655/80.121/80.629/0.630 ms

[ser970]

Пинг от клиента есть

Код:

[root@kommunar /home/elhan]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=56 time=38.529 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=38.424 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=38.653 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=38.620 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=56 time=38.456 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=56 time=38.616 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=56 time=38.537 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=56 time=39.479 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=56 time=53.330 ms
^C
--- 8.8.8.8 ping statistics ---
9 packets transmitted, 9 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 38.424/40.294/53.330/4.619 ms
[root@kommunar /home/elhan]# ^C
[root@kommunar /home/elhan]# ping mail.ru
PING mail.ru (94.100.191.202): 56 data bytes
64 bytes from 94.100.191.202: icmp_seq=0 ttl=55 time=80.315 ms
64 bytes from 94.100.191.202: icmp_seq=1 ttl=55 time=78.655 ms
64 bytes from 94.100.191.202: icmp_seq=2 ttl=55 time=80.619 ms
64 bytes from 94.100.191.202: icmp_seq=3 ttl=55 time=80.629 ms
64 bytes from 94.100.191.202: icmp_seq=4 ttl=55 time=80.206 ms
64 bytes from 94.100.191.202: icmp_seq=5 ttl=55 time=80.384 ms
64 bytes from 94.100.191.202: icmp_seq=6 ttl=55 time=80.040 ms
^C
--- mail.ru ping statistics ---
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 78.655/80.121/80.629/0.630 ms

от какого клиента?  я походу ослеп.

єто клиент 8.8.8.8
или єто mail.ru?
что ты называешь клиентом?

ето я так понял сервак root@kommunar ?

а где пинг с виндовса

с виндовса в режиме авторизации (ключик или впн или что там у тебя ) запусти  ping 193.193.193.100  и ping mail.ru

стукни в аську