Hello Michal, Monday, November 24, 2008, 1:51:34 PM, you wrote: > On Mon, Nov 24, 2008 at 10:22:53AM -0800, Chuck Forsberg WA7KGX N2469R wrote: >> Here it is on Rawhide. I did not enter 70... as netmask! > .... >> BROADCAST=70.89.176.169 > ..... >> IPADDR=70.89.176.169 >> NETMASK=70.89.176.170 ## entered as 255.255.255.252 > With 255.255.255.252 (/30) for a netmask a broadcast address above > does not make any sense too. It should read 70.89.176.171. > Do you really have only two hosts interfaces on this network as your > /30 netmask choice would indicate? > Michal My experiences are identical - static networking is extremely unwell for the FC10 release right now. Something (system-config-network ?) is setting the NETMASK value to the value entered for NETWORK. system-config-network also terminates with an exception when I try to enable MTU and set to 1492 (I'm on DSL). One must manually change the /etc/sysconfig/networking/devices files to restore normal operation. I have installed FC10 on 2 machines this weekend, one X64 (upgrade from FC8) and one i386 (fresh install on new 1 TB drive) with the same results. I am setting them up with static networking as both are intended to host both BIND and DHCP servers. The X64 machine was fine running the default NetworkManager configuration while the i386 provided those services under FC8, but immediately failed this way when set to static addressing to act as interim server. After much frustration, the X64 machine was operational enough to commence the i386 install - which immediately failed the same way when networking services were changed to swap NetworkManager out for Network and to set eth0 to static IP values. It is very frustrating for such a basic/critical service fails so badly! Al -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
