All of lore.kernel.org
 help / color / mirror / Atom feed
From: Babarovic Ivica <ivica@asist-traffic.com>
To: linux-ppp@vger.kernel.org
Subject: advice needed
Date: Wed, 18 Jan 2006 17:10:57 +0000	[thread overview]
Message-ID: <43CE76A1.1020409@asist-traffic.com> (raw)

Hi!

I have a working setup with a vxworks machine sending
data over GPRS modem. It sets up a modem and establish
a ppp link with provider.

Now I have to send some additional data(pictures) which hardware
that vxworks runs on cannot provide. That's why I included a small
industrial board with framegraber an put linux on it. Basically I inserted
this linux box between vxworks box and a GPRS modem connecting
them with serial lines.

Since I need to keep vxworks setup and programs untouched  (it needs to
work as
plug in linux box, plug out linux box) I've come with a following idea.

I made a program that connects serial ports on linux board so vxworks
box can
freely access modem across linux box and initialize it. I'm catching the
"CONNECT" string here  and after that, I break the serial port
connection/exit
program. I start ppp link on serial side towards vxworks and that makes
it happy.

Now the problem comes when I want to attach to a connected stream towards
modem on linux. Remember this stream was created by vxworks box.
I thought I want be having any problems but pppd refuses to connect or
refuses to attach itself to this stream and start ppp negotiation.
I thought pppd will behave similar as when manually dialing to a provider.
Scenario: Minicom, dial, connect, exit minicom, start pppd, ppp link
comes up.

But for some reason pppd refuses this for the stream vxworks box created.

All I get in log is: pppd 2.4.3 started by root, uid 0
no further lines.

Let me add that if I kill this stream somehow(enter minicom and exit)
I can easily establish my own link from scratch. But of course this needs
to be automated. So what do you think is causing pppd not to establish
ppp link with the stream vxworks creates?


I hope I was clear enough since my English is a bit basic. If not please ask
for whatever info you need. I'll provide.


TIA,
I.B.

             reply	other threads:[~2006-01-18 17:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 17:10 Babarovic Ivica [this message]
2006-01-18 17:19 ` advice needed Bill Unruh
2006-01-18 17:35 ` James Carlson
2006-01-19 11:36 ` Babarovic Ivica
2006-01-19 11:41 ` Babarovic Ivica
2006-01-19 17:45 ` Bill Unruh
  -- strict thread matches above, loose matches on Subject: below --
2007-01-31 16:52 Advice needed W.P.
2007-01-31 17:22 ` David Daney
2007-01-31 18:16   ` W.P.
     [not found]     ` <1170276219.6791.18.camel@localhost>
2007-01-31 21:34       ` W.P.
2007-01-31 21:39 ` Sergio Aguayo
2007-01-31 21:59   ` Florian Fainelli
2007-01-31 22:28     ` W.P.
2007-02-01 13:09       ` Sergio Aguayo
2007-02-01 14:50         ` W.P.
2007-02-02 13:43           ` Sergio Aguayo
     [not found]             ` <45C3BB23.2070309@wp.pl>
2007-02-03  5:57               ` Sergio Aguayo
     [not found]                 ` <45C45DDA.1000805@wp.pl>
2007-02-05 14:34                   ` Sergio Aguayo
2007-02-07 18:07                     ` W.P.
2007-02-08 15:09                       ` Sergio Aguayo
2007-02-08 15:16                       ` Sergio Aguayo
2007-02-08 17:41                         ` W.P.
2007-05-25 15:23 zImage.elf loads but does not start Mirek23
2007-05-25 16:56 ` Advice needed Charles Krinke

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=43CE76A1.1020409@asist-traffic.com \
    --to=ivica@asist-traffic.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 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.