Hi Marcelo,<br><br><div class="gmail_quote">On Sun, Nov 30, 2008 at 11:47, Marcelo Magno T. Sales <span dir="ltr"><<a href="mailto:mmtsales@gmail.com" target="_blank">mmtsales@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Andre,<br>
<br>
Em Dom 30 Nov 2008, Andre Costa escreveu:<br>
<div><div>> Hi,<br>
><br>
> I just installed F10 on my system (replacing -- not upgrading -- a<br>
> previous F9 installation). In general, installation went by just<br>
> fine. However, setting up my network has been unbelievably hard.<br>
><br>
> I have a DI-624 router, and I am using static IP (I turned its DHCP<br>
> server off because it was rebooting when my wife's MacBook Pro<br>
> connected). This setup has worked flawlessly with F9 and even F8.<br>
><br>
> First weird symptom: NetworkManager refuses to allow me to edit<br>
> settings for eth0. It doesn't ask me for any kind of authentication<br>
> and simply shows all fields disabled. I don't know why it started<br>
> doing this, because right after I booted for the first time I was<br>
> able to edit it. Later on I disabled SELinux, don't know if this is<br>
> related somehow. This is specially annoying because I can't configure<br>
> DNS servers this way, and must always edit /etc/resolv.conf manually.<br>
><br>
> Second weird symptom: System > Administration > Network Device<br>
> Control didn't show any interfaces I could manage (maybe this is the<br>
> correct behavior when NetworkManger is in charge, I don't know...)<br>
><br>
> So, I turned NM off and switched back to plain system-config-network<br>
> (which I'd rather not do, since I need to use NetworkManager every<br>
> now and then to manage a GSM modem).<br>
><br>
> To my surprise, even though I try to set my subnet mask to<br>
> <a href="http://255.255.255.0" target="_blank">255.255.255.0</a>, it was setting it to my IP address (<a href="http://192.168.0.100" target="_blank">192.168.0.100</a>), or<br>
> sometimes to my gateway address (<a href="http://192.168.0.1" target="_blank">192.168.0.1</a>). I had to manually go<br>
> through the files at /etc/sysconfig/network/ to fix this. Also, s-c-n<br>
> allowed me to create a copy of eth0 profile, but didn't allow me to<br>
> remove it (had to do it manually as well).<br>
><br>
> Right now everything is working just fine I guess, but if I reenable<br>
> NM it screws things up again.<br>
><br>
> AFAICS I'm probably experiencing many bugs at once (NM and s-c-n).<br>
> Anyone experienced anything like this? Should I start filing bug<br>
> reports?<br>
<br>
</div></div>It seems that, for using static IP address, it's indeed better to use<br>
the old network daemon than NetworkManager. I had the same problem too<br>
and have read many, many reports of similar ones on the net.<br>
Regarding the system-config-network problem with the netmask, this is<br>
already reported in Redhat's bugzilla and a new version of system-<br>
config-network which solves the problem has already been push to<br>
updates. It's not available for download yet, but should be in the next<br>
few days. For now, if you want to use static addresses, you need to edit<br>
the /etc/sysconfig/network-scripts/ifcfg-eth* files to correct the<br>
netmask.<br>
<font color="#888888"><br>
</font></blockquote><div></div><div>Thks for the info, indeed something is really broken with NM + static IP, I just can't make it work -- and, worst of all, it screws a working eth0 configuration. It's really a pity, because I rely on NM to manage my non-eth0 connections, losing it will imply much more manual work. And, it was working on F9...</div>
<div>But, it doesn't help to keep moaning about it (aside from the fact that it sucks this got past QA =/ ), I'll file a bug report if one doesn't exist already and hope this gets fixed soon.</div><div></div>
<div>... I just searched Bugzilla and found this one, seems to be what I am experiencing:</div><div>
</div><div><a href="https://bugzilla.redhat.com/show_bug.cgi?id=473002" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=473002</a></div>
<div><a href="https://bugzilla.redhat.com/show_bug.cgi?id=427072" target="_blank"></a></div><div>I'll leave a comment describing my problem hoping it will help catching attention to this problem.</div><div></div><div>
Regards,</div><div></div><div>Andre</div></div>