PPPoE

Hello everyone,

I’m having trouble getting PPPoE to run on my QNX RTOS installation.

My io-net command during startup looks like this:

io-net -v -d dm9pci -p tcpip forward -p pppmgr -p pppoe &

This results in the following error messages:
io-net: warning: autoload of “ncm-ppp_ip.so” failed: Library cannot be
found
io-net: warning: autoload of “ncm-ppp_en.so” failed: Library cannot be
found

Though it’s only a warning, the result is that my network doesn’t
start up at all.

If I do not include “-p pppoe” in the initial io-net command and try
to start it later with “mount -T ioß-net npm-pppoe.so”, it seems to
work, I mean “ppp_en” shows up in “/dev/io-net”. But in either case, I
get a “Memory fault” when trying to start pppoed.

I’d appreciate your suggestions - either direct me to those two
missing files which hopefully fix the problem (I couldn’t find them on
the qnx website) or give a hint what I might be doing wrong.

Regards,
Christian Schiller

What happens if you don’t use the forward directive for tcpip? What is the
exact error when you get the memory fault?


Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
“Christian Schiller” <cschill@de.ibm.com> wrote in message
news:d5hd4ukishfocno3didvn21bqlbdhtr02n@4ax.com

Hello everyone,

I’m having trouble getting PPPoE to run on my QNX RTOS installation.

My io-net command during startup looks like this:

io-net -v -d dm9pci -p tcpip forward -p pppmgr -p pppoe &

This results in the following error messages:
io-net: warning: autoload of “ncm-ppp_ip.so” failed: Library cannot be
found
io-net: warning: autoload of “ncm-ppp_en.so” failed: Library cannot be
found

Though it’s only a warning, the result is that my network doesn’t
start up at all.

If I do not include “-p pppoe” in the initial io-net command and try
to start it later with “mount -T ioß-net npm-pppoe.so”, it seems to
work, I mean “ppp_en” shows up in “/dev/io-net”. But in either case, I
get a “Memory fault” when trying to start pppoed.

I’d appreciate your suggestions - either direct me to those two
missing files which hopefully fix the problem (I couldn’t find them on
the qnx website) or give a hint what I might be doing wrong.

Regards,
Christian Schiller

Adam,

the problem is still the same even if I don’t use the tcpip forward
option.

Now, the following scenario:

command in startup file:
io-net -v -a -dm9pci -p tcpip forward -p pppmgr &

This brings up my local ethernet interface fine, no error messages. I
also start syslogd.

Then I use the following command:
mount -T io-net npm-pppoe.so

The same error messages are logged (“ncm… is missing”) as when I put
“-p pppoe” directly in the io-net command.

Now, when I start pppoed with the following options:
pppoed verbose=10

I get the simple message “Memory fault” on the shell where I executed
the command. Nothing is looged via syslogd.

Any other things I could try? I appreciate your help!

Best regards,
Christian



On Thu, 17 Jan 2002 08:31:54 -0500, “Adam Mallory” <amallory@qnx.com>
wrote:

What happens if you don’t use the forward directive for tcpip? What is the
exact error when you get the memory fault?

“Christian Schiller” <cschill@de.ibm.com> wrote in message
news:lnvd4ukhe5p65r84b9e9ugnkiu877v27bc@4ax.com

command in startup file:
io-net -v -a -dm9pci -p tcpip forward -p pppmgr &

This brings up my local ethernet interface fine, no error messages. I
also start syslogd.

Then I use the following command:
mount -T io-net npm-pppoe.so

The same error messages are logged (“ncm… is missing”) as when I put
“-p pppoe” directly in the io-net command.

Can you do a sanity check, and make sure that you have /lib/dll/npm-pppoe.so
… Also can you post the full syslog entry for that error, as I don’t get
the same when replicate your steps.

\

Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>

One thing I should add, instead of running pppoed on your own, do your
io-net command line as usual - but use the photon app called phlip (network
configuration) and setup a new connection for PPPoE.


Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
“Adam Mallory” <amallory@qnx.com> wrote in message
news:a272b5$p9l$1@nntp.qnx.com

“Christian Schiller” <> cschill@de.ibm.com> > wrote in message
news:> lnvd4ukhe5p65r84b9e9ugnkiu877v27bc@4ax.com> …

command in startup file:
io-net -v -a -dm9pci -p tcpip forward -p pppmgr &

This brings up my local ethernet interface fine, no error messages. I
also start syslogd.

Then I use the following command:
mount -T io-net npm-pppoe.so

The same error messages are logged (“ncm… is missing”) as when I put
“-p pppoe” directly in the io-net command.

Can you do a sanity check, and make sure that you have
/lib/dll/npm-pppoe.so
. Also can you post the full syslog entry for that error, as I don’t get
the same when replicate your steps.

\

Cheers,
Adam

QNX Software Systems Ltd.
[ > amallory@qnx.com > ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net

Adam,

the full syslog entry is as follows:

io-net: warning: autoload of “ncm-ppp_ip.so” failed: Library cannot be
found
io-net: warning: autoload of “ncm-ppp_en.so” failed: Library cannot be
found

The library npm-pppoe.so is definitively existant.

I’m running QNXRTOS on an embedded platform (64mb flash, x86-based)
without a GUI, hence I cannot use phlip.

I’ve done a “sanity check” both on the embedded system and on me, both
seem to be working fine… :wink:
In fact, QNX runs gorgeously well on the embedded system, except
PPPoE.

Any other suggestions?

Regards,
Christian


On Thu, 17 Jan 2002 12:41:28 -0500, “Adam Mallory” <amallory@qnx.com>
wrote:

“Christian Schiller” <> cschill@de.ibm.com> > wrote in message
news:> lnvd4ukhe5p65r84b9e9ugnkiu877v27bc@4ax.com> …

command in startup file:
io-net -v -a -dm9pci -p tcpip forward -p pppmgr &

This brings up my local ethernet interface fine, no error messages. I
also start syslogd.

Then I use the following command:
mount -T io-net npm-pppoe.so

The same error messages are logged (“ncm… is missing”) as when I put
“-p pppoe” directly in the io-net command.

Can you do a sanity check, and make sure that you have /lib/dll/npm-pppoe.so
. Also can you post the full syslog entry for that error, as I don’t get
the same when replicate your steps.

The warning is normal, you can disregard its verbosity.

When you start pppoed, what options are you passing it? The Dialer app uses
the following:

pppoed -v nodetach noscript logfd=2 logstatus name=
en= services=


Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
“Christian Schiller” <cschill@de.ibm.com> wrote in message
news:orlq4ucg0kq7mj5onehtmcijjbn7b0du5p@4ax.com

Adam,

the full syslog entry is as follows:

io-net: warning: autoload of “ncm-ppp_ip.so” failed: Library cannot be
found
io-net: warning: autoload of “ncm-ppp_en.so” failed: Library cannot be
found

The library npm-pppoe.so is definitively existant.

I’m running QNXRTOS on an embedded platform (64mb flash, x86-based)
without a GUI, hence I cannot use phlip.

I’ve done a “sanity check” both on the embedded system and on me, both
seem to be working fine… > :wink:
In fact, QNX runs gorgeously well on the embedded system, except
PPPoE.

Any other suggestions?

Regards,
Christian


On Thu, 17 Jan 2002 12:41:28 -0500, “Adam Mallory” <> amallory@qnx.com
wrote:

“Christian Schiller” <> cschill@de.ibm.com> > wrote in message
news:> lnvd4ukhe5p65r84b9e9ugnkiu877v27bc@4ax.com> …

command in startup file:
io-net -v -a -dm9pci -p tcpip forward -p pppmgr &

This brings up my local ethernet interface fine, no error messages. I
also start syslogd.

Then I use the following command:
mount -T io-net npm-pppoe.so

The same error messages are logged (“ncm… is missing”) as when I put
“-p pppoe” directly in the io-net command.

Can you do a sanity check, and make sure that you have
/lib/dll/npm-pppoe.so
. Also can you post the full syslog entry for that error, as I don’t get
the same when replicate your steps.

On Tue, 22 Jan 2002 09:22:51 -0500, “Adam Mallory” <amallory@qnx.com>
wrote:

The warning is normal, you can disregard its verbosity.

Okay

When you start pppoed, what options are you passing it? The Dialer app uses
the following:
pppoed -v nodetach noscript logfd=2 logstatus name=<server name
en= services=<service name

Initially I tried it without any options, which produces a “Memory
fault”. I’ve tried it now with the following, according to your
suggestion:

pppoed -v nodetach noscript logfd=2 logstatus name="" en=en0
services=""

Still, this produces just another “Memory fault”.

The platform I’m running this on is an embedded system with a National
Semiconductors GX1 processer (233 MHz). The /usr/bin/pppoed file I
have is 17020 bytes, and the /lib/dll/npm-pppoe.so is 31559 bytes.
Maybe I’ve got corrupt files? Unfortunately noone here at IBM seems to
have worked with PPPoE yet, and I can’t track down where those files
originated… Maybe you have newer ones I could try?

Regards,
Christian

Christian Schiller <cschill@de.ibm.com> wrote:

On Tue, 22 Jan 2002 09:22:51 -0500, “Adam Mallory” <> amallory@qnx.com
wrote:

The warning is normal, you can disregard its verbosity.

Okay

When you start pppoed, what options are you passing it? The Dialer app uses
the following:
pppoed -v nodetach noscript logfd=2 logstatus name=<server name
en= services=<service name

Initially I tried it without any options, which produces a “Memory
fault”. I’ve tried it now with the following, according to your
suggestion:

pppoed -v nodetach noscript logfd=2 logstatus name="" en=en0
services=""

Still, this produces just another “Memory fault”.

The platform I’m running this on is an embedded system with a National
Semiconductors GX1 processer (233 MHz). The /usr/bin/pppoed file I
have is 17020 bytes, and the /lib/dll/npm-pppoe.so is 31559 bytes.
Maybe I’ve got corrupt files? Unfortunately noone here at IBM seems to
have worked with PPPoE yet, and I can’t track down where those files
originated… Maybe you have newer ones I could try?

Can you post result from “ewhich -l pppoed” and
"/usr/sbin/pkgctl which -l pppoed"?

-xtang

On 22 Jan 2002 22:59:58 GMT, Xiaodan Tang <xtang@qnx.com> wrote:

Can you post result from “ewhich -l pppoed” and
"/usr/sbin/pkgctl which -l pppoed"?

Hello Xiaodan,

the qnx installation on my embedded system does not have these files
(ewhich and pkgctl), and I do not have the installation sourcefiles.
In case you can send me binaries for the NS GX1 processor, I can try
those commands.

Regards,
Christian

Hi Christian and Xiaofan,

the -v option causes the Memory fault. Execute like this:
pppoed verbose=n nodetach noscript logfd=2 logstatus name="" en=en0 services=""
n=1…10.

Cheers,

Freddy

PS: Do you have to fill in the service name???



On 22 Jan 2002 22:59:58 GMT, Xiaodan Tang <xtang@qnx.com> wrote:

Christian Schiller <> cschill@de.ibm.com> > wrote:
On Tue, 22 Jan 2002 09:22:51 -0500, “Adam Mallory” <> amallory@qnx.com
wrote:

The warning is normal, you can disregard its verbosity.

Okay

When you start pppoed, what options are you passing it? The Dialer app uses
the following:
pppoed -v nodetach noscript logfd=2 logstatus name=<server name
en= services=<service name

Initially I tried it without any options, which produces a “Memory
fault”. I’ve tried it now with the following, according to your
suggestion:

pppoed -v nodetach noscript logfd=2 logstatus name="" en=en0
services=""

Still, this produces just another “Memory fault”.

The platform I’m running this on is an embedded system with a National
Semiconductors GX1 processer (233 MHz). The /usr/bin/pppoed file I
have is 17020 bytes, and the /lib/dll/npm-pppoe.so is 31559 bytes.
Maybe I’ve got corrupt files? Unfortunately noone here at IBM seems to
have worked with PPPoE yet, and I can’t track down where those files
originated… Maybe you have newer ones I could try?

Can you post result from “ewhich -l pppoed” and
"/usr/sbin/pkgctl which -l pppoed"?

-xtang

Freddy Martens
Field Application Engineer

Prime EDA
Keesomstraat 17
6717 AH Ede, The Netherlands
T: +31 318 692 720
F: +31 547 367 332
M: +31 622 605 232
E: freddy@prime-eda.com
W: http://www.prime-eda.com

Build a more reliable world
http://www.qnx.com