From: Steve Comfort <steve@4dllc.com>
To: lartc@vger.kernel.org
Subject: [LARTC] VPN over PPP - more detail
Date: Thu, 13 Oct 2005 07:38:39 +0000 [thread overview]
Message-ID: <434E0EFF.2030707@4dllc.com> (raw)
Hi All,
Let me try again, this time with fixed width !
First off the scenario. We have a local and remote site, both of which
connect to the internet via a wireless network. The wireless cards
themselves have both an ethernet (ixp1) and an "Atheros" (ath0)
interface. The devices connect via PPPoE, and so there is also a ppp0
interface on each device.
On one side we have :
IXP1 IP address : 192.168.200.202
PPP0 IP address : 192.168.94.134
ATH0 IP address : Unassigned
And on the other side :
IXP1 : 192.168.2.200
PPP0 : 192.168.94.132
ATH0 : Unassigned
I have tried various combinations of local and remote addresses, and
have tried both IPSec and GRE tunnels, all to no avail. There is a
masquerading firewall on the PPP interfaces, but turning this off does
not have any effect. I have tried excluding the 192.168.2.200 address
from being masqueraded, also to no avail.
I can quite happily ssh to either of the two PPP interfaces, but cannot
access anything behind the PPP interfaces.I am going to try assigning an
intermediate address such as 192.168.200.11 to the tunnel interface, but
I have the feeling that the tunnels are not even being created. I do do
the tunneling from both sides, so I don't think that is the problem,
unless there are very short timeouts associated with their creation ??
Does anyone know if there is any information hidden away in the /proc
interface which will tell me whether the tunnels have failed?
Can anyone explain how the various IP addresses would be encapsulated in
an IPSec over PPP interface. Maybe then I could figure out my routing etc.
Best regards
Steve Comfort
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2005-10-13 7:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=434E0EFF.2030707@4dllc.com \
--to=steve@4dllc.com \
--cc=lartc@vger.kernel.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.