Description of problem: I have a Sagem Fast 800 USB Modem, and it is not supported by NetworkManager, though popular in Europe and Africa Version-Release number of selected component (if applicable): NetworkManager-0.7.996-6.git20091021.fc12.i686 How reproducible: Always Steps to Reproduce: 1.Plug in ur USB Modem 2.Try to get connected using NetworkManager 3.No connection ! Actual results: no connection Expected results: get connected Additional info: To get connected using this modem, i need first to install the firmware ( https://bugzilla.redhat.com/show_bug.cgi?id=516312 ), then wait for synchronization, after that I issue the following commands : **************************************************** 1 - pkill NetworkManager 2 - br2684ctl -c 0 -b -a 8.35 3 - ifconfig nas0 up 4 - pppd call menara-adsl 5 - rm -f /etc/resolv.conf 6 - ln -s /var/run/ppp/resolv.conf /etc/resolv.conf **************************************************** where menara-adsl is a script of the form (in /etc/ppp/peers/): **************************************************** user "user@menara" plugin rp-pppoe.so nas0 noipdefault usepeerdns defaultroute persist noauth **************************************************** password is stored in /etc/ppp/chap-secrets Explanation and ideas : 1 - make applications network unaware and connect automatically. 2 - create a virtual ethernet interface nas 0, the parameter -a varies from ISP to ISP (in fact they are two parameters, VPI and VCI). 3 - bring up nas0 4 - call pppd with the specified config file (menara-adsl) 5,6 - Workaround for the bug : https://bugzilla.redhat.com/show_bug.cgi?id=524767 And here is my idea on how it should be implemented : - Detect the modem based on its usb serial. - Wait for Synchronization : when synchronization is done a message is issued by the driver ueagle-atm in /var/log/messages - First time wizard : ask for username and password, connection type (PPPoA or PPPoE ), and then the VPI, VCI values. There is a list of known ISPs on http://faq.eagle-usb.org/wakka.php?wiki=ListConfigADSL. After, write the config file in /etc/ppp/peers/adsl-provider - call the above commands In my case the connection is PPPoE, if it is PPPoA, there is no need for nas0. Also, if the Modem's chipset is 1,2 or 3, issue a warning that the firmware isn't available (https://bugzilla.redhat.com/show_bug.cgi?id=516311) due to license issues.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.