Red Hat Bugzilla – Bug 234935
ppp0 with USB ADSL modem and ATM protocol not working at boot time
Last modified: 2008-05-06 15:26:47 EDT
Description of problem:
Whenever I started my PC connected to and ADSL USB modem (Huawei) I have to make
the conection by hand. Now I entered the commands to the /etc/rc.local and
connection is comming up at boot time, but I think the place for this is in the
network configuration scripts, especificaly
The lines I have to add are:
br2684ctl -c 0 -b -a 0.33
ifconfig nas0 up
Version-Release number of selected component (if applicable):
As mentioned above
Steps to Reproduce:
If I enable ppp0 at boot it doesn't work
ppp0 has to come up in boot time.
1) if you need to load that module by hand, it's a bug in that module
2) the br2684ctl line looks like it's best done in a udev script
3) what is nas0?
Sorry Bill. Got it fixed in modprobe.conf:
alias nas0 br2684
install br2684 /sbin/modprobe --ignore-install br2684 && /usr/sbin/br2684ctl -c
0 -b -a 0.33 >/dev/null 2>&1 || :
The thing was that there was no information on how to automatize this. Seeing
how the sound card got loaded I tried those lines in modprobe.conf whcih work
like a charme.
With that, does it work?
If it's a USB device, the driver really should be loading automatically.
The problem was not with the USB module, which is the ueagle-atm, but with the
br2685 module (I'm not an expert on this) that is a bridge to the ATM protocol.
The thing is that there are parameters that have to be given to the module (the
br2684) to make it work with my ISP (the -a 0.33 argument), and the only way I
knew how to do it was with the command lines that I stated in the original
Maybe, as there is a proliferance of USB modem there should be a graphical
interface in Fedora con configure them.
Moving to system-config-network, then. Not sure how automatically this could be
detected and configured, though.
very difficult to automatize this...
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.