<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: Bridging over serial line
From: "A.J. Werkman" <werkman,AT,digifarma,DOT,nl>
Date: Sun, 11 Nov 2001 23:12:24 +0100

I want to to bridge two ethernet networks over a serial connection in order 
to become one logical ethernet.

I have the following situation (hope this shows):

   Net 1                             Net 2
  ------------                        ---------------
             |                        |
      -------------  PPP   ----------------
      |   hst1  |------------|    hst2    |
      -------------            ----------------

I want Net 1 and Net 2 to be combined into one logical IP-subnet. I come up 
with the serial line because I have to fysically bridge a few kilometers.
Because I do not have complete controle over the hand-out of the 
IP-addresses, routing is not an option.

I have installed cipe 1.5.2 (compiled with protocol=4) and the bridge-utils.

I use the following option-files:
Machine A:
ptpaddr 172.17.21.102
ipaddr          172.17.21.101
mask            255.255.255.192
bcast           172.17.21.127
mtu             1500
hwaddr  00:00:5e:c2:00:ef
me              192.168.84.1:6543
peer            192.168.85.1:6789
key             xxxxxxxxxxxxxxxxxxxxxxxxx

Machine B:
ptpaddr 172.17.21.101
ipaddr          172.17.21.102
mask            255.255.255.192
bcast           172.17.21.127
mtu             1500
hwaddr  00:00:5e:c2:01:ef
peer            192.168.84.1:6543
me              192.168.85.1:6789
key             xxxxxxxxxxxxxxxxxxxxxxxxx

I can ping directly over the PPP connection, so this works.
After starting ciped on both machines I can ping through the cipe device 
from A to B and from B to A.

Then I configure the bridge as follows on both machines:
brctl addbr br0
brctl addif br0 eth0
ifconfig eth0 0.0.0.0
brctl addif br0 cipdb0
ifconfig cipdb0 0.0.0.0
A: ifconfig br0 172.17.21.101 netmask 255.255.255.192 br0
B: ifconfig br0 172.17.21.102 netmask 255.255.255.192 br0

After this I can still ping to the 192.168.x.x interfaces, but the cipe 
devices stop functioning.
In the logfile I get the next error messages:

Nov 11 20:56:03 werk ciped-db[2835]: CIPE daemon vers 1.5.2 (c) Olaf Titz 
1996-2000
Nov 11 20:56:03 werk kernel: cipdb: rtnl_lock() at ../cipe/device.c:625
Nov 11 20:56:03 werk kernel: cipdb: cipe_alloc_dev 0
Nov 11 20:56:03 werk kernel: cipdb: rtnl_unlock() at ../cipe/device.c:627
Nov 11 20:56:03 werk kernel: cipdb: read_lock(&tasklist_lock) at 
../cipe/device.c:216
Nov 11 20:56:03 werk kernel: cipdb: read_unlock(&tasklist_lock) at 
../cipe/device.c:225
Nov 11 20:56:03 werk kernel: cipdb0: cipe_sendmsg
Nov 11 20:56:03 werk kernel: cipdb0: cipe_recvmsg
Nov 11 20:56:03 werk ciped-db[2835]: peer configuration info: proto=4, 
crypto=b, version=1.5, correct key parser
Nov 11 20:56:03 werk kernel: cipdb0: cipe_recvmsg
Nov 11 20:56:09 werk kernel: cipdb0: cipe_sendmsg
Nov 11 20:56:09 werk kernel: cipdb0: cipe_recvmsg
Nov 11 20:56:09 werk kernel: cipdb0: cipe_sendmsg
Nov 11 20:56:09 werk kernel: cipdb0: cipe_recvmsg
Nov 11 20:57:02 werk kernel: cipdb0: cipe_xmit packet length problem 60/782
Nov 11 20:57:04 werk kernel: cipdb0: cipe_xmit packet length problem 60/782
Nov 11 20:57:06 werk kernel: cipdb0: cipe_xmit reentrance
Nov 11 20:57:16 werk kernel: cipdb0: cipe_xmit packet length problem 60/782
Nov 11 20:57:18 werk kernel: cipdb0: cipe_xmit packet length problem 60/782
Nov 11 20:57:20 werk kernel: cipdb0: cipe_xmit reentrance

Here I am kind of stuck. Am I using the wrong options or am I totally 
looking in the wrong direction???

Koos. 





<< | Thread Index | >> ]    [ << | Date Index | >> ]