Bug 355281 - ifup MyModem fails claiming a script error
Summary: ifup MyModem fails claiming a script error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: ppp
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Jiri Skala
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-27 14:57 UTC by Brian G. Anderson
Modified: 2014-11-09 22:30 UTC (History)
1 user (show)

Fixed In Version: ppp-2.4.4-6.fc9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-19 13:20:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/var/log/message when ppp tries to connect. (1.27 KB, application/octet-stream)
2007-10-27 14:57 UTC, Brian G. Anderson
no flags Details

Description Brian G. Anderson 2007-10-27 14:57:21 UTC
Description of problem:
I have a bluetooth phone setup up according to the instruction at this site
http://72.14.253.104/search?q=cache:RRhBK7dmkIgJ:tronbikes.com/linux/+cu500+fedora&hl=en&client=firefox-a&gl=us&strip=0
Even though it is for FC5 and an T41,  it is the same setup for my FC6,FC7,FC8
Dell D620.  Under FC8 I get "The connect script failed (maybe wrong password or
wrong phone number)".  The log only reports "Connect script failed".

However when I "wvdial Cingular" as root is connects fine, though it doesn't
update "resolve.conf" properly.  I've attached the relevant part of
/var/log/message below.

Both times I stopped NetworkManager, though under FC6 and FC7 this was never
necessary.

/var/log/ppp *never* has anything in it.  Even when I successfully connect using
wvdail.  I'm guessing it's not logging for some reason.

Even though I'm using a bluetooth connection, I don't think it has anything to
do with bluetooth, since I am able to use minicom to the phone over the
/dev/rfcomm0 device and manually instruct it to dial with no problems. 
Unfortunately,  my laptop only has a softmodem so I cannot test ppp any other way.


Version-Release number of selected component (if applicable):
ppp-2.4.4-2


How reproducible:
every time

Steps to Reproduce:
1. setup connection
2. use ifup <Connection>
3.
  
Actual results:


Expected results:
connect ppp

Additional info:

Comment 1 Brian G. Anderson 2007-10-27 14:57:21 UTC
Created attachment 240471 [details]
/var/log/message when ppp tries to connect.

Comment 2 Martin Nagy 2008-04-07 13:24:44 UTC
PPP doesn't write to /var/log/ppp because it is a bug, see Bug 249152 . It is
now fixed with ppp-2.4.4-6.fc9, otherwise, the logs go to /etc/ppp, but SELinux
probably prevents that. The link you gave is no longer working.. Can you find it
anywhere?
Also, could you please attach your /etc/sysconfig/network-scripts/ifcfg- of the
connection you are trying to use? (just be careful, there might be sensitive
informations in there). Thanks.

Comment 3 Bug Zapper 2008-05-14 03:46:00 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Brennan Ashton 2008-06-08 02:48:52 UTC
Reporter, could you please reply to the previous question? If you won't reply in
one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

Comment 5 Brian G. Anderson 2008-06-09 12:42:33 UTC
As of FC9,  I don't see this problem anymore.

Comment 6 Jiri Skala 2008-06-19 13:20:53 UTC
(In reply to comment #5)
> As of FC9,  I don't see this problem anymore.

Hi, in relation to your comment I'll close the bug.


Note You need to log in before you can comment on or make changes to this bug.