mNo edit summary |
(add workaround for the ethernet issue) |
||
| Line 15: | Line 15: | ||
=== Ethernet connections are not started at first boot === | === Ethernet connections are not started at first boot === | ||
See [[rhbug:498207|Bug #498207]]. If you install Fedora 11 using a non-network-based method (e.g. CD or DVD), ethernet connections will not be automatically initialized at first boot, which is not the behaviour most people would expect. This is in fact intentional (enabling network interfaces on boot by default has security implications in some situations), but in future Fedora releases, there will be an option in the installer to designate which interfaces should be started at boot time. | See [[rhbug:498207|Bug #498207]]. If you install Fedora 11 using a non-network-based method (e.g. CD or DVD), ethernet connections will not be automatically initialized at first boot, which is not the behaviour most people would expect. This is in fact intentional (enabling network interfaces on boot by default has security implications in some situations), but in future Fedora releases, there will be an option in the installer to designate which interfaces should be started at boot time. You can use the NetworkManager tray icon to enable the ethernet interface you wish to use, but you would have to do this at each boot. To specify that an interface should always be started on boot, use the Network Connections tool: in the system menu, it is under System > Preferences > Network Connections. In the ''Wired'' tab, select the interface you wish to start at boot, and click ''Edit''. Check the box marked ''Connect automatically'', then click ''Apply'', and quit the tool. | ||
Revision as of 17:54, 4 June 2009
Networking
This section contains information about networking changes in Fedora 11.
DNSSEC
The 
binddlv.sc.org DLV Registry. This behavior can be modified in /etc/sysconfig/dnssec by changing the DNSSEC and DLV settings.
With DNSSEC enabled, when a domain supplies DNSSEC data (such as .gov, .se, the ENUM zone and other TLD's) then that data will be cryptographically validated on the recursive DNS server. If validation fails due to attempts at cache poisoning, for example via a Kaminsky Attack, then the end user will not be given this forged/spoofed data. DNSSEC deployment is gaining speed rapidly, and is a crucial and logical step to make the Internet more secure for end users. DLV is used to add DNSSEC signed domains into TLD's that themselves are not yet signed, such as .com and .org.
TigerVNC
TigerVNC is used as default VNC project. Package names were changed to libvnc.so module has been moved to the
Ethernet connections are not started at first boot
See Bug #498207. If you install Fedora 11 using a non-network-based method (e.g. CD or DVD), ethernet connections will not be automatically initialized at first boot, which is not the behaviour most people would expect. This is in fact intentional (enabling network interfaces on boot by default has security implications in some situations), but in future Fedora releases, there will be an option in the installer to designate which interfaces should be started at boot time. You can use the NetworkManager tray icon to enable the ethernet interface you wish to use, but you would have to do this at each boot. To specify that an interface should always be started on boot, use the Network Connections tool: in the system menu, it is under System > Preferences > Network Connections. In the Wired tab, select the interface you wish to start at boot, and click Edit. Check the box marked Connect automatically, then click Apply, and quit the tool.