No subject
Sun Feb 14 16:26:24 CET 2016
the web UI's firmware upgrade page for WR-1043ND v3 appeared in revision
151021. Renaming the image file has no effect. But that lock doesn't
appear to affect its TFTP recovery mode (yet).
On Wed, Mar 16, 2016 at 7:29 AM, Musti <musti at wlan-si.net> wrote:
> Hi,
>
> I have just tried: wr-1043nd v3 (default firmware 3.16.9 Build 150514
> Rel.72381n)
>
> There is no lock, only renaming to wr1043v3_tp_recovery.bin is required
> to upgrade to openwrt.
>
> Kind regards,
> Musti
>
> On 16.3.2016 3:52, Ben West wrote:
> > Actually, w/r/t to previous requests to start collecting reports of the
> > locked encountered on devices, I fould this OpenWRT forum thread asking
> > for precisely that. So I appended to that thread, too.
> > https://forum.openwrt.org/viewtopic.php?pid=315048
> >
> > Also added a note the OpenWRT wiki for this device:
> > https://wiki.openwrt.org/toh/tp-link/tl-wr1043nd#installation
> >
> >
> > On Tue, Mar 15, 2016 at 8:07 PM, Ben West <ben at gowasabi.net
> > <mailto:ben at gowasabi.net>> wrote:
> >
> > I can imagine the firmware locks are not implemented uniformly
> > across all devices. The WR1043ND doesn't have a 5.8GHz radio, so it
> > shouldn't even be relevant to the new FCC rules.
> >
> > If you (and others on this list) find a way to flash a locked
> > WDR3600, would you mind posting to this list under a unique subject,
> > e.g. "TP-Link TL-WDR3600 v1.5 flashed to patched OpenWRT trunk via
> > TFTP", along with the exact hardware and firmware revisions? Having
> > such details under unique subject headings improves search
> > accessibility.
> >
> > Likewise for replying to this thread if a TL-WR1043ND v3 appears
> > with stronger firmware locks.
> >
> >
> > On Tue, Mar 15, 2016 at 8:01 PM, Adam Longwill
> > <adam.longwill at gmail.com <mailto:adam.longwill at gmail.com>> wrote:
> >
> > Aw dang. Mine worked. Must have been old. Nevermind.
> >
> > On Mar 15, 2016 8:40 PM, "Adam Longwill"
> > <adam.longwill at metamesh.org <mailto:adam.longwill at metamesh.org>>
> > wrote:
> >
> > You must have an older version of this hardware or
> > something. I have personal experience with the 3600 the
> > image is requested from that address, a response is sent
> > from .66 but the the request packet comes across the wire
> > again and again.
> >
> > I actually have a brand new in box 3600,in my car. Perhaps I
> > could test this tonight.
> >
> > On Mar 15, 2016 8:29 PM, "Ben West" <ben at gowasabi.net
> > <mailto:ben at gowasabi.net>> wrote:
> >
> > Following up from a couple requests made here on the
> > list about a suitable venue/wiki to start recording
> > verified techniques for flashing devices with
> > countermeasures.
> >
> > TP-Link TL-WR1043ND v3.0 (purchased from Newegg this
> month)
> > Stock firmware: 3.16.9 Build 151021 Rel.74655n
> >
> > The web UI refused OpenWRT factory image on "version of
> > the upgraded file was incorrect."
> >
> > However, a TFTP server at 192.168.0.66, with the OpenWRT
> > trunk factory image for this device under the name
> > "wr1043v3_tp_recovery.bin" in TFTP server root, did
> > work. Specifically, I held down the reset button,
> > powered on, and then released the reset button after
> ~20sec.
> >
> > No modification to the OpenWRT trunk factory image was
> done.
> >
> > Again, good venue for recording these details
> > (candidates listed below)? These details are scattered
> > everywhere on the Internets, but having attention
> > focused here could help consolidate things.
> >
> > https://wiki.openwrt.org/ <https://wiki.openwrt.org/>
> > http://battlemesh.org/
> > https://wirelesspt.net/wiki/P%C3%A1gina_principal
> > <https://wirelesspt.net/wiki/P%C3%A1gina_principal>
> > https://libreplanet.org/wiki/Main_Page
> > <https://libreplanet.org/wiki/Main_Page>
> >
> > Hope this helps.
> >
> > --
> > Ben West
> > http://gowasabi.net
> > ben at gowasabi.net <mailto:ben at gowasabi.net>
> > 314-246-9434 <tel:314-246-9434>
> >
> > _______________________________________________
> > Battlemesh mailing list
> > Battlemesh at ml.ninux.org <mailto:Battlemesh at ml.ninux.org>
> > http://ml.ninux.org/mailman/listinfo/battlemesh
> >
> >
> > _______________________________________________
> > Battlemesh mailing list
> > Battlemesh at ml.ninux.org <mailto:Battlemesh at ml.ninux.org>
> > http://ml.ninux.org/mailman/listinfo/battlemesh
> >
> >
> >
> >
> > --
> > Ben West
> > http://gowasabi.net
> > ben at gowasabi.net <mailto:ben at gowasabi.net>
> > 314-246-9434 <tel:314-246-9434>
> >
> >
> >
> >
> > --
> > Ben West
> > http://gowasabi.net
> > ben at gowasabi.net <mailto:ben at gowasabi.net>
> > 314-246-9434
> >
> >
> > _______________________________________________
> > Battlemesh mailing list
> > Battlemesh at ml.ninux.org
> > http://ml.ninux.org/mailman/listinfo/battlemesh
> >
> _______________________________________________
> Battlemesh mailing list
> Battlemesh at ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/battlemesh
>
--
Ben West
http://gowasabi.net
ben at gowasabi.net
314-246-9434
--001a114e3f988e0449052e29ddb3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><a href=3D"https://forum.openwrt.org/viewtopic.php?pid=3D3=
11456#p311456" target=3D"_blank">From what I'd read</a>, the lock on th=
e web UI's firmware upgrade page for WR-1043ND v3 appeared in revision =
151021.=C2=A0 Renaming the image file has no effect.=C2=A0 But that lock do=
esn't appear to affect its TFTP recovery mode (yet).<br><div class=3D"g=
mail_extra"><br><div class=3D"gmail_quote">On Wed, Mar 16, 2016 at 7:29 AM,=
Musti <span dir=3D"ltr"><<a href=3D"mailto:musti at wlan-si.net" target=3D=
"_blank">musti at wlan-si.net</a>></span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">Hi,<br>
<br>
I have just tried: wr-1043nd v3 (default firmware 3.16.9 Build 150514<br>
Rel.72381n)<br>
<br>
There is no lock, only renaming to wr1043v3_tp_recovery.bin is required<br>
to upgrade to openwrt.<br>
<br>
Kind regards,<br>
Musti<br>
<span><br>
On 16.3.2016 3:52, Ben West wrote:<br>
> Actually, w/r/t to previous requests to start collecting reports of th=
e<br>
> locked encountered on devices, I fould this OpenWRT forum thread askin=
g<br>
> for precisely that.=C2=A0 So I appended to that thread, too.<br>
> <a href=3D"https://forum.openwrt.org/viewtopic.php?pid=3D315048" rel=
=3D"noreferrer" target=3D"_blank">https://forum.openwrt.org/viewtopic.php?p=
id=3D315048</a><br>
><br>
> Also added a note the OpenWRT wiki for this device:<br>
> <a href=3D"https://wiki.openwrt.org/toh/tp-link/tl-wr1043nd#installati=
on" rel=3D"noreferrer" target=3D"_blank">https://wiki.openwrt.org/toh/tp-li=
nk/tl-wr1043nd#installation</a><br>
><br>
><br>
> On Tue, Mar 15, 2016 at 8:07 PM, Ben West <<a href=3D"mailto:ben at go=
wasabi.net" target=3D"_blank">ben at gowasabi.net</a><br>
</span><span>> <mailto:<a href=3D"mailto:ben at gowasabi.net" target=3D"=
_blank">ben at gowasabi.net</a>>> wrote:<br>
><br>
>=C2=A0 =C2=A0 =C2=A0I can imagine the firmware locks are not implemente=
d uniformly<br>
>=C2=A0 =C2=A0 =C2=A0across all devices.=C2=A0 The WR1043ND doesn't =
have a 5.8GHz radio, so it<br>
>=C2=A0 =C2=A0 =C2=A0shouldn't even be relevant to the new FCC rules=
.<br>
><br>
>=C2=A0 =C2=A0 =C2=A0If you (and others on this list) find a way to flas=
h a locked<br>
>=C2=A0 =C2=A0 =C2=A0WDR3600, would you mind posting to this list under =
a unique subject,<br>
>=C2=A0 =C2=A0 =C2=A0e.g. "TP-Link TL-WDR3600 v1.5 flashed to patch=
ed OpenWRT trunk via<br>
>=C2=A0 =C2=A0 =C2=A0TFTP", along with the exact hardware and firmw=
are revisions?=C2=A0 Having<br>
>=C2=A0 =C2=A0 =C2=A0such details under unique subject headings improves=
search<br>
>=C2=A0 =C2=A0 =C2=A0accessibility.<br>
><br>
>=C2=A0 =C2=A0 =C2=A0Likewise for replying to this thread if a TL-WR1043=
ND v3 appears<br>
>=C2=A0 =C2=A0 =C2=A0with stronger firmware locks.<br>
><br>
><br>
>=C2=A0 =C2=A0 =C2=A0On Tue, Mar 15, 2016 at 8:01 PM, Adam Longwill<br>
</span><span>>=C2=A0 =C2=A0 =C2=A0<<a href=3D"mailto:adam.longwill at gm=
ail.com" target=3D"_blank">adam.longwill at gmail.com</a> <mailto:<a href=
=3D"mailto:adam.longwill at gmail.com" target=3D"_blank">adam.longwill at gmail.c=
om</a>>> wrote:<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Aw dang. Mine worked. Must have been =
old. Nevermind.<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0On Mar 15, 2016 8:40 PM, "Adam L=
ongwill"<br>
</span>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<<a href=3D"mailto:adam.lon=
gwill at metamesh.org" target=3D"_blank">adam.longwill at metamesh.org</a> <ma=
ilto:<a href=3D"mailto:adam.longwill at metamesh.org" target=3D"_blank">adam.l=
ongwill at metamesh.org</a>>><br>
<span>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0wrote:<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0You must have an older =
version of this hardware or<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0something. I have perso=
nal experience with the 3600 the<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0image is requested from=
that address, a response is sent<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0from .66 but the the re=
quest packet comes across the wire<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0again and again.<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0I actually have a brand=
new in box 3600,in my car. Perhaps I<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0could test this tonight=
.<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0On Mar 15, 2016 8:29 PM=
, "Ben West" <<a href=3D"mailto:ben at gowasabi.net" target=3D"_b=
lank">ben at gowasabi.net</a><br>
</span><span>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<mailto=
:<a href=3D"mailto:ben at gowasabi.net" target=3D"_blank">ben at gowasabi.net</a>=
>> wrote:<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Following=
up from a couple requests made here on the<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0list abou=
t a suitable venue/wiki to start recording<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0verified =
techniques for flashing devices with<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0counterme=
asures.<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0TP-Link T=
L-WR1043ND v3.0 (purchased from Newegg this month)<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Stock fir=
mware: 3.16.9 Build 151021 Rel.74655n<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The web U=
I refused OpenWRT factory image on "version of<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0the upgra=
ded file was incorrect."<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0However, =
a TFTP server at 192.168.0.66, with the OpenWRT<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0trunk fac=
tory image for this device under the name<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0"wr1=
043v3_tp_recovery.bin" in TFTP server root, did<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0work.=C2=
=A0 Specifically, I held down the reset button,<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0powered o=
n, and then released the reset button after ~20sec.<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0No modifi=
cation to the OpenWRT trunk factory image was done.<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Again, go=
od venue for recording these details<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(candidat=
es listed below)? These details are scattered<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0everywher=
e on the Internets, but having attention<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0focused h=
ere could help consolidate things.<br>
><br>
</span>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a=
href=3D"https://wiki.openwrt.org/" rel=3D"noreferrer" target=3D"_blank">ht=
tps://wiki.openwrt.org/</a> <<a href=3D"https://wiki.openwrt.org/" rel=
=3D"noreferrer" target=3D"_blank">https://wiki.openwrt.org/</a>><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=
=3D"http://battlemesh.org/" rel=3D"noreferrer" target=3D"_blank">http://bat=
tlemesh.org/</a><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=
=3D"https://wirelesspt.net/wiki/P%C3%A1gina_principal" rel=3D"noreferrer" t=
arget=3D"_blank">https://wirelesspt.net/wiki/P%C3%A1gina_principal</a><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<<a hr=
ef=3D"https://wirelesspt.net/wiki/P%C3%A1gina_principal" rel=3D"noreferrer"=
target=3D"_blank">https://wirelesspt.net/wiki/P%C3%A1gina_principal</a>>=
;<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=
=3D"https://libreplanet.org/wiki/Main_Page" rel=3D"noreferrer" target=3D"_b=
lank">https://libreplanet.org/wiki/Main_Page</a><br>
<span>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<=
;<a href=3D"https://libreplanet.org/wiki/Main_Page" rel=3D"noreferrer" targ=
et=3D"_blank">https://libreplanet.org/wiki/Main_Page</a>><br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Hope this=
helps.<br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0--<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Ben West<=
br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=
=3D"http://gowasabi.net" rel=3D"noreferrer" target=3D"_blank">http://gowasa=
bi.net</a><br>
</span>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a=
href=3D"mailto:ben at gowasabi.net" target=3D"_blank">ben at gowasabi.net</a> &l=
t;mailto:<a href=3D"mailto:ben at gowasabi.net" target=3D"_blank">ben at gowasabi=
.net</a>><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=
=3D"tel:314-246-9434" value=3D"+13142469434" target=3D"_blank">314-246-9434=
</a> <tel:<a href=3D"tel:314-246-9434" value=3D"+13142469434" target=3D"=
_blank">314-246-9434</a>><br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0_________=
______________________________________<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Battlemes=
h mailing list<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=
=3D"mailto:Battlemesh at ml.ninux.org" target=3D"_blank">Battlemesh at ml.ninux.o=
rg</a> <mailto:<a href=3D"mailto:Battlemesh at ml.ninux.org" target=3D"_bla=
nk">Battlemesh at ml.ninux.org</a>><br>
<span>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a =
href=3D"http://ml.ninux.org/mailman/listinfo/battlemesh" rel=3D"noreferrer"=
target=3D"_blank">http://ml.ninux.org/mailman/listinfo/battlemesh</a><br>
><br>
><br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0_____________________________________=
__________<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Battlemesh mailing list<br>
</span>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:Battlemesh at m=
l.ninux.org" target=3D"_blank">Battlemesh at ml.ninux.org</a> <mailto:<a hr=
ef=3D"mailto:Battlemesh at ml.ninux.org" target=3D"_blank">Battlemesh at ml.ninux=
.org</a>><br>
<span>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://ml.ninux.org/=
mailman/listinfo/battlemesh" rel=3D"noreferrer" target=3D"_blank">http://ml=
.ninux.org/mailman/listinfo/battlemesh</a><br>
><br>
><br>
><br>
><br>
>=C2=A0 =C2=A0 =C2=A0--<br>
>=C2=A0 =C2=A0 =C2=A0Ben West<br>
>=C2=A0 =C2=A0 =C2=A0<a href=3D"http://gowasabi.net" rel=3D"noreferrer" =
target=3D"_blank">http://gowasabi.net</a><br>
</span>>=C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:ben at gowasabi.net" target=
=3D"_blank">ben at gowasabi.net</a> <mailto:<a href=3D"mailto:ben at gowasabi.=
net" target=3D"_blank">ben at gowasabi.net</a>><br>
>=C2=A0 =C2=A0 =C2=A0<a href=3D"tel:314-246-9434" value=3D"+13142469434"=
target=3D"_blank">314-246-9434</a> <tel:<a href=3D"tel:314-246-9434" va=
lue=3D"+13142469434" target=3D"_blank">314-246-9434</a>><br>
<span>><br>
><br>
><br>
><br>
> --<br>
> Ben West<br>
> <a href=3D"http://gowasabi.net" rel=3D"noreferrer" target=3D"_blank">h=
ttp://gowasabi.net</a><br>
</span>> <a href=3D"mailto:ben at gowasabi.net" target=3D"_blank">ben at gowas=
abi.net</a> <mailto:<a href=3D"mailto:ben at gowasabi.net" target=3D"_blank=
">ben at gowasabi.net</a>><br>
<div><div>> <a href=3D"tel:314-246-9434" value=3D"+13142469434" target=
=3D"_blank">314-246-9434</a><br>
><br>
><br>
> _______________________________________________<br>
> Battlemesh mailing list<br>
> <a href=3D"mailto:Battlemesh at ml.ninux.org" target=3D"_blank">Battlemes=
h at ml.ninux.org</a><br>
> <a href=3D"http://ml.ninux.org/mailman/listinfo/battlemesh" rel=3D"nor=
eferrer" target=3D"_blank">http://ml.ninux.org/mailman/listinfo/battlemesh<=
/a><br>
><br>
_______________________________________________<br>
Battlemesh mailing list<br>
<a href=3D"mailto:Battlemesh at ml.ninux.org" target=3D"_blank">Battlemesh at ml.=
ninux.org</a><br>
<a href=3D"http://ml.ninux.org/mailman/listinfo/battlemesh" rel=3D"noreferr=
er" target=3D"_blank">http://ml.ninux.org/mailman/listinfo/battlemesh</a><b=
r>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br><div>Ben We=
st<div><a href=3D"http://gowasabi.net" target=3D"_blank">http://gowasabi.ne=
t</a><br><a href=3D"mailto:ben at gowasabi.net" target=3D"_blank">ben at gowasabi=
.net</a><br><a href=3D"tel:314-246-9434" value=3D"+13142469434" target=3D"_=
blank">314-246-9434</a><br></div></div>
</div></div>
--001a114e3f988e0449052e29ddb3--
More information about the Battlemesh
mailing list