From: Christopher Fowler <cfowler@outpostsentinel.com>
To: linux-ppp@vger.kernel.org
Subject: Re: Can we run a PPP server & client simultaneously???
Date: Mon, 23 Jul 2007 12:08:45 +0000 [thread overview]
Message-ID: <1185192525.29974.3.camel@shuttle.linxdev.com> (raw)
In-Reply-To: <11741524.post@talk.nabble.com>
On Mon, 2007-07-23 at 07:59 -0400, James Carlson wrote:
> On the Annex communications server, we wrote special demand-dial
> management code to look up a dormant interface by address and bring it
> to life when the peer called us. That way, the return traffic (reply
> packets) wouldn't trigger an outbound attempt that would fail.
>
> On Linux, you may be able to get away with it if both links have
> different sets of IP addresses.
You can do it on Linux. I have hundreds doing this. Yes you do have 2
interfaces. I'm curious as to details on how you solved it on the
Annex. They way we solved it is via if-down and if-up. That is a C
program on our device. When pppd calls that program it looks for an
interface that is in the UP state but not our own. It places that
interface in the DOWN state. When if-down is called it looks for an
interface that is DOWN but not our own and it places that in UP. The
effect is that you'll end up with 2 ppp interfaces with the same
address. Only one is UP.
I've had this working for a couple years now and I've not had any
problems. I think the only problem I could see is if pppd died and
never called if-down. You would end up with a PPP interface in the DOWN
state and the remote could never call home. Calling from the server
would rectify the situation.
next prev parent reply other threads:[~2007-07-23 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 10:52 Can we run a PPP server & client simultaneously??? LeeD
2007-07-23 11:59 ` James Carlson
2007-07-23 12:08 ` Christopher Fowler [this message]
2007-07-23 12:28 ` James Carlson
2007-07-23 12:35 ` Christopher Fowler
2007-07-23 16:23 ` Bill Unruh
2007-07-24 8:07 ` Lee Davies
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=1185192525.29974.3.camel@shuttle.linxdev.com \
--to=cfowler@outpostsentinel.com \
--cc=linux-ppp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).