Начало Вход/Регистрация Помощ Tazi stranica s latinski bukwi
Области
 Новини
 Актуална тема
 Linux портали
 Какво е Линукс?
 Въпроси-отговори
 Форуми
   •Трудова борса
   •Конкурс
 Статии
 Дистрибуции
   •Поръчка на CD
 Made In BG
 Файлове
 Връзки
 Галерия
 Конференции
Настройки
 Външен вид
 Предложения
 Направи си сам
И още ...
 За нас
 Линукс за българи ЕООД
 Линк към нас
 Предложения

Подкрепяно от:
TelePoint - Място за хора със свободни идеи

SiteGround

initLab

Adsys Group

SAP Bulgaria

Въпроси отговори
Въпрос: Problem s netacct-mysql-0.76
[Търси: ]

ВНИМАНИЕ: Използвайте форумите на сайта за дa зададете вашите въпроси.

Към началото |Добави въпрос |Отговори
 
Въпрос
От: meto Дата: 08/27/2004
Zdraveite!
 Instaliral sam netacct-mysql-0.76 i netstat-3.04 na
 Slackware 10 i vsichko tragna dobre s tazi razlika che v
 bazata pishe samo international traffic drugite razdeli sa
 prazni ..... slojil sam faila "nacctpeering" za BG peering-a
 i pak neshte da pishe v bazata za Bg Peering. Mashinata mi e
gateway kam ISP.
Moje li niakoi da mi kaje kade barkam
Blagodaria



Отговор #1
От: devane Дата: 08/27/2004
 veroiatno problema e na koi interfeis si go pusnal da slusha
 a shtato taka i mrejite koito si opisal v compactnet ..
toest moje predi tova na drug interfeis da pravish NAT


Отговор #2
От: meto Дата: 08/27/2004
prashtam ti conf-a
eth1 e ot vatreshnata mreja 192.168.0.0/24
eth0 e ot vanshnata 212.147.138.0/24

na mashinata varvi i MASQUERADE


database mysql			# must be mysql for now
				
mysql_user acct			# usually you don't need to change this

mysql_password acct	# change this to your password

 mysql_host localhost		# sometimes you need to change this
to
				# 127.0.0.1 instead of localhost

mysql_port 0			# mysql port, 0 if you are using a socket

 mysql_database netacct		# usually you don't need to change
this

pidfile  /var/run/nacctd.pid	# set pid file
				# tis will help if you want to
				# two (or more) nacctd on same machine

compactnet 192.168.0.0 255.255.255.0

 				# log traffic only for these networks 
				# all other packets are NOT logged
				
ournet 192.168.0.0 255.255.255.0
ournet 192.168.0.0 255.255.255.0

				# Ours IP nets for diferenciation of
				# peering traffic types

direct_peer 212.147.138.0 255.255.255.0

				# log traffic between 2 or more regional ISP-s

flush 30                       # flush every 5 minutes
				# this gives the interval in seconds
				# when the accumulated data is flushed
				# to the output file

fdelay 60			# this defines after how many seconds
				# of inactivity a certain record of
				# traffic information may be written out
				# this helps making the logfiles smaller
				# since only one output record will be
				# generated for related traffic

#notdev eth0			# Dont log entries for this device
                                 # Use this on routers that
you dont
                                 # log forwarded packets
twice.

 device eth1                     # device to put into
promiscous mode
				# you can specify as many as you want
				# and you don't have to specify one
				# (e.g. if this runs on your router)
				#
				# if you plan to use it on some *BSD
				# system put here apropriate device
				# i.e. - device ep0

# iflimit eth0			# on machines with multiple interfaces,
				# log only packets on this interface
				# mutually exclusive with hostlimit

 # ignoremask 255.255.255.0        # Ignore traffic on same
class C net
				# This means traffic that is on
				# your local LAN is not counted.
				# This is useful for NFS etc.
				# Not giving this option causes everything
				# to be counted.
				# This can degrade performance seriously!

ignorenet 127.0.0.0 255.0.0.0   # ignore loopback net
				# You can define as many ignorenets as
				# you want. Ignoring a net with
				# ignorenet is not as efficient as
				# ignoremask. Thus you should exclude
				# your local network with ignoremask,
				# not with ignorenet (although this is
				# is possible).

debug 1                         # set debugging level
debugfile /tmp/nacctd.debug	# where to put debugging info

# Device configuration
 # Defines where the real data starts for each type of
interface
 # First give the name prefix, then the offset in bytes to
the start
 # of the real data, then the offset of the type field in
bytes. If 
# there is no type field, just give a 0.
 # Don't specify SLIP or PPP devices here, otherwise
association of
# dynamic ip-addresses with usernames won't work
# Put device types with more traffic last.

headers	tr	40	38
headers	lo	14	12
headers	isdn	4	0
 # headers isdn	14	0	# for hdlc/trans/cisco and
hdlc/trans/raw
headers	eth	14	12
headers	plip	14	12

 # hostlimit 12.34.56.78		# log only packets to/from this
host
# hostlimit 34.56.78.12         # and this one too
				# this option is mutually exclusive with iflimit



Отговор #3
От: meto Дата: 08/27/2004
ednata ournet 192.168.0.0 255.255.255.0 
vsashtnost e ournet 192.168.1.0 255.255.255.0
pri copiraneto sam obarkal no ne e tova prichinata

a faila "nacctpeering" si e standartnia koito e s BG mrejite



Отговор #4
От: devane Дата: 08/30/2004
hm ami da ne bi userite da polzvat niakakvo proxy?
vsichko izglejda uj ok mnogo stranno


Отговор #5
От: nobody Дата: 08/31/2004
zdrasti ima edin file v /usr/local/etc nacctpeering
 dobavi si vutre celiq peering i sha ti zasicha i vunshniq
net i peeringa ako za tva stava duma :))



<< Трябва ми малко помощ за FreeBSD 4.10 (1 ) | не мога да разбера (1 ) >>

 
© 2011-... Асоциация "Линукс за българи"
© 2007-2010 Линукс за българи ЕООД
© 1999-2006 Slavej Karadjov
Ако искате да препечатате или цитирате информация от този сайт прочетете първо това
Външния вид е направен от MOMCHE
Code Version: 1.0.8 H (Revision: 23-09-2011)
 
Изпълнението отне: 0 wallclock secs ( 0.08 usr + 0.01 sys = 0.09 CPU)