Bug 234935 - ppp0 with USB ADSL modem and ATM protocol not working at boot time
ppp0 with USB ADSL modem and ATM protocol not working at boot time
Product: Fedora
Classification: Fedora
Component: system-config-network (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Depends On:
  Show dependency treegraph
Reported: 2007-04-02 18:03 EDT by Martí­n Marqués
Modified: 2008-05-06 15:26 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 15:26:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Martí­n Marqués 2007-04-02 18:03:43 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:

modprobe br2684
br2684ctl -c 0 -b -a 0.33
ifconfig nas0 up
ifup ppp0

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


How reproducible:

As mentioned above

Steps to Reproduce:
Actual results:

If I enable ppp0 at boot it doesn't work

Expected results:

ppp0 has to come up in boot time.

Additional info:
Comment 1 Bill Nottingham 2007-04-05 23:28:32 EDT
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?

Comment 2 Martí­n Marqués 2007-04-06 16:34:28 EDT
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.

Thaks anyway.
Comment 3 Bill Nottingham 2007-04-07 18:16:29 EDT
With that, does it work?

If it's a USB device, the driver really should be loading automatically.
Comment 4 Martí­n Marqués 2007-04-08 10:32:30 EDT
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
message here.

Maybe, as there is a proliferance of USB modem there should be a graphical
interface in Fedora con configure them.
Comment 5 Bill Nottingham 2007-04-16 18:05:27 EDT
Moving to system-config-network, then. Not sure how automatically this could be
detected and configured, though.
Comment 6 Harald Hoyer 2007-04-17 03:54:21 EDT
very difficult to automatize this...
Comment 7 Bug Zapper 2008-04-04 02:44:34 EDT
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
the change.

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
Comment 8 Bug Zapper 2008-05-06 15:26:45 EDT
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.

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