hi
Since I’ve installed 6.1 I can’t connect myself to the internet using
QNX
I’ve configured my connection correctly, then I tried to connect
it dials up
Then it connects correctly, and less than 2seconds later it says “PPD
connection closed”
Help’s required…
what have I to do?
I found on the knowledge some time ago that a lot of people were having
this problem with 6.1, and that QNX staff was keeping an eye on it.
does someone know what to do, or when a fix is going to be released?
thx a lot
malv
I have similar problems. Home PatchA for 6.1 will resolve this pppd
issue. Are you fixed this problem?
Pascal Malvert wrote:
hi
Since I’ve installed 6.1 I can’t connect myself to the internet using
QNX
I’ve configured my connection correctly, then I tried to connect
it dials up
Then it connects correctly, and less than 2seconds later it says “PPD
connection closed”
Help’s required…
what have I to do?
I found on the knowledge some time ago that a lot of people were having
this problem with 6.1, and that QNX staff was keeping an eye on it.
does someone know what to do, or when a fix is going to be released?
thx a lot
malv
Jordan Ostreff wrote:
I have similar problems. Home PatchA for 6.1 will resolve this pppd
issue. Are you fixed this problem?
Pascal Malvert wrote:
…
I found on the knowledge some time ago that a lot of people were having
this problem with 6.1, and that QNX staff was keeping an eye on it.
does someone know what to do, or when a fix is going to be released?
The Patch-A Release Notes don’t mention this at all as something
that has been fixed. Howeverm there’s been other stuff fixed
in Patch A that isn’t mentioned in the Release Notes, so I
don’t think they are at all “definitive”. It would help if
they were more detailed and covered all known fixed bugs.
http://qdn.qnx.com/news/releases/releasenotes_A.html
I searched all of QDN for PPPD giving problems and didn’t find any
update
on one on PPPoE giving “Fatal signal 11”.
I got this on the weekend:
=================
Dialing xxxxxxxx…
ATDTxxxxxxxx
connect 115200
Link Established
Negotiating PPP connection
pppd Started
Using interface ppp0
Connect: ppp0 <–> /dev/ser1
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xab0b80c3>
]
rcvd [LCP ConfReq id=0x0 <mru 1500> <asyncmap 0x0> < 11
04 05 dc> < 13 07 02 cb 17 f4 fe>]
sent [LCP ConfRej id=0x0 < 11 04 05 dc> < 13 07 02 cb 17 f4 fe>]
rcvd [LCP ConfReq id=0x1 <mru 1500> <asyncmap 0x0> ]
sent [LCP ConfAck id=0x1 <mru 1500> <asyncmap 0x0> ]
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xab0b80c3>
]
rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0xab0b80c3>
]
rcvd [LCP ConfReq id=0x2 <mru 1500> <asyncmap 0x0> ]
sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0xd2e7d8dc>
]
sent [LCP ConfAck id=0x2 <mru 1500> <asyncmap 0x0> ]
rcvd [LCP ConfAck id=0x2 <asyncmap 0x0> <magic 0xd2e7d8dc>
]
rcvd [CHAP Challenge id=0x1 <6418edc36a98005df5032e9ab729ce05>, name =
“”]
Fatal signal 11
PPPD connection closed
=================
NOTE:
- I assume “Fatal signal 11” is SIGSEGV?
- It failed during CHAP.
- I haven’t set up anything in /etc/ppp/whatever because it shouldn’t
be needed for the CLIENT. Anyway, it shouldn’t SIGSEGV.
- The CHAP server send an EMPTY name. Does this crash QNX?
- If you have the above, you can get around it by adding
the UNDOCUMENTED (fix this please - update the documentation)
option “-chap” to ~/ppprc as long as your server supports PAP.
- I can’t install Patch A to see if that fixes it because PPP
is so unreliable that It won’t stay up long enough to
finish downloading the “patch” (36.4Megs is more than a
“patch” 
.
- If QNX wants to duplicate this problem, send me email and I’ll
send you the phone number to try to connect to.
Tom Evans
InitialSurnameAt
tennyson.com.au
Sigh.
I thought by now it is already somewhere in the knowladge database.
Get http://develpers.qnx.com/Fixes/Software/pppd.tar.gz
-xtang
Tom Evans <tom@nospam.invalid> wrote:
Jordan Ostreff wrote:
I have similar problems. Home PatchA for 6.1 will resolve this pppd
issue. Are you fixed this problem?
Pascal Malvert wrote:
…
I found on the knowledge some time ago that a lot of people were having
this problem with 6.1, and that QNX staff was keeping an eye on it.
does someone know what to do, or when a fix is going to be released?
The Patch-A Release Notes don’t mention this at all as something
that has been fixed. Howeverm there’s been other stuff fixed
in Patch A that isn’t mentioned in the Release Notes, so I
don’t think they are at all “definitive”. It would help if
they were more detailed and covered all known fixed bugs.
http://qdn.qnx.com/news/releases/releasenotes_A.html
I searched all of QDN for PPPD giving problems and didn’t find any
update
on one on PPPoE giving “Fatal signal 11”.
I got this on the weekend:
=================
Dialing xxxxxxxx…
ATDTxxxxxxxx
connect 115200
Link Established
Negotiating PPP connection
pppd Started
Using interface ppp0
Connect: ppp0 <–> /dev/ser1
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xab0b80c3> ]
rcvd [LCP ConfReq id=0x0 <mru 1500> <asyncmap 0x0> < 11
04 05 dc> < 13 07 02 cb 17 f4 fe>]
sent [LCP ConfRej id=0x0 < 11 04 05 dc> < 13 07 02 cb 17 f4 fe>]
rcvd [LCP ConfReq id=0x1 <mru 1500> <asyncmap 0x0> ]
sent [LCP ConfAck id=0x1 <mru 1500> <asyncmap 0x0> ]
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xab0b80c3> ]
rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0xab0b80c3> ]
rcvd [LCP ConfReq id=0x2 <mru 1500> <asyncmap 0x0> ]
sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0xd2e7d8dc> ]
sent [LCP ConfAck id=0x2 <mru 1500> <asyncmap 0x0> ]
rcvd [LCP ConfAck id=0x2 <asyncmap 0x0> <magic 0xd2e7d8dc> ]
rcvd [CHAP Challenge id=0x1 <6418edc36a98005df5032e9ab729ce05>, name =
“”]
Fatal signal 11
PPPD connection closed
=================
NOTE:
- I assume “Fatal signal 11” is SIGSEGV?
- It failed during CHAP.
- I haven’t set up anything in /etc/ppp/whatever because it shouldn’t
be needed for the CLIENT. Anyway, it shouldn’t SIGSEGV.
- The CHAP server send an EMPTY name. Does this crash QNX?
- If you have the above, you can get around it by adding
the UNDOCUMENTED (fix this please - update the documentation)
option “-chap” to ~/ppprc as long as your server supports PAP.
- I can’t install Patch A to see if that fixes it because PPP
is so unreliable that It won’t stay up long enough to
finish downloading the “patch” (36.4Megs is more than a
“patch” > > .
- If QNX wants to duplicate this problem, send me email and I’ll
send you the phone number to try to connect to.
Tom Evans
InitialSurnameAt
tennyson.com.au