[Bug 825177] New: loopback is not added to routing table by NetworkManager at all
https://bugzilla.novell.com/show_bug.cgi?id=825177 https://bugzilla.novell.com/show_bug.cgi?id=825177#c0 Summary: loopback is not added to routing table by NetworkManager at all Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mikeandmore@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 I'm enabling NetworkManager to use the wireless, and NetworkManager manage the loopback interface as well. NetworkManager is able to bring up the lo interface, but it'ss not adding lo to the routing table. Here is my ifcfg-lo # Loopback (lo) configuration IPADDR=127.0.0.1 NETMASK=255.0.0.0 NETWORK=127.0.0.0 BROADCAST=127.255.255.255 STARTMODE=auto USERCONTROL=no ONBOOT=yes FIREWALL=no NAME=loopback and here is what happened: mike@mike-laptop% /sbin/ifconfig lo lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:104 errors:0 dropped:0 overruns:0 frame:0 TX packets:104 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:11735 (11.4 Kb) TX bytes:11735 (11.4 Kb) mike@mike-laptop% ip route default via 192.168.1.1 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.140 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 ^^^^^^^^^^^^^^ Here, there is no dev lo in the routing table at all. Right now I'm adding ip route add into boot.local as a workaround, but it's not a clean solution. Reproducible: Always Steps to Reproduce: 1. Boot 2. /sbin/ifconfig and see lo interface is up 3. ip route couldn't see lo in the routing table Actual Results: ifconfig should report lo is up, and ip route should be able to see lo in the routing table. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825177 https://bugzilla.novell.com/show_bug.cgi?id=825177#c FeiXiang Zhang <fxzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |bnc-team-gnome@forge.provo. |ovo.novell.com |novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=825177 https://bugzilla.novell.com/show_bug.cgi?id=825177#c1 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |dimstar@opensuse.org InfoProvider| |mikeandmore@gmail.com --- Comment #1 from Dominique Leuenberger <dimstar@opensuse.org> 2014-08-11 21:41:40 UTC --- Apologies for the etrnal late reply - for some reason this one never figured on my list.. Looking at the report, I must be missing something: why do you expxect an entry for 127.0.0.0/8 dev lo in your output? Is there anything not working, besides the fact that it's not listed in the output of 'ip route' ? (please try 'ping 127.4.5.6' to test) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com