discuss-pt-br September 2016

discuss-pt-br@lists.centos.org

13 participants
13 discussions

NTP!
by Glenio Cortes Himmen 29 Sep '16

29 Sep '16

Percebi que o servidor NTP está instalado e ativo no proxy (172.16.0.4), mas quando coloco o endereço no Windows para ele buscar no proxy, o windows me retorna a mensagem informando que o tempo expirou. Como faço para arrumar esta operação? Glênio Côrtes Himmen SMTA - Sup. Municipal de Trânsito de Aparecida glenio.11622x(a)aparecida.go.gov.br

1 0

Auto-Re: NTP!
by 江明 29 Sep '16

29 Sep '16

邮件收到

1 0

Re: [CentOS-pt-br] Digest CentOS-pt-br, volume 114, assunto 7
by Glenio Cortes Himmen 29 Sep '16

29 Sep '16

/etc/sarg/sarg.conf # sarg.conf # # TAG: access_log file # Where is the access.log file # sarg -l file # #access_log /usr/local/squid/var/logs/access.log access_log /var/log/squid/access.log # TAG: graphs yes|no # Use graphics where is possible. # graph_days_bytes_bar_color blue|green|yellow|orange|brown|red # graphs yes graph_days_bytes_bar_color orange # TAG: graph_font # The full path to the TTF font file to use to create the graphs. It is required # if graphs is set to yes. # graph_font /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf # TAG: title # Especify the title for html page. # title "Squid User Access Reports" # TAG: font_face # Especify the font for html page. # font_face Tahoma,Verdana,Arial # TAG: header_color # Especify the header color # header_color darkblue # TAG: header_bgcolor # Especify the header bgcolor # header_bgcolor blanchedalmond # TAG: font_size # Especify the text font size # font_size 12px # TAG: header_font_size # Especify the header font size # header_font_size 12px # TAG: title_font_size # Especify the title font size # title_font_size 11px # TAG: background_color # TAG: background_color # Html page background color # background_color white # TAG: text_color # Html page text color # text_color #000000 # TAG: text_bgcolor # Html page text background color # #text_bgcolor lavender # TAG: title_color # Html page title color # #title_color green # TAG: logo_image # Html page logo. # #logo_image none # TAG: logo_text # Html page logo text. # width height # #image_size 80 45 # TAG: background_image # Html page background image # #background_image none # TAG: password # User password file used by Squid authentication scheme # If used, generate reports just for that users. # #password none # TAG: temporary_dir # Temporary directory name for work files # sarg -w dir # #temporary_dir /tmp # TAG: output_dir # The reports will be saved in that directory # sarg -o dir # output_dir /var/www/html/squid-reports #output_dir /var/www/sarg/ONE-SHOT # TAG: output_email # Email address to send the reports. If you use this tag, no html reports will be generated. # sarg -e email # #output_email none # TAG: resolve_ip yes/no # Convert ip address to dns name # sarg -n #resolve_ip no resolve_ip yes # TAG: user_ip yes/no # Use Ip Address instead userid in reports. # sarg -p #user_ip no # TAG: topuser_sort_field field normal/reverse # Sort field for the Topuser Report. # Allowed fields: USER CONNECT BYTES TIME # #topuser_sort_field BYTES reverse # TAG: user_sort_field field normal/reverse # Sort field for the User Report. # Allowed fields: SITE CONNECT BYTES TIME # #user_sort_field BYTES reverse # TAG: exclude_users file # users within the file will be excluded from reports. # you can use indexonly to have only index.html file. # #exclude_users none # TAG: exclude_hosts file # Hosts, domains or subnets will be excluded from reports. # # Eg.: 192.168.10.10 - exclude ip address only # 192.168.10.0/24 - exclude full C class # s1.acme.foo - exclude hostname only # *.acme.foo - exclude full domain name # #exclude_hosts none # TAG: useragent_log file # useragent.log file patch to generate useragent report. # #useragent_log none # TAG: date_format # Date format in reports: e (European=dd/mm/yy), u (American=mm/dd/yy), w (Weekly=yy.ww) # date_format e # TAG: per_user_limit file MB # Saves userid on file if download exceed n MB. # This option allow you to disable user access if user exceed a download limit. # #per_user_limit none # TAG: lastlog n # How many reports files must be keept in reports directory. # The oldest report file will be automatically removed. # 0 - no limit. # #lastlog 0 # TAG: remove_temp_files yes # Remove temporary files: geral, usuarios, top, periodo from root report directory. # #remove_temp_files yes # TAG: index yes|no|only # Generate the main index.html. # only - generate only the main index.html # #index yes # TAG: index_tree date|file # How to generate the index. # #index_tree file # TAG: overwrite_report yes|no # yes - if report date already exist then will be overwrited. # no - if report date already exist then will be renamed to filename.n, filename.n+1 # #overwrite_report no # TAG: records_without_userid ignore|ip|everybody # What can I do with records without user id (no authentication) in access.log file ? # # ignore - This record will be ignored. # ip - Use ip address instead. (default) # everybody - Use "everybody" instead. # #records_without_userid ip # TAG: use_comma no|yes # Use comma instead point in reports. # Eg.: use_comma yes => 23,450,110 # use_comma no => 23.450.110 # #use_comma no # TAG: mail_utility # Mail command to use to send reports via SMTP. Sarg calls it like this: # mail_utility -s "SARG report, date" "output_email" <"mail_content" # # Therefore, it is possible to add more arguments to the command by specifying them # here. # # If you need too, you can use a shell script to process the content of /dev/stdin # (/dev/stdin is the mail_content passed by sarg to the script) and call whatever # command you like. It is not limited to mailing the report via SMTP. # # Don't forget to quote the command if necessary (i.e. if the path contains # characters that must be quoted). # #mail_utility mailx mail_utility mail # TAG: topsites_num n # How many sites in topsites report. # #topsites_num 100 # TAG: topsites_sort_order CONNECT|BYTES A|D # Sort for topsites report, where A=Ascendent, D=Descendent # #topsites_sort_order CONNECT D # TAG: index_sort_order A/D # Sort for index.html, where A=Ascendent, D=Descendent # #index_sort_order D # TAG: exclude_codes file # Ignore records with these codes. Eg.: NONE/400 # Write one code per line. Lines starting with a # are ignored. # Only codes matching exactly one of the line is rejected. The # comparison is not case sensitive. # #exclude_codes /usr/local/sarg/exclude_codes # TAG: replace_index string # Replace "index.html" in the main index file with this string # If null "index.html" is used # #replace_index <?php echo str_replace(".", "_", $REMOTE_ADDR); echo ".html"; ?> # TAG: max_elapsed milliseconds # If elapsed time is recorded in log is greater than max_elapsed use 0 for elapsed time. # Use 0 for no checking # #max_elapsed 28800000 # 8 Hours # TAG: report_type type # What kind of reports to generate. # topusers - users, sites, times, bytes, connects, links to accessed sites, etc # topsites - site, connect and bytes report # sites_users - users and sites report # users_sites - accessed sites by the user report # date_time - bytes used per day and hour report # denied - denied sites with full URL report # auth_failures - autentication failures report # site_user_time_date - sites, dates, times and bytes report # downloads - downloads per user report # # Eg.: report_type topsites denied # #report_type topusers topsites sites_users users_sites date_time denied auth_failures site_user_time_date downloads # TAG: usertab filename # You can change the "userid" or the "ip address" to be a real user name on the reports. # If resolve_ip is active, the ip address is resolved before being looked up into this # file. That is, if you want to map the ip address, be sure to set resolv_ip to no or # the resolved name will be looked into the file instead of the ip address. Note that # it can be used to resolve any ip address known to the dns and then map the unresolved # ip addresses to a name found in the usertab file. # Table syntax: # userid name or ip address name # Eg: # SirIsaac Isaac Newton # vinci Leonardo da Vinci # 192.168.10.1 Karol Wojtyla # # Each line must be terminated with '\n' # If usertab have value "ldap" (case ignoring), user names # will be taken from LDAP server. This method as approaches for reception # of usernames from Active Didectory # #usertab none # TAG: LDAPHost hostname # FQDN or IP address of host with LDAP service or AD DC # default is '127.0.0.1' #LDAPHost 127.0.0.1 # TAG: LDAPPort port # LDAP service port number # default is '389' #LDAPPort 389 # TAG: LDAPBindDN CN=username,OU=group,DC=mydomain,DC=com # DN of LDAP user, who is authorized to read user's names from LDAP base # default is empty line #LDAPBindDN cn=proxy,dc=mydomain,dc=local # TAG: LDAPBindPW secret # Password of DN, who is authorized to read user's names from LDAP base # default is empty line #LDAPBindPW secret # TAG: LDAPBaseSearch OU=users,DC=mydomain,DC=com # LDAP search base # default is empty line #LDAPBaseSearch ou=users,dc=mydomain,dc=local # TAG: LDAPFilterSearch (uid=%s) # User search filter by user's logins in LDAP # First founded record will be used # %s - will be changed to userlogins from access.log file # filter string can have up to 5 '%s' tags # default value is '(uid=%s)' #LDAPFilterSearch (uid=%s) # TAG: LDAPTargetAttr attributename # Name of the attribute containing a name of the user # default value is 'cn' #LDAPTargetAttr cn # TAG: long_url yes|no # If yes, the full url is showed in report. # If no, only the site will be showed # # YES option generate very big sort files and reports. # #long_url no # TAG: date_time_by bytes|elap # Date/Time reports show the downloaded volume or the elapsed time or both. # #date_time_by bytes # TAG: charset name # ISO 8859 is a full series of 10 standardized multilingual single-byte coded (8bit) # graphic character sets for writing in alphabetic languages # You can use the following charsets: # Latin1 - West European # Latin2 - East European # Latin3 - South European # Latin4 - North European # Cyrillic # Arabic # Greek # Hebrew # Latin5 - Turkish # Latin6 # Windows-1251 # Japan # Koi8-r # UTF-8 # charset Latin1 # TAG: user_invalid_char "&/" # Records that contain invalid characters in userid will be ignored by Sarg. # #user_invalid_char "&/" # TAG: privacy yes|no # privacy_string "***.***.***.***" # privacy_string_color blue # In some countries the sysadm cannot see the visited sites by a restrictive law. # Using privacy yes the visited url will be changes by privacy_string and the link # will be removed from reports. # #privacy no #privacy_string "***.***.***.***" #privacy_string_color blue # TAG: include_users "user1:user2:...:usern" # Reports will be generated only for listed users. # #include_users none # TAG: exclude_string "string1:string2:...:stringn" # Records from access.log file that contain one of listed strings will be ignored. # #exclude_string none # TAG: show_successful_message yes|no # Shows "Successful report generated on dir" at end of process. # #show_successful_message yes show_successful_message no # TAG: show_read_statistics yes|no # Shows some reading statistics. # #show_read_statistics yes # TAG: topuser_fields # Which fields must be in Topuser report. # #topuser_fields NUM DATE_TIME USERID CONNECT BYTES %BYTES IN-CACHE-OUT USED_TIME MILISEC %TIME TOTAL AVERAGE # TAG: user_report_fields # Which fields must be in User report. # #user_report_fields CONNECT BYTES %BYTES IN-CACHE-OUT USED_TIME MILISEC %TIME TOTAL AVERAGE # TAG: bytes_in_sites_users_report yes|no # Bytes field must be in Site & Users Report ? # #bytes_in_sites_users_report no # TAG: topuser_num n # How many users in topsites report. 0 = no limit # #topuser_num 0 # TAG: datafile file # Save the report results in a file to populate some database # #datafile none # TAG: datafile_delimiter ";" # ascii character to use as a field separator in datafile # #datafile_delimiter ";" # TAG: datafile_fields all # Which data fields must be in datafile # user;date;time;url;connect;bytes;in_cache;out_cache;elapsed # #datafile_fields user;date;time;url;connect;bytes;in_cache;out_cache;elapsed # TAG: datafile_url ip|name # Saves the URL as ip or name in datafile # #datafile_url ip # TAG: weekdays # The weekdays to take into account ( Sunday->0, Saturday->6 ) # Example: #weekdays 1-3,5 # Default: #weekdays 0-6 # TAG: hours # The hours to take into account # Example: #hours 7-12,14,16,18-20 # Default: #hours 0-23 # TAG: dansguardian_conf file # DansGuardian.conf file path # Generate reports from DansGuardian logs. # Use 'none' to disable it. # dansguardian_conf /usr/dansguardian/dansguardian.conf # #dansguardian_conf none # TAG: dansguardian_filter_out_date on|off # This option replaces dansguardian_ignore_date whose name was not appropriate with respect to its action. # Note the change of parameter value compared with the old option. # 'off' use the record even if its date is outside of the range found in the input log file. # 'on' use the record only if its date is in the range found in the input log file. # #dansguardian_filter_out_date on # TAG: squidguard_conf file # path to squidGuard.conf file # Generate reports from SquidGuard logs. # Use 'none' to disable. # You can use sarg -L filename to use an alternate squidGuard log. # squidguard_conf /usr/local/squidGuard/squidGuard.conf # #squidguard_conf none # TAG: redirector_log file # the location of the web proxy redirector log such as one created by squidGuard or Rejik. The option # may be repeated up to 64 times to read multiple files. # If this option is specified, it takes precedence over squidguard_conf. # The command line option -L override this option. # #redirector_log /usr/local/squidGuard/var/logs/urls.log # TAG: redirector_filter_out_date on|off # This option replaces squidguard_ignore_date and redirector_ignore_date whose names were not # appropriate with respect to their action. # Note the change of parameter value compared with the old options. # 'off' use the record even if its date is outside of the range found in the input log file. # 'on' use the record only if its date is in the range found in the input log file. # # #redirector_filter_out_date on # TAG: redirector_log_format # Format string for web proxy redirector logs. # This option was named squidguard_log_format before sarg 2.3. # REJIK #year#-#mon#-#day# #hour# #list#:#tmp# #ip# #user# #tmp#/#tmp#/#url#/#end# # SQUIDGUARD #year#-#mon#-#day# #hour# #tmp#/#list#/#tmp#/#tmp#/#url#/#tmp# #ip#/#tmp# #user# #end# #redirector_log_format #year#-#mon#-#day# #hour# #tmp#/#list#/#tmp#/#tmp#/#url#/#tmp# #ip#/#tmp# #user# #end# # TAG: show_sarg_info yes|no # shows sarg information and site path on each report bottom # #show_sarg_info yes # TAG: show_sarg_logo yes|no # shows sarg logo # #show_sarg_logo yes # TAG: parsed_output_log directory # Saves the processed log in a sarg format after parsing the squid log file. # This is a way to dump all of the data structures out, after parsing from # the logs (presumably this data will be much smaller than the log files themselves), # and pull them back in for later processing and merging with data from previous logs. # #parsed_output_log none # TAG: parsed_output_log_compress /bin/gzip|/usr/bin/bzip2|nocompress # Command to run to compress sarg parsed output log. It may contain # options (such as -f to overwrite existing target file). The name of # the file to compresse is provided at the end of this # command line. Don't forget to quote things appropriately. # #parsed_output_log_compress /bin/gzip # TAG: displayed_values bytes|abbreviation # how the values will be displayed in reports. # eg. bytes - 209.526 # abbreviation - 210K # #displayed_values bytes # Report limits # TAG: authfail_report_limit n # TAG: denied_report_limit n # TAG: siteusers_report_limit n # TAG: squidguard_report_limit n # TAG: user_report_limit n # TAG: dansguardian_report_limit n # TAG: download_report_limit n # report limits (lines). # '0' no limit # #authfail_report_limit 10 #denied_report_limit 10 #siteusers_report_limit 0 #squidguard_report_limit 10 #dansguardian_report_limit 10 #user_report_limit 10 #user_report_limit 50 # TAG: www_document_root dir # Where is your Web DocumentRoot # Sarg will create sarg-php directory with some PHP modules: # - sarg-squidguard-block.php - add urls from user reports to squidGuard DB # #www_document_root /var/www/html # TAG: block_it module_url # This tag allow you to pass urls from user reports to a cgi or php module, # to be blocked by some Squid acl # # Eg.: block_it /sarg-php/sarg-block-it.php # sarg-block-it is a php that will append a url to a flat file. # You must change /var/www/html/sarg-php/sarg-block-it to point to your file # in $filename variable, and chown to a httpd owner. # # sarg will pass http://module_url?url=url # #block_it none # TAG: external_css_file path # Provide the path to an external css file to link into the HTML reports instead of # the inline css written by sarg when this option is not set. # # In versions prior to 2.3, this used to be an absolute file name to # a file to include verbatim in each HTML page but, as it takes a lot of # space, version 2.3 switched to a link to an external css file. # Therefore, this option must contain the HTTP server path on which a client # browser may find the css file. # # Sarg use theses style classes: # .logo logo class # .info sarg information class, align=center # .title_c title class, align=center # .header_c header class, align:center # .header_l header class, align:left # .header_r header class, align:right # .text text class, align:right # .data table text class, align:right # .data2 table text class, align:left # .data3 table text class, align:center # .link link class # # Sarg can be instructed to output the internal css it inline # into the reports with this command: # # sarg --css # # You can redirect the output to a file of your choice and edit # it to your liking. # #external_css_file none external_css_file /var/www/sarg/sarg.css # TAG: user_authentication yes|no # Allow user authentication in User Reports using .htaccess # Parameters: # AuthUserTemplateFile - The template to use to create the # .htaccess file. In the template, %u is replaced by the # user's ID for which the report is generated. The path of the # template is relative to the directory containing sarg # configuration file. # # user_authentication no # AuthUserTemplateFile sarg_htaccess # TAG: download_suffix "suffix,suffix,...,suffix" # file suffix to be considered as "download" in Download report. # Use 'none' to disable. # download_suffix "zip,arj,bzip,gz,ace,doc,iso,adt,bin,cab,com,dot,drv$,lha,lzh,mdb,mso,ppt,rtf,src,shs,sys,exe,dll,mp3,avi,mpg,mpeg" # TAG: ulimit n # The maximum number of open file descriptors to avoid "Too many open files" error message. # You need to run sarg as root to use ulimit tag. # If you run sarg with a low privilege user, set to 'none' to disable ulimit # #ulimit 20000 # TAG: ntlm_user_format username|domainname+username # NTLM users format. # #ntlm_user_format domainname+username # TAG: realtime_refresh_time num sec # How many time to auto refresh the realtime report # 0 = disable # # realtime_refresh_time 3 # TAG: realtime_access_log_lines num # How many last lines to get from access.log file # # realtime_access_log_lines 1000 # TAG: realtime_types: GET,PUT,CONNECT,ICP_QUERY,POST # Which records must be in realtime report. # # realtime_types GET,PUT,CONNECT # TAG: realtime_unauthenticated_records: ignore|show # What to do with unauthenticated records in realtime report. # # realtime_unauthenticated_records: show # TAG: byte_cost value no_cost_limit # Cost per byte. # Eg. byte_cost 0.01 100000000 # per byte cost = 0.01 # bytes with no cost = 100 Mb # 0 = disable # # byte_cost 0.01 50000000 # TAG: squid24 on|off # Compatilibity with squid version <= 2.4 when using emulate_http_log on # # squid24 off /usr/local/etc/sarg.conf # sarg.conf # # TAG: access_log file # Where is the access.log file # sarg -l file # access_log /var/log/squid/access.log # TAG: graphs yes|no # Use graphics where is possible. # graph_days_bytes_bar_color blue|green|yellow|orange|brown|red # graphs yes graph_days_bytes_bar_color orange # TAG: graph_font # The full path to the TTF font file to use to create the graphs. It is required # if graphs is set to yes. # #graph_font /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf # TAG: title # Especify the title for html page. # #title "Squid User Access Reports" title "RELATORIOS DE ACESSO A INTERNET - SARG" # TAG: font_face # Especify the font for html page. # #font_face Tahoma,Verdana,Arial font_face Arial # TAG: header_color # Especify the header color # #header_color darkblue # TAG: header_bgcolor # Especify the header bgcolor # #header_bgcolor blanchedalmond # TAG: font_size font_size 12px # Especify the text font size # #font_size 9px # TAG: header_font_size # Especify the header font size # #header_font_size 9px # TAG: title_font_size # Especify the title font size # #title_font_size 11px # TAG: background_color # TAG: background_color # Html page background color # # background_color white # TAG: text_color # Html page text color # #text_color #000000 # TAG: text_bgcolor # Html page text background color # #text_bgcolor lavender # TAG: title_color # Html page title color # #title_color green # TAG: logo_image # Html page logo. # #logo_image none # TAG: logo_text # Html page logo text. # #logo_text "" # TAG: logo_text_color # Html page logo texti color. # #logo_text_color #000000 # TAG: logo_image_size # Html page logo image size. # width height # #image_size 80 45 # TAG: background_image # Html page background image # #background_image none # TAG: password # User password file used by Squid authentication scheme # If used, generate reports just for that users. # #password none password /var/www/html/squid-reports/.htpasswd # TAG: temporary_dir # Temporary directory name for work files # sarg -w dir # #temporary_dir /tmp # TAG: output_dir # The reports will be saved in that directory # sarg -o dir # output_dir /var/www/html/squid-reports # TAG: anonymous_output_files yes/no # Use anonymous file and directory names in the report. If it is set to # no (the default), the user id/ip/name is slightly mangled to create a # suitable file name to store the report of the user but the user's # identity can easily be guessed from the mangled name. If this option is # set, any file or directory belonging to the user is replaced by a short # number. The purpose is to hide the identity of the user when looking # at the report file names but it may serve to shorten the path too. # #anonymous_output_files no # TAG: output_email # Email address to send the reports. If you use this tag, no html reports will be generated. # sarg -e email # #output_email none # TAG: resolve_ip modulelist # List the modules to use to convert IP addresses into names. # Each named module is tried in sequence until one returns a result. Therefore # the order of the modules is relevant. # The modules must be listed on one line each separated from the previous one with # a space. # # The possible modules are # dns Use the DNS. # exec Call an external program with the IP address as argument. # # For compatibility with previous versions, yes is a synonymous for dns and # no does nothing. # sarg -n forces the use of the dns module. #resolve_ip no # TAG: resolve_ip_exec command # If resolve_ip selects the exec module, this is the command to run to # resolve an IP address. The command must contain a placeholder where the # IP address is inserted. The placeholder must be %IP in uppercases. The # placeholder may be repeated multiple times if necessary. # # The command is expected to return the host name without frills on its # standard output. If the command returns nothing, it is assumed that the # command could not resolve the IP address and the next module in the # chain is given a try with the same address. # # This option can only be used once. Therefore there is only one command # available to resolve an IP address but the program can do anything it # deems fit including attempting several strategies. # # Beware that running an external program is exceedingly slow. So you # should try the DNS first and only call an external program if the DNS # fails. #resolve_ip_exec nmblookup -A %IP | sed -n -e 's/^ *$.*$ *<00> - *B.*/\1/p' # TAG: user_ip yes/no # Use Ip Address instead userid in reports. # sarg -p #user_ip no # TAG: topuser_sort_field field normal/reverse # Sort field for the Topuser Report. # Allowed fields: USER CONNECT BYTES TIME # #topuser_sort_field BYTES reverse # TAG: user_sort_field field normal/reverse # Sort field for the User Report. # Allowed fields: SITE CONNECT BYTES TIME # #user_sort_field BYTES reverse # TAG: exclude_users file # users within the file will be excluded from reports. # you can use indexonly to have only index.html file. # #exclude_users none # TAG: exclude_hosts file # Hosts, domains or subnets will be excluded from reports. # # Eg.: 192.168.10.10 - exclude ip address only # 192.168.10.0/24 - exclude full C class # s1.acme.foo - exclude hostname only # *.acme.foo - exclude full domain name # #exclude_hosts none # TAG: useragent_log file # useragent.log file patch to generate useragent report. # #useragent_log none # TAG: date_format # Date format in reports: e (European=dd/mm/yy), u (American=mm/dd/yy), w (Weekly=yy.ww) # #date_format u # TAG: per_user_limit file MB # Saves userid on file if download exceed n MB. # This option allow you to disable user access if user exceed a download limit. # #per_user_limit none # TAG: lastlog n # How many reports files must be keept in reports directory. # The oldest report file will be automatically removed. # 0 - no limit. # #lastlog 0 # TAG: remove_temp_files yes # Remove temporary files: geral, usuarios, top, periodo from root report directory. # #remove_temp_files yes # TAG: index yes|no|only # Generate the main index.html. # only - generate only the main index.html # #index yes # TAG: index_tree date|file # How to generate the index. # #index_tree file # TAG: index_fields # The columns to show in the index of the reports # Columns are: dirsize # #index_fields dirsize # TAG: overwrite_report yes|no # yes - if report date already exist then will be overwrited. # no - if report date already exist then will be renamed to filename.n, filename.n+1 # #overwrite_report no # TAG: records_without_userid ignore|ip|everybody # What can I do with records without user id (no authentication) in access.log file ? # # ignore - This record will be ignored. # ip - Use ip address instead. (default) # everybody - Use "everybody" instead. # #records_without_userid ip # TAG: use_comma no|yes # Use comma instead point in reports. # Eg.: use_comma yes => 23,450,110 # use_comma no => 23.450.110 # #use_comma no # TAG: mail_utility # Mail command to use to send reports via SMTP. Sarg calls it like this: # mail_utility -s "SARG report, date" "output_email" <"mail_content" # # Therefore, it is possible to add more arguments to the command by specifying them # here. # # If you need too, you can use a shell script to process the content of /dev/stdin # (/dev/stdin is the mail_content passed by sarg to the script) and call whatever # command you like. It is not limited to mailing the report via SMTP. # # Don't forget to quote the command if necessary (i.e. if the path contains # characters that must be quoted). # #mail_utility mailx # TAG: topsites_num n # How many sites in topsites report. # #topsites_num 100 # TAG: topsites_sort_order CONNECT|BYTES|TIME|USER A|D # Sort for topsites report, where A=Ascendent, D=Descendent # #topsites_sort_order CONNECT D # TAG: index_sort_order A/D # Sort for index.html, where A=Ascendent, D=Descendent # #index_sort_order D # TAG: exclude_codes file # Ignore records with these codes. Eg.: NONE/400 # Write one code per line. Lines starting with a # are ignored. # Only codes matching exactly one of the line is rejected. The # comparison is not case sensitive. # #exclude_codes /usr/local/sarg/exclude_codes # TAG: replace_index string # Replace "index.html" in the main index file with this string # If null "index.html" is used # #replace_index <?php echo str_replace(".", "_", $REMOTE_ADDR); echo ".html"; ?> # TAG: max_elapsed milliseconds # If elapsed time is recorded in log is greater than max_elapsed use 0 for elapsed time. # Use 0 for no checking # #max_elapsed 28800000 # 8 Hours # TAG: report_type type # What kind of reports to generate. # topusers - users, sites, times, bytes, connects, links to accessed sites, etc # topsites - site, connect and bytes report # sites_users - users and sites report # users_sites - accessed sites by the user report # date_time - bytes used per day and hour report # denied - denied sites with full URL report # auth_failures - autentication failures report # site_user_time_date - sites, dates, times and bytes report # downloads - downloads per user report # # Eg.: report_type topsites denied # #report_type topusers topsites sites_users users_sites date_time denied auth_failures site_user_time_date downloads # TAG: usertab filename # You can change the "userid" or the "ip address" to be a real user name on the reports. # If resolve_ip is active, the ip address is resolved before being looked up into this # file. That is, if you want to map the ip address, be sure to set resolv_ip to no or # the resolved name will be looked into the file instead of the ip address. Note that # it can be used to resolve any ip address known to the dns and then map the unresolved # ip addresses to a name found in the usertab file. # Table syntax: # userid name or ip address name # Eg: # SirIsaac Isaac Newton # vinci Leonardo da Vinci # 192.168.10.1 Karol Wojtyla # # Each line must be terminated with '\n' # If usertab have value "ldap" (case ignoring), user names # will be taken from LDAP server. This method as approaches for reception # of usernames from Active Didectory # #usertab none # TAG: LDAPHost hostname # FQDN or IP address of host with LDAP service or AD DC # default is '127.0.0.1' #LDAPHost 127.0.0.1 # TAG: LDAPPort port # LDAP service port number # default is '389' #LDAPPort 389 # TAG: LDAPBindDN CN=username,OU=group,DC=mydomain,DC=com # DN of LDAP user, who is authorized to read user's names from LDAP base # default is empty line #LDAPBindDN cn=proxy,dc=mydomain,dc=local # TAG: LDAPBindPW secret # Password of DN, who is authorized to read user's names from LDAP base # default is empty line #LDAPBindPW secret # TAG: LDAPBaseSearch OU=users,DC=mydomain,DC=com # LDAP search base # default is empty line #LDAPBaseSearch ou=users,dc=mydomain,dc=local # TAG: LDAPFilterSearch (uid=%s) # User search filter by user's logins in LDAP # First founded record will be used # %s - will be changed to userlogins from access.log file # filter string can have up to 5 '%s' tags # default value is '(uid=%s)' #LDAPFilterSearch (uid=%s) # TAG: LDAPTargetAttr attributename # Name of the attribute containing a name of the user # default value is 'cn' #LDAPTargetAttr cn # TAG: long_url yes|no # If yes, the full url is showed in report. # If no, only the site will be showed # # YES option generate very big sort files and reports. # #long_url no # TAG: date_time_by bytes|elap # Date/Time reports show the downloaded volume or the elapsed time or both. # #date_time_by bytes # TAG: charset name # ISO 8859 is a full series of 10 standardized multilingual single-byte coded (8bit) # graphic character sets for writing in alphabetic languages # You can use the following charsets: # Latin1 - West European # Latin2 - East European # Latin3 - South European # Latin4 - North European # Cyrillic # Arabic # Greek # Hebrew # Latin5 - Turkish # Latin6 # Windows-1251 # Japan # Koi8-r # UTF-8 # #charset Latin1 # TAG: user_invalid_char "&/" # Records that contain invalid characters in userid will be ignored by Sarg. # #user_invalid_char "&/" # TAG: privacy yes|no # privacy_string "***.***.***.***" # privacy_string_color blue # In some countries the sysadm cannot see the visited sites by a restrictive law. # Using privacy yes the visited url will be changes by privacy_string and the link # will be removed from reports. # #privacy no #privacy_string "***.***.***.***" #privacy_string_color blue # TAG: include_users "user1:user2:...:usern" # Reports will be generated only for listed users. # #include_users none # TAG: exclude_string "string1:string2:...:stringn" # Records from access.log file that contain one of listed strings will be ignored. # #exclude_string none # TAG: show_successful_message yes|no # Shows "Successful report generated on dir" at end of process. # #show_successful_message yes # TAG: show_read_statistics yes|no # Shows some reading statistics. # #show_read_statistics yes # TAG: topuser_fields # Which fields must be in Topuser report. # #topuser_fields NUM DATE_TIME USERID CONNECT BYTES %BYTES IN-CACHE-OUT USED_TIME MILISEC %TIME TOTAL AVERAGE # TAG: user_report_fields # Which fields must be in User report. # #user_report_fields CONNECT BYTES %BYTES IN-CACHE-OUT USED_TIME MILISEC %TIME TOTAL AVERAGE # TAG: bytes_in_sites_users_report yes|no # Bytes field must be in Site & Users Report ? # #bytes_in_sites_users_report no # TAG: topuser_num n # How many users in topsites report. 0 = no limit # #topuser_num 0 # TAG: datafile file # Save the report results in a file to populate some database # #datafile none # TAG: datafile_delimiter ";" # ascii character to use as a field separator in datafile # #datafile_delimiter ";" # TAG: datafile_fields all # Which data fields must be in datafile # user;date;time;url;connect;bytes;in_cache;out_cache;elapsed # #datafile_fields user;date;time;url;connect;bytes;in_cache;out_cache;elapsed # TAG: datafile_url ip|name # Saves the URL as ip or name in datafile # #datafile_url ip # TAG: weekdays # The weekdays to take into account ( Sunday->0, Saturday->6 ) # Example: #weekdays 1-3,5 # Default: #weekdays 0-6 # TAG: hours # The hours to take into account # Example: #hours 7-12,14,16,18-20 # Default: #hours 0-23 # TAG: dansguardian_conf file # DansGuardian.conf file path # Generate reports from DansGuardian logs. # Use 'none' to disable it. # dansguardian_conf /usr/dansguardian/dansguardian.conf # #dansguardian_conf none # TAG: dansguardian_filter_out_date on|off # This option replaces dansguardian_ignore_date whose name was not appropriate with respect to its action. # Note the change of parameter value compared with the old option. # 'off' use the record even if its date is outside of the range found in the input log file. # 'on' use the record only if its date is in the range found in the input log file. # #dansguardian_filter_out_date on # TAG: squidguard_conf file # path to squidGuard.conf file # Generate reports from SquidGuard logs. # Use 'none' to disable. # You can use sarg -L filename to use an alternate squidGuard log. # squidguard_conf /usr/local/squidGuard/squidGuard.conf # #squidguard_conf none # TAG: redirector_log file # the location of the web proxy redirector log such as one created by squidGuard or Rejik. The option # may be repeated up to 64 times to read multiple files. # If this option is specified, it takes precedence over squidguard_conf. # The command line option -L override this option. # #redirector_log /usr/local/squidGuard/var/logs/urls.log # TAG: redirector_filter_out_date on|off # This option replaces squidguard_ignore_date and redirector_ignore_date whose names were not # appropriate with respect to their action. # Note the change of parameter value compared with the old options. # 'off' use the record even if its date is outside of the range found in the input log file. # 'on' use the record only if its date is in the range found in the input log file. # #redirector_filter_out_date on # TAG: redirector_log_format # Format string for web proxy redirector logs. # This option was named squidguard_log_format before sarg 2.3. # REJIK #year#-#mon#-#day# #hour# #list#:#tmp# #ip# #user# #tmp#/#tmp#/#url#/#end# # SQUIDGUARD #year#-#mon#-#day# #hour# #tmp#/#list#/#tmp# #url# #ip#/#tmp# #user# #end# #redirector_log_format #year#-#mon#-#day# #hour# #tmp#/#list#/#tmp# #url# #ip#/#tmp# #user# #end# # TAG: show_sarg_info yes|no # shows sarg information and site path on each report bottom # #show_sarg_info yes # TAG: show_sarg_logo yes|no # shows sarg logo # #show_sarg_logo yes # TAG: parsed_output_log directory # Saves the processed log in a sarg format after parsing the squid log file. # This is a way to dump all of the data structures out, after parsing from # the logs (presumably this data will be much smaller than the log files themselves), # and pull them back in for later processing and merging with data from previous logs. # #parsed_output_log none # TAG: parsed_output_log_compress /bin/gzip|/usr/bin/bzip2|nocompress # Command to run to compress sarg parsed output log. It may contain # options (such as -f to overwrite existing target file). The name of # the file to compresse is provided at the end of this # command line. Don't forget to quote things appropriately. # #parsed_output_log_compress /bin/gzip # TAG: displayed_values bytes|abbreviation # how the values will be displayed in reports. # eg. bytes - 209.526 # abbreviation - 210K # #displayed_values bytes # Report limits # TAG: authfail_report_limit n # TAG: denied_report_limit n # TAG: siteusers_report_limit n # TAG: squidguard_report_limit n # TAG: user_report_limit n # TAG: dansguardian_report_limit n # TAG: download_report_limit n # report limits (lines). # '0' no limit # #authfail_report_limit 10 #denied_report_limit 10 #siteusers_report_limit 0 #squidguard_report_limit 10 #dansguardian_report_limit 10 #user_report_limit 10 #user_report_limit 50 # TAG: www_document_root dir # Where is your Web DocumentRoot # Sarg will create sarg-php directory with some PHP modules: # - sarg-squidguard-block.php - add urls from user reports to squidGuard DB # #www_document_root /var/www/html # TAG: block_it module_url # This tag allow you to pass urls from user reports to a cgi or php module, # to be blocked by some Squid acl # # Eg.: block_it /sarg-php/sarg-block-it.php # sarg-block-it is a php that will append a url to a flat file. # You must change /var/www/html/sarg-php/sarg-block-it to point to your file # in $filename variable, and chown to a httpd owner. # # sarg will pass http://module_url?url=url # #block_it none # TAG: external_css_file path # Provide the path to an external css file to link into the HTML reports instead of # the inline css written by sarg when this option is not set. # # In versions prior to 2.3, this used to be an absolute file name to # a file to include verbatim in each HTML page but, as it takes a lot of # space, version 2.3 switched to a link to an external css file. # Therefore, this option must contain the HTTP server path on which a client # browser may find the css file. # # Sarg use theses style classes: # .logo logo class # .info sarg information class, align=center # .title_c title class, align=center # .header_c header class, align:center # .header_l header class, align:left # .header_r header class, align:right # .text text class, align:right # .data table text class, align:right # .data2 table text class, align:left # .data3 table text class, align:center # .link link class # # Sarg can be instructed to output the internal css it inline # into the reports with this command: # # sarg --css # # You can redirect the output to a file of your choice and edit # it to your liking. # # #external_css_file none # TAG: user_authentication yes|no # Allow user authentication in User Reports using .htaccess # Parameters: # AuthUserTemplateFile - The template to use to create the # .htaccess file. In the template, %u is replaced by the # user's ID for which the report is generated. The path of the # template is relative to the directory containing sarg # configuration file. # # user_authentication no # AuthUserTemplateFile sarg_htaccess # TAG: download_suffix "suffix,suffix,...,suffix" # file suffix to be considered as "download" in Download report. # Use 'none' to disable. # #download_suffix "zip,arj,bzip,gz,ace,doc,iso,adt,bin,cab,com,dot,drv$,lha,lzh,mdb,mso,ppt,rtf,src,shs,sys,exe,dll,mp3,avi,mpg,mpeg" # TAG: ulimit n # The maximum number of open file descriptors to avoid "Too many open files" error message. # You need to run sarg as root to use ulimit tag. # If you run sarg with a low privilege user, set to 'none' to disable ulimit # #ulimit 20000 # TAG: ntlm_user_format user|domainname+username # NTLM users format. # #ntlm_user_format domainname+username # TAG: realtime_refresh_time num sec # How many time to auto refresh the realtime report # 0 = disable # # realtime_refresh_time 3 # TAG: realtime_access_log_lines num # How many last lines to get from access.log file # # realtime_access_log_lines 1000 # TAG: realtime_types: GET,PUT,CONNECT,ICP_QUERY,POST # Which records must be in realtime report. # # realtime_types GET,PUT,CONNECT # TAG: realtime_unauthenticated_records: ignore|show # What to do with unauthenticated records in realtime report. # # realtime_unauthenticated_records: show # TAG: byte_cost value no_cost_limit # Cost per byte. # Eg. byte_cost 0.01 100000000 # per byte cost = 0.01 # bytes with no cost = 100 Mb # 0 = disable # # byte_cost 0.01 50000000 # TAG: squid24 on|off # Compatilibity with squid version <= 2.4 when using emulate_http_log on # # squid24 off # TAG: sorttable path # The path to a javascript script to dynamically sort the tables. # The path is the link a browser must follow to find the script. For instance, # it may be http://www.myproxy.org/sorttable.js or just /sorttable.js if the script # is at the root of your web site. # # If the path starts with "../" then it is assumed to be a relative # path and sarg adds as many "../" as necessary to locate the js script from # the output directory. Therefore, ../../sorttable.js links to the javascript # one level above output_dir. # # If this entry is set, each sortable table will have the "sortable" class set. # You may have a look at http://www.kryogenix.org/code/browser/sorttable/ # for the implementation on which sarg is based. # # sorttable /sorttable.js # TAG: hostalias # The name of a text file containing the host names one per line and the # optional alias to use in the report instead of that host name. # Host names may contain up to one wildcard denoted by a *. The wildcard # must not end the host name. # The host name may be followed by an optional alias but if no alias is # provided, the host name, including the wildcard, replaces any matching # host name found in the log. # Host names replaced by identical aliases are grouped together in the # reports. # IP addresses are supported and accept the CIDR notation both for IPv4 and # IPv6 addresses. # Regular expressions can also be used if sarg was compiled with libpcre. # A regular expression is formated as re:/regexp/ alias # The regexp is a perl regular expression (see man perlre). # Subpatterns are allowed in the alias. Sarg recognizes sed (\1) or perl ($1) # subpatterns. Only 9 subpatterns are allowed in the replacement string. # # Example: # *.gstatic.com # mt*.google.com # *.myphone.microsoft.com # *.myphone.microsoft.com:443 *.myphone.microsoft.com:secure # *.freeav.net antivirus:freeav # *.mail.live.com # 65.52.00.00/14 *.mail.live.com # re:/\.dropbox\.com(:443)?/ dropbox # re:/([\w-]+)\.(\w*[a-zA-Z]\w*)(?::\d+)?$/\1.\2 #hostalias /usr/local/sarg/hostalias # TAG: keep_temp_log yes|no # Keep temporary files created by sarg to produce its reports. The normal # operation mode is to delete those files when they are not necessary any more. # # Never leave that option to "yes" for normal operation as temporary files # left over by previous run can be included in subsequent reports. # # Use this option only to diagnose a problem with your reports. A better # alternative is to run sarg from the command line with optino -k. #keep_temp_log no [root@proxy ~]# sarg SARG: Registros no arquivo: 200787, lendo: 100,00% SARG: Nenhum registro encontrado SARG: Fim [root@proxy ~]# time real 0m0.000s user 0m0.000s sys 0m0.000s [root@proxy ~]# date Qui Set 29 09:34:40 BRT 2016 [root@proxy ~]# vim /etc/sarg/sarg.conf [root@proxy ~]# cd / [root@proxy /]# find . -name sarg.conf -print ./usr/local/etc/sarg.conf ./etc/sarg/sarg.conf [root@proxy /]# vim /usr/local/etc/sarg.conf De: centos-pt-br-request(a)centos.org Para: centos-pt-br(a)centos.org Enviadas: Quinta-feira, 29 de setembro de 2016 9:00:01 Assunto: Digest CentOS-pt-br, volume 114, assunto 7 Enviar submissões para a lista de discussão CentOS-pt-br para centos-pt-br(a)centos.org Para se cadastrar ou descadastrar via WWW, visite o endereço https://lists.centos.org/mailman/listinfo/centos-pt-br ou, via email, envie uma mensagem com a palavra 'help' no assunto ou corpo da mensagem para centos-pt-br-request(a)centos.org Você poderá entrar em contato com a pessoa que gerencia a lista pelo endereço centos-pt-br-owner(a)centos.org Quando responder, por favor edite sua linha Assunto assim ela será mais específica que "Re: Contents of CentOS-pt-br digest..." Tópicos de Hoje: 1. Sarg! (Glenio Cortes Himmen) 2. Auto-Re: Sarg! (=?GBK?B?va3D9w==?=) 3. Re: Sarg! (Vitor Lobo) ---------------------------------------------------------------------- Message: 1 Date: Wed, 28 Sep 2016 15:15:28 -0300 (BRT) From: Glenio Cortes Himmen <glenio.11622x(a)aparecida.go.gov.br> To: centos-pt-br(a)centos.org Subject: [CentOS-pt-br] Sarg! Message-ID: <536860194.486985.1475086528075.JavaMail.zimbra(a)aparecida.go.gov.br> Content-Type: text/plain; charset="utf-8" Senhores, Estou tendo problemas com o Sarg. Ele não está lendo os novos registros. Abaixo as mensagens. SARG: Registros no arquivo: 181872, lendo: 100,00% SARG: Nenhum registro encontrado SARG: Fim SARG: Registros no arquivo: 181383, lendo: 100,00% SARG: Nenhum registro encontrado SARG: Fim ARQUIVO/PERÍODO DATA DE CRIAÇÃO USUÁRIOS BYTES MÉDIA 2016Sep19-2016Sep22 Qui 22 Set 2016 13:38:38 BRT 1 351.57M 351.57M 2016Sep18-2016Sep22 Qui 22 Set 2016 10:06:54 BRT 28 4.43G 158.30M 2015Mar23-2015Mar27 Sex 27 Mar 2015 10:49:56 BRT 52 13.89G 267.25M 2015Mar08-2015Mar10 Ter 10 Mar 2015 16:34:32 BRT 47 3.90G 83.14M 2015Mar01-2015Mar05 Qui 05 Mar 2015 10:28:29 BRT 57 5.53G 97.05M 2015Feb23-2015Feb27 Sex 27 Fev 2015 08:41:04 BRT 62 5.11G 82.57M 2015Feb23-2015Feb26 Qui 26 Fev 2015 09:18:22 BRT 55 3.21G 58.42M 2015Feb23-2015Feb23 Seg 23 Fev 2015 17:08:32 BRT 49 1.78G 36.42M 2015Feb15-2015Feb20 Sex 20 Fev 2015 16:37:56 BRST 47 6.18G 131.69M 23Mar2015-27Mar2015 Sex 27 Mar 2015 10:49:08 BRT 52 13.87G 266.85M Como vocês podem ver, a leitura feita em dois horários diferentes mostra que o arquivo contem mais dados, mas na hora de gerar o relatório, ele fala que não tem novidades. Alguma dica? CentOS release 6.8 (Final) Gerado por sarg-2.3.8 Feb-07-2014 em Set/22/2016 13:38 Glênio Côrtes Himmen SMTA - Sup. Municipal de Trânsito de Aparecida glenio.11622x(a)aparecida.go.gov.br -------------- Próxima Parte ---------- Um anexo em HTML foi limpo... URL: <http://lists.centos.org/pipermail/centos-pt-br/attachments/20160928/aff83cc…> ------------------------------ Message: 2 Date: Thu, 29 Sep 2016 02:11:14 +0800 From: "=?GBK?B?va3D9w==?=" <kjjm(a)ahpu.edu.cn> To: centos-pt-br(a)centos.org Subject: [CentOS-pt-br] Auto-Re: Sarg! Message-ID: <1609290211145e0d7e2a6e07b47bb0904b829ab9eeab(a)ahpu.edu.cn> Content-Type: text/plain; charset="GBK" ???? ------------------------------ Message: 3 Date: Thu, 29 Sep 2016 07:39:04 -0300 From: Vitor Lobo <lobocode(a)gmail.com> To: "Portuguese (Brazilian) CentOS mailing list" <centos-pt-br(a)centos.org> Subject: Re: [CentOS-pt-br] Sarg! Message-ID: <CAOcJv=kFxzCdAcPY+P1D3R=TL7r7nsv3p9wgBXZ+Hk6_aWYFag(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Glenio, bom dia. Precisamos visualizar os arquivos de configuração do Sarg para lhe auxiliar. Neste caso, se puder, posta no pastebim privado (abre conta la). Visualiza também sem o timestamp da máquina host está correto. Att, Em 28 de setembro de 2016 15:15, Glenio Cortes Himmen < glenio.11622x(a)aparecida.go.gov.br> escreveu: > Senhores, > > Estou tendo problemas com o Sarg. > > Ele não está lendo os novos registros. > > Abaixo as mensagens. > > SARG: Registros no arquivo: 181872, lendo: 100,00% > SARG: Nenhum registro encontrado > SARG: Fim > > SARG: Registros no arquivo: 181383, lendo: 100,00% > SARG: Nenhum registro encontrado > SARG: Fim > > ARQUIVO/PERÍODO DATA DE CRIAÇÃO USUÁRIOS BYTES MÉDIA > 2016Sep19-2016Sep22 Qui 22 Set 2016 13:38:38 BRT 1 351.57M > 351.57M > 2016Sep18-2016Sep22 Qui 22 Set 2016 10:06:54 BRT 28 4.43G > 158.30M > 2015Mar23-2015Mar27 Sex 27 Mar 2015 10:49:56 BRT 52 13.89G > 267.25M > 2015Mar08-2015Mar10 Ter 10 Mar 2015 16:34:32 BRT 47 3.90G > 83.14M > 2015Mar01-2015Mar05 Qui 05 Mar 2015 10:28:29 BRT 57 5.53G > 97.05M > 2015Feb23-2015Feb27 Sex 27 Fev 2015 08:41:04 BRT 62 5.11G > 82.57M > 2015Feb23-2015Feb26 Qui 26 Fev 2015 09:18:22 BRT 55 3.21G > 58.42M > 2015Feb23-2015Feb23 Seg 23 Fev 2015 17:08:32 BRT 49 1.78G > 36.42M > 2015Feb15-2015Feb20 Sex 20 Fev 2015 16:37:56 BRST 47 6.18G > 131.69M > 23Mar2015-27Mar2015 Sex 27 Mar 2015 10:49:08 BRT 52 13.87G > 266.85M > > Como vocês podem ver, a leitura feita em dois horários diferentes mostra > que o arquivo contem mais dados, mas na hora de gerar o relatório, ele fala > que não tem novidades. > > Alguma dica? > > CentOS release 6.8 (Final) > Gerado por sarg-2.3.8 Feb-07-2014 <http://sarg.sourceforge.net> em > Set/22/2016 13:38 > > Glênio Côrtes Himmen > SMTA - Sup. Municipal de Trânsito de Aparecida > glenio.11622x(a)aparecida.go.gov.br > > _______________________________________________ > CentOS-pt-br mailing list > CentOS-pt-br(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-pt-br > > -- *Vitor Lobo* Analista de Sistemas Jr. LEMAF - Laboratório de Estudos e Projetos em Manejo Florestal Campus UFLA - Cp: 3060 Lavras - MG Cep - 37200-000 (35) 99236-7502 -------------- Próxima Parte ---------- Um anexo em HTML foi limpo... URL: <http://lists.centos.org/pipermail/centos-pt-br/attachments/20160929/20cfd69…> ------------------------------ _______________________________________________ CentOS-pt-br mailing list CentOS-pt-br(a)centos.org https://lists.centos.org/mailman/listinfo/centos-pt-br Fim da Digest CentOS-pt-br, volume 114, assunto 7 *************************************************

1 0

Sarg!
by Glenio Cortes Himmen 29 Sep '16

29 Sep '16

Senhores, Estou tendo problemas com o Sarg. Ele não está lendo os novos registros. Abaixo as mensagens. SARG: Registros no arquivo: 181872, lendo: 100,00% SARG: Nenhum registro encontrado SARG: Fim SARG: Registros no arquivo: 181383, lendo: 100,00% SARG: Nenhum registro encontrado SARG: Fim ARQUIVO/PERÍODO DATA DE CRIAÇÃO USUÁRIOS BYTES MÉDIA 2016Sep19-2016Sep22 Qui 22 Set 2016 13:38:38 BRT 1 351.57M 351.57M 2016Sep18-2016Sep22 Qui 22 Set 2016 10:06:54 BRT 28 4.43G 158.30M 2015Mar23-2015Mar27 Sex 27 Mar 2015 10:49:56 BRT 52 13.89G 267.25M 2015Mar08-2015Mar10 Ter 10 Mar 2015 16:34:32 BRT 47 3.90G 83.14M 2015Mar01-2015Mar05 Qui 05 Mar 2015 10:28:29 BRT 57 5.53G 97.05M 2015Feb23-2015Feb27 Sex 27 Fev 2015 08:41:04 BRT 62 5.11G 82.57M 2015Feb23-2015Feb26 Qui 26 Fev 2015 09:18:22 BRT 55 3.21G 58.42M 2015Feb23-2015Feb23 Seg 23 Fev 2015 17:08:32 BRT 49 1.78G 36.42M 2015Feb15-2015Feb20 Sex 20 Fev 2015 16:37:56 BRST 47 6.18G 131.69M 23Mar2015-27Mar2015 Sex 27 Mar 2015 10:49:08 BRT 52 13.87G 266.85M Como vocês podem ver, a leitura feita em dois horários diferentes mostra que o arquivo contem mais dados, mas na hora de gerar o relatório, ele fala que não tem novidades. Alguma dica? CentOS release 6.8 (Final) Gerado por sarg-2.3.8 Feb-07-2014 em Set/22/2016 13:38 Glênio Côrtes Himmen SMTA - Sup. Municipal de Trânsito de Aparecida glenio.11622x(a)aparecida.go.gov.br

2 1

Auto-Re: Sarg!
by 江明 28 Sep '16

28 Sep '16

邮件收到

1 0

Algum cliente para OneDrive no Centos 7?
by Wiliam Freitas 23 Sep '16

23 Sep '16

Alguém conhece/recomenda um cliente para OneDrive no Centos 7? Pessoal da facul usa essa ferramenta pra compartilhar arquivos. Sou o único em 40 pessoas que usa Linux. []'s -- Wiliam Freitas .twitter: @wili4m .mail: wiliamjf(a)yahoo.com.br .blog: http://blogporta80.com.br

3 2

Re: [CentOS-pt-br] Digest CentOS-pt-br, volume 114, assunto 5
by Mored Berdat 23 Sep '16

23 Sep '16

Bom dia. Tente isso, pesquisei pelo google. https://www.storagemadeeasy.com/LinuxDrive/ Mored. On 09/23/2016 09:00 AM, centos-pt-br-request(a)centos.org wrote: > Enviar submissões para a lista de discussão CentOS-pt-br para > centos-pt-br(a)centos.org > > Para se cadastrar ou descadastrar via WWW, visite o endereço > https://lists.centos.org/mailman/listinfo/centos-pt-br > ou, via email, envie uma mensagem com a palavra 'help' no assunto ou > corpo da mensagem para > centos-pt-br-request(a)centos.org > > Você poderá entrar em contato com a pessoa que gerencia a lista pelo > endereço > centos-pt-br-owner(a)centos.org > > Quando responder, por favor edite sua linha Assunto assim ela será > mais específica que "Re: Contents of CentOS-pt-br digest..." > > > Tópicos de Hoje: > > 1. Algum cliente para OneDrive no Centos 7? (Wiliam Freitas) > 2. Re: Algum cliente para OneDrive no Centos 7? (Cássio Elias) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 22 Sep 2016 17:41:52 +0000 (UTC) > From: Wiliam Freitas <wiliamjf(a)yahoo.com.br> > To: "centos-pt-br(a)centos.org" <centos-pt-br(a)centos.org> > Subject: [CentOS-pt-br] Algum cliente para OneDrive no Centos 7? > Message-ID: <1398236043.3147161.1474566112828(a)mail.yahoo.com> > Content-Type: text/plain; charset="utf-8" > > Alguém conhece/recomenda um cliente para OneDrive no Centos 7? > Pessoal da facul usa essa ferramenta pra compartilhar arquivos. > Sou o único em 40 pessoas que usa Linux. > []'s -- Wiliam Freitas .twitter: @wili4m .mail: wiliamjf(a)yahoo.com.br .blog: http://blogporta80.com.br > -------------- Próxima Parte ---------- > Um anexo em HTML foi limpo... > URL: <http://lists.centos.org/pipermail/centos-pt-br/attachments/20160922/d32ec21…> > > ------------------------------ > > Message: 2 > Date: Thu, 22 Sep 2016 15:09:37 -0300 > From: Cássio Elias <cassioelias(a)corples.com.br> > To: centos-pt-br(a)centos.org > Subject: Re: [CentOS-pt-br] Algum cliente para OneDrive no Centos 7? > Message-ID: <2b536a1d-6068-d054-d908-958cedff9d39(a)corples.com.br> > Content-Type: text/plain; charset="windows-1252"; Format="flowed" > > Sinceramente eu acho muito difícil existir algo do tipo.. > > Alguém com mais tempo do que eu pode ajudar, mas o Wine não funcionaria > para rodar o cliente Windows não? > > Att, > > Cássio Elias. > > > Em 22/09/2016 14:41, Wiliam Freitas escreveu: >> Alguém conhece/recomenda um cliente para OneDrive no Centos 7? >> >> Pessoal da facul usa essa ferramenta pra compartilhar arquivos. >> >> Sou o único em 40 pessoas que usa Linux. >> >> []'s >> -- Wiliam Freitas .twitter: @wili4m .mail: wiliamjf(a)yahoo.com.br >> .blog: http://blogporta80.com.br >> >> >> _______________________________________________ >> CentOS-pt-br mailing list >> CentOS-pt-br(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos-pt-br -- Grato. Mored Berdat SANCRED Sist. Nac. de Recup. de Cred. Ltda. Telefone: (19) 3512-0200 sancred.com.br Aviso: Esta mensagem é destinada exclusivamente para a(s) pessoa(s) a quem é dirigida, podendo conter informação confidencial e legalmente protegida. Se você não for destinatário desta mensagem, desde já fica notificado de abster-se a divulgar, copiar, distribuir, examinar ou, de qualquer forma, utilizar a informação contida nesta mensagem, por ser ilegal. Caso você tenha recebido esta mensagem por engano, pedimos que responda essa mensagem informando o acontecido.

1 0

Codigo fonte de aplicativos
by Rodrigo Cunha 20 Sep '16

20 Sep '16

srs, no debian via apt-get é possivel obter o código fonte de uma aplicação apartir dos repositórios, é possivel fazer isso no Centos com o yum? -- Atenciosamente, Rodrigo da Silva Cunha

2 2

Auto-Re: Codigo fonte de aplicativos
by 江明 20 Sep '16

20 Sep '16

邮件收到

1 0

Re: [CentOS-pt-br] Digest CentOS-pt-br, volume 114, assunto 2
by Glenio Cortes Himmen 08 Sep '16

08 Sep '16

Coloquei a regra conforme abaixo e estou recebendo as mensagens de erro logo a seguir. #### Regras para liberar o programa SPI ### inicio... $IPT -t filter -I FORWARD -d 177.135.260.61 -p tcp -m multiport --dport 3051,5836,5837,725 -j ACCEPT $IPT -t filter -I FORWARD -d 177.135.260.61 -p udp -m multiport --dport 3051,5836,5837,725 -j ACCEPT #### Regras para liberar o programa SPI ### final... [root@proxy ~]# /etc/rc.d/init.d/firewall.sh INICIANDO FIREWALL ...................[OK] LIMPANDO AS REGRAS ...................[OK] APLICADO REGRAS PADRÕES ..............[OK] APLICANDO REGRAS MANUAIS .............[OK] iptables v1.4.7: host/network `177.135.260.61' not found Try `iptables -h' or 'iptables --help' for more information. iptables v1.4.7: host/network `177.135.260.61' not found Try `iptables -h' or 'iptables --help' for more information. FIREWALL INICIADO ....................[OK] Coloquei as linhas de regras antes das linhas descritas abaixo. $IPT -t filter -A FORWARD -m state --state INVALID,RELATED,ESTABLISHED -j ACCEPT $IPT -t filter -A FORWARD -j LOG $LOG_OPTIONS --log-prefix "LOG_FORWARD" $IPT -t filter -A FORWARD -j DROP De: centos-pt-br-request(a)centos.org Para: centos-pt-br(a)centos.org Enviadas: Quarta-feira, 7 de setembro de 2016 9:00:02 Assunto: Digest CentOS-pt-br, volume 114, assunto 2 Enviar submissões para a lista de discussão CentOS-pt-br para centos-pt-br(a)centos.org Para se cadastrar ou descadastrar via WWW, visite o endereço https://lists.centos.org/mailman/listinfo/centos-pt-br ou, via email, envie uma mensagem com a palavra 'help' no assunto ou corpo da mensagem para centos-pt-br-request(a)centos.org Você poderá entrar em contato com a pessoa que gerencia a lista pelo endereço centos-pt-br-owner(a)centos.org Quando responder, por favor edite sua linha Assunto assim ela será mais específica que "Re: Contents of CentOS-pt-br digest..." Tópicos de Hoje: 1. Iptables! (Glenio Cortes Himmen) 2. Assunto: Iptables! (Adroaldo Cavalheiro) 3. Re: Iptables! (João Paulo Ferreira) ---------------------------------------------------------------------- Message: 1 Date: Tue, 6 Sep 2016 14:03:25 -0300 (BRT) From: Glenio Cortes Himmen <glenio.11622x(a)aparecida.go.gov.br> To: CentOS-pt-br(a)centos.org Subject: [CentOS-pt-br] Iptables! Message-ID: <1251459852.311112.1473181405819.JavaMail.zimbra(a)aparecida.go.gov.br> Content-Type: text/plain; charset="utf-8" Sou novo com IPTABLES e SQUID, preciso liberar um determinado programa para acessar o endereço e portas abaixo relacionados sem passar pelo proxy. 177.135.260.61:3051 177.135.250.61:5836 177.135.250.61:5837 177.135.250.61:725 As requisições de saída sairão do IP 172.16.0.48/255.255.255.192. Abaixo o script firewall.sh que utilizo. #!/bin/bash #___________.__________________________ __ _____ .____ .____ #\_ _____/| \______ \_ _____/ \ / \/ _ \ | | | | # | __) | || _/| __)_\ \/\/ / /_\ \| | | | # | \ | || | \| \\ / | \ |___| |___ # \___ / |___||____|_ /_______ / \__/\ /\____|__ /_______ \_______ \ # \/ \/ \/ \/ \/ \/ \/ ##################################################################### # VARIAVEIS ##################################################################### # -d ip de destino - rede destino - ip da rede 192.168.2.1 192.168.0.0/24 # -s ip de origem - rede de origem - ip da internet # --sport NUMERO porta origem # --dport NUMERO porta destino # -j ACAO LOG_OPTIONS="--log-tcp-sequence --log-ip-options --log-tcp-options --log-level info" IPT="/sbin/iptables" ### INTERFACE DA REDE EXTERNA INTERNET IF_EXT="eth0" ### INTERFACE DA REDE INTERNA LAN IF_INT="eth1" ### REDE INTERNA REDE_INTERNA="172.16.0.0/26" ### PORTAS LIBERADAS TCP INPUT PORTAS_REDE_INTERNA="23 25 53 137 443 8080 1194 2928 3128 3389 80" ### PORTAS LIBERADAS UDP INPUT PORTAS_UDP="53 161 3128" ### Portas liberadas de fora internet para a rede interna PORTAS_FORWARD="23 25 53 443 8080 137 1194 2928 3389 3128" # ======== FORWARD LIBERADO PARA IP EXTERNO IP_FORWARD_EXTERNO=" 189.2.188.173 187.5.111.45 " ### FORWARD LIBERADO PARA IP DA REDE INTERNA ### Informar os IP's da rede interna que poderão passar sem configurar o proxy IP_FORWARD_INTERNO=" 172.16.0.3 172.16.0.7 172.16.0.25 172.16.0.11 172.16.0.50 172.16.0.47 172.16.0.38 172.16.0.61 172.16.0.24 172.16.0.10 172.16.0.9 172.16.0.49 172.16.0.18 172.16.0.15 172.16.0.36 172.16.0.51 172.16.0.39 172.16.0.45 172.16.0.29 172.16.0.36 " echo "INICIANDO FIREWALL ...................[OK]" ##################################################################### # MODULOS ##################################################################### /sbin/modprobe ip_conntrack /sbin/modprobe ip_conntrack_ftp /sbin/modprobe ip_nat_ftp /sbin/modprobe iptable_nat /sbin/modprobe ipt_tos /sbin/modprobe ipt_MASQUERADE echo "LIMPANDO AS REGRAS ...................[OK]" ### APAGANDO REGRAS PADRAO $IPT -F $IPT -t nat -F $IPT -t mangle -F ### APAGANDO CHAINS $IPT -X $IPT -t nat -X $IPT -t mangle -X ### ZERANDO CONTADORES $IPT -Z $IPT -t nat -Z $IPT -t mangle -Z echo "APLICADO REGRAS PADRÕES ..............[OK]" ###################################################################### # REGRAS PADROES ###################################################################### $IPT -P INPUT DROP $IPT -P FORWARD DROP $IPT -P OUTPUT ACCEPT ### HABILITANDO ROTEAMENTO NO KERNEL echo "1" > /proc/sys/net/ipv4/ip_forward ###################################################################### # REGRAS DE NAT ###################################################################### ### COMPARTILHAR INTERNET #$IPT -t nat -A POSTROUTING -s $REDE_INTERNA -o $IF_EXT -j MASQUERADE $IPT -t nat -A POSTROUTING -o $IF_EXT -j MASQUERADE #Redirecionar 443 para 3128 #$IPT -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-ports 3128 ### PROXY TRANSPARENTE #$IPT -t nat -A PREROUTING -i $IF_EXT -p tcp --dport 80 -j DNAT --to 10.1.1.1:3128 #$IPT -t nat -A PREROUTING -i $IF_INT -p tcp --dport 80 -j REDIRECT --to-port 3128 ### REDIRECIONAR ACESSO EXTERNO RDP PARA HOST INTERNO #$IPT -t nat -A PREROUTING -i $IF_EXT -p tcp --dport 3389 -j DNAT --to-destination 10.1.1.54:3389 #$IPT -t filter -A FORWARD -i $IF_EXT -d 10.1.1.54 -p tcp --dport 3389 -j ACCEPT echo "APLICANDO REGRAS MANUAIS .............[OK]" ##################################################################### # REGRAS INPUT ##################################################################### $IPT -t filter -A INPUT -p tcp -i lo -j ACCEPT $IPT -t filter -A INPUT -p icmp -j ACCEPT $IPT -t filter -A INPUT -p tcp --dport 443 -j DROP for i in $PORTAS_REDE_INTERNA; do $IPT -t filter -A INPUT -p tcp --dport $i -j ACCEPT done for i in $PORTAS_UDP; do $IPT -A INPUT -p udp --dport $i -j ACCEPT done $IPT -t filter -A INPUT -m state --state INVALID,RELATED,ESTABLISHED -j ACCEPT $IPT -t filter -A INPUT -j LOG $LOG_OPTIONS --log-prefix "LOG_INPUT" $IPT -t filter -A INPUT -j DROP ##################################################################### # REGRAS DE FORWARD ##################################################################### ### PORTAS FORWARD for i in $PORTAS_FORWARD; do $IPT -A FORWARD -p tcp --dport $i -j ACCEPT done ### FORWARD EXTERNA INTERNET for i in $IP_FORWARD_EXTERNO; do $IPT -A FORWARD -d $i -j ACCEPT done ### FORWARD INTERNO INTERNT for i in $IP_FORWARD_INTERNO; do $IPT -A FORWARD -s $i -j ACCEPT done ### for i in $PORTAS_UDP; do $IPT -t filter -A FORWARD -p udp --dport $i -j ACCEPT done $IPT -t filter -A FORWARD -m state --state INVALID,RELATED,ESTABLISHED -j ACCEPT $IPT -t filter -A FORWARD -j LOG $LOG_OPTIONS --log-prefix "LOG_FORWARD" $IPT -t filter -A FORWARD -j DROP echo "FIREWALL INICIADO ....................[OK]" Gostaria da ajuda para saber o comando e onde colocar. -------------- Próxima Parte ---------- Um anexo em HTML foi limpo... URL: <http://lists.centos.org/pipermail/centos-pt-br/attachments/20160906/5ed31ef…> ------------------------------ Message: 2 Date: Tue, 6 Sep 2016 22:33:01 +0000 (UTC) From: Adroaldo Cavalheiro <adroaldo_goncalves(a)yahoo.com.br> To: "Portuguese (Brazilian) CentOS mailing list" <centos-pt-br(a)centos.org> Subject: [CentOS-pt-br] Assunto: Iptables! Message-ID: <700822086.704018.1473201181100(a)mail.yahoo.com> Content-Type: text/plain; charset="utf-8" Tenta isso. iptables -A FORWARD -p tcp --dport 3051 -d 177.135.260.61 -j ACCEPTFaz o mesmo com as outras portas, é só repetir a regra. Tirei deste Post no Vivaolinux. Enviado do Yahoo Mail no Android Em 14:03 ter, 6 de set de PM, Glenio Cortes Himmen<glenio.11622x(a)aparecida.go.gov.br> escreveu: Sou novo com IPTABLES e SQUID, preciso liberar um determinado programa para acessar o endereço e portas abaixo relacionados sem passar pelo proxy. 177.135.260.61:3051 177.135.250.61:5836 177.135.250.61:5837 177.135.250.61:725 As requisições de saída sairão do IP 172.16.0.48/255.255.255.192. Abaixo o script firewall.sh que utilizo. #!/bin/bash #___________.__________________________ __ _____ .____ .____ #\_ _____/| \______ \_ _____/ \ / \/ _ \ | | | | # | __) | || _/| __)_\ \/\/ / /_\ \| | | | # | \ | || | \| \\ / | \ |___| |___ # \___ / |___||____|_ /_______ / \__/\ /\____|__ /_______ \_______ \ # \/ \/ \/ \/ \/ \/ \/ ##################################################################### # VARIAVEIS ##################################################################### # -d ip de destino - rede destino - ip da rede 192.168.2.1 192.168.0.0/24 # -s ip de origem - rede de origem - ip da internet # --sport NUMERO porta origem # --dport NUMERO porta destino # -j ACAO LOG_OPTIONS="--log-tcp-sequence --log-ip-options --log-tcp-options --log-level info" IPT="/sbin/iptables" ### INTERFACE DA REDE EXTERNA INTERNET IF_EXT="eth0" ### INTERFACE DA REDE INTERNA LAN IF_INT="eth1" ### REDE INTERNA REDE_INTERNA="172.16.0.0/26" ### PORTAS LIBERADAS TCP INPUT PORTAS_REDE_INTERNA="23 25 53 137 443 8080 1194 2928 3128 3389 80" ### PORTAS LIBERADAS UDP INPUT PORTAS_UDP="53 161 3128" ### Portas liberadas de fora internet para a rede interna PORTAS_FORWARD="23 25 53 443 8080 137 1194 2928 3389 3128" # ======== FORWARD LIBERADO PARA IP EXTERNO IP_FORWARD_EXTERNO=" 189.2.188.173 187.5.111.45 " ### FORWARD LIBERADO PARA IP DA REDE INTERNA ### Informar os IP's da rede interna que poderão passar sem configurar o proxy IP_FORWARD_INTERNO=" 172.16.0.3 172.16.0.7 172.16.0.25 172.16.0.11 172.16.0.50 172.16.0.47 172.16.0.38 172.16.0.61 172.16.0.24 172.16.0.10 172.16.0.9 172.16.0.49 172.16.0.18 172.16.0.15 172.16.0.36 172.16.0.51 172.16.0.39 172.16.0.45 172.16.0.29 172.16.0.36 " echo "INICIANDO FIREWALL ...................[OK]" ##################################################################### # MODULOS ##################################################################### /sbin/modprobe ip_conntrack /sbin/modprobe ip_conntrack_ftp /sbin/modprobe ip_nat_ftp /sbin/modprobe iptable_nat /sbin/modprobe ipt_tos /sbin/modprobe ipt_MASQUERADE echo "LIMPANDO AS REGRAS ...................[OK]" ### APAGANDO REGRAS PADRAO $IPT -F $IPT -t nat -F $IPT -t mangle -F ### APAGANDO CHAINS $IPT -X $IPT -t nat -X $IPT -t mangle -X ### ZERANDO CONTADORES $IPT -Z $IPT -t nat -Z $IPT -t mangle -Z echo "APLICADO REGRAS PADRÕES ..............[OK]" ###################################################################### # REGRAS PADROES ###################################################################### $IPT -P INPUT DROP $IPT -P FORWARD DROP $IPT -P OUTPUT ACCEPT ### HABILITANDO ROTEAMENTO NO KERNEL echo "1" > /proc/sys/net/ipv4/ip_forward ###################################################################### # REGRAS DE NAT ###################################################################### ### COMPARTILHAR INTERNET #$IPT -t nat -A POSTROUTING -s $REDE_INTERNA -o $IF_EXT -j MASQUERADE $IPT -t nat -A POSTROUTING -o $IF_EXT -j MASQUERADE #Redirecionar 443 para 3128 #$IPT -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-ports 3128 ### PROXY TRANSPARENTE #$IPT -t nat -A PREROUTING -i $IF_EXT -p tcp --dport 80 -j DNAT --to 10.1.1.1:3128 #$IPT -t nat -A PREROUTING -i $IF_INT -p tcp --dport 80 -j REDIRECT --to-port 3128 ### REDIRECIONAR ACESSO EXTERNO RDP PARA HOST INTERNO #$IPT -t nat -A PREROUTING -i $IF_EXT -p tcp --dport 3389 -j DNAT --to-destination 10.1.1.54:3389 #$IPT -t filter -A FORWARD -i $IF_EXT -d 10.1.1.54 -p tcp --dport 3389 -j ACCEPT echo "APLICANDO REGRAS MANUAIS .............[OK]" ##################################################################### # REGRAS INPUT ##################################################################### $IPT -t filter -A INPUT -p tcp -i lo -j ACCEPT $IPT -t filter -A INPUT -p icmp -j ACCEPT $IPT -t filter -A INPUT -p tcp --dport 443 -j DROP for i in $PORTAS_REDE_INTERNA; do $IPT -t filter -A INPUT -p tcp --dport $i -j ACCEPT done for i in $PORTAS_UDP; do $IPT -A INPUT -p udp --dport $i -j ACCEPT done $IPT -t filter -A INPUT -m state --state INVALID,RELATED,ESTABLISHED -j ACCEPT $IPT -t filter -A INPUT -j LOG $LOG_OPTIONS --log-prefix "LOG_INPUT" $IPT -t filter -A INPUT -j DROP ##################################################################### # REGRAS DE FORWARD ##################################################################### ### PORTAS FORWARD for i in $PORTAS_FORWARD; do $IPT -A FORWARD -p tcp --dport $i -j ACCEPT done ### FORWARD EXTERNA INTERNET for i in $IP_FORWARD_EXTERNO; do $IPT -A FORWARD -d $i -j ACCEPT done ### FORWARD INTERNO INTERNT for i in $IP_FORWARD_INTERNO; do $IPT -A FORWARD -s $i -j ACCEPT done ### for i in $PORTAS_UDP; do $IPT -t filter -A FORWARD -p udp --dport $i -j ACCEPT done $IPT -t filter -A FORWARD -m state --state INVALID,RELATED,ESTABLISHED -j ACCEPT $IPT -t filter -A FORWARD -j LOG $LOG_OPTIONS --log-prefix "LOG_FORWARD" $IPT -t filter -A FORWARD -j DROP echo "FIREWALL INICIADO ....................[OK]" Gostaria da ajuda para saber o comando e onde colocar. -------------- Próxima Parte ---------- Um anexo em HTML foi limpo... URL: <http://lists.centos.org/pipermail/centos-pt-br/attachments/20160906/a8d6e24…> ------------------------------ Message: 3 Date: Tue, 6 Sep 2016 23:51:26 -0300 From: João Paulo Ferreira <jferreira.ba(a)gmail.com> To: "Portuguese (Brazilian) CentOS mailing list" <centos-pt-br(a)centos.org> Subject: Re: [CentOS-pt-br] Iptables! Message-ID: <CA+fqMVCoKcY0Ej+fz5py6wSuGcnghdU2AXdJ2GRihpW+OfDqYA(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" iptables -t filter -I FORWARD -d 177.135.260.61 -p tcp -m multiport --dport 3051,5836,5837,725 -j ACCEPT iptables -t filter -I FORWARD -d 177.135.260.61 -p udp -m multiport --dport 3051,5836,5837,725 -j ACCEPT Como você não informou o protocolo da camada de transporte estou colocando a regra para UDP e TCP. Atenciosamente, *João Paulo Ferreira* *B.S. Ciência da Computação* - UNIVERSIDADE SALVADOR *Esp. Redes de Computadores e Telecomunicações* - UNIVERSIDADE SALVADOR *Novell Certified Linux Administrator* - NOVELL *Certified Linux Professional Institute *- LPI *CompTIA Linux+* - COMPTIA *Mikrotik Certified Network Associate* - MIKROTIK Cel.: +55 (71) 9918-1235 VIVO Cel.: +55 (71) 8837-7080 OI Skype.: joaopaulo.cf G-Talk/Mail: jferreira.ba(a)gmail.com Em 6 de setembro de 2016 14:03, Glenio Cortes Himmen < glenio.11622x(a)aparecida.go.gov.br> escreveu: > Sou novo com IPTABLES e SQUID, preciso liberar um determinado programa > para acessar o endereço e portas abaixo relacionados sem passar pelo proxy. > > 177.135.260.61:3051 > 177.135.250.61:5836 > 177.135.250.61:5837 > 177.135.250.61:725 > > As requisições de saída sairão do IP 172.16.0.48/255.255.255.192. > > Abaixo o script firewall.sh que utilizo. > > #!/bin/bash > #___________.__________________________ __ _____ .____ .____ > #\_ _____/| \______ \_ _____/ \ / \/ _ \ | | | | > # | __) | || _/| __)_\ \/\/ / /_\ \| | | | > # | \ | || | \| \\ / | \ |___| |___ > # \___ / |___||____|_ /_______ / \__/\ /\____|__ /_______ \_______ \ > # \/ \/ \/ \/ \/ \/ \/ > ##################################################################### > # VARIAVEIS > ##################################################################### > # -d ip de destino - rede destino - ip da rede 192.168.2.1 > 192.168.0.0/24 > # -s ip de origem - rede de origem - ip da internet > # --sport NUMERO porta origem > # --dport NUMERO porta destino > # -j ACAO > LOG_OPTIONS="--log-tcp-sequence --log-ip-options --log-tcp-options > --log-level info" > IPT="/sbin/iptables" > ### INTERFACE DA REDE EXTERNA INTERNET > IF_EXT="eth0" > > ### INTERFACE DA REDE INTERNA LAN > IF_INT="eth1" > > ### REDE INTERNA > REDE_INTERNA="172.16.0.0/26" > > ### PORTAS LIBERADAS TCP INPUT > PORTAS_REDE_INTERNA="23 25 53 137 443 8080 1194 2928 3128 3389 80" > > ### PORTAS LIBERADAS UDP INPUT > PORTAS_UDP="53 161 3128" > > ### Portas liberadas de fora internet para a rede interna > PORTAS_FORWARD="23 25 53 443 8080 137 1194 2928 3389 3128" > > # ======== FORWARD LIBERADO PARA IP EXTERNO > IP_FORWARD_EXTERNO=" > 189.2.188.173 > 187.5.111.45 > " > ### FORWARD LIBERADO PARA IP DA REDE INTERNA > ### Informar os IP's da rede interna que poderão passar sem configurar o > proxy > IP_FORWARD_INTERNO=" > 172.16.0.3 > 172.16.0.7 > 172.16.0.25 > 172.16.0.11 > 172.16.0.50 > 172.16.0.47 > 172.16.0.38 > 172.16.0.61 > 172.16.0.24 > 172.16.0.10 > 172.16.0.9 > 172.16.0.49 > 172.16.0.18 > 172.16.0.15 > 172.16.0.36 > 172.16.0.51 > 172.16.0.39 > 172.16.0.45 > 172.16.0.29 > 172.16.0.36 > " > echo "INICIANDO FIREWALL ...................[OK]" > ##################################################################### > # MODULOS > ##################################################################### > /sbin/modprobe ip_conntrack > /sbin/modprobe ip_conntrack_ftp > /sbin/modprobe ip_nat_ftp > /sbin/modprobe iptable_nat > /sbin/modprobe ipt_tos > /sbin/modprobe ipt_MASQUERADE > > echo "LIMPANDO AS REGRAS ...................[OK]" > ### APAGANDO REGRAS PADRAO > $IPT -F > $IPT -t nat -F > $IPT -t mangle -F > > ### APAGANDO CHAINS > $IPT -X > $IPT -t nat -X > $IPT -t mangle -X > > ### ZERANDO CONTADORES > $IPT -Z > $IPT -t nat -Z > $IPT -t mangle -Z > > echo "APLICADO REGRAS PADRÕES ..............[OK]" > ###################################################################### > # REGRAS PADROES > ###################################################################### > $IPT -P INPUT DROP > $IPT -P FORWARD DROP > $IPT -P OUTPUT ACCEPT > > ### HABILITANDO ROTEAMENTO NO KERNEL > echo "1" > /proc/sys/net/ipv4/ip_forward > > ###################################################################### > # REGRAS DE NAT > ###################################################################### > ### COMPARTILHAR INTERNET > > #$IPT -t nat -A POSTROUTING -s $REDE_INTERNA -o $IF_EXT -j MASQUERADE > $IPT -t nat -A POSTROUTING -o $IF_EXT -j MASQUERADE > > #Redirecionar 443 para 3128 > #$IPT -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-ports 3128 > > ### PROXY TRANSPARENTE > #$IPT -t nat -A PREROUTING -i $IF_EXT -p tcp --dport 80 -j DNAT --to > 10.1.1.1:3128 > #$IPT -t nat -A PREROUTING -i $IF_INT -p tcp --dport 80 -j REDIRECT > --to-port 3128 > > ### REDIRECIONAR ACESSO EXTERNO RDP PARA HOST INTERNO > #$IPT -t nat -A PREROUTING -i $IF_EXT -p tcp --dport 3389 -j DNAT > --to-destination 10.1.1.54:3389 > #$IPT -t filter -A FORWARD -i $IF_EXT -d 10.1.1.54 -p tcp --dport 3389 -j > ACCEPT > > echo "APLICANDO REGRAS MANUAIS .............[OK]" > ##################################################################### > # REGRAS INPUT > ##################################################################### > $IPT -t filter -A INPUT -p tcp -i lo -j ACCEPT > $IPT -t filter -A INPUT -p icmp -j ACCEPT > $IPT -t filter -A INPUT -p tcp --dport 443 -j DROP > > for i in $PORTAS_REDE_INTERNA; do > $IPT -t filter -A INPUT -p tcp --dport $i -j ACCEPT > done > > for i in $PORTAS_UDP; do > $IPT -A INPUT -p udp --dport $i -j ACCEPT > done > > $IPT -t filter -A INPUT -m state --state INVALID,RELATED,ESTABLISHED -j > ACCEPT > $IPT -t filter -A INPUT -j LOG $LOG_OPTIONS --log-prefix "LOG_INPUT" > $IPT -t filter -A INPUT -j DROP > > ##################################################################### > # REGRAS DE FORWARD > ##################################################################### > ### PORTAS FORWARD > for i in $PORTAS_FORWARD; do > $IPT -A FORWARD -p tcp --dport $i -j ACCEPT > done > > ### FORWARD EXTERNA INTERNET > for i in $IP_FORWARD_EXTERNO; do > $IPT -A FORWARD -d $i -j ACCEPT > done > > ### FORWARD INTERNO INTERNT > for i in $IP_FORWARD_INTERNO; do > $IPT -A FORWARD -s $i -j ACCEPT > done > ### > > for i in $PORTAS_UDP; do > $IPT -t filter -A FORWARD -p udp --dport $i -j ACCEPT > done > > $IPT -t filter -A FORWARD -m state --state INVALID,RELATED,ESTABLISHED -j > ACCEPT > $IPT -t filter -A FORWARD -j LOG $LOG_OPTIONS --log-prefix "LOG_FORWARD" > $IPT -t filter -A FORWARD -j DROP > > echo "FIREWALL INICIADO ....................[OK]" > > Gostaria da ajuda para saber o comando e onde colocar. > > _______________________________________________ > CentOS-pt-br mailing list > CentOS-pt-br(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-pt-br > > -------------- Próxima Parte ---------- Um anexo em HTML foi limpo... URL: <http://lists.centos.org/pipermail/centos-pt-br/attachments/20160906/7ba7798…> ------------------------------ _______________________________________________ CentOS-pt-br mailing list CentOS-pt-br(a)centos.org https://lists.centos.org/mailman/listinfo/centos-pt-br Fim da Digest CentOS-pt-br, volume 114, assunto 2 *************************************************

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

discuss-pt-br September 2016