All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Leach <raymondl@knowledgefactory.co.za>
To: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: Re-2: connection to vpn Server (pptp) behind iptables FW
Date: Fri, 12 Mar 2004 14:20:26 +0200	[thread overview]
Message-ID: <1079094025.15566.90.camel@raylinux.internal> (raw)
In-Reply-To: <1079092896.2722.17.camel@anduril.intranet.cartel-securite.net>

[-- Attachment #1: Type: text/plain, Size: 955 bytes --]

On Fri, 2004-03-12 at 14:01, Cedric Blancher wrote:
> Le ven 12/03/2004 à 11:34, peter.gehle@sbgit.com a écrit :  
> > > Micro$oft has a 'technote' on this in their technet section on the
> > > website. AFAIR you need to allow protocol 37 to be forwarded between the
> > > two.
> > I have added a rule that forwards the protocol 37, but it still not works?
> 
> PPTP relies on a slightly modified GRE tunnel, which protocol _47_, not
> 37.

Yup, you are correct. My mistake. I found the info at Technet in their
document entitled 'VPN servers and firewall configuration'

> cbr@anduril:~$ grep gre /etc/protocols
> gre     47      GRE             # General Routing Encapsulation
-- 
--
Raymond Leach <raymondl@knowledgefactory.co.za>
Network Support Specialist
http://www.knowledgefactory.co.za
"lynx -source http://www.rchq.co.za/raymondl.asc | gpg --import"
Key fingerprint = 7209 A695 9EE0 E971 A9AD  00EE 8757 EE47 F06F FB28
--

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-03-12 12:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-12 10:34 Re-2: connection to vpn Server (pptp) behind iptables FW peter.gehle
2004-03-12 10:50 ` Antony Stone
2004-03-12 11:02 ` Ray Leach
2004-03-12 12:01 ` Cedric Blancher
2004-03-12 12:20   ` Ray Leach [this message]

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=1079094025.15566.90.camel@raylinux.internal \
    --to=raymondl@knowledgefactory.co.za \
    --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.