From: Eduardo Ukstin <ukstin@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: VPN rules
Date: Thu, 5 Jan 2006 09:51:23 -0200 [thread overview]
Message-ID: <bb8a5cd0601050351u670ea043k8c155195fe17c0a8@mail.gmail.com> (raw)
In-Reply-To: <43bc5996.2a448af9.5d0f.6ff7SMTPIN_ADDED@mx.gmail.com>
I've created some rules to see what the vpn client is trying to do,
and saw some interesting things.
In the negociation the client goes throw the vpn server (outside my
lan) and everything works, but after this, it tries to ping a
192.43... ip, my firewall doesn't rotate this, and of course this ping
requisition cannot goes through. But I'm a little confused about what
to do, create a route for this 192 or make a prerouting rule, in any
of this cases I'm not certain of what I need to do.
My internal network has ip 10.....
On 1/4/06, P. Harlow <wolf-r1@wispertel.net> wrote:
> It depends on the type of VPN you are using.
>
> IPSec based VPNs typically use:
>
> UDP 500 - IPSec negotiation
> IP 51 - Authentication Header (AH) for IPSec negotiation
> IP 50 - IPSec data
>
> PPTP based VPNs typically use:
>
> IP 47 - General Routing Encapsulation (GRE)PPTP data channel
> TCP 1723 - PPTP control channel
>
> You are going to want to figure out which type of VPN you are using and
> allow for those ports. I would assume that since you're getting
> authentication requests with port 500 open however your TCP 500 causes me to
> wonder what type of VPN you have.
>
next prev parent reply other threads:[~2006-01-05 11:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bb8a5cd0601041416w4e85d5e7i7031b0454408a1fe@mail.gmail.com>
2006-01-04 22:18 ` VPN rules Eduardo Ukstin
2006-01-04 23:25 ` P. Harlow
[not found] ` <43bc5996.2a448af9.5d0f.6ff7SMTPIN_ADDED@mx.gmail.com>
2006-01-05 11:51 ` Eduardo Ukstin [this message]
[not found] ` <9255886c0601050404r2c09053bo42096794b31fee13@mail.gmail.com>
2006-01-05 12:31 ` Eduardo Ukstin
2006-01-08 4:46 ` /dev/rob0
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=bb8a5cd0601050351u670ea043k8c155195fe17c0a8@mail.gmail.com \
--to=ukstin@gmail.com \
--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.