openadk/target/linux/config/Config.in.network

menu "Network support"

config ADK_KERNEL_INET
	boolean
	default y

config ADK_KERNEL_IP_FIB_HASH
	boolean
	default y

config ADK_KERNEL_SYN_COOKIES
	boolean
	default n

config ADK_KERNEL_IP_PNP_BOOTP
	boolean
	default n

config ADK_KERNEL_IP_PNP_RARP
	boolean
	default n

config ADK_KERNEL_NET_IPGRE_BROADCAST
	boolean
	default n

config ADK_KERNEL_PPP_ASYNC
	boolean
	default n

config ADK_KERNEL_SLHC
	boolean
	default n

config ADK_KERNEL_IMQ
	tristate
	default n

config ADK_KERNEL_LLC
	tristate
	default n

config ADK_KPACKAGE_KMOD_ATM
	prompt "kmod-atm.......................... Asynchronous Transfer Mode (ATM)"
	tristate
	default n
	help
	 ATM is a high-speed networking technology for Local Area Networks
	 and Wide Area Networks.  It uses a fixed packet size and is
	 connection oriented, allowing for the negotiation of minimum
	 bandwidth requirements.

	 In order to participate in an ATM network, your Linux box needs an
	 ATM networking card. If you have that, say Y here and to the driver
	 of your ATM card below.

	 Note that you need a set of user-space programs to actually make use
	 of ATM.  See the file <file:Documentation/networking/atm.txt> for
	 further details.

config ADK_KPACKAGE_KMOD_ATM_BR2684
	prompt "kmod-atm-br2684................... BR2684 ATM module"
	tristate
	default n
	help

config ADK_KPACKAGE_KMOD_BRIDGE
	prompt "kmod-net-bridge................... 802.1d Ethernet Bridging"
	tristate
	select ADK_KERNEL_LLC
	default n
	help
	  If you say Y here, then your Linux box will be able to act as an
	  Ethernet bridge, which means that the different Ethernet segments it
	  is connected to will appear as one Ethernet to the participants.
	  Several such bridges can work together to create even larger
	  networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
	  As this is a standard, Linux bridges will cooperate properly with
	  other third party bridge products.

	  In order to use the Ethernet bridge, you'll need the bridge
	  configuration tools; see <file:Documentation/networking/bridge.txt>
	  for location. Please read the Bridge mini-HOWTO for more
	  information.

	  If you enable iptables support along with the bridge support then you
	  turn your bridge into a bridging IP firewall.
	  iptables will then see the IP packets being bridged, so you need to
	  take this into account when setting up your firewall rules.
	  Enabling arptables support when bridging will let arptables see
	  bridged ARP traffic in the arptables FORWARD chain.

config ADK_KPACKAGE_KMOD_INET_TUNNEL
	tristate
	default n
	help

config ADK_KPACKAGE_KMOD_NET_IPIP
	prompt "kmod-net-ipip..................... IP in IP encapsulation support"
	tristate
	select ADK_KPACKAGE_KMOD_INET_TUNNEL
	default n
	help
	  Tunneling means encapsulating data of one protocol type within
	  another protocol and sending it over a channel that understands the
	  encapsulating protocol. This particular tunneling driver implements
	  encapsulation of IP within IP, which sounds kind of pointless, but
	  can be useful if you want to make your (or some other) machine
	  appear on a different network than it physically is, or to use
	  mobile-IP facilities (allowing laptops to seamlessly move between
	  networks without changing their IP addresses).


config ADK_KPACKAGE_KMOD_NET_IPGRE
	prompt "kmod-net-ipgre.................... GRE tunnels over IP"
	tristate
	#depends on ADK_KPACKAGE_KMOD_NET_IPGRE_BROADCAST
	default n
	help
	  Tunneling means encapsulating data of one protocol type within
	  another protocol and sending it over a channel that understands the
	  encapsulating protocol. This particular tunneling driver implements
	  GRE (Generic Routing Encapsulation) and at this time allows
	  encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
	  This driver is useful if the other endpoint is a Cisco router: Cisco
	  likes GRE much better than the other Linux tunneling driver ("IP
	  tunneling" above). In addition, GRE allows multicast redistribution
	  through the tunnel.

config ADK_KPACKAGE_KMOD_IPV6
	prompt "kmod-ipv6......................... IPv6 support"
	tristate
	default n
	help
	  This is complemental support for the IP version 6.
	  You will still be able to do traditional IPv4 networking as well.

	  For general information about IPv6, see
	  <http://playground.sun.com/pub/ipng/html/ipng-main.html>.
	  For Linux IPv6 development information, see <http://www.linux-ipv6.org>.
	  For specific information about IPv6 under Linux, read the HOWTO at
	  <http://www.bieringer.de/linux/IPv6/>.

config ADK_KPACKAGE_KMOD_IPV6_SIT
	prompt "kmod-ipv6-sit..................... IPv6-in-IPv4 tunnel (SIT driver)"
	tristate
	select ADK_KPACKAGE_KMOD_INET_TUNNEL
	default n
	help
	  Tunneling means encapsulating data of one protocol type within
	  another protocol and sending it over a channel that understands the
	  encapsulating protocol. This driver implements encapsulation of IPv6
	  into IPv4 packets. This is useful if you want to connect two IPv6
	  networks over an IPv4-only path.

config ADK_KPACKAGE_KMOD_PPP
	prompt "kmod-ppp.......................... PPP support"
	tristate
	select ADK_KERNEL_NETDEVICES
	select ADK_KERNEL_PPP_ASYNC
	select ADK_KERNEL_SLHC
	select ADK_KPACKAGE_KMOD_CRC_CCITT
	default n
	help
	  PPP (Point to Point Protocol) is a newer and better SLIP.  It serves
	  the same purpose: sending Internet traffic over telephone (and other
	  serial) lines.  Ask your access provider if they support it, because
	  otherwise you can't use it; most Internet access providers these
	  days support PPP rather than SLIP.

	  To use PPP, you need an additional program called pppd as described
	  in the PPP-HOWTO, available at
	  <http://www.tldp.org/docs.html#howto>.  Make sure that you have
	  the version of pppd recommended in <file:Documentation/Changes>.
	  The PPP option enlarges your kernel by about 16 KB.

	  There are actually two versions of PPP: the traditional PPP for
	  asynchronous lines, such as regular analog phone lines, and
	  synchronous PPP which can be used over digital ISDN lines for
	  example.  If you want to use PPP over phone lines or other
	  asynchronous serial lines, you need to say Y (or M) here and also to
	  the next option, "PPP support for async serial ports".  For PPP over
	  synchronous lines, you should say Y (or M) here and to "Support
	  synchronous PPP", below.

config ADK_KPACKAGE_KMOD_PPP_MPPE
	prompt   "kmod-ppp-mppe................... PPP MPPE/MPPC module"
	tristate
	default n
	depends on ADK_KPACKAGE_KMOD_PPP
	select ADK_KERNEL_CRYPTO
	select ADK_KPACKAGE_KMOD_CRYPTO_ARC4
	select ADK_KPACKAGE_KMOD_CRYPTO_SHA1
	select ADK_KPACKAGE_KMOD_CRYPTO_ECB if ADK_LINUX_2_6
	help
         Support for the MPPE Encryption protocol, as employed by the
	 Microsoft Point-to-Point Tunneling Protocol.

	 See http://pptpclient.sourceforge.net/ for information on
	 configuring PPTP clients and servers to utilize this method.

config ADK_KPACKAGE_KMOD_PPPOATM
	prompt   "kmod-pppoatm.................... PPPoA (PPP over ATM) kernel support"
	tristate
	default n
	depends on ADK_KPACKAGE_KMOD_PPP
	select ADK_KPACKAGE_KMOD_ATM
	help
	  Support for PPP over ATM

config ADK_KPACKAGE_KMOD_PPPOE
	prompt   "kmod-pppoe...................... PPPoE (PPP over Ethernet) kernel support"
	tristate
	default n
	depends on ADK_KPACKAGE_KMOD_PPP
	help
	  Support for PPP over Ethernet

config ADK_KPACKAGE_KMOD_TUN
	prompt "kmod-tun.......................... Universal TUN/TAP driver"
	tristate
	default n
	help
	  Kernel support for the TUN/TAP tunneling device

config ADK_KPACKAGE_KMOD_BONDING
	prompt "kmod-bonding...................... Bonding driver support"
	tristate
	default n
	help
  	  Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
	  Channels together. This is called 'Etherchannel' by Cisco,
	  'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.

	  The driver supports multiple bonding modes to allow for both high
	  performance and high availability operation.

	  Refer to <file:Documentation/networking/bonding.txt> for more
	  information.

source target/linux/config/Config.in.sched
source target/linux/config/Config.in.ipsec

endmenu