|
|
| Line 1: |
Line 1: |
| == Networking == | | == Networking == |
|
| |
|
| This section contains information about networking changes in Fedora 11.
| | === NetworkManager with system wide connections and enhanced support for Mobile Broadband === |
|
| |
|
| === DNSSEC ===
| | NetworkManager can now create and edit system-wide network connections in /etc/sysconfig. NetworkManager has been able to read information about system-wide network connections from /etc/sysconfig for a while. Now we have enabled full read-write support for system connections. The ability to create or modify new system connections will be controlled by PolicyKit policies. Initially, only wired/wireless connections will be supported. Later on, vpn connections will follow. For connections that require secrets, those will be stored in .keys files in /etc/sysconfig. |
|
| |
|
| The {{package|bind}} and {{package|unbound}} recursive DNS servers now enable DNSSEC validation in their default configuration. DNSSEC Lookaside Verification (DLV) is also enabled with the <code>dlv.sc.org</code> DLV Registry. This behavior can be modified in {{filename|/etc/sysconfig/dnssec}} by changing the DNSSEC and DLV settings.
| | By providing a database of preconfigured mobile broadband providers, supporting more hardware and permit to scan GSM networks, NetworkManager makes the use of mobile broadband much easier. Your broadband provider will be automatically recognized by NetworkManager and it will make it easy to just plug it your USB device and get you online within minutes. |
|
| |
|
| 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.
| | [[Category:Docs Project]] |
| | | [[Category:Draft documentation]] |
| === TigerVNC ===
| |
| | |
| TigerVNC is used as default VNC project. Package names were changed to {{package|tigervnc}}, {{package|tigervnc-server}} and {{package|tigervnc-server-module}}. Binary names are the same as in previous versions. The {{filename|libvnc.so}} module has been moved to the {{package|tigervnc-server-module}} subpackage. Otherwise there should be no difference.
| |
| | |
| === 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.
| |
| | |
| 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.
| |
Networking
NetworkManager with system wide connections and enhanced support for Mobile Broadband
NetworkManager can now create and edit system-wide network connections in /etc/sysconfig. NetworkManager has been able to read information about system-wide network connections from /etc/sysconfig for a while. Now we have enabled full read-write support for system connections. The ability to create or modify new system connections will be controlled by PolicyKit policies. Initially, only wired/wireless connections will be supported. Later on, vpn connections will follow. For connections that require secrets, those will be stored in .keys files in /etc/sysconfig.
By providing a database of preconfigured mobile broadband providers, supporting more hardware and permit to scan GSM networks, NetworkManager makes the use of mobile broadband much easier. Your broadband provider will be automatically recognized by NetworkManager and it will make it easy to just plug it your USB device and get you online within minutes.
