From: Mike Jagdis <jaggy@purplet.demon.co.uk>
To: Owain McGuire <owain@ofrm.demon.co.uk>
Cc: linux-diald@vger.kernel.org
Subject: Re: tap0 or ppp0?
Date: Sun, 30 Mar 2003 23:22:01 +0000 [thread overview]
Message-ID: <3E877C19.6030908@purplet.demon.co.uk> (raw)
In-Reply-To: 009d01c2efcb$778cf040$0200000a@tower
Owain McGuire wrote:
> Simple question really??
>
> I have upgraded from diald 0.9 to 1.0 and sorted out all of the
> ethertap stuff. The only thing is that the masqueraded machines don't
> seem to be able to bring up the ppp connections themselves. The
> "server" machine can though. I have followed the IP_Masq_Howto for
> 2.4 kernels but I have a question for the rc.firewall-2.4 script.
> Should the external interface be tap0 or ppp0? I am confused as to
> how the flow or handoever of traffic from tap0 to ppp0 works.
Without knowing what rc.firewall-2.4 does exactly it's difficult to
be sure. However you generally want the proxy interface to either
allow any packet out or to have exactly the same fiewalling of
outgoing packets that the real link would (which may reduce some
false triggers depending how you have diald itself configured).
You do _not_ want masquerading active on the proxy interface. It
gets sort of complicated to follow, but on a machine doing forwarding
with dynamic addresses on the diald link diald will send proxy
packets back to the kernel via the proxy interface and the kernel
will then route them out the real interface, masquerading if
necessary. If you masquerade on the proxy interface as well you
pick up a likely bogus source address which prevents the connection
from working until the client times out and tries again - if that's
after the link has timed out the retry won't work either.
The best answer is probably to make the ppp interface an external,
the proxy a wide open internal (remember the real link has all the
firewalling you need anyway), and configure diald carefully to
only bring the link up for the traffic you want.
Mike
prev parent reply other threads:[~2003-03-30 23:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 17:01 tap0 or ppp0? Owain McGuire
2003-03-22 2:02 ` Mark Frey
2003-03-30 23:22 ` Mike Jagdis [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=3E877C19.6030908@purplet.demon.co.uk \
--to=jaggy@purplet.demon.co.uk \
--cc=linux-diald@vger.kernel.org \
--cc=owain@ofrm.demon.co.uk \
/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.