Dear Wiki user, You have subscribed to a wiki page or wiki category on "Fedora Project Wiki" for change notification. The following page has been changed by KarstenWade: http://fedoraproject.org/wiki/Docs/Beats/Networking The comment on the change is: up for FC6t2 ------------------------------------------------------------------------------ - {{{ - Fedora Core 5 Release Notes Content is marked like this. - }}} = Networking = + This section has not been updated for Fedora Core [[GetVal(DocsDict,BeatsVer)]] by the [http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Beats beat writer]. + == User Tools == - {{{ - === NetworkManager === + This section has not been updated for Fedora Core [[GetVal(DocsDict,BeatsVer)]] by the [http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Beats beat writer]. - '''Network``Manager''' now has support for DHCP hostname, NIS, ISDN, WPA, WPA supplicant (`wpa_supplicant`), and WPA-Enteprise. It has a new wireless security layer. The VPN and dial up support has been enhanced. Applications such as '''Evolution''' now integrate with '''Network``Manager''' to provide dynamic networking capabilities. '''Network``Manager''' is disabled by default in Fedora as it is not yet suitable for certain configurations, such as system-wide static IPs, bonding devices, or starting a wireless network connection before login. - - To enable '''Network``Manager''' from the desktop: - - 1. Open the '''Services''' application from the menu ''System > Administration Services'' - 1. From the ''Edit Runlevel menu'', choose ''Runlevel All'' - 1. Ensure that the 3 boxes next to the ''dhcdbd'' item in left-side list are checked - 1. Select ''dhcdbd'' in the list, and click the ''Start'' button - 1. Ensure that the 3 boxes next to the ''named'' item in left-hand list are checked - 1. Select ''named'' in the list, and click the ''Start'' button - 1. Ensure that the 3 boxes next to the ''NetworkManager'' item in left-side list are checked - 1. Select ''NetworkManager'' in the list, and click the ''Start'' button - - To enable '''Network``Manager''' from the command line or terminal: - - 1. su -c '/sbin/chkconfig --level 345 dhcdbd on' - 1. su -c '/sbin/service dhcdbd start' - 1. su -c '/sbin/chkconfig --level 345 named on' - 1. su -c '/sbin/service named start' - 1. su -c '/sbin/chkconfig --level 345 NetworkManager on' - 1. su -c '/sbin/service NetworkManager start' - - For a list of common wireless cards and drivers that '''Network``Manager''' supports, refer to the [http://live.gnome.org/NetworkManagerHardware NetworkManager Hardware] page. - - === iproute === - - The IPv4 address deletion algorithm did not take the prefix length into account up to kernel version 2.6.12. Since this has changed, the `ip` tool from the `iproute` package now issues a warning if no prefix length is provided, to warn about possible unintended deletions: - - {{{ip addr list dev eth0 - 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 - inet 10.0.0.3/24 scope global eth0 - ##}}} - {{{su -c 'ip addr del 10.0.0.3 dev eth0' - Warning: Executing wildcard deletion to stay compatible with old - scripts. Explicitly specify the prefix length (10.0.0.3/32) to - avoid this warning. This special behaviour is likely to disappear - in further releases, fix your scripts! - ##}}} - - The correct method of deleting the address and thus avoiding the warning is: - - {{{su -c 'ip addr del 10.0.0.3/24 dev eth0' - ##}}} - - Previously, it was not possible to tell if an interface was down administratively or because no carrier was found, such as if a cable were unplugged. The new flag {{{NO-CARRIER}}} now appears as a link flag if the link is administratively up but no carrier can be found. - - The `ip` command now supports a batch mode via the argument {{{-batch}}}, which works similar to the `tc` command to speed up batches of tasks. - }}} == Major Kernel Changes == - {{{ - === 2.6.11 - 2.6.15 === - Refer to http://wiki.kernelnewbies.org/LinuxChanges for a list of major changes. Some of them are highlighted below. + This section has not been updated for Fedora Core [[GetVal(DocsDict,BeatsVer)]] by the [http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Beats beat writer]. - === IPv4 Address Promotion === - - Starting with version 2.6.12 of the kernel, a new feature has been added called ''named address promotion''. This feature allows secondary IPv4 addresses to be promoted to primary addresses. Usually when the primary address is deleted, all secondary addresses are deleted as well. If you enable the new `sysctl` key {{{net.ipv4.conf.all.promote_secondaries}}}, or one of the interface specific variants, you can change this behavior to promote one of the secondary addresses to be the new primary address. - - === Configurable Source Address for ICMP Errors === - - By default, when selecting the source address for ICMP error messages, the kernel uses the address of the interface on which the ICMP error is going to be sent. Kernel version 2.6.12 introduces the new `sysctl` key {{{net.ipv4.icmp_errors_use_inbound_ifaddr}}}. If you enable this option the kernel uses the address of the interface that received the original error-causing packet. - - Suppose the kernel receives a packet on interface `eth0` which generates an ICMP error, and the routing table causes the error message to be generated on interface `eth1`. If the new `sysctl` option is enabled, the ICMP error message indicates the source address as interface `eth0`, instead of the default `eth1`. This feature may ease network debugging in asynchronous routing setups. - - === LC-Trie Based Routing Lookup Algorithm === - - A new routing lookup algorithm called ''trie'' has been added. It is intended for large routing tables and shows a clear performance improvement over the original hash implementation, at the cost of increased memory consumption and complexity. - - === Pluggable Congestion Control Algorithm Infrastructure === - - TCP congestion control algorithms are now pluggable and thus modular. The legacy New''''''Reno algorithm remains the default, and acts as the fallback algorithm. The following new congestion control algorithms have been added: - - * High Speed TCP congestion control - * TCP Hybla congestion avoidance - * H-TCP congestion control - * Scalable TCP congestion control - - All existing congestion control modules have been converted to this new infrastructure, and the BIC congestion control has received enhancements from BICTCP 1.1 to handle low latency links. - - || {i} '''Affecting the Congestion Control Algorithm''' || - || The congestion control algorithm is socket specific, and may be changed via the socket option {{{TCP_CONGESTION}}}. || - - === Queue Avoidance upon Carrier Loss === - - When a network driver notices a carrier loss, such as when the cable is pulled out, the driver stops the queue in front of the driver. In the past, this stoppage caused the packets to be queued at the queueing discipline layer for an unbound period of time causing unexpected effects. In order to prevent this effect, the core networking stack now refuses to queue any packets for a device that is operationally down, that is, has its queue disabled. - - === DCCP Protocol Support === - - Kernel version 2.6.14-rc1 was the first version to receive support for the DCCP protocol. The implementation is still experimental, but is known to work. Developers have begun work to make userspace applications aware of this new protocol. - - === Wireless === - - A new HostAP driver appears in the kernel starting in 2.6.14-rc1, which allows the emulation of a wireless access point through software. Currently this driver only works for Intersil Prism2-based cards (PC Card/PCI/PLX). Support for wireless cards Intel(R) PRO/Wireless 2100 and 2200 has been added. - - === Miscellaneous === - - * Many TCP Segmentation Offloading (TSO) related fixes are included. - * A new textsearch infrastructure has been added, and is usable with corresponding iptables and extended match. - * Both the IPv4 and IPv6 multicast joining interface visible by userspace have been reworked and brought up to the latest standards. - * The SNMPv2 MIB counter ipInAddrErrors is supported for IPv4. - * Various new socket options proposed in Advanced API (RFC3542) have been added. - }}} -
