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
|
Please read the manpage for brcfg for details on bridge operating.
This directory includes a patch that you might have to apply to your kernel
to make it work reliably as a bridge. Linux 2.0.22 already contains this
patch.
Linux customarily only autodetects one Ethernet board. To enable the
detection of another add the following configuration option at the lilo
prompt
eth=0,0,eth1
for further information regarding multiple Ethernetboards and Linux
please review the Ethernet HOWTO (probably in /usr/doc/HOWTO if you
installed the HOWTOs).
If you are running the bridging software under Debian:
1. Customize /etc/init.d/bridge if you do not want to do bridging only
between eth0 and eth1
2. Run
/etc/init.d/bridge start
to activate the bridge.
Known Problems:
---------------
1. Reachability of the Bridge PC
--------------------------------
The Bridge does not bridge packets for itself. You might not be able
to reach the bridge itself from one side which is the side for which
you have no routing setup. Curiously to reach the bridge itself the routing
must be functional. This would vanish if we could restrict routing to
certain protocols and thus do IP routing while bridging other protocols.
I have the following setup:
eth0 10.0.0.30 with a route and a default gw
eth1 10.0.0.31
The bridge itself is only reachable from the eth0 side. The IP address
10.0.0.31 never respond since there is no routing set up for it.
2. Multicast problems
---------------------
It seems that the bridge does not support Multicasting in a correct way. We
have had partiall loss of connectivity with AppleTalk on Campus.
3. Bridge not coming up
-----------------------
The bridge will not properly function if the ethernet boards are not in
a sane state. If you have lots of network problem reports during bridge
startup then please fix the problem with the boards (attach a cable for
example, some network cards dont like to be separated from the net)
and restart the machine.
Future Developments
-------------------
bridge-0.2 is under development with additional protocol filtering options
and will be available from ftp.fuller.edu/Linux/debian/bridge.
This version bridge-0.1 is for 2.0.X Kernels and will no longer be maintained.
Christoph Lameter, <clameter@debian.org>
|
