نمایش نتایج: از شماره 1 تا 9 از مجموع 9
سپاس ها 1سپاس

موضوع: Squid Transparent

  
  1. #1
    نام حقيقي: ایمان قربانعلی

    خواننده شناسه تصویری Iman.gh
    تاریخ عضویت
    Jul 2005
    محل سکونت
    Iran - Tehran
    نوشته
    832
    سپاسگزاری شده
    305
    سپاسگزاری کرده
    177

    Squid Transparent

    سلام

    من squid را روی centos نصب کردم و کارم میکنه فقط transparent کار نمی کنه و تنظیماتشم عین اموزش اقای حکیمی انجام دادم تنظیم Linux و Squid به عنوان Web Proxy

    و 1 مشکل دیگه چی کار کنم تا وقتی پشت squid هستم https باز بشه ؟؟؟



    موضوعات مشابه:

  2. #2
    نام حقيقي: Peyman Yousefi

    عضو ویژه شناسه تصویری darklove
    تاریخ عضویت
    Oct 2005
    محل سکونت
    ABHAR
    نوشته
    3,330
    سپاسگزاری شده
    1005
    سپاسگزاری کرده
    318
    نوشته های وبلاگ
    7
    میشه تنظیمات شما را دید ؟



  3. #3
    نام حقيقي: ایمان قربانعلی

    خواننده شناسه تصویری Iman.gh
    تاریخ عضویت
    Jul 2005
    محل سکونت
    Iran - Tehran
    نوشته
    832
    سپاسگزاری شده
    305
    سپاسگزاری کرده
    177
    squid.conf

    # WELCOME TO SQUID 2
    # ------------------
    #
    # This is the default Squid configuration file. You may wish
    # to look at the Squid home page (squid : Optimising Web Delivery)
    # for the FAQ and other documentation.
    #
    # The default Squid config file shows what the defaults for
    # various options happen to be. If you don't need to change the
    # default, you shouldn't uncomment the line. Doing so may cause
    # run-time problems. In some cases "none" refers to no default
    # setting at all, while in other cases it refers to a valid
    # option - the comments for that keyword indicate if this is the
    # case.
    #
    # This line was added to make rpm -U Do The Right Thing (interim fix)


    # NETWORK OPTIONS
    # -----------------------------------------------------------------------------

    # TAG: http_port
    # Usage: port
    # hostnameort
    # 1.2.3.4ort
    #
    # The socket addresses where Squid will listen for HTTP client
    # requests. You may specify multiple socket addresses.
    # There are three forms: port alone, hostname with port, and
    # IP address with port. If you specify a hostname or IP
    # address, Squid binds the socket to that specific
    # address. This replaces the old 'tcp_incoming_address'
    # option. Most likely, you do not need to bind to a specific
    # address, so you can use the port number alone.
    #
    # The default port number is 3128.
    #
    # If you are running Squid in accelerator mode, you
    # probably want to listen on port 80 also, or instead.
    #
    # The -a command line option will override the *first* port
    # number listed here. That option will NOT override an IP
    # address, however.
    #
    # You may specify multiple socket addresses on multiple lines.
    #
    # If you run Squid on a dual-homed machine with an internal
    # and an external interface we recommend you to specify the
    # internal addressort in http_port. This way Squid will only be
    # visible on the internal address.
    #
    Default:
    http_port 3128

    # TAG: https_port
    # Usage: [ip:]port cert=certificate.pem [key=key.pem] [options...]
    #
    # The socket address where Squid will listen for HTTPS client
    #
    # The socket address where Squid will listen for HTTPS client
    # requests.
    #
    # This is really only useful for situations where you are running
    # squid in accelerator mode and you want to do the SSL work at the
    # accelerator level.
    #
    # You may specify multiple socket addresses on multiple lines,
    # each with their own SSL certificate and/or options.
    #
    # Options:
    #
    # cert= Path to SSL certificate (PEM format)
    #
    # key= Path to SSL private key file (PEM format)
    # if not specified, the certificate file is
    # assumed to be a combined certificate and
    # key file
    #
    # version= The version of SSL/TLS supported
    # 1 automatic (default)
    # 2 SSLv2 only
    # 3 SSLv3 only
    # 4 TLSv1 only
    #
    # cipher= Colon separated list of supported ciphers
    #
    # options= Various SSL engine options. The most important
    # being:
    # NO_SSLv2 Disallow the use of SSLv2
    # NO_SSLv3 Disallow the use of SSLv3
    # NO_TLSv1 Disallow the use of TLSv1
    # See src/ssl_support.c or OpenSSL documentation
    # for a more complete list.
    #
    #Default:
    # none

    # TAG: ssl_unclean_shutdown
    # Some browsers (especially MSIE) bugs out on SSL shutdown
    # messages.
    #
    #Default:
    # ssl_unclean_shutdown off

    # TAG: icp_port
    # The port number where Squid sends and receives ICP queries to
    # and from neighbor caches. Default is 3130. To disable use
    # "0". May be overridden with -u on the command line.
    #
    #Default:
    # icp_port 3130

    # TAG: htcp_port
    # Note: This option is only available if Squid is rebuilt with the
    # --enable-htcp option
    #
    # The port number where Squid sends and receives HTCP queries to
    #
    # The port number where Squid sends and receives HTCP queries to
    # and from neighbor caches. Default is 4827. To disable use
    # "0".
    #
    #Default:
    # htcp_port 4827

    # TAG: mcast_groups
    # This tag specifies a list of multicast groups which your server
    # should join to receive multicasted ICP queries.
    #
    # NOTE! Be very careful what you put here! Be sure you
    # understand the difference between an ICP _query_ and an ICP
    # _reply_. This option is to be set only if you want to RECEIVE
    # multicast queries. Do NOT set this option to SEND multicast
    # ICP (use cache_peer for that). ICP replies are always sent via
    # unicast, so this option does not affect whether or not you will
    # receive replies from multicast group members.
    #
    # You must be very careful to NOT use a multicast address which
    # is already in use by another group of caches.
    #
    # If you are unsure about multicast, please read the Multicast
    # chapter in the Squid FAQ (Squid FAQ has moved).
    #
    # Usage: mcast_groups 239.128.16.128 224.0.1.20
    #
    # By default, Squid doesn't listen on any multicast groups.
    #
    #Default:
    # none

    # TAG: udp_incoming_address
    # TAG: udp_outgoing_address
    # udp_incoming_address is used for the ICP socket receiving packets
    # from other caches.
    # udp_outgoing_address is used for ICP packets sent out to other
    # caches.
    #
    # The default behavior is to not bind to any specific address.
    #
    # A udp_incoming_address value of 0.0.0.0 indicates Squid
    # should listen for UDP messages on all available interfaces.
    #
    # If udp_outgoing_address is set to 255.255.255.255 (the default)
    # it will use the same socket as udp_incoming_address. Only
    # change this if you want to have ICP queries sent using another
    # address than where this Squid listens for ICP queries from other
    # caches.
    #
    # NOTE, udp_incoming_address and udp_outgoing_address can not
    # have the same value since they both use port 3130.
    #
    #Default:
    # udp_incoming_address 0.0.0.0
    # udp_outgoing_address 255.255.255.255
    OPTIONS WHICH AFFECT THE NEIGHBOR SELECTION ALGORITHM
    # -----------------------------------------------------------------------------

    # TAG: cache_peer
    # To specify other caches in a hierarchy, use the format:
    #
    # cache_peer hostname type http_port icp_port
    #
    # For example,
    #
    # # proxy icp
    # # hostname type port port options
    # # -------------------- -------- ----- ----- -----------
    # cache_peer parent.foo.net parent 3128 3130 [proxy-only]
    # cache_peer sib1.foo.net sibling 3128 3130 [proxy-only]
    # cache_peer sib2.foo.net sibling 3128 3130 [proxy-only]
    #
    # type: either 'parent', 'sibling', or 'multicast'.
    #
    # proxy_port: The port number where the cache listens for proxy
    # requests.
    #
    # icp_port: Used for querying neighbor caches about
    # objects. To have a non-ICP neighbor
    # specify '7' for the ICP port and make sure the
    # neighbor machine has the UDP echo port
    # enabled in its /etc/inetd.conf file.
    #
    # options: proxy-only
    # weight=n
    # ttl=n
    # no-query
    # default
    # round-robin
    # multicast-responder
    # closest-only
    # no-digest
    # no-netdb-exchange
    # no-delay
    # login=userassword | PASS | *assword
    # connect-timeout=nn
    # digest-url=url
    # allow-miss
    # max-conn
    # htcp
    # carp-load-factor
    #
    # use 'proxy-only' to specify objects fetched
    # from this cache should not be saved locally.
    #
    # use 'weight=n' to specify a weighted parent.
    # The weight must be an integer. The default weight
    # is 1, larger weights are favored more.
    #
    # use 'ttl=n' to specify a IP multicast TTL to use
    # when sending an ICP queries to this address.
    # Only useful when sending to a multicast group.
    # * When multiple domains are given for a particular
    # cache-host, the first matched domain is applied.
    # * Cache hosts with no domain restrictions are queried
    # for all requests.
    # * There are no defaults.
    # * There is also a 'cache_peer_access' tag in the ACL
    # section.
    #
    #Default:
    # none

    # TAG: neighbor_type_domain
    # usage: neighbor_type_domain neighbor parent|sibling domain domain ...
    #
    # Modifying the neighbor type for specific domains is now
    # possible. You can treat some domains differently than the the
    # default neighbor type specified on the 'cache_peer' line.
    # Normally it should only be necessary to list domains which
    # should be treated differently because the default neighbor type
    # applies for hostnames which do not match domains listed here.
    #
    #EXAMPLE:
    # cache_peer parent cache.foo.org 3128 3130
    # neighbor_type_domain cache.foo.org sibling .com .net
    # neighbor_type_domain cache.foo.org sibling .au .de
    #
    #Default:
    # none

    # TAG: icp_query_timeout (msec)
    # Normally Squid will automatically determine an optimal ICP
    # query timeout value based on the round-trip-time of recent ICP
    # queries. If you want to override the value determined by
    # Squid, set this 'icp_query_timeout' to a non-zero value. This
    # value is specified in MILLISECONDS, so, to use a 2-second
    # timeout (the old default), you would write:
    #
    # icp_query_timeout 2000
    #
    #Default:
    # icp_query_timeout 0

    # TAG: maximum_icp_query_timeout (msec)
    # Normally the ICP query timeout is determined dynamically. But
    # sometimes it can lead to very large values (say 5 seconds).
    # Use this option to put an upper limit on the dynamic timeout
    # value. Do NOT use this option to always use a fixed (instead
    # of a dynamic) timeout value. To set a fixed timeout see the
    # 'icp_query_timeout' directive.
    #
    #Default:
    # maximum_icp_query_timeout 2000

    # TAG: mcast_icp_query_timeout (msec)
    # For Multicast peers, Squid regularly sends out ICP "probes" to
    # count how many other peers are listening on the given multicast
    # address. This value specifies how long Squid should wait to
    # count all the replies. The default is 2000 msec, or 2
    # seconds.
    # count all the replies. The default is 2000 msec, or 2
    # seconds.
    #
    #Default:
    # mcast_icp_query_timeout 2000

    # TAG: dead_peer_timeout (seconds)
    # This controls how long Squid waits to declare a peer cache
    # as "dead." If there are no ICP replies received in this
    # amount of time, Squid will declare the peer dead and not
    # expect to receive any further ICP replies. However, it
    # continues to send ICP queries, and will mark the peer as
    # alive upon receipt of the first subsequent ICP reply.
    #
    # This timeout also affects when Squid expects to receive ICP
    # replies from peers. If more than 'dead_peer' seconds have
    # passed since the last ICP reply was received, Squid will not
    # expect to receive an ICP reply on the next query. Thus, if
    # your time between requests is greater than this timeout, you
    # will see a lot of requests sent DIRECT to origin servers
    # instead of to your parents.
    #
    #Default:
    # dead_peer_timeout 10 seconds

    # TAG: hierarchy_stoplist
    # A list of words which, if found in a URL, cause the object to
    # be handled directly by this cache. In other words, use this
    # to not query neighbor caches for certain objects. You may
    # list this option multiple times. Note: never_direct overrides
    # this option.
    #We recommend you to use at least the following line.
    hierarchy_stoplist cgi-bin ?

    # TAG: no_cache
    # A list of ACL elements which, if matched, cause the request to
    # not be satisfied from the cache and the reply to not be cached.
    # In other words, use this to force certain objects to never be cached.
    #
    # You must use the word 'DENY' to indicate the ACL names which should
    # NOT be cached.
    #
    #We recommend you to use the following two lines.
    acl QUERY urlpath_regex cgi-bin \?
    no_cache deny QUERY


    # OPTIONS WHICH AFFECT THE CACHE SIZE
    # -----------------------------------------------------------------------------

    # TAG: cache_mem (bytes)
    # NOTE: THIS PARAMETER DOES NOT SPECIFY THE MAXIMUM PROCESS SIZE.
    # IT ONLY PLACES A LIMIT ON HOW MUCH ADDITIONAL MEMORY SQUID WILL
    # USE AS A MEMORY CACHE OF OBJECTS. SQUID USES MEMORY FOR OTHER
    # THINGS AS WELL. SEE THE SQUID FAQ SECTION 8 FOR DETAILS.
    #
    # 'cache_mem' specifies the ideal amount of memory to be used
    # for:
    # * In-Tra# TAG: http_access
    # Allowing or Denying access based on defined access lists
    #
    # Access to the HTTP port:
    # http_access allow|deny [!]aclname ...
    #
    # NOTE on default values:
    #
    # If there are no "access" lines present, the default is to deny
    # the request.
    #
    # If none of the "access" lines cause a match, the default is the
    # opposite of the last line in the list. If the last line was
    # deny, the default is allow. Conversely, if the last line
    # is allow, the default will be deny. For these reasons, it is a
    # good idea to have an "deny all" or "allow all" entry at the end
    # of your access lists to avoid potential confusion.
    #
    #Default:
    # http_access deny all
    #
    #Recommended minimum configuration:
    #
    # Only allow cachemgr access from localhost
    http_access allow manager localhost
    http_access deny manager
    # Deny requests to unknown ports
    http_access deny !Safe_ports
    # Deny CONNECT to other than SSL ports
    http_access deny CONNECT !SSL_ports
    #
    # We strongly recommend the following be uncommented to protect innocent
    # web applications running on the proxy server who think the only
    # one who can access services on "localhost" is a local user
    #http_access deny to_localhost
    #
    # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS

    # Example rule allowing access from your local networks. Adapt
    # to list your (internal) IP networks from where browsing should
    # be allowed
    acl our_networks src 94.101.187.32/27
    http_access allow our_networks

    # And finally deny all other access to this proxy
    http_access allow localhost
    http_access deny all

    # TAG: http_reply_access

    # TAG: httpd_accel_single_host on|off
    # If you are running Squid as an accelerator and have a single backend
    # server set this to on. This causes Squid to forward the request
    # to this server, regardless of what any redirectors or Host headers
    # say.
    #
    # Leave this at off if you have multiple backend servers, and use a
    # redirector (or host table or private DNS) to map the requests to the
    # appropriate backend servers. Note that the mapping needs to be a
    # 1-1 mapping between requested and backend (from redirector) domain
    # names or caching will fail, as caching is performed using the
    # URL returned from the redirector.
    #
    # See also redirect_rewrites_host_header.
    #
    Default:
    httpd_accel_single_host on

    # TAG: httpd_accel_with_proxy on|off
    # If you want to use Squid as both a local httpd accelerator
    # and as a proxy, change this to 'on'. Note however your
    # proxy users may have trouble to reach the accelerated domains
    # unless their browsers are configured not to use this proxy for
    # those domains (for example via the no_proxy browser configuration
    # setting)
    #
    Default:
    httpd_accel_with_proxy on

    # TAG: httpd_accel_uses_host_header on|off
    # HTTP/1.1 requests include a Host: header which is basically the
    # hostname from the URL. The Host: header is used for domain based
    # virtual hosts. If your accelerator needs to provide domain based
    # virtual hosts on the same IP address you will need to turn this
    # on.
    #
    # Note Squid does NOT check the value of the Host header matches
    # any of your accelerated server, so it may open a big security hole
    # unless you take care to set up access controls proper. We recommend
    # this option remain disabled unless you are sure of what you
    # are doing.
    #
    # However, you will need to enable this option if you run Squid
    # as a transparent proxy. Otherwise, virtual servers which
    # require the Host: header will not be properly cached.
    #
    Default:
    httpd_accel_uses_host_header on

    # TAG: httpd_accel_no_pmtu_disc on|off
    # In many setups of transparently intercepting proxies Path-MTU
    # discovery can not work on traffic towards the clients. This is
    # the case when the intercepting device does not fully track
    # connections and fails to forward ICMP must fragment messages
    # to the cache server.
    #
    # If you have such setup and experience that certain clients
    # sporadically hang or never complete requests set this to on.

    # If you have such setup and experience that certain clients
    # sporadically hang or never complete requests set this to on.
    #
    #Default:
    # httpd_accel_no_pmtu_disc off


    # MISCELLANEOUS
    # -----------------------------------------------------------------------------

    # TAG: dns_testnames
    # The DNS tests exit as soon as the first site is successfully looked up
    #
    # This test can be disabled with the -D command line option.
    #
    #Default:
    # dns_testnames netscape.com internic.net nlanr.net microsoft.com

    # TAG: logfile_rotate
    # Specifies the number of logfile rotations to make when you
    # type 'squid -k rotate'. The default is 10, which will rotate
    # with extensions 0 through 9. Setting logfile_rotate to 0 will
    # disable the rotation, but the logfiles are still closed and
    # re-opened. This will enable you to rename the logfiles
    # yourself just before sending the rotate signal.
    #
    # Note, the 'squid -k rotate' command normally sends a USR1
    # signal to the running squid process. In certain situations
    # (e.g. on Linux with Async I/O), USR1 is used for other
    # purposes, so -k rotate uses another signal. It is best to get
    # in the habit of using 'squid -k rotate' instead of 'kill -USR1
    # <pid>'.
    #
    #logfile_rotate 0
    #
    #Default:
    # logfile_rotate 0

    # TAG: append_domain
    # Appends local domain name to hostnames without any dots in
    # them. append_domain must begin with a period.
    #
    # Be warned there are now Internet names with no dots in
    # them using only top-domain names, so setting this may
    # cause some Internet sites to become unavailable.
    #
    #Example:
    # append_domain .yourdomain.com
    #
    #Default:
    # none

    # TAG: tcp_recv_bufsize (bytes)
    # Size of receive buffer to set for TCP sockets. Probably just
    # as easy to change your kernel's default. Set to zero to use
    # the default buffer size.
    #
    #Default:
    # tcp_recv_bufsize 0 bytes

    # An overhead for maintaining memory pools is not taken into account
    # when the limit is checked. This overhead is close to four bytes per
    # object kept. However, pools may actually _save_ memory because of
    # reduced memory thrashing in your malloc library.
    #
    #Default:
    # memory_pools_limit 5 MB

    # TAG: forwarded_for on|off
    # If set, Squid will include your system's IP address or name
    # in the HTTP requests it forwards. By default it looks like
    # this:
    #
    # X-Forwarded-For: 192.1.2.3
    #
    # If you disable this, it will appear as
    #
    # X-Forwarded-For: unknown
    #
    #Default:
    # forwarded_for on

    # TAG: log_icp_queries on|off
    # If set, ICP queries are logged to access.log. You may wish
    # do disable this if your ICP load is VERY high to speed things
    # up or to simplify log analysis.
    #
    #Default:
    # log_icp_queries on

    # TAG: icp_hit_stale on|off
    # If you want to return ICP_HIT for stale cache objects, set this
    # option to 'on'. If you have sibling relationships with caches
    # in other administrative domains, this should be 'off'. If you only
    # have sibling relationships with caches under your control,
    # it is probably okay to set this to 'on'.
    # If set to 'on', your siblings should use the option "allow-miss"
    # on their cache_peer lines for connecting to you.
    #
    #Default:
    # icp_hit_stale off

    # TAG: minimum_direct_hops
    # If using the ICMP pinging stuff, do direct fetches for sites
    # which are no more than this many hops away.
    #
    #Default:
    # minimum_direct_hops 4

    # TAG: minimum_direct_rtt




  4. #4
    نام حقيقي: ایمان قربانعلی

    خواننده شناسه تصویری Iman.gh
    تاریخ عضویت
    Jul 2005
    محل سکونت
    Iran - Tehran
    نوشته
    832
    سپاسگزاری شده
    305
    سپاسگزاری کرده
    177
    iptables

    -A INPUT -j RH-Firewall-1-INPUT
    -A FORWARD -j RH-Firewall-1-INPUT
    -A RH-Firewall-1-INPUT -i lo -j ACCEPT
    -A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT
    -A RH-Firewall-1-INPUT -p 50 -j ACCEPT
    -A RH-Firewall-1-INPUT -p 51 -j ACCEPT
    -A RH-Firewall-1-INPUT -m state --state NEW,ESTABLISHED,RELATED -m tcp -p tcp --dport 3128 -j ACCEPT
    -A INPUT -p tcp --dport 5051 -j ACCEPT
    -A INPUT -p tcp --dport 5061 -j ACCEPT
    -A INPUT -p tcp --dport 5050 -j ACCEPT
    -A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT
    -A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
    -A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
    -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
    -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
    -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 21 -j ACCEPT
    -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 25 -j ACCEPT
    -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
    COMMIT



  5. #5
    نام حقيقي: علی ابوالحلاج

    عضو عادی شناسه تصویری Abulhallaj
    تاریخ عضویت
    Mar 2003
    محل سکونت
    در پهنه وب
    نوشته
    215
    سپاسگزاری شده
    48
    سپاسگزاری کرده
    22
    کد:
    http_port 3128 transparent




  6. #6
    نام حقيقي: ایمان قربانعلی

    خواننده شناسه تصویری Iman.gh
    تاریخ عضویت
    Jul 2005
    محل سکونت
    Iran - Tehran
    نوشته
    832
    سپاسگزاری شده
    305
    سپاسگزاری کرده
    177
    نقل قول نوشته اصلی توسط Abulhallaj نمایش پست ها
    کد:
    http_port 3128 transparent
    این جواب نداد



  7. #7
    نام حقيقي: x

    عضو عادی
    تاریخ عضویت
    Jun 2009
    محل سکونت
    Internet
    نوشته
    71
    سپاسگزاری شده
    49
    سپاسگزاری کرده
    18
    ترافیک پورت 80 رو روی 3128 ری دایرکت کنید



  8. #8
    نام حقيقي: ایمان قربانعلی

    خواننده شناسه تصویری Iman.gh
    تاریخ عضویت
    Jul 2005
    محل سکونت
    Iran - Tehran
    نوشته
    832
    سپاسگزاری شده
    305
    سپاسگزاری کرده
    177
    سلام
    -A PREROUTING -p tcp -m tcp -s 0.0.0.0/255.255.255.224 --dport 80:3128 -j REDIRECT --to-ports 3128
    من این و نوشتم و وقتی iptables رو ریست کردم این error را می ده

    Applying iptables firewall rules: iptables-restore: line 14 failed
    [FAILED]



  9. #9
    نام حقيقي: Peyman Yousefi

    عضو ویژه شناسه تصویری darklove
    تاریخ عضویت
    Oct 2005
    محل سکونت
    ABHAR
    نوشته
    3,330
    سپاسگزاری شده
    1005
    سپاسگزاری کرده
    318
    نوشته های وبلاگ
    7
    کد:
    iptables -t nat  -A PREROUTING -p tcp -m tcp -s 192.1.1.0/255.255.255.224 --dport 80 -j REDIRECT  --to-port 3128



    mgholami سپاسگزاری کرده است.

کلمات کلیدی در جستجوها:

squid

neighbor selectionaccelerator squid درفعال كردن x-forwarded

برچسب برای این موضوع

مجوز های ارسال و ویرایش

  • شما نمی توانید موضوع جدید ارسال کنید
  • شما نمی توانید به پست ها پاسخ دهید
  • شما نمی توانید فایل پیوست ضمیمه کنید
  • شما نمی توانید پست های خود را ویرایش کنید
  •