Accès serveur apache par ip externe impossible ?

Marsh Posté le 31-12-2007 à 11:38:28

salut,

J'ai un gros souci avec la mise en place d'un serveur http local apache.

Je suis sur Linux Fedora 8 avec apache 2. Mon FAI est free.

Les accès à mon site par des ip autres que l'ip local de la machine du serveur apache échouent.

J'accède bien à mon RocumentRoot par le réseaux local genre 192.168.0.2 (machine serveur), mais pas par l'ip externe de ma freebox 82.XXX.XXX.XXX

Il me met l'erreur suivante si je charge http://82.XXX.XXX.XXX

Code :

FORBIDDEN
You don't have permission to access this file on this server.
Cheyenne/2.0.36 Server at localhost Port 80

Ce qui me surprend c'est que si je charge la même ip avec un nom de fichier de mon site (Ex : http://82.XXX.XXX.XXX/essai.txt), il me met

Code :

NOT FOUND
The request url was not found on this server
Cheyenne/2.0.36 Server at localhost Port 80

A noter qu'il ne me met aucune erreur si je charge http://192.168.0.2/essai.txt

Cela veut donc dire que je n'abouti pas au même répertoire de mon disque selon que je charge l'ip externe ou l'ip interne ????!!!!

Je ne comprends pas trop pourquoi !

Pour les testes, tous les répertoires de / jusqu'à DocumentRoot sont en droit 755 et les fichiers de mon site en droit 777

Voici ma configuration sur ma freebox qui est en mode routeur NAT:

ip freebox : 192.168.0.254
début DHCP : 192.168.0.1
fin DHCP : 192.168.0.50

ip DMZ : rien
ip freeplayer : rien

Réponse ping : désactiver
proxy WOL : désactiver

Redirection ports :

8080 tcp 192.168.0.2 8080
6220 tcp 192.168.0.1 6220
5852 udp 192.168.0.1 5852
8080 udp 192.168.0.2 8080

Apparemment la redirection doit se faire sur le port 8080 car linux fedora inclus un firewall par défaut. Le port pour traverser ce firewall est apparemment 8080.

Ai-je oubvlié quelque chose, pourquoi je ne peux pas y accéder la un ip externe ?

Reply

Marsh Posté le 31-12-2007 à 11:38:28

Reply

Marsh Posté le 31-12-2007 à 14:00:14

je ne connais pas les regles de filtrage de fedora mais c'est bien étrange ce que tu raconte !

déja balance ton fichier de conf apache. tu dois avoir des virtualhosts qui te font aboutir sur des dossiers différents selon que tu y accede en local ou depuis ton ip publique.

et que donne "iptable -L" ?
quels sont les droits unix sur les DocumentRoot ?

---------------
Blog photo/récits activités en montagne http://planetcaravan.net

Reply

Marsh Posté le 31-12-2007 à 14:33:44

voici mon httpd.conf :

Code :

#
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2/> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
#
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process as a
# whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default' server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "/etc/httpd" will be interpreted by the
# server as "/etc/httpd/logs/foo.log".
#
### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#
#
# Don't give away too much information about all the subcomponents
# we are running. Comment out this line if you don't mind remote sites
# finding out what major optional modules you are running
ServerTokens OS
#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation
# (available at <URL:http://httpd.apache.org/docs/2.2/mod/mpm_common.html#lockfile> );
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
ServerRoot "/etc/httpd"
#
# PidFile: The file in which the server should record its process
# identification number when it starts.
#
PidFile run/httpd.pid
#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 120
#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive Off
#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100
#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 15
##
## Server-Pool Size Regulation (MPM specific)
##
# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# ServerLimit: maximum value for MaxClients for the lifetime of the server
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule prefork.c>
StartServers 8
MinSpareServers 5
MaxSpareServers 20
ServerLimit 256
MaxClients 256
MaxRequestsPerChild 4000
</IfModule>
# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule worker.c>
StartServers 2
MaxClients 150
MinSpareThreads 25
MaxSpareThreads 75
ThreadsPerChild 25
MaxRequestsPerChild 0
</IfModule>
#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, in addition to the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
#Listen 12.34.56.78:80
Listen 80
#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authn_alias_module modules/mod_authn_alias.so
LoadModule authn_anon_module modules/mod_authn_anon.so
LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule ldap_module modules/mod_ldap.so
LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
LoadModule include_module modules/mod_include.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule logio_module modules/mod_logio.so
LoadModule env_module modules/mod_env.so
LoadModule ext_filter_module modules/mod_ext_filter.so
LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule expires_module modules/mod_expires.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule headers_module modules/mod_headers.so
LoadModule usertrack_module modules/mod_usertrack.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule mime_module modules/mod_mime.so
LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule info_module modules/mod_info.so
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule actions_module modules/mod_actions.so
LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule cache_module modules/mod_cache.so
LoadModule suexec_module modules/mod_suexec.so
LoadModule disk_cache_module modules/mod_disk_cache.so
LoadModule file_cache_module modules/mod_file_cache.so
LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule cgi_module modules/mod_cgi.so
#
# The following modules are not loaded by default:
#
#LoadModule cern_meta_module modules/mod_cern_meta.so
#LoadModule asis_module modules/mod_asis.so
#
# Load config files from the config directory "/etc/httpd/conf.d".
#
Include conf.d/*.conf
#
# ExtendedStatus controls whether Apache will generate "full" status
# information (ExtendedStatus On) or just basic information (ExtendedStatus
# Off) when the "server-status" handler is called. The default is Off.
#
#ExtendedStatus On
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# . On SCO (ODT 3) use "User nouser" and "Group nogroup".
# . On HPUX you may not be able to use shared memory as nobody, and the
# suggested workaround is to create a user www and use that user.
# NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)
# when the value of (unsigned)Group is above 60000;
# don't use Group #-1 on these systems!
#
User apache
Group apache
### Section 2: 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#
#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. admin@your-domain.com
#
ServerAdmin root@localhost
#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If this is not set to valid DNS name for your host, server-generated
# redirections will not work. See also the UseCanonicalName directive.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address anyway, and this will make
# redirections work in a sensible way.
#
#ServerName www.example.com:80
ServerName hometranet
#
# UseCanonicalName: Determines how Apache constructs self-referencing
# URLs and the SERVER_NAME and SERVER_PORT variables.
# When set "Off", Apache will use the Hostname and Port supplied
# by the client. When set "On", Apache will use the value of the
# ServerName directive.
#
UseCanonicalName Off
#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
#DocumentRoot "/var/www/html"
DocumentRoot "/var"
#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#
#
# This should be changed to whatever you set DocumentRoot to.
#
#<Directory "/var/www/html">
<Directory "/var">
#
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
#
Options Indexes FollowSymLinks
#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride None
#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all
</Directory>
#
# UserDir: The name of the directory that is appended onto a user's home
# directory if a ~user request is received.
#
# The path to the end user account 'public_html' directory must be
# accessible to the webserver userid. This usually means that ~userid
# must have permissions of 711, ~userid/public_html must have permissions
# of 755, and documents contained therein must be world-readable.
# Otherwise, the client will only receive a "403 Forbidden" message.
#
# See also: http://httpd.apache.org/docs/misc/FAQ.html#forbidden
#
<IfModule mod_userdir.c>
#
# UserDir is disabled by default since it can confirm the presence
# of a username on the system (depending on home directory
# permissions).
#
UserDir disable
#
# To enable requests to /~user/ to serve the user's public_html
# directory, remove the "UserDir disable" line above, and uncomment
# the following line instead:
#
#UserDir public_html
</IfModule>
#
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
#
#<Directory /home/*/public_html>
# AllowOverride FileInfo AuthConfig Limit
# Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
# <Limit GET POST OPTIONS>
# Order allow,deny
# Allow from all
# </Limit>
# <LimitExcept GET POST OPTIONS>
# Order deny,allow
# Deny from all
# </LimitExcept>
#</Directory>
#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
# The index.html.var file (a type-map) is used to deliver content-
# negotiated documents. The MultiViews Option can be used for the
# same purpose, but it is much slower.
#
DirectoryIndex index.html index.html.var
#
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives. See also the AllowOverride
# directive.
#
AccessFileName .htaccess
#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ~ "^\.ht">
Order allow,deny
# Deny from all
Allow from all
</Files>
#
# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
#
TypesConfig /etc/mime.types
#
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain
#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
<IfModule mod_mime_magic.c>
# MIMEMagicFile /usr/share/magic.mime
MIMEMagicFile conf/magic
</IfModule>
#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off
#
# EnableMMAP: Control whether memory-mapping is used to deliver
# files (assuming that the underlying OS supports it).
# The default is on; turn this off if you serve from NFS-mounted
# filesystems. On some systems, turning it off (regardless of
# filesystem) can improve performance; for details, please see
# http://httpd.apache.org/docs/2.2/m [...] enablemmap
#
#EnableMMAP off
#
# EnableSendfile: Control whether the sendfile kernel support is
# used to deliver files (assuming that the OS supports it).
# The default is on; turn this off if you serve from NFS-mounted
# filesystems. Please see
# http://httpd.apache.org/docs/2.2/m [...] lesendfile
#
#EnableSendfile off
#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog logs/error_log
#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn
#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
#
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent
# "combinedio" includes actual counts of actual bytes received (%I) and sent (%O); this
# requires the mod_logio module to be loaded.
#LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
#
#CustomLog logs/access_log common
#
# If you would like to have separate agent and referer logfiles, uncomment
# the following directives.
#
#CustomLog logs/referer_log referer
#CustomLog logs/agent_log agent
#
# For a single logfile with access, agent, and referer information
# (Combined Logfile Format), use the following directive:
#
CustomLog logs/access_log combined
#
# Optionally add a line containing the server version and virtual host
# name to server-generated pages (internal error documents, FTP directory
# listings, mod_status and mod_info output etc., but not CGI generated
# documents or custom error documents).
# Set to "EMail" to also include a mailto: link to the ServerAdmin.
# Set to one of: On | Off | EMail
#
ServerSignature On
#
# Aliases: Add here as many aliases as you need (with no limit). The format is
# Alias fakename realname
#
# Note that if you include a trailing / on fakename then the server will
# require it to be present in the URL. So "/icons" isn't aliased in this
# example, only "/icons/". If the fakename is slash-terminated, then the
# realname must also be slash terminated, and if the fakename omits the
# trailing slash, the realname must also omit it.
#
# We include the /icons/ alias for FancyIndexed directory listings. If you
# do not use FancyIndexing, you may comment this out.
#
Alias /icons/ "/var/www/icons/"
<Directory "/var/www/icons">
Options Indexes MultiViews FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all
</Directory>
#
# WebDAV module configuration section.
#
<IfModule mod_dav_fs.c>
# Location of the WebDAV lock database.
DAVLockDB /var/lib/dav/lockdb
</IfModule>
#
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the realname directory are treated as applications and
# run by the server when requested rather than as documents sent to the client.
# The same rules about trailing "/" apply to ScriptAlias directives as to
# Alias.
#
ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"
#
# "/var/www/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/var/www/cgi-bin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>
#
# Redirect allows you to tell clients about documents which used to exist in
# your server's namespace, but do not anymore. This allows you to tell the
# clients where to look for the relocated document.
# Example:
# Redirect permanent /foo http://www.example.com/bar
#
# Directives controlling the display of server-generated directory listings.
#
#
# IndexOptions: Controls the appearance of server-generated directory
# listings.
#
IndexOptions FancyIndexing VersionSort NameWidth=* HTMLTable
#
# AddIcon* directives tell the server which icon to show for different
# files or filename extensions. These are only displayed for
# FancyIndexed directories.
#
AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip
AddIconByType (TXT,/icons/text.gif) text/*
AddIconByType (IMG,/icons/image2.gif) image/*
AddIconByType (SND,/icons/sound2.gif) audio/*
AddIconByType (VID,/icons/movie.gif) video/*
AddIcon /icons/binary.gif .bin .exe
AddIcon /icons/binhex.gif .hqx
AddIcon /icons/tar.gif .tar
AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
AddIcon /icons/a.gif .ps .ai .eps
AddIcon /icons/layout.gif .html .shtml .htm .pdf
AddIcon /icons/text.gif .txt
AddIcon /icons/c.gif .c
AddIcon /icons/p.gif .pl .py
AddIcon /icons/f.gif .for
AddIcon /icons/dvi.gif .dvi
AddIcon /icons/uuencoded.gif .uu
AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
AddIcon /icons/tex.gif .tex
AddIcon /icons/bomb.gif core
AddIcon /icons/back.gif ..
AddIcon /icons/hand.right.gif README
AddIcon /icons/folder.gif ^^DIRECTORY^^
AddIcon /icons/blank.gif ^^BLANKICON^^
#
# DefaultIcon is which icon to show for files which do not have an icon
# explicitly set.
#
DefaultIcon /icons/unknown.gif
#
# AddDescription allows you to place a short description after a file in
# server-generated indexes. These are only displayed for FancyIndexed
# directories.
# Format: AddDescription "description" filename
#
#AddDescription "GZIP compressed document" .gz
#AddDescription "tar archive" .tar
#AddDescription "GZIP compressed tar archive" .tgz
#
# ReadmeName is the name of the README file the server will look for by
# default, and append to directory listings.
#
# HeaderName is the name of a file which should be prepended to
# directory indexes.
ReadmeName README.html
HeaderName HEADER.html
#
# IndexIgnore is a set of filenames which directory indexing should ignore
# and not include in the listing. Shell-style wildcarding is permitted.
#
IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t
#
# DefaultLanguage and AddLanguage allows you to specify the language of
# a document. You can then use content negotiation to give a browser a
# file in a language the user can understand.
#
# Specify a default language. This means that all data
# going out without a specific language tag (see below) will
# be marked with this one. You probably do NOT want to set
# this unless you are sure it is correct for all cases.
#
# * It is generally better to not mark a page as
# * being a certain language than marking it with the wrong
# * language!
#
# DefaultLanguage nl
#
# Note 1: The suffix does not have to be the same as the language
# keyword --- those with documents in Polish (whose net-standard
# language code is pl) may wish to use "AddLanguage pl .po" to
# avoid the ambiguity with the common suffix for perl scripts.
#
# Note 2: The example entries below illustrate that in some cases
# the two character 'Language' abbreviation is not identical to
# the two character 'Country' code for its country,
# E.g. 'Danmark/dk' versus 'Danish/da'.
#
# Note 3: In the case of 'ltz' we violate the RFC by using a three char
# specifier. There is 'work in progress' to fix this and get
# the reference data for rfc1766 cleaned up.
#
# Catalan (ca) - Croatian (hr) - Czech (cs) - Danish (da) - Dutch (nl)
# English (en) - Esperanto (eo) - Estonian (et) - French (fr) - German (de)
# Greek-Modern (el) - Hebrew (he) - Italian (it) - Japanese (ja)
# Korean (ko) - Luxembourgeois* (ltz) - Norwegian Nynorsk (nn)
# Norwegian (no) - Polish (pl) - Portugese (pt)
# Brazilian Portuguese (pt-BR) - Russian (ru) - Swedish (sv)
# Simplified Chinese (zh-CN) - Spanish (es) - Traditional Chinese (zh-TW)
#
AddLanguage ca .ca
AddLanguage cs .cz .cs
AddLanguage da .dk
AddLanguage de .de
AddLanguage el .el
AddLanguage en .en
AddLanguage eo .eo
AddLanguage es .es
AddLanguage et .et
AddLanguage fr .fr
AddLanguage he .he
AddLanguage hr .hr
AddLanguage it .it
AddLanguage ja .ja
AddLanguage ko .ko
AddLanguage ltz .ltz
AddLanguage nl .nl
AddLanguage nn .nn
AddLanguage no .no
AddLanguage pl .po
AddLanguage pt .pt
AddLanguage pt-BR .pt-br
AddLanguage ru .ru
AddLanguage sv .sv
AddLanguage zh-CN .zh-cn
AddLanguage zh-TW .zh-tw
#
# LanguagePriority allows you to give precedence to some languages
# in case of a tie during content negotiation.
#
# Just list the languages in decreasing order of preference. We have
# more or less alphabetized them here. You probably want to change this.
#
LanguagePriority en ca cs da de el eo es et fr he hr it ja ko ltz nl nn no pl pt pt-BR ru sv zh-CN zh-TW
#
# ForceLanguagePriority allows you to serve a result page rather than
# MULTIPLE CHOICES (Prefer) [in case of a tie] or NOT ACCEPTABLE (Fallback)
# [in case no accepted languages matched the available variants]
#
ForceLanguagePriority Prefer Fallback
#
# Specify a default charset for all content served; this enables
# interpretation of all content as UTF-8 by default. To use the
# default browser choice (ISO-8859-1), or to allow the META tags
# in HTML content to override this choice, comment out this
# directive:
#
AddDefaultCharset UTF-8
#
# AddType allows you to add to or override the MIME configuration
# file mime.types for specific file types.
#
#AddType application/x-tar .tgz
#
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
# Despite the name similarity, the following Add* directives have nothing
# to do with the FancyIndexing customization directives above.
#
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
#
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz
#
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
#
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#
#AddHandler cgi-script .cgi
#
# For files that include their own HTTP headers:
#
#AddHandler send-as-is asis
#
# For type maps (negotiated resources):
# (This is enabled by default to allow the Apache "It Worked" page
# to be distributed in multiple languages.)
#
AddHandler type-map var
#
# Filters allow you to process content before it is sent to the client.
#
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#
AddType text/html .shtml
AddOutputFilter INCLUDES .shtml
#
# Action lets you define media types that will execute a script whenever
# a matching file is called. This eliminates the need for repeated URL
# pathnames for oft-used CGI file processors.
# Format: Action media/type /cgi-script/location
# Format: Action handler-name /cgi-script/location
#
#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#
#
# Putting this all together, we can internationalize error responses.
#
# We use Alias to redirect any /error/HTTP_<error>.html.var response to
# our collection of by-error message multi-language collections. We use
# includes to substitute the appropriate text.
#
# You can modify the messages' appearance without changing any of the
# default HTTP_<error>.html.var files by adding the line:
#
# Alias /error/include/ "/your/include/path/"
#
# which allows you to create your own set of files by starting with the
# /var/www/error/include/ files and
# copying them to /your/include/path/, even on a per-VirtualHost basis.
#
Alias /error/ "/var/www/error/"
<IfModule mod_negotiation.c>
<IfModule mod_include.c>
<Directory "/var/www/error">
AllowOverride None
Options IncludesNoExec
AddOutputFilter Includes html
AddHandler type-map var
Order allow,deny
Allow from all
LanguagePriority en es de fr
ForceLanguagePriority Prefer Fallback
</Directory>
# ErrorDocument 400 /error/HTTP_BAD_REQUEST.html.var
# ErrorDocument 401 /error/HTTP_UNAUTHORIZED.html.var
# ErrorDocument 403 /error/HTTP_FORBIDDEN.html.var
# ErrorDocument 404 /error/HTTP_NOT_FOUND.html.var
# ErrorDocument 405 /error/HTTP_METHOD_NOT_ALLOWED.html.var
# ErrorDocument 408 /error/HTTP_REQUEST_TIME_OUT.html.var
# ErrorDocument 410 /error/HTTP_GONE.html.var
# ErrorDocument 411 /error/HTTP_LENGTH_REQUIRED.html.var
# ErrorDocument 412 /error/HTTP_PRECONDITION_FAILED.html.var
# ErrorDocument 413 /error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var
# ErrorDocument 414 /error/HTTP_REQUEST_URI_TOO_LARGE.html.var
# ErrorDocument 415 /error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var
# ErrorDocument 500 /error/HTTP_INTERNAL_SERVER_ERROR.html.var
# ErrorDocument 501 /error/HTTP_NOT_IMPLEMENTED.html.var
# ErrorDocument 502 /error/HTTP_BAD_GATEWAY.html.var
# ErrorDocument 503 /error/HTTP_SERVICE_UNAVAILABLE.html.var
# ErrorDocument 506 /error/HTTP_VARIANT_ALSO_VARIES.html.var
</IfModule>
</IfModule>
#
# The following directives modify normal HTTP response behavior to
# handle known problems with browser implementations.
#
BrowserMatch "Mozilla/2" nokeepalive
BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
BrowserMatch "RealPlayer 4\.0" force-response-1.0
BrowserMatch "Java/1\.0" force-response-1.0
BrowserMatch "JDK/1\.0" force-response-1.0
#
# The following directive disables redirects on non-GET requests for
# a directory that does not include the trailing slash. This fixes a
# problem with Microsoft WebFolders which does not appropriately handle
# redirects for folders with DAV methods.
# Same deal with Apple's DAV filesystem and Gnome VFS support for DAV.
#
BrowserMatch "Microsoft Data Access Internet Publishing Provider" redirect-carefully
BrowserMatch "MS FrontPage" redirect-carefully
BrowserMatch "^WebDrive" redirect-carefully
BrowserMatch "^WebDAVFS/1.[0123]" redirect-carefully
BrowserMatch "^gnome-vfs/1.0" redirect-carefully
BrowserMatch "^XML Spy" redirect-carefully
BrowserMatch "^Dreamweaver-WebDAV-SCM1" redirect-carefully
#
# Allow server status reports generated by mod_status,
# with the URL of http://servername/server-status
# Change the ".example.com" to match your domain to enable.
#
#<Location /server-status>
# SetHandler server-status
# Order deny,allow
# Deny from all
# Allow from .example.com
#</Location>
#
# Allow remote server configuration reports, with the URL of
# http://servername/server-info (requires that mod_info.c be loaded).
# Change the ".example.com" to match your domain to enable.
#
#<Location /server-info>
# SetHandler server-info
# Order deny,allow
# Deny from all
# Allow from .example.com
#</Location>
#
# Proxy Server directives. Uncomment the following lines to
# enable the proxy server:
#
#<IfModule mod_proxy.c>
#ProxyRequests On
#
#<Proxy *>
# Order deny,allow
# Deny from all
# Allow from .example.com
#</Proxy>
#
# Enable/disable the handling of HTTP/1.1 "Via:" headers.
# ("Full" adds the server version; "Block" removes all outgoing Via: headers)
# Set to one of: Off | On | Full | Block
#
#ProxyVia On
#
# To enable a cache of proxied content, uncomment the following lines.
# See http://httpd.apache.org/docs/2.2/mod/mod_cache.html for more details.
#
#<IfModule mod_disk_cache.c>
# CacheEnable disk /
# CacheRoot "/var/cache/mod_proxy"
#</IfModule>
#
#</IfModule>
# End of proxy directives.
### Section 3: Virtual Hosts
#
# VirtualHost: If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
#
# Please see the documentation at
# <URL:http://httpd.apache.org/docs/2.2/vhosts/>
# for further details before you try to setup virtual hosts.
#
# You may use the command line option '-S' to verify your virtual host
# configuration.
#
# Use name-based virtual hosting.
#
#NameVirtualHost *:80
#
# NOTE: NameVirtualHost cannot be used without a port specifier
# (e.g. :80) if mod_ssl is being used, due to the nature of the
# SSL protocol.
#
#
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for requests without a known
# server name.
#
#<VirtualHost *:80>
# ServerAdmin webmaster@dummy-host.example.com
# DocumentRoot /www/docs/dummy-host.example.com
# ServerName dummy-host.example.com
# ErrorLog logs/dummy-host.example.com-error_log
# CustomLog logs/dummy-host.example.com-access_log common
#</VirtualHost>

voici ce que donne la commande iptables -L :

Code :

Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT udp -- anywhere anywhere udp dpt:domain
ACCEPT tcp -- anywhere anywhere tcp dpt:domain
ACCEPT udp -- anywhere anywhere udp dpt:bootps
ACCEPT tcp -- anywhere anywhere tcp dpt:bootps
RH-Firewall-1-INPUT all -- anywhere anywhere
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere 192.168.122.0/24 state RELATED,ESTABLISHED
ACCEPT all -- 192.168.122.0/24 anywhere
ACCEPT all -- anywhere anywhere
REJECT all -- anywhere anywhere reject-with icmp-port-unreachable
REJECT all -- anywhere anywhere reject-with icmp-port-unreachable
REJECT all -- anywhere anywhere reject-with icmp-host-prohibited
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain RH-Firewall-1-INPUT (1 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT icmp -- anywhere anywhere icmp any
ACCEPT esp -- anywhere anywhere
ACCEPT ah -- anywhere anywhere
ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns
ACCEPT udp -- anywhere anywhere udp dpt:ipp
ACCEPT tcp -- anywhere anywhere tcp dpt:ipp
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh
REJECT all -- anywhere anywhere reject-with icmp-host-prohibited

le repertoire DocumentRoot est en 777 (pour mes testes)

Reply

Marsh Posté le 31-12-2007 à 15:03:09

Faut configurer ton routeur pour que toutes les connections http soit renvoyer vers ton serveur.

Mon routeur speedtouch:

Message cité 1 fois
Message édité par Ik12 le 31-12-2007 à 15:06:18

---------------
on est au 21 siècle plus person ne écrit correctement sur les forum ni sur msn ni sur les SMS.

Reply

Marsh Posté le 31-12-2007 à 15:04:57

t'aurai pas pu mêtre plus long encore ?!

ça essai useCanonicalName à on
et ton serveur web m'a pas l'air joignable de l'extérieur, vu les regles iptables.
Pour ouvrir: iptable -A INPUT -p tcp --dport 80 -j ACCEPT

clean un peu ton fichier de conf.
De plus un DocumentRoot à /var c'est quoi cette conf ?!

---------------
Blog photo/récits activités en montagne http://planetcaravan.net

Reply

Marsh Posté le 31-12-2007 à 15:06:22

Ik12 a écrit :

Faut configurer ton routeur pour que toutes les connections http soit renvoyer vers ton serveur.

effectivement les ports forwardés sur ta freebox on s'en fou (8080), il faut forwarder le port 80 vers l'ip de ton serveur (port 80 également)

---------------
Blog photo/récits activités en montagne http://planetcaravan.net

Reply

Marsh Posté le 31-12-2007 à 15:12:45

A IK12 :

Mais je croyais que c'était ce que j'avais fait en redirigeant les ports 8080 tcp/udp vers l'ip locale de mon serveur 192.168.0.2 ?

A zecrazytux :

oui je sais mais il s'agit de teste actuellement comme je l'ai préciser. De toute façon un DocumentRoot sur /home/monSite/www avait aussi précédemment échoué.

Et pour information j'ai déjà essayer de rerouter le port 80, mais là il n'accède carément pas au serveur. Il me met "serveur inaccessible".

Je vais recommencer avec le port 80, on va voir

"effectivement les ports forwardés sur ta freebox on s'en fou (8080)", je ne comprend plus je croyais que c'était cette configuration qui orientait les requête de l'extérieur vers la bonne machine de l'intranet ????

Reply

Marsh Posté le 31-12-2007 à 15:17:34

Citation :

A IK12 :

Mais je croyais que c'était ce que j'avais fait en redirigeant les ports 8080 tcp/udp vers l'ip locale de mon serveur 192.168.0.2 ?

HTTP c'est port 80 en TCP

Citation :

A zecrazytux :

oui je sais mais il s'agit de teste actuellement comme je l'ai préciser. De toute façon un DocumentRoot sur /home/monSite/www avait aussi précédemment échoué.

C'est crade, test ou pas ! pourquoi ne pas laisser /var/www/ ?

Citation :

Et pour information j'ai déjà essayer de rerouter le port 80, mais là il n'accède carément pas au serveur. Il me met "serveur inaccessible".

justement le port forwarding était bon, et le serveur inacessible car tes regles iptables t'empêchait d'y acceder !

Citation :

"effectivement les ports forwardés sur ta freebox on s'en fou (8080)", je ne comprend plus je croyais que c'était cette configuration qui orientait les requête de l'extérieur vers la bonne machine de l'intranet ????

pas sur le port 8080 sauf config bizarroide de ta part (un listen 8080 pour apache) et de toute façon un client va acceder à ton site via le port 80 donc la redirection était de toute façon incorrecte. (ne sert a rien)

Message édité par zecrazytux le 31-12-2007 à 15:18:45

---------------
Blog photo/récits activités en montagne http://planetcaravan.net

Reply

Marsh Posté le 31-12-2007 à 15:20:15

voila j'ai changer le port 8080 en port 80 sur tcp et udp.

Voici je message d'erreur à présent :

Code :

un problème s'est produit lors du chargement de http://82.XXX.XXX.XXX
impossible de se connecter à l'hote 82.XXX.XXX.XXX

A noter que j'ai déjà mis un serveur de ce type en place sur une mandrake avec plein de virtualhost qui marchait très bien...

Reply

Marsh Posté le 31-12-2007 à 15:34:49

80 udp pas besoin, le http c'est du TCP.

as tu ouvert le port 80 sur ton serveur comme je te l'ai déja dit 3 fois ?

---------------
Blog photo/récits activités en montagne http://planetcaravan.net

Reply

Marsh Posté le 31-12-2007 à 15:34:49

Reply

Marsh Posté le 31-12-2007 à 15:40:34

Ce n'est pas le peine d'être désagréable. J'essaye d'apprendre c'est tout.

Oui j'ai fait cette manipulation et j'ai ouvert SEULEMENT le port 80 tcp.

Mais il faut peut être que je redémarre complètement ma machine.

Message cité 1 fois

Reply

Marsh Posté le 31-12-2007 à 15:47:56

Il n'y a pas besoin de redémarrer ta machine pour quoi que ce soit.
Met la configuration qui marche pour le réseau local.
Met sur la freebox le forward de port pour le port 80 vers l'adresse de ta machine et :
- soit teste depuis l'extérieur de ton réseau (un ami, un cyber café...)
- soit teste depuis ton réseau mais en utilisant un proxy qui lui se trouve sur internet.

Ne teste pas en utilisant ton adresse public depuis ton réseau local.

Message édité par o'gure le 31-12-2007 à 15:48:45

---------------
Relax. Take a deep breath !

Reply

Marsh Posté le 31-12-2007 à 15:55:11

Alors je ne comprends plus.

ça signifie que je ne peux pas accéder à mon site internet à partir d'un poste du réseaux local, même si j'utilise internet. (Ex http://ip_public/mon_fichier.php) ?

Je croyais que c'était possible ??!!!

Reply

Marsh Posté le 31-12-2007 à 15:58:37

Ca dépend des routeurs, certains "n'aiment pas" ce genre de trafic. Pour la freebox je ne suis pas sûr (il me semble avoir déja eut des cas sur ce forum avec la freebox), c'est pour ca que je te donne la bonne manière pour tester correctement de manière sûre !

Ceci s'explique par le fait que certains routeurs mettent la règle du NAT (redirection de trafic pour le port 80 dans notre cas) uniquement pour le trafic qui provient réellement d'internet. La ton trafic provient du LAN, il se peut qui ne soit pas confronté.
Pour comprendre un peu mieux, renseigne toi par exemple sur comment marche netfilter.

edit: et ta phrase :
"ça signifie que je ne peux pas accéder à mon site internet à partir d'un poste du réseaux local, même si j'utilise internet."
n'est pas claire.

Ca veut juste dire que depuis ton LAN tu utilises l'adresse privée, et depuis internet tu utilises l'adresse public. C'est tout.

Message cité 1 fois
Message édité par o'gure le 31-12-2007 à 16:04:26

---------------
Relax. Take a deep breath !

Reply

Marsh Posté le 31-12-2007 à 16:24:43

o'gure a écrit :

Ca dépend des routeurs, certains "n'aiment pas" ce genre de trafic. Pour la freebox je ne suis pas sûr (il me semble avoir déja eut des cas sur ce forum avec la freebox), c'est pour ca que je te donne la bonne manière pour tester correctement de manière sûre !

Mon site/blog est hébergé dans mon placard derrière une freebox et je n'ai aucun problème.

---------------
Blog photo/récits activités en montagne http://planetcaravan.net

Reply

Marsh Posté le 31-12-2007 à 16:29:09

jamesbond2 a écrit :

Ce n'est pas le peine d'être désagréable. J'essaye d'apprendre c'est tout.

Oui j'ai fait cette manipulation et j'ai ouvert SEULEMENT le port 80 tcp.

Mais il faut peut être que je redémarre complètement ma machine.

je ne suis pas désagréable. C'est toi qui a certainement mal pris le "comme je te l'ai déja dit 3 fois ?", mais je ne pouvais pas deviner puisque tu n'avais pas confirmé l'avoir fait !

D'ailleurs cette directive, il serai bon que tu l'intègre à ton script de filtrage car au redémarrage elle n'y sera plus.

bon, qu'on y voit un peu plus clair:

iptable -L
netstat -lapute
nmap ip_du_serveur

---------------
Blog photo/récits activités en montagne http://planetcaravan.net

Reply

Marsh Posté le 31-12-2007 à 16:33:17

cette manipulation : "iptable -A INPUT -p tcp --dport 80 -j ACCEPT " est-elle a effectuer à chaque fois que je redémarre ma machine ou un fois suffit ?

Ceci étant, le problème reste entier.

Ce qui me surprend le plus, c'est qu'un serveur mandrake 10 derrière une freebox (sur mon lieu de travail) avait déjà accueilli notre serveur interne de sauvegarde et ce serveur était tout à fait accessible depuis l'intranet par son ip public...

y aurait-il un paramètrage quelconque au niveau de mon firewall peut être ?

Reply

Marsh Posté le 31-12-2007 à 16:42:18

effectivement j'avais mal compris....

iptables -L :

Code :

Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT udp -- anywhere anywhere udp dpt:domain
ACCEPT tcp -- anywhere anywhere tcp dpt:domain
ACCEPT udp -- anywhere anywhere udp dpt:bootps
ACCEPT tcp -- anywhere anywhere tcp dpt:bootps
RH-Firewall-1-INPUT all -- anywhere anywhere
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere 192.168.122.0/24 state RELATED,ESTABLISHED
ACCEPT all -- 192.168.122.0/24 anywhere
ACCEPT all -- anywhere anywhere
REJECT all -- anywhere anywhere reject-with icmp-port-unreachable
REJECT all -- anywhere anywhere reject-with icmp-port-unreachable
REJECT all -- anywhere anywhere reject-with icmp-host-prohibited
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain RH-Firewall-1-INPUT (1 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT icmp -- anywhere anywhere icmp any
ACCEPT esp -- anywhere anywhere
ACCEPT ah -- anywhere anywhere
ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns
ACCEPT udp -- anywhere anywhere udp dpt:ipp
ACCEPT tcp -- anywhere anywhere tcp dpt:ipp
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh
REJECT all -- anywhere anywhere reject-with icmp-host-prohibited

netstat -lapute :

Code :

Connexions Internet actives (serveurs et établies)
Proto Recv-Q Send-Q Local Address Foreign Address State Utilisatr Inode PID/Program name
tcp 0 0 hometranet:irdmi *:* LISTEN root 5342 2425/nasd
tcp 0 0 *:sunrpc *:* LISTEN root 4536 2169/rpcbind
tcp 0 0 192.168.122.1:domain *:* LISTEN root 5622 2613/dnsmasq
tcp 0 0 hometranet:ipp *:* LISTEN root 5644 2614/cupsd
tcp 0 0 hometranet:smtp *:* LISTEN root 5285 2406/sendmail: acce
tcp 0 0 *:46271 *:* LISTEN root 4666 2188/rpc.statd
tcp 0 0 *:http *:* LISTEN root 8452 3103/httpd
tcp 0 0 *:ssh *:* LISTEN root 5155 2385/sshd
tcp 0 0 *:https *:* LISTEN root 8456 3103/httpd
udp 0 0 *:filenet-tms *:* root 4663 2188/rpc.statd
udp 0 0 *:filenet-rpc *:* avahi 5453 2522/avahi-daemon:
udp 0 0 *:filenet-nch *:* nobody 5630 2613/dnsmasq
udp 0 0 *:rrp *:* root 4535 2169/rpcbind
udp 0 0 192.168.122.1:domain *:* root 5623 2613/dnsmasq
udp 0 0 *:bootps *:* root 5615 2613/dnsmasq
udp 0 0 *:708 *:* root 4658 2188/rpc.statd
udp 0 0 *:bootpc *:* root 4256 2070/dhclient
udp 0 0 *:mdns *:* avahi 5452 2522/avahi-daemon:
udp 0 0 *:sunrpc *:* root 4532 2169/rpcbind
udp 0 0 *:ipp *:* root 5647 2614/cupsd

nmap 82.XXX.XXX.XXX

Code :

Starting Nmap 4.20 ( http://insecure.org ) at 1999-06-12 16:40 CEST
Interesting ports on vil69-6-82-239-196-198.fbx.proxad.net (82.239.196.198):
Not shown: 1695 filtered ports
PORT STATE SERVICE
554/tcp open rtsp
9100/tcp open jetdirect
Nmap finished: 1 IP address (1 host up) scanned in 20.506 seconds

Reply

Marsh Posté le 31-12-2007 à 17:10:42

Le problème est que le port 80 n'est pas ouvert sur ton serveur. Si tu as bien tappé mon commande c'est étonnant...

je ne connais pas fedora (quelques tests il y a quelques années), essai de trouver où configurer le firewall ou où est placé le script de filtrage iptable.

J'ai l'habitude de scripter moi même un iptable-start et stop

en tout cas il te faut la règle suivante:
iptables -A INPUT -p tcp --dport 80 -j ACCEPT

au démarrage !

edit: pas si étonnant, puisque la regle est rajouté après la policy rh-firewall-1-input qui prend tout le reste.
il faut au choix: modifier la policy rh-firewall-1-input pour y associer l'ouverture du port 80, soit ouvrir le port 80 avant d'appliquer la policy rh-...

pour tester: regles de bases pour accepter seulement http
(vide les regles iptables et autorise le port 80)

iptables -F
iptables -P INPUT DROP
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
iptables -A INPUT -i lo -j ACCEPT
iptables -A INPUT -p tcp --dport 80 -j ACCEPT

Message édité par zecrazytux le 31-12-2007 à 17:19:25

---------------
Blog photo/récits activités en montagne http://planetcaravan.net

Reply

Marsh Posté le 31-12-2007 à 17:34:14

Voici le iptables après avoir effectué tes instructions :

Code :

Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT tcp -- anywhere anywhere tcp dpt:http
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain RH-Firewall-1-INPUT (0 references)
target prot opt source destination

Reply

Marsh Posté le 31-12-2007 à 17:45:57

ça me semble correct.

un nmap sur l'ip du serveur devrait te donner une ligne:

80/tcp OPEN www ou http

et ton serveur devrait être joignable du reseau local ou du net si le port forwarding est correctement configuré

---------------
Blog photo/récits activités en montagne http://planetcaravan.net

Reply

Marsh Posté le 31-12-2007 à 17:53:10

le souci c'est que les instructions précédentes m'ont coupé d'internet, j'ai du redémarrer la machine.

Donc au démarrage je refais un :

Code :

iptables -A INPUT -p tcp --dport 80 -j ACCEPT

mais le nmap de me donne que :

Code :

544/tcp open rtsp
9100/tcp open jetdirect

Faut-il qu'à chaque redémarrage je fasse toutes les instructions que tu m'a précisé ou le "iptables -A INPUT..." suffit ?

Reply

Marsh Posté le 31-12-2007 à 18:08:45

Citation :

le souci c'est que les instructions précédentes m'ont coupé d'internet, j'ai du redémarrer la machine.

Coupé internet de qui ? tu poste depuis le serveur ? tu accede au net en NAT derrière ce serveur ?

mes instructions autorisent seulement le port 80 en entrée. (tout en sortie, pas de ping)

Citation :

Code :

iptables -A INPUT -p tcp --dport 80 -j ACCEPT

mais le nmap de me donne que :

Code :

544/tcp open rtsp
9100/tcp open jetdirect

oui, comme dit dans mon "edit" d'un post précédent la règle est inefficace car après la policy rh-firewall-1-input.
insère là plutôt de cette manière:
iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT

celà aura pour effet d'insérer la règle en première position

Citation :

Faut-il qu'à chaque redémarrage je fasse toutes les instructions que tu m'a précisé ou le "iptables -A INPUT..." suffit ?

Avec l'insertion, seule cette instruction suffit. il faudrait l'ajouter dans un script pour eviter d'avoir a faire ça à la main à chaque fois

---------------
Blog photo/récits activités en montagne http://planetcaravan.net

Reply

Marsh Posté le 31-12-2007 à 18:18:20

SUPER !!!

j'ai saisi le nouvel iptables et mon nmap me renvoie bien

80/tcp open http

et l'url suivante marche à présent http://82.XXX.XXX.XXX/index.html

Donc en gros tu dis au firewall de laisser passer les requetes du port 80 ? c'est ça ?

Cela dois venir du firewall fedora, car avec mon ancienne mandrake, je n'ai jamais eu à faire ça...

Message cité 1 fois

Reply

Marsh Posté le 31-12-2007 à 18:30:15

jamesbond2 a écrit :

SUPER !!!

j'ai saisi le nouvel iptables et mon nmap me renvoie bien

80/tcp open http

et l'url suivante marche à présent http://82.XXX.XXX.XXX/index.html

Donc en gros tu dis au firewall de laisser passer les requetes du port 80 ? c'est ça ?

Cela dois venir du firewall fedora, car avec mon ancienne mandrake, je n'ai jamais eu à faire ça...

vi, alors le mieux pour comprendre tout ça c'est de lire un ti tuto iptables

en vitesse:

Des règles de filtrage iptables te permettent de décider quels ports ports sont ouverts ou fermés. de cette manière tu peux autoriser ou non des protocoles puisque ceux-cis utilisent un ou plusieurs ports, généralement définis (fixes)

Ainsi tu désire ouvrir le port 80 en entrée (tu est serveur, ce sont tes visiteurs qui viennent chez toi).
on ajoute/insere donc une regle pour celà dans la chaine INPUT.

Or la chain INPUT laisse une partie du filtrage à une chaine crée par fedora, la fameuse chaine RH-Firewall-1-INPUT
D'autres règles de filtrage sont donc définies dans cette chaine propre à fedora (red hat)

C'est pour ne pas mélanger les règles de base et les règles par défaut du niveau de sécurité de fedora (il y a en a plusieurs, au moins 3 de tête, et tu peux remarquer le chiffre 1 dans le nom de la chaine je supose donc que tu a choisis un niveau de sécurité faible pour ta distro )

sur Mandriva, c'est shorewall qui est utilisé maintenant afin de définir les règles iptables mais je ne sais pas ce qui était mis en place sur la mandrake 10.
Tout celà varie celon les distros, à toi de t'adapter à celle que tu utilise (et de lire sa doc correspondante ). Sous Debian par exemple tout est ouvert, il n'y a pas de règle, pas de firewall, on écris nous même les règles.

---------------
Blog photo/récits activités en montagne http://planetcaravan.net

Reply

Marsh Posté le 31-12-2007 à 18:36:02

ok d'acc

Merci beaucoup en tout cas et BONNE ANNEE

Bye

Reply

Marsh Posté le

Reply

Accès serveur apache par ip externe impossible ?

Sujets relatifs:

Leave a Replay