Proxy auf vServer einrichten

  • Thread starter Thread starter Sensenmann
  • Start date Start date
S

Sensenmann

Guest
Hallo Leute
Ich wollte auf meinem Debian Server einen Proxy einrichten, damit ich per Homeleitung über diesen Proxy ins Inet kann und meine ServerIp angezeigt wird.

Ist das iwie möglich?
Wenn ja, was ich mal schwer hoffe und denke, was muss ich anstellen?

LG Sense
 
Ich verwende tinyproxy. Aber Achtung: Nur für Deine Home-IP freigeben, oder nur ans Loopback-Interface binden und per SSH-Tunnel darauf zugreifen (so mache ich es).
 
Und dann wird wirklich überall meine ServerIP angezeigt?
 
hmm..die installation scheint mir ziemlich kompliziert...kann mir da evtl. jemand helfen?
 
Code: 
apt-get install tinyproxy

Dann /etc/tinyproxy.conf anpassen und den Proxy mit
Code: 
/etc/init.d/tinyproxy restart
neu starten. Sollte kein Problem sein.
 
und dann?

Was muss ich denn an meinem Laptop (per wlan mit einem Router verbunden) einstellen?
 
Last edited by a moderator:
kannst du mir mal eine beispiels config schicken?
Iwie steige ich da nicht ganz durch
 
Meine /etc/tinyproxy/tinyproxy.conf:

Code: 
#
# Proxy soll unter einem unprivilegierten User laufen
#
User nobody
Group nogroup

#
# Port to listen on.
#
Port 8080

#
# Wird nur ans Loopback-Interface gebunden, ich verbinde mich ja per SSH
# mit dem Server
#
Listen 127.0.0.1

#
# Timeout: The number of seconds of inactivity a connection is allowed to
# have before it closed by tinyproxy.
#
Timeout 600

# 
# DefaultErrorFile: The HTML file that gets sent if there is no
# HTML file defined with an ErrorFile keyword for the HTTP error
# that has occured.
#
DefaultErrorFile "/usr/share/tinyproxy/default.html"

#
# StatFile: The HTML file that gets sent when a request is made
# for the stathost.  If this file doesn't exist a basic page is
# hardcoded in tinyproxy.
#
StatFile "/usr/share/tinyproxy/stats.html"

#
# Where to log the information. Either LogFile or Syslog should be set,
# but not both.
#
Logfile "/var/log/tinyproxy.log"
# Syslog On

# LogLevel
LogLevel Connect

#
# PidFile: Write the PID of the main tinyproxy thread to this file so it
# can be used for signalling purposes.
#
PidFile "/var/run/tinyproxy.pid"

#
# Include the X-Tinyproxy header, which has the client's IP address when
# connecting to the sites listed.
# => deaktiviert lassen, wenn die Client-IP nicht übermittelt werden soll!
#
#XTinyproxy mydomain.com

#
# This is the absolute highest number of threads which will be created. In
# other words, only MaxClients number of clients can be connected at the
# same time.
#
MaxClients 100

#
# These settings set the upper and lower limit for the number of
# spare servers which should be available. If the number of spare servers
# falls below MinSpareServers then new ones will be created. If the number
# of servers exceeds MaxSpareServers then the extras will be killed off.
#
MinSpareServers 5
MaxSpareServers 10

#
# Number of servers to start initially.
#
StartServers 5

#
# MaxRequestsPerChild is the number of connections a thread will handle
# before it is killed. In practise this should be set to 0, which disables
# thread reaping. If you do notice problems with memory leakage, then set
# this to something like 10000
#
MaxRequestsPerChild 0

#
# Zugriff nur von localhost erlauben
#
Allow 127.0.0.1

#
# The "Via" header is required by the HTTP RFC, but using the real host name
# is a security concern.  If the following directive is enabled, the string
# supplied will be used as the host name in the Via header; otherwise, the
# server's host name will be used.
#
ViaProxyName "tinyproxy"

# This is a list of ports allowed by tinyproxy when the CONNECT method
# is used.  To disable the CONNECT method altogether, set the value to 0.
# If no ConnectPort line is found, all ports are allowed (which is not
# very secure.)
#
# The following two ports are used by SSL.
#
ConnectPort 443
ConnectPort 563
 
You must log in or register to reply here.
Back
Top