1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
|
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_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
|
