Hi Thomas,

Thanks for your help. I'm now able to set topologies.

Regards,
Siva.

On Mon, Jan 21, 2013 at 11:11 PM, <[email protected]>wrote:

> Send Devel mailing list submissions to
>         [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
> or, via email, send a message with subject or body 'help' to
>         [email protected]
>
> You can reach the person managing the list at
>         [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Devel digest..."
>
>
> Today's Topics:
>
>    1. Re: Kernel Panic (Sivateja Patibandla)
>    2. Mesh topology (Sivateja Patibandla)
>    3. Re: Kernel Panic (Bob Copeland)
>    4. Re: Mesh topology (Thomas Pedersen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 21 Jan 2013 17:47:27 -0500
> From: Sivateja Patibandla <[email protected]>
> To: [email protected]
> Subject: Re: Kernel Panic
> Message-ID:
>         <
> ca+lehhe3eubvgihivfnhu_icluydr4yswgffz-g0z1rgyz-...@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Bob Copeland,
>
> Thank you for your response. I'm working on the open80211s stack on the
> wifi modem with 4 mb flash. So, I could not get to load gdb on it. Could
> you please point me at a right direction of debugging the kernel panic.
>
> Best Regards,
> Siva.
>
> On Thu, Dec 20, 2012 at 7:00 AM, <[email protected]>
> wrote:
>
> > Send Devel mailing list submissions to
> >         [email protected]
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >         http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
> > or, via email, send a message with subject or body 'help' to
> >         [email protected]
> >
> > You can reach the person managing the list at
> >         [email protected]
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Devel digest..."
> >
> >
> > Today's Topics:
> >
> >    1. Re: [PATCH] mac80211: RMC buckets are just list heads
> >       (Johannes Berg)
> >    2. Re: Kernel Panic (Bob Copeland)
> >    3. Mesh Network Configuration (Nelson Terra)
> >    4. Re: Mesh Network Configuration (Thomas Pedersen)
> >    5. Re: Mesh Network Configuration (Yeoh Chun-Yeow)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Wed, 19 Dec 2012 13:09:23 +0100
> > From: Johannes Berg <[email protected]>
> > To: Thomas Pedersen <[email protected]>
> > Cc: [email protected], [email protected]
> > Subject: Re: [PATCH] mac80211: RMC buckets are just list heads
> > Message-ID: <[email protected]>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > On Mon, 2012-12-17 at 18:41 -0800, Thomas Pedersen wrote:
> > > The array of rmc_entrys is redundant since only the
> > > list_head is used. Make this an array of list_heads
> > > instead and save ~6k per vif at runtime :D
> >
> > :)
> > Applied.
> >
> > johannes
> >
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Wed, 19 Dec 2012 11:48:50 -0500
> > From: Bob Copeland <[email protected]>
> > To: [email protected]
> > Subject: Re: Kernel Panic
> > Message-ID: <20121219164850.GB27261@localhost>
> > Content-Type: text/plain; charset=us-ascii
> >
> > On Fri, Dec 14, 2012 at 09:39:49PM -0500, Sivateja Patibandla wrote:
> > > It would be really helpful if you guys can help me debugging it. Please
> > let
> > > me know if you need anymore information.
> > >
> > > [  368.930000]         8092d900 801c4920 80e00a80 8092d900 80e05020
> > > 80e00a80 8092d900 80402694
> > > [  368.930000]         00000000 00000000 802c3d50 80e00a80 80f47830
> > > 802c3d50 00000000 00000001
> > > [  368.930000]         0000002b 0000000c 0000d000 8041e8ec 00000000
> > > 00008800 1000f001 8092d900
> > > [  368.930000]         ...
> > > [  368.930000] Call Trace:
> > > [  368.930000] [<80ed14e4>] ath5k_tx_queue+0x2c4/0xbac [ath5k]
> > > [  368.930000] [<8041e8ec>] ieee80211_rts_get+0x300/0x700 [mac80211]
> >
> > Can you do:
> >
> > $ gdb /path/to/ath5k.ko
> > (gdb) l *(ath5k_tx_queue+0x2c4)
> >
> > and post the output?
> >
> > --
> > Bob Copeland %% www.bobcopeland.com
> >
> >
> > ------------------------------
> >
> > Message: 3
> > Date: Wed, 19 Dec 2012 18:57:18 -0200
> > From: Nelson Terra <[email protected]>
> > To: [email protected]
> > Subject: Mesh Network Configuration
> > Message-ID:
> >         <CAPzcM7siSM=
> > [email protected]>
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> > Hello all,
> >
> > I am trying to configure a open mesh network with iw and using this
> howto:
> >
> > https://github.com/cozybit/open80211s/wiki/HOWTO
> >
> > I am using Debian Wheezy with kernel 3.2.0, and a usb wireless adaptor
> > dlink dwa-125 which in this link
> >
> > http://linuxwireless.org/en/users/Devices/USB
> >
> > says it uses rt2800usb driver, and according to iw list it is capable of
> > mesh point interface mode.
> >
> > I am following all the steps for open mesh setup but when I run the
> command
> >
> > iw dev $MESH_IFACE station dump
> >
> > I get nothing, any output, and nodes can't ping each other.
> >
> > I miss something?
> >
> > Thank you all!
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: <
> >
> http://lists.open80211s.org/pipermail/devel/attachments/20121219/5ef904e2/attachment-0001.html
> > >
> >
> > ------------------------------
> >
> > Message: 4
> > Date: Wed, 19 Dec 2012 15:37:32 -0800
> > From: Thomas Pedersen <[email protected]>
> > To: [email protected]
> > Subject: Re: Mesh Network Configuration
> > Message-ID:
> >         <CAG6hwVMaeVjWgd9G_wv78xf-GOyKZy1qCM=
> > [email protected]>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > On Wed, Dec 19, 2012 at 12:57 PM, Nelson Terra <[email protected]>
> wrote:
> > > Hello all,
> > >
> > > I am trying to configure a open mesh network with iw and using this
> > howto:
> > >
> > > https://github.com/cozybit/open80211s/wiki/HOWTO
> > >
> > > I am using Debian Wheezy with kernel 3.2.0, and a usb wireless adaptor
> > dlink
> > > dwa-125 which in this link
> > >
> > > http://linuxwireless.org/en/users/Devices/USB
> > >
> > > says it uses rt2800usb driver, and according to iw list it is capable
> of
> > > mesh point interface mode.
> > >
> > > I am following all the steps for open mesh setup but when I run the
> > command
> > >
> > > iw dev $MESH_IFACE station dump
> > >
> > > I get nothing, any output, and nodes can't ping each other.
> >
> > Even though the driver may advertise mesh mode support, it sounds like
> > this broke recently. Likely they aren't even beaconing. Maybe the
> > fastest way to narrow this down is check out a copy of the 3.2.0
> > sources and look at 'git log drivers/net/wireless/rt2x00' for any
> > interesting commits.
> >
> > Thomas
> >
> >
> > ------------------------------
> >
> > Message: 5
> > Date: Thu, 20 Dec 2012 08:43:42 +0800
> > From: Yeoh Chun-Yeow <[email protected]>
> > To: [email protected]
> > Subject: Re: Mesh Network Configuration
> > Message-ID:
> >         <
> > caefj987-mfctb+tsakbd0d9qq-sqmbbh05-o2evss-hk+ze...@mail.gmail.com>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > I have used the TL-WN727N USB adapter which uses rt2800usb driver and
> > confirm that mesh is working.
> >
> > Perhaps, you can try the latest compat-wireless.
> >
> > --
> > Chun-Yeow
> >
> > On Thu, Dec 20, 2012 at 7:37 AM, Thomas Pedersen <[email protected]>
> > wrote:
> > > On Wed, Dec 19, 2012 at 12:57 PM, Nelson Terra <[email protected]>
> > wrote:
> > >> Hello all,
> > >>
> > >> I am trying to configure a open mesh network with iw and using this
> > howto:
> > >>
> > >> https://github.com/cozybit/open80211s/wiki/HOWTO
> > >>
> > >> I am using Debian Wheezy with kernel 3.2.0, and a usb wireless adaptor
> > dlink
> > >> dwa-125 which in this link
> > >>
> > >> http://linuxwireless.org/en/users/Devices/USB
> > >>
> > >> says it uses rt2800usb driver, and according to iw list it is capable
> of
> > >> mesh point interface mode.
> > >>
> > >> I am following all the steps for open mesh setup but when I run the
> > command
> > >>
> > >> iw dev $MESH_IFACE station dump
> > >>
> > >> I get nothing, any output, and nodes can't ping each other.
> > >
> > > Even though the driver may advertise mesh mode support, it sounds like
> > > this broke recently. Likely they aren't even beaconing. Maybe the
> > > fastest way to narrow this down is check out a copy of the 3.2.0
> > > sources and look at 'git log drivers/net/wireless/rt2x00' for any
> > > interesting commits.
> > >
> > > Thomas
> > > _______________________________________________
> > > 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
> >
> >
> > End of Devel Digest, Vol 10, Issue 20
> > *************************************
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.open80211s.org/pipermail/devel/attachments/20130121/6e21cfc6/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Mon, 21 Jan 2013 20:04:35 -0500
> From: Sivateja Patibandla <[email protected]>
> To: [email protected]
> Subject: Mesh topology
> Message-ID:
>         <CA+LeHHFAg+=yL-8PrYUqzxEcrFGy5TAhvNkg4qYsNk=
> [email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
>
> Could anyone tell me how to force a mesh topology permanently (at least for
> that boot session). I was forcing with iw wlan0 mpath set ADDR next_hop
> ADDR. The problem with this is that the mesh path table gets overridden by
> the protocol to the best possible paths. Hence loosing my topology
> information. I need to set certain topologies in order to perform
> experiments on throughput and delay. Any help would be greatly appreciated.
>
> Also, Could you also tell me how to read the mesh path table in a C
> program?
>
> Best Regards,
> Siva.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.open80211s.org/pipermail/devel/attachments/20130121/a0bda3b6/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Mon, 21 Jan 2013 21:25:26 -0500
> From: Bob Copeland <[email protected]>
> To: [email protected]
> Subject: Re: Kernel Panic
> Message-ID: <20130122022526.GA999@localhost>
> Content-Type: text/plain; charset=us-ascii
>
> On Mon, Jan 21, 2013 at 05:47:27PM -0500, Sivateja Patibandla wrote:
> > > Can you do:
> > >
> > > $ gdb /path/to/ath5k.ko
> > > (gdb) l *(ath5k_tx_queue+0x2c4)
> > >
> > > and post the output?
>
> > Thank you for your response. I'm working on the open80211s stack on the
> > wifi modem with 4 mb flash. So, I could not get to load gdb on it. Could
> > you please point me at a right direction of debugging the kernel panic.
>
> I'm just using gdb in this case to resolve symbols to the line of code --
> there are other ways.  Cross-gdb is probably a headache, but if you have
> a cross-objdump for your target then that is generally just as good.  I
> have often compared "objdump -S foo.ko" output against the "Code" section
> of the oops to find the oopsing instructions.  "scripts/markup_oops.pl"
> can
> automate this somewhat.
>
> In general, check out Documentation/oops-tracing.txt in the kernel source
> for some hints.
>
> --
> Bob Copeland %% www.bobcopeland.com
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 21 Jan 2013 20:10:54 -0800
> From: Thomas Pedersen <[email protected]>
> To: [email protected]
> Subject: Re: Mesh topology
> Message-ID:
>         <
> cag6hwvp_rrxhsmonagvx4v6y+c5y1-oho-rt-itu3rxq8tz...@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi Siva,
>
> On Mon, Jan 21, 2013 at 5:04 PM, Sivateja Patibandla
> <[email protected]> wrote:
> > Hi,
> >
> > Could anyone tell me how to force a mesh topology permanently (at least
> for
> > that boot session). I was forcing with iw wlan0 mpath set ADDR next_hop
> > ADDR. The problem with this is that the mesh path table gets overridden
> by
> > the protocol to the best possible paths. Hence loosing my topology
> > information. I need to set certain topologies in order to perform
> > experiments on throughput and delay. Any help would be greatly
> appreciated.
>
> Use iw dev <devname> station set <MAC address> plink_action <open|block>
>
> > Also, Could you also tell me how to read the mesh path table in a C
> program?
>
> Check the iw source for mpath dump hooks :)
>
> --
> Thomas
>
>
> ------------------------------
>
> _______________________________________________
> Devel mailing list
> [email protected]
> http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
>
>
> End of Devel Digest, Vol 11, Issue 16
> *************************************
>
_______________________________________________
Devel mailing list
[email protected]
http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel

Reply via email to