Try this:
1. add mesh interfaces without setting meshid
2. don't mess with the mac addresses
3. link up
4. mesh join
--
thomas
On Tue, Sep 16, 2014, at 11:26 AM, Ashish Gupta via Devel wrote:
> Thanks for the prompt responses Bob Copeland and Yeoh Chun Yeow.
>
> I took your advice and set up a monitor interface.which in fact senses
> all the beacon frames that one station is transmitting. I was able to
> verify the beacon frames on Station 2 as well as Station3. The problem
> is, I cannot "connect" to the station 1 when its running the mesh.
>
> This is what I try to do :
>
> On station 1 :
> set up an interface mp0 over wlan0
> Set meshid on mp0 to "meshnet"
> Assign unique mac address to mp0
> Assign IP address to mp0
> ifconfig up the interface mp0
>
> On station 2:
> set up an interface mp1 over wlan0
> Do not set meshid to anything
> Assign unique mac
> Assign IP address to mp1
> ifconfig up the interface mp1
> Try to join mesh with mesh join command ("meshnet")
>
> On station 3 :
> Set up as a monitor. Capturing packets/frames using wireshark.
>
> Once I do this, I can observe that the station 1 keeps broadcasting
> beacon frames (can see this on station 3). Station 2 does not
> broadcast any frames till the time the join command is executed.
>
> After executing mesh join on station 2 , something seems to happen
> although there's no sign of a connection being established. Station 2
> now starts broadcasting beacon frames broadcasting "meshnet". But
> there is no connection between Station 1 and Station 2. Station 2
> seems to connect to itself somehow and assume that its the only mesh
> node in it's mesh and therefore starts broadcasting itself. Station 1
> is still broadcasting it's beacon frames like it was.
>
> What should I be expecting to see when Station 2 connects to Station 1
> ? And do I need to "mesh join" on both machines even when one of them
> has an already set mesh id ? When they are connected, I should be able
> to ping one host from another. I can't. I'd appreciate it if you could
> point me into the right direction.
>
> Thanks!
>
> Regards,
> Ashish Gupta
>
>
> On Mon, Sep 15, 2014 at 10:19 PM, Yeoh Chun-Yeow <[email protected]>
> wrote:
> > Suggest to bring up a monitor interface and try to capture on the same
> > channel. Check whether the beacon frame is available and etc.
> >
> > ----
> > Chun-Yeow
> >
> >
> > On Mon, Sep 15, 2014 at 11:46 PM, Bob Copeland via Devel
> > <[email protected]> wrote:
> >> On Mon, Sep 15, 2014 at 08:39:52PM +0530, Ashish Gupta via Devel wrote:
> >>> root@xyz:/home/yz# iw --debug dev wlan0 interface add mp1 type mp
> >>> root@xyz:/home/yz# iw --debug dev mp1 set channel 2
> >>> root@xyz:/home/yz# ifconfig mp1 hw ether 94:a0:c0:b1:11:45
> >>> root@xyz:/home/yz# ifconfig mp1 192.168.3.84
> >>>
> >>> root@xyz:/home/yz# iw --debug dev mp1 mesh join abcdefgh
> >>
> >> ^^^ should be mp0 (or is that a copy paste error)??
> >>
> >>> root@xyz:/home/yz# iw dev mp0 station dump
> >>>
> >>> root@xyz:/home/yz# iw --debug dev mp1 mesh join abcdefgh
> >>> command failed: Operation already in progress (-114)
> >>
> >> ^^^ because you already joined on mp1 (instead of mp0)?
> >>
> >>> Interface mp0 and mp1 on the SAME machine.
> >>> Interface mp0 and mp1 on Different machines.
> >>
> >> Generally you will want them on different machines, because by
> >> default frames won't get routed over the air if both interfaces
> >> are local (though you can play games to make this happen anyway).
> >>
> >> --
> >> Bob Copeland %% www.bobcopeland.com
> >> _______________________________________________
> >> Devel mailing list
> >> [email protected]
> >> http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
> _______________________________________________
> Devel mailing list
> [email protected]
> http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
