Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Help: Iptables rules
Date: Thu, 15 Jan 2004 21:53:22 +0000	[thread overview]
Message-ID: <200401152153.23002.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <OF487854B5.F9A9C49A-ON88256E1C.006A8AE9-88256E1C.006DA0EC@statsus.com>

On Thursday 15 January 2004 7:57 pm, Minh Cao wrote:

> > 3. You say the above has not worked - how have you tested it?
>
> Yes, I tested
> I used VPN client, which connected to remote side. After connected, the
> password authentication is timeout in 2 minutes.

I really would recommend testing the setup with something a lot simpler than a 
VPN client :)

For example, a web browser, email, ssh, ftp - something which uses fairly 
standard TCP connections, and is likely to work through NAT.

Depending on what sort of VPN you are trying to use, you may have significant 
problems getting it work (but then again you may not - as I say it depends 
what sort of VPN it is).   For example, IPsec ESP (tunnel mode) is not too 
difficult to get working, IPsec AH (transport mode) will not work across NAT.   
PPTP requires a special helper module, and there are other sorts of VPN about 
which I have no idea.

Start with something easy and work your way up to a VPN gradually.

> > 6. Did the machine work as a simple router before you tried adding
> > netfilter rules?
>
> Two NICs are on different subnet. Can I config as a router w/o using
> netfilter ?

Er, yes :)   You really should make sure the machine will route packets 
properly before setting up netfilter, which (basically) blocks things.

It sounds as though you might benefit from reading the standard Linux 
Networking HOWTO befoer tackling Oska Andreassen's netfilter tutorial which I 
recommended to you yesterday.

Regards,

Antony.

-- 
"Note: Windows 98, Windows 98SE and Windows 95 are not affected by [MS
Blaster].   However, these products are no longer supported.   Users of these
products are strongly encouraged to upgrade to later versions."

(which *are* affected by MS Blaster...)

http://www.microsoft.com/security/security_bulletins/ms03-026.asp

                                                     Please reply to the list;
                                                           please don't CC me.



  parent reply	other threads:[~2004-01-15 21:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15 19:57 Help: Iptables rules Minh Cao
2004-01-15 20:11 ` Aldo S. Lagana
2004-01-15 21:53 ` Antony Stone [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-15 23:13 Minh Cao
2004-01-15 23:27 ` Antony Stone
2004-01-16  2:04 ` Alexis
     [not found] <OFE1656F2A.7FFED69B-ON88256E1C.000829BB-88256E1C.00088CCC@statsus.com>
2004-01-15  1:39 ` Antony Stone
2004-01-15  1:41 ` Antony Stone
2004-01-15  1:04 Minh Cao
2004-01-15  1:24 ` Antony Stone

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=200401152153.23002.Antony@Soft-Solutions.co.uk \
    --to=antony@soft-solutions.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox