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 518189 - Static IP Does Not Work
Static IP Does Not Work
Status: RESOLVED INCOMPLETE
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2008-02-23 04:01 UTC by Jason Tang
Modified: 2009-01-19 12:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jason Tang 2008-02-23 04:01:32 UTC
Please describe the problem:
Using NM 0.7 in Fedora 8.

Static IP addressing does not appear to work on eth device.  Static does work when NM is disabled, but when NM service is started, it immediately retrieves a DHCP address.

Steps to reproduce:
1. Set static IP.
2. ifup eth0
3. ifconfig eth0 (verify)
4. service NetworkManager start
5. ifconfig eth0 (see NM ignore static settings)


Actual results:
User gets very frustrated.  Disables NM.  Fires off a bug report.

Expected results:
I would expect NM to respect static IP settings on a per-device basis (at least), and hopefully someday allow for per-AP wlan settings.

Does this happen every time?
Yes.

Other information:
Comment 1 Joseph Piche 2008-03-20 19:58:53 UTC
This bug has been reported in Ubuntu:

https://bugs.launchpad.net/network-manager-applet/+bug/202605

This is a common problem that should be confirmed.
Comment 2 Dan Williams 2008-03-20 20:07:36 UTC
NM now respects static IP configurations via the system settings service, for which there are plugins for Fedora and SUSE.  If you have a static IP address specified in, for example, /etc/sysconfig/network-scripts/ifcfg-eth0 (and you have created it with system-config-network), NM will use those static IP settings to configure the device.
Comment 3 Jason Tang 2008-03-20 22:10:15 UTC
Sorry Dan, but that's simplyt not the behaviour we've been experiencing.  I'm using the latest NM with Fedora 8.  Static IP simply does not work with NM.


[root@jt001 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
GATEWAY=192.168.25.1
TYPE=Ethernet
DEVICE=eth0
HWADDR=00:04:0b:80:80:80
BOOTPROTO=none
NETMASK=255.255.255.0
IPADDR=192.168.25.100
ONBOOT=no
USERCTL=no
PEERDNS=yes
IPV6INIT=no
NM_CONTROLLED=yes


The above is my static config.  Starting NM produces the following:

[root@jt001 ~]# ifconfig 
eth0      Link encap:Ethernet  HWaddr 00:04:0B:80:80:80  
          inet addr:192.168.25.197  Bcast:192.168.25.255  Mask:255.255.255.0
          inet6 addr: fe80::204:bff:fe80:8080/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:456601 errors:0 dropped:0 overruns:0 frame:0
          TX packets:268219 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:598546975 (570.8 MiB)  TX bytes:23320717 (22.2 MiB)
          Interrupt:19 Base address:0x8000 


Do you have any ideas on how to fix this bug?
Comment 4 Dan Williams 2008-04-08 21:54:35 UTC
So the version currently in F8 (svn3235) looks for ifcfgs where system-config-network puts them, in /etc/sysconfig/networking/profiles/default/, which is actually the wrong place.  Later versions (in rawhide, will filter back to F8 too) look in /etc/sysconfig/network-scripts/
Comment 5 Jason Tang 2008-04-08 22:08:27 UTC
(In reply to comment #4)
> So the version currently in F8 (svn3235) looks for ifcfgs where
> system-config-network puts them, in
> /etc/sysconfig/networking/profiles/default/, which is actually the wrong place.
>  Later versions (in rawhide, will filter back to F8 too) look in
> /etc/sysconfig/network-scripts/
> 

F8 has the exact same ifcfg-eth0 script in both
/etc/sysconfig/network-scripts
/etc/sysconfig/networking/profiles/default

This should ensure compatibility.
Comment 6 Dan Williams 2008-04-27 21:41:45 UTC
Jason: what exact version are you using?  Latest is svn3370 I believe, that reads the correct files from /etc/sysconfig/network-scripts/ these days.  Also, make sure that your ifcfg-* files don't have "NM_CONTROLLED=no" in them; if they do, change that to "NM_CONTROLLED=yes".
Comment 7 Christoph Wurm 2009-01-19 12:09:43 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!