Hey Gargi,

i've read your setup as you described it, and as far as i understood
it is supposed to work. I've already built up similar setups
without problems and don't see what your problem is here.

Maybe you can provide some more information, e.g. your startup script,
to get a clue here?

kind regards,
        Simon

On Tue, Apr 07, 2009 at 05:25:08PM -0500, Gargi Purohit wrote:
> Sorry was not clear in the configuration
> 
> = = AP to AP wireless link
> ^ ^ AP to client wireless link
> Server1 and RB1 on wired n/w
> 
>   My configuration is like this:
> 
>  -Server 1 --|
>                 |
>                 |-----(RB1) =   =   (RB2)
>                         ^                 ^
>                         ^                 ^
>                         ^                 ^
>                       C1              C2
> 
> 
> > On Tue, Apr 7, 2009 at 5:18 PM, Gargi Purohit <gaar...@gmail.com> wrote:
> >> Hi
> >>
> >> I have configured a Layer 2 mesh (Using batman kernel module) on
> >> Routerboard 433.  These are boards equipped with 2 interfaces.  I have
> >> configured/created a virtual interface on every physical interface.
> >> So for E.g. my routerboard 1 (RB1) has ath0 (Phy interface - Adhoc
> >> mode), ath1 (Virtual interface - Master mode), ath2 (Phy interface -
> >> Adhoc mode) and ath3 (Virtual interface in Master mode).
> >>
> >> My set up has 2 routerboards - one is wired and the other is wireless.
> >> Thus RB1 has (ath0, ath1, ath2, ath3 and eth0)
> >> RB2 has (ath0, ath1, ath2, ath3)
> >>
> >> The proc is as follows on both RB1 and RB2
> >>
> >> r...@open-mesh:~# cat /proc/net/batman-adv/interfaces
> >> ath0 ath2
> >>
> >> I have created a bridge between all interfaces.
> >> The bridge config on RB1 is:
> >>
> >> r...@open-mesh:~# brctl show
> >> bridge name     bridge id               STP enabled     interfaces
> >> br0             8000.000c422fbfe4       no                  eth0
> >>                                                                         
> >> ath1
> >>                                                                         
> >> ath3
> >>                                                                         
> >> bat0
> >>
> >>
> >> The bridge config on RB2 is:
> >> r...@open-mesh:~# brctl show
> >> bridge name     bridge id               STP enabled     interfaces
> >> br0             8000.00ff8fffdcc7       no                     bat0
> >>                                                                         
> >> ath1
> >>                                                                         
> >> ath3
> >>
> >>
> >> I can connect clients to each of these RB and they can get Internet access.
> >>
> >> My configuration is like this:
> >>
> >> -------------------Server 1 -------------|
> >>                                             |
> >>                                             |-------------Wired AP
> >> (RB1)   =   =   =   =   =   =   = Wireless AP (RB2)
> >>                                             |
> >> ^                                                               ^
> >>                                             |
> >> ^                                                               ^
> >>                                             |
> >> ^                                                               ^
> >>                                             |
> >> C1 (Client of RB1)                                      C2 (Client of
> >> RB2)
> >>
> >>
> >> The APs RB1 and RB2 are connected to each other over 2 mesh wireless
> >> links on different channels (ath0 and ath2)
> >>
> >> I am trying to ssh to Server 1 from all these nodes.  I can ssh to
> >> Server 1 from anyone but RB2 (RB1, C1, C2 can ssh Server 1 but RB2
> >> cannot).
> >>
> >> Likewise I can ssh all nodes from each other.  E.g from anywhere on
> >> LAN I can ssh to each of these nodes.  But RB2 can be sshed only from
> >> nodes directly connected (eg. RB1 and C2).
> >>
> >> Note however i can ping Server 1 from RB2.
> >>
> >> Am not sure where I am going wrong?
> >>
> >> Regards
> >>
> >> Gargi
> >>
> >
> _______________________________________________
> B.A.T.M.A.N mailing list
> b.a.t.m....@open-mesh.net
> https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n
> 

Attachment: signature.asc
Description: Digital signature

Reply via email to