Now I have more problems with PPPD

Hi again!

Since the last post I have updated my system:
uanme -a:
QNX localhost 6.00 2002/01/31-08:18 ASPEN shle

Updated pppd as follows:
pppd → 22nd Jan. 2002 patch
npm-pppmgr.so → 22nd Jan.2002 patch

Now I don’t get the SIGSEGV’s in io-net anymore but now PPPD is failing when
dialing.

Before, I was able to establish a connection although it crashed when
shutting down.
Now I can dial the ISP but I will not get a DNS and PPPD will not detach.
If I start PPPD in the background I can ping ip-addresses (gateway function
working) but
obviosly I can’t ping a named server.


the flags I use this time are:
/dev/ser3 updetach +resconf defaultroute +stdinsecret name idle 300
also tested:
/dev/ser3 updetach resconf defaultroute +stdinsecret name idle 300
usepeerdns confstr

  • same result.

before I had the require-ns flag set but it does not seem to be avilable
anymore.
Again



regards,
Jerker Christopherson
email:jerker.christoffersson@mecel.se

“jerker christopherson” <jerker.christopherson@mecel.se> wrote in
news:a5fkpa$kn3$1@inn.qnx.com:

Since the last post I have updated my system:
uanme -a:
QNX localhost 6.00 2002/01/31-08:18 ASPEN shle

Have you tried 6.1patch A to see if the problem still exists

Updated pppd as follows:
pppd → 22nd Jan. 2002 patch
npm-pppmgr.so → 22nd Jan.2002 patch

Now I don’t get the SIGSEGV’s in io-net anymore but now PPPD is failing
when dialing.

Before, I was able to establish a connection although it crashed when
shutting down.
Now I can dial the ISP but I will not get a DNS and PPPD will not
detach. If I start PPPD in the background I can ping ip-addresses
(gateway function working) but
obviosly I can’t ping a named server.

Does the ppp0 interface indicate a completed neogiation (ie. you have an IP
address and the address of the point you’re connected to)? Can you ping
IP’s of machines outside of the gateway?

the flags I use this time are:
/dev/ser3 updetach +resconf defaultroute +stdinsecret name <name
idle 300 also tested:
/dev/ser3 updetach resconf defaultroute +stdinsecret name idle
300 usepeerdns confstr

  • same result.

before I had the require-ns flag set but it does not seem to be
avilable anymore.

Have you tried running with the debug flag on, and checking the syslog for
ideas on what might be going wrong (required syslogd of course). Have you
tried forcing the nameserver using the “nameserver” option?

\

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:Xns91C157D18EDBamalloryqnxcom@209.226.137.4

“jerker christopherson” <> jerker.christopherson@mecel.se> > wrote in
news:a5fkpa$kn3$> 1@inn.qnx.com> :

Since the last post I have updated my system:
uanme -a:
QNX localhost 6.00 2002/01/31-08:18 ASPEN shle

Have you tried 6.1patch A to see if the problem still exists

I’m running on aspen and the procnto is from jan 31 this year.
the pppd I’m running is from jan 22 20001.

When running PPPD on 6.1 x86 the pppd options were all different - but it
worked.
I had an option named “require-ns” - which is no longer supported.
The options I’ve been trying to use now is usepeerdns.

When I moved to SH4 (mid 2001 code base) the whole thing still worked but
when
I tried to slay pppd I got a SIGSEGV in io-net.

Because of this I updated procnto, pppd and pppmgr to the latest versions
and the
rest of the codebase to around august 2001.
After this the “updetach” stopped working.
This may be because I don’t get a DNS and therefore PPPD does not consider
the negotiation completed.

If I start PPPD in the background I can still ping IP addresses on the
internet ( I do a ping on a different machine to get the IP number) but the
DNS lookups obvioulsy does not work.

using the +resconf option I don’t see that the /etc/resolv.conf gets
updated. There is supposedly a CS_RESOLVE environment variable which the
system might use instead so I also tried the confstr option but it still
does not work.

When I run the following:
pppd connect “/bin/chat -v -f /home/rv/myscript” defaultroute +resconf
115200 updetach /dev/ser3
I get the following:
Serial connection established.

Using interface ppp0

Connect: ppp0 <–> /dev/ser3

LCP: timeout sending Config-Requests

Connection terminated.


this exact thing worked with previous version of PPPD/procnto


Any ideas :wink:

/ Jerker



Updated pppd as follows:
pppd → 22nd Jan. 2002 patch
npm-pppmgr.so → 22nd Jan.2002 patch

Now I don’t get the SIGSEGV’s in io-net anymore but now PPPD is failing
when dialing.

Before, I was able to establish a connection although it crashed when
shutting down.
Now I can dial the ISP but I will not get a DNS and PPPD will not
detach. If I start PPPD in the background I can ping ip-addresses
(gateway function working) but
obviosly I can’t ping a named server.

Does the ppp0 interface indicate a completed neogiation (ie. you have an
IP
address and the address of the point you’re connected to)? Can you ping
IP’s of machines outside of the gateway?

the flags I use this time are:
/dev/ser3 updetach +resconf defaultroute +stdinsecret name <name
idle 300 also tested:
/dev/ser3 updetach resconf defaultroute +stdinsecret name idle
300 usepeerdns confstr

  • same result.

before I had the require-ns flag set but it does not seem to be
avilable anymore.

Have you tried running with the debug flag on, and checking the syslog for
ideas on what might be going wrong (required syslogd of course). Have you
tried forcing the nameserver using the “nameserver” option?

\

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