public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
* [B.A.T.M.A.N.] Need help bridging Regular AP to Batman
@ 2016-01-14 16:31 André Pouliot
  2016-01-14 17:05 ` Simon Wunderlich
  0 siblings, 1 reply; 2+ messages in thread
From: André Pouliot @ 2016-01-14 16:31 UTC (permalink / raw)
  To: b.a.t.m.a.n@lists.open-mesh.org

Hi,

I'm trying to do a mesh network using the RaspberryPi and Batman. 

My problem is I'm using 2 wifi card on one raspberrypi one for batman and the other one for connecting to my wireless access point.

I already made my mesh network I can ping on layer 2 or 3 between 2 raspberrypi. When connecting the Ethernet cable(on the raspberry with 2 wifi dongle) I can use the bridge to ping toward the internet. But when I disconnect the cable I can't ping internet anymore.

I already verified my batman interface and my bridge both seem to work

The AP is connected on wlan1, wlan1 doesn't have an IP address assigned to it. The AP is configured with WPA2. When trying to assign a address using dhclient to the bridge interface the system can't seem to find a way and the command is waiting.

If I want to connected my batman network to a standard wifi AP do I need to use a bridge or the functionality exist with batman? 

If it's with the bridge how can it work?

I'm putting the output of a few command at the end of the email. If you want anything else It will be my pleasure to send it.

André Pouliot

-----
root@raspberrypi:/home/pi# ifconfig
bat0      Link encap:Ethernet  HWaddr 72:4c:12:42:f2:d4
          inet6 addr: fe80::704c:12ff:fe42:f2d4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:354 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5857 errors:0 dropped:791 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:19536 (19.0 KiB)  TX bytes:821562 (802.3 KiB)

eth0      Link encap:Ethernet  HWaddr b8:27:eb:06:21:f3
          inet addr:172.17.94.48  Bcast:172.17.95.255  Mask:255.255.240.0
          inet6 addr: fe80::ba27:ebff:fe06:21f3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9628 errors:0 dropped:5 overruns:0 frame:0
          TX packets:3273 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1054143 (1.0 MiB)  TX bytes:380009 (371.1 KiB)

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:65536  Metric:1
          RX packets:216 errors:0 dropped:0 overruns:0 frame:0
          TX packets:216 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:22172 (21.6 KiB)  TX bytes:22172 (21.6 KiB)

mesh-bridge Link encap:Ethernet  HWaddr 00:0f:60:04:03:a6
          inet addr:172.17.94.29  Bcast:172.17.95.255  Mask:255.255.240.0
          inet6 addr: fe80::20f:60ff:fe04:3a6/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9123 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2856 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:963896 (941.3 KiB)  TX bytes:316106 (308.6 KiB)

wlan0     Link encap:Ethernet  HWaddr 40:a5:ef:01:23:c8
          inet6 addr: fe80::42a5:efff:fe01:23c8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1532  Metric:1
          RX packets:22070 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29900 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2408956 (2.2 MiB)  TX bytes:4165384 (3.9 MiB)

wlan1     Link encap:Ethernet  HWaddr 00:0f:60:04:03:a6
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:2195 errors:0 dropped:1 overruns:0 frame:0
          TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:276922 (270.4 KiB)  TX bytes:3110 (3.0 KiB)

root@raspberrypi:/home/pi# brctl show
bridge name     bridge id               STP enabled     interfaces
mesh-bridge             8000.000f600403a6       no              bat0
                                                        eth0
                                                        wlan1


root@raspberrypi:/home/pi# batctl o
[B.A.T.M.A.N. adv 2015.0, MainIF/MAC: wlan0/40:a5:ef:01:23:c8 (bat0 BATMAN_IV)]
  Originator      last-seen (#/255)           Nexthop [outgoingIF]:   Potential nexthops ...
40:a5:ef:01:2f:58    0.010s   (255) 40:a5:ef:01:2f:58 [     wlan0]: 40:a5:ef:01:2f:58 (255)
  

root@raspberrypi:/home/pi# iw dev wlan1 link

Connected to 00:24:01:65:e4:6d (on wlan1)
        SSID: C2T3-Prod
        freq: 2437
        RX: 16265 bytes (149 packets)
        TX: 180 bytes (3 packets)
        signal: -43 dBm
        tx bitrate: 6.5 MBit/s MCS 0

        bss flags:      short-preamble short-slot-time
        dtim period:    1
        beacon int:     100



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [B.A.T.M.A.N.] Need help bridging Regular AP to Batman
  2016-01-14 16:31 [B.A.T.M.A.N.] Need help bridging Regular AP to Batman André Pouliot
@ 2016-01-14 17:05 ` Simon Wunderlich
  0 siblings, 0 replies; 2+ messages in thread
From: Simon Wunderlich @ 2016-01-14 17:05 UTC (permalink / raw)
  To: b.a.t.m.a.n

[-- Attachment #1: Type: text/plain, Size: 1653 bytes --]

Hi Andre,

On Thursday 14 January 2016 16:31:08 André Pouliot wrote:
> Hi,
> 
> I'm trying to do a mesh network using the RaspberryPi and Batman.
> 
> My problem is I'm using 2 wifi card on one raspberrypi one for batman and
> the other one for connecting to my wireless access point.
> 
> I already made my mesh network I can ping on layer 2 or 3 between 2
> raspberrypi. When connecting the Ethernet cable(on the raspberry with 2
> wifi dongle) I can use the bridge to ping toward the internet. But when I
> disconnect the cable I can't ping internet anymore.
> 
> I already verified my batman interface and my bridge both seem to work

You are using your second non-mesh WiFi card (wlan 1) in client mode, right? 
You can't include client mode into a bridge, because a WiFi client (normally) 
does not support bridging. Actually your system should prevent it ...

> 
> The AP is connected on wlan1, wlan1 doesn't have an IP address assigned to
> it. The AP is configured with WPA2. When trying to assign a address using
> dhclient to the bridge interface the system can't seem to find a way and
> the command is waiting.
> 
> If I want to connected my batman network to a standard wifi AP do I need to
> use a bridge or the functionality exist with batman?

If you want to connect your Raspi to your WiFi AP, I see the following 
options:
 * Use Layer 3 Routing and keep the WiFi Client
 * Configure your Raspi as AP and your WiFi AP into client mode (if it supports 
that)
 * Connect one of your Raspis to Ethernet and don't use the WiFi AP at all.

Hope I got your question right .... :)

Cheers,
      Simon

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-01-14 17:05 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-01-14 16:31 [B.A.T.M.A.N.] Need help bridging Regular AP to Batman André Pouliot
2016-01-14 17:05 ` Simon Wunderlich

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox