All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bruno Negrão" <vpopmail@engepel.com.br>
To: netfilter@lists.netfilter.org
Subject: Re: Tunneling other protocols over TCP port 80
Date: Tue, 21 Jun 2005 16:59:56 -0300	[thread overview]
Message-ID: <005201c5769b$cbefdc70$5100a8c0@14bis> (raw)
In-Reply-To: Pine.LNX.4.60.0506211547280.18742@darkstar.sysinfo.com

Hi Ron,

Thanks for the warning. Actually, we already tried to create a PPTP vpn from 
that client to my gateway server, but the remote network administrator couldn't 
manage his equipment to let the appropriate packages to pass. (he doesn't 
understand GRE no way).

I will inform him we're setting up this new vpn tunnel. I just don't want to ask 
him to move, since he doesn't have the skills to make it.

Damon, thanks for the note on the ssh tunnel. Can you point me a document to 
look for this kind of configuration?

Regards,
Bruno.

----- Original Message ----- 
From: "R. DuFresne" <dufresne@sysinfo.com>
To: "Damon Gray" <dgray@internap.com>
Cc: "Bruno Negrão" <vpopmail@engepel.com.br>; <netfilter@lists.netfilter.org>
Sent: Tuesday, June 21, 2005 4:49 PM
Subject: Re: Tunneling other protocols over TCP port 80


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tue, 21 Jun 2005, Damon Gray wrote:
>
>>
>> Bad security policies aside.... :)
>>
>> You could always run the telnet server on port 80. Or run netcat (aka nc) on
>> the box on port 80 redirecting to port 23.
>>
>
> He could, if he wanted to really violate the policies in place and tunnel
> traffic in the clear.  he's actually asking about something that would be
> deemed a tad more seucre/private in nature, though still likely a
> violation os the security policies currently in place and thus subjecting
> himself to likely termination once the tunnel was discovered, let alone
> potential prosecution.
>
>
> Thanks,
>
> Ron DuFresne
>
>>
>> On Tue, 21 Jun 2005, [iso-8859-1] Bruno Negrão wrote:
>>
>>> Hi guys,
>>>
>>> I need to create a VPN to my linux server from a remote
>>> workstation(windows) inside a private network of another company. The LAN
>>> where the workstation is located is protected by a firewall. This firewall
>>> only lets pass through outgoing traffic to port 80(http).
>>>
>>> I need this workstation to telnet a telnet server inside my private
>>> network. Is it possible to set up a tunnel over port 80 to create a VPN
>>> between the workstation and my gateway, so that the workstation can telnet
>>> my internal server?
>>>
>>> The network administrator where this workstation is located is
>>> inaccessible, so I have to create this workaround.
>>>
>>> Thank you,
>>> -------------------------------------------------
>>> Bruno Negrao - Support Analyst
>>> Engepel Teleinformática. 55-31-34812311
>>> Belo Horizonte, MG, Brazil
>>>
>>
>
> - -- 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>         admin & senior security consultant:  sysinfo.com
>                         http://sysinfo.com
> Key fingerprint = 9401 4B13 B918 164C 647A  E838 B2DF AFCC 94B0 6629
>
> ...We waste time looking for the perfect lover
> instead of creating the perfect love.
>
>                 -Tom Robbins <Still Life With Woodpecker>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>
> iD8DBQFCuG9Yst+vzJSwZikRAgeQAJkBQRMIkhqTvT9XAUU5Ri5e+ybzigCgzXEA
> AvPSv6yw4Em98204pnSEhWk=
> =iaYC
> -----END PGP SIGNATURE----- 



  parent reply	other threads:[~2005-06-21 19:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21 19:05 Tunneling other protocols over TCP port 80 Bruno Negrão
2005-06-21 19:16 ` R. DuFresne
2005-06-21 19:20 ` Damon Gray
2005-06-21 19:49   ` R. DuFresne
2005-06-21 19:47     ` Damon Gray
2005-06-21 19:59     ` Bruno Negrão [this message]
2005-06-21 20:20       ` Damon Gray
2005-06-21 20:20       ` R. DuFresne
2005-06-21 21:27 ` CompuGenic
2005-06-21 21:27   ` CompuGenic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='005201c5769b$cbefdc70$5100a8c0@14bis' \
    --to=vpopmail@engepel.com.br \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.