Hi,

I am trying to use the bridge to connect Bluetooth devices with my LAN
and the internet. I have used the instructions/hints in the PAN HOWTO
(http://bluez.sourceforge.net/contrib/HOWTO-PAN) and have successfully
configured most parts. My network looks like this:

                     Linux PC (SuSE 8)
                      [   BRIDGE   ]         Linux box with
LAN/internet <------> [eth0] [bnep0] <-----> Bluetooth (BlueZ)
     (A)                   (B)                      (C)

In more detail, the Linux PC (B) in the middle acts as the bridge. It is
connected to the LAN (A) via the eth0 interface, and when a connection
is made between it and the Bluetooth box (C), the interface bnep0 is
created.

The problem I am having is that the Bluetooth box (C) cannot access the
LAN/web (A) and vice-versa. The bridge PC (B) can ping both the LAN/web
and the Bluetooth box. The Bluetooth box and machines on the LAN can
ping the bridge (B).

The bridge is set up on (B) using the commands:

brctl addbr bridge
brctl addif bridge eth0
brctl setfd bridge 0
brctl stp bridge off
ifup bridge
ifconfig eth0 0.0.0.0
route add default gw 10.0.0.1 dev bridge

(10.0.0.1 is the gateway on the LAN; when the bridge comes up, it gets
it's IP address from the LAN using DHCP - usually 10.0.1.54)

When the Bluetooth device (C) connects (and the interface bnep0
created), it is added to the bridge using the commands:

brctl addif bridge bnep0
ifconfig bnep0 0.0.0.0 up
route add -net 192.168.10.0 netmask 255.255.255.0 dev bridge

(The Bluetooth device(s) (C) have IP addresses in the range
192.168.10.x).

After the bridge has been set up (and a Bluetooth device has connected),
ifconfig on (B) gives:

bnep0     Link encap:Ethernet  HWaddr 00:04:76:E1:E9:7C  
          inet6 addr: fe80::204:76ff:fee1:e97c/10 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:676 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26072 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:182391 (178.1 Kb)  TX bytes:3306344 (3.1 Mb)

bridge    Link encap:Ethernet  HWaddr 00:04:75:7E:12:6D  
          inet addr:10.0.1.54  Bcast:10.0.63.255  Mask:255.255.192.0
          inet6 addr: fe80::204:75ff:fe7e:126d/10 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:37676 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5321 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:6402397 (6.1 Mb)  TX bytes:896780 (875.7 Kb)

eth0      Link encap:Ethernet  HWaddr 00:04:75:7E:12:6D  
          inet6 addr: fe80::204:75ff:fe7e:126d/10 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2301605 errors:0 dropped:0 overruns:0 frame:0
          TX packets:420140 errors:0 dropped:0 overruns:0 carrier:0
          collisions:488 txqueuelen:100 
          RX bytes:604505667 (576.5 Mb)  TX bytes:58335949 (55.6 Mb)
          Interrupt:11 Base address:0x3000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:521 errors:0 dropped:0 overruns:0 frame:0
          TX packets:521 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:44942 (43.8 Kb)  TX bytes:44942 (43.8 Kb)

At this point, (B) and the LAN/web (A) work fine together and (B) can
ping (C). However, (C) cannot ping (B) until bnep0 is given an IP
address using 'ifconfig bnep0 192.168.10.1'.

The routing table at (B), as given by 'route' is:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.10.0    *               255.255.255.0   U     0      0        0
bridge
10.0.0.0        *               255.255.192.0   U     0      0        0
bridge
default         10.0.0.1        0.0.0.0         UG    0      0        0
bridge

The routing table at (C) is set to use its Bluetooth interface for all
destinations.

For other machines on the LAN, I have added an entry to their routing
tables so that they use (B) as a gateway for accessing the Bluetooth
devices (C). However, they can't ping (C).

--
In summary, the problem I am having is that the machines on the LAN can
access other machines on the LAN, including the one acting as a bridge.
The Bluetooth devices can also access the bridge, but no traffic seems
to be able to flow over the bridge, i.e. the Bluetooth devices can't
access the LAN/web and machines on the LAN can't access the Bluetooth
devices.

If you have read this far - thank you and well done! If you have any
possiblie ideas/solutions to this PLEASE could you reply to this email.

Many thanks in advance for any help/suggestions.

Regards,
Edward


_______________________________________________
Bridge mailing list
[EMAIL PROTECTED]
http://www.math.leidenuniv.nl/mailman/listinfo/bridge

Reply via email to