On Sunday, February 24, 2019 5:51:13 PM CET Sven Eckelmann wrote:
> batman-adv allows to configure three different objects:
>
> * batadv hardif
>
> - network interface used by batadv meshif to transport the batman-adv
> packets
> - its master interface is set to the batadv meshif
>
> * b
Let's meet in Berlin in May :)
-- Forwarded Message --
Subject: [Battlemesh] Mesh is in the air! - 7th-13th of May 2018, Berlin,
Germany
Date: Friday, March 9, 2018, 10:13:56 PM CET
From: Monic Meisel
To: Battle of the Mesh Mailing List
Dear fellow Battlemesh enthusiasts,
T
>
> Thanks.
> Xuebing Wang
>
> On Thu, Apr 6, 2017 at 3:13 PM, Sven Eckelmann wrote:
> > On Donnerstag, 6. April 2017 09:04:50 CEST Simon Wunderlich wrote:
> > > Hello Xuebing,
> > >
> > > it sounds like you have WiFi driver issues. There are some e
Hi,
this event may be interesting for anyone interested in Wireless Mesh networks.
Please join and spread the word!
Thanks,
Simon
-- Forwarded Message --
==
The Wireless Battle Mesh v10
5th - 11th of June 2017, Vien
On Friday, September 23, 2016 10:18:49 PM CEST Pedersen, Thomas wrote:
> On Mon, 2016-09-19 at 08:43 +0200, Simon Wunderlich wrote:
>
> > On Tuesday, September 13, 2016 5:54:38 PM CEST Pedersen, Thomas wrote:
> >
> > > On Tue, 2016-09-13 at 14:30 +0
On Tuesday, September 13, 2016 5:54:38 PM CEST Pedersen, Thomas wrote:
> On Tue, 2016-09-13 at 14:30 +0200, Simon Wunderlich wrote:
>
> > [...]
> >
> > Thanks for the clarification. We will then stick to the 70's branch
> > then.
> >
> > Does any
On Tuesday, September 13, 2016 11:25:21 AM CEST Valo, Kalle wrote:
> Simon Wunderlich writes:
> > On Tuesday, September 13, 2016 10:59:31 AM CEST Valo, Kalle wrote:
> >> Simon Wunderlich writes:
> >> > we have done some experiments last week on ath10k, trying to
On Tuesday, September 13, 2016 10:59:31 AM CEST Valo, Kalle wrote:
> Simon Wunderlich writes:
> > we have done some experiments last week on ath10k, trying to run mesh
> > (802.11s) and access point at the same time, both encrypted.
> >
> > We have tested a recent LEDE
Hi,
we have done some experiments last week on ath10k, trying to run mesh
(802.11s) and access point at the same time, both encrypted.
We have tested a recent LEDE (reboot-1519-g42f559e) but with
firmware-5.bin_10.2.4.70.42-2 and the included wpa_supplicant, which gave us a
working encrypted
On Tuesday 15 March 2016 10:14:03 Saverio Proto wrote:
> > who says that we have to involve them into a decisional process? All they
> > do is offer money for some projects in which industry partners are
> > interested in as well. Of course, bringing the contributions back to
> > upstream should be
Hey Saverio,
On Wednesday 09 March 2016 09:58:57 Saverio Proto wrote:
> > I don't have a number off hand, that's still being decided. My feeling has
> > been that's it'd be in the tens of thousands USD total. I'll try to get
> > more of finalized amount as soon as possible.
>
> Hello Eric,
>
> c
Hi,
this event may be interesting for anyone interested in Wireless Mesh networks.
Please join and spread the word!
Thanks,
Simon
-- Forwarded Message --
Subject: [Battlemesh] Battlemesh v9 announcement
Date: Tuesday 12 January 2016, 22:04:41
From: Simon Wunderlich
To
I'm sure there are some on this list who will be interested in joining! Please
spread the word. :)
-- Forwarded Message --
Subject: [Battlemesh] Announcing Battlemesh V8 Maribor, Slovenia
Date: Monday 23 March 2015, 17:13:18
From: Musti
To: Battle of the Mesh Mailing List
==
Hello list,
the battlemesh v7 call for talks is out, it would be great to see your
WiFi/Mesh related talks and workshops in Leipzig this year. :)
If you haven't booked a hotel yet, have a look at the accomodation package
[1], where you can get bed and breakfast for the whole week (early bird pr
Hello list and happy new year!
Forwarding the announcement of the Wireless Battle Mesh v7 - this is an event
no one interested in mesh networks should miss. :)
Looking forward to see you in Leipzig!
Simon
> Dear Battlemesh enthusiasts,
>
> hope you all had a smooth start into the year 2014
ath9k fellows,
as it seems no one could find the cause for this problem so far. I'd therefore
like to create a workaround by checking one/some registers for 0xdeadbeef and
reset the chip if this is found.
Can anyone recommend a register which should never go 0xdeadbeef in a normal
case?
From wh
Shafi,
On Mon, Sep 03, 2012 at 07:23:26PM +0530, Mohammed Shafi wrote:
> seems we are getting beacon stuck, though its not sufficient for triggering
> chip reset (or) atleast start noise floor calibration. Is this is in a
> congested
> environment ? we can dump cycle counters . I think we need to
Hey guys,
now, finally after approx. 9 days the problem hit us again, this time with
debug enabled.
The symptoms are the same as described before. I'm pasting part of the syslog
of routers
200 and 201 where the calibrating output changes - this is the only thing I
could find
which was really d
Hello Adrian,
thanks for your comments!
On Wed, Aug 22, 2012 at 11:57:04AM -0700, Adrian Chadd wrote:
> Yeah. The deadbeef means "something's turned off."
>
> I'd start with the SoC reset register and see if the MAC/WMAC bits are
> correctly set. Ie, that something hasn't gone and reset the wire
Hello,
just to bump again - isn't there anyone who can give us some hint or
clue regarding these 0xdeadbeef entries in the registers? Couldn't find
a connection to other reports deadbeef on the mailing list so far.
Thanks!
Simon
On Mon, Aug 13, 2012 at 06:53:40PM +0200, Simon
20 matches
Mail list logo
