After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 630332 - NetworkManager should not disconnect from any networks while connecting to another
NetworkManager should not disconnect from any networks while connecting to an...
Status: RESOLVED DUPLICATE of bug 559134
Product: NetworkManager
Classification: Platform
Component: general
git master
Other Linux
: Normal major
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2010-09-22 11:29 UTC by Vitaly
Modified: 2010-09-22 21:51 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
ifconfig and route tables log (5.50 KB, text/plain)
2010-09-22 11:29 UTC, Vitaly
Details

Description Vitaly 2010-09-22 11:29:52 UTC
Created attachment 170826 [details]
ifconfig and route tables log

Overview:
My ISP provides metropolitan area Ethernet network (eth0) and PPPoE connection for access to Internet (ppp0). However, NetworkManager (NM) disconnects eth0 while establishing ppp0 (log with ifconfig and route tables is attached).
I believe that this bug is caused by assumption that PPPoE and Ethernet can not run simultaneously without conflicts.  Or probably by assumption that one network may work only if some other are on/off.  However, I can setup these networks (with system-config-network tool) to work simultaneously.
I think NM should be able to turn on/off each network separately and independently. Right now NM implements something like switching between networks. I'm sure, this is a wrong way. Actually it complicates NM setup and also its development and bugfixing. I have looked at buglist, I have found some bugs which are resulted by this inconvenience.
Why don't to let the user to decide which network he like to run or to turn off? It will not violate your Design Goals. If something goes wrong (routes conflicts, lost connection, etc.), NM always may notify the user.

Steps to reproduce:
1) Setup Ethernet and PPPoE connections (you should have a machine connected to such networks)
2) Run Ethernet interface
3) Run PPPoE connection

Actual Results:
If you open nm-applet menu (click left button on tray icon) you will see that the Ethernet connection now is inactive.

Expected Results:
Ethernet should be on.

Build Date & Platform:
Build from master branch Wed Sep 22, 9:00 GMT, Fedora 13.
Comment 1 Dan Williams 2010-09-22 21:51:47 UTC
Correct you are, we should be running PPPoE while preserving LAN connectivity on that interface.

*** This bug has been marked as a duplicate of bug 559134 ***