I think we'll be able to find these for quite some time (you can still find
wrt54gs on amazon...), but the writing is on the wall. Unfortunately it
doesn't look like there's a ton of agreement on what would be the successor:
https://lists.openwrt.org/pipermail/openwrt-devel/2015-July/033996.html
"The WDR3600/4300/4900 seem to be EOL here too (the Netherlands), which
> is pretty frustrating, as I wanted to use the WDR3600 for some purposes."
It looks like the next iteration might be the tp-link archer c2 which is an
AC device, but is using ath10k drivers for 5ghz and might not yet be
completely supported in openwrt. Not something that I think we really need
to worry much about :)
One of the inquiries that we've received. Getting closer, but probably
still out of our price range unless we can get a significant number of
people connected and contributing....
Just FYI, I asked about a connection to the omni.
---------- Forwarded message ----------
From: Gavin Van Hyning <gavin(a)fastmetrics.com>
Date: Fri, Jul 31, 2015 at 9:46 AM
Subject: internet @ 4799 Shattuck Ave, 94609
To: maxb.personal(a)gmail.com
Hi Max!
Thanks for your contact. I verified that your specific location qualifies
for our metricFIBER Internet solution with free installation! metricFIBER
is our fastest and most reliable method for internet delivery. Here are the
details for service:
*metricFIBER Internet with Free Install, Setup and Equipment* -
https://www.fastmetrics.com/fiber-optic-internet.php
(Includes All taxes, fees and hardware)
*36-month term pricing*
*500x500 Mbps…$2800/month*
*500Mbps burstable to 1Gbps…$4600/month *($3.50/Mb 95th percentile billing)
<https://en.wikipedia.org/wiki/Burstable_billing>
*1:1 1Gbps (1000Mbps)…$5800/month*
*Internet Includes:* Installation & Setup, Equipment with Ethernet Handoff,
Static IPs, Unlimited Usage, SLA guarantee (see attached), and Local Live
Support.
Please let me know if there are any questions. Since your building is in
our fiber network we can activate your connection within 45-60 calendar
days.
Thanks!
-Gavin Van Hyning-
Fastmetrics, Inc.
415-778-5108 Direct
At Omni we're using TP-Link dual-band home routers (N750) and modifying
them for PoE.
These routers have gigabit ethernet.
Unfortunately gigabit ethernet and PoE at the same requires special
ethernet transformers and these routers don't have that type of transformer.
This means that they drop to 100 mbit when we modify them for PoE (but only
on the port we modify).
I was looking into how to get around this problem.
I thought maybe there was a way to do gigabit half-duplex on two or three
pairs, but it seems like that's not possible.
BUT! It looks like TP-Link makes a PoE splitter which can apparently handle
gigabit:
The TL-POE10R
Here it is for $12:
http://www.ebay.com/itm/TP-LINK-TL-POE10R-Gigabit-PoE-Splitter-Adapter-IEEE…
I ordered one so we can try it out. If it works we should just do that to
all of the routers. No reason not to have gigabit if it's only $12 extra
per router. It's still only $77 total for router + PoE splitter.
oh and btw, someone is selling dirt cheap Ubiquiti Unifi UAP devices:
http://www.ebay.com/itm/New-Ubiquiti-UniFi-UAP-802-11n-300-Mbps-Wireless-Ac…
Caution: They are 2.4 GHz only.
I ordered one for the mesh, just so we have it to test our firmware on.
--
marc/juul
Here's my shitty first attempt at diagram to illustrate how it all hangs
together with vlan, bridging and tunnels:
https://i.imgur.com/B0jzM9h.jpg
Hopefully this can inform a better diagram made
The big thing in the middle is a home node. The chunky things sticking out
of it to the left are antennas. The two things on the right are extender
nodes.
The numbers are VLAN IDs. As you can see there is one VLAN for the open
network (VLAN 10), one VLAN for the private network (VLAN 11) and then one
VLAN per extender node for the mesh network (VLANs 1 and 2).
You can see that the private and public network interfaces are connected
together between wifi, ethernet, home and extender nodes by putting the
interfaces on the same VLAN (for ethernet) and then bridging to the wifi
interfaces.
The mesh network interfaces are connected together by enabling babeld on
all of them, or in the case of the connection between home and extender
nodes they are connected by being on the same VLAN.
On this diagram all three networks are available on all radios both on home
and extender nodes. This is not yet fully implemented, but it is a small
enough change that we should be able to finish it this week.
--
marc/juul
The mesh will soon be receiving two flutter boards since we funded their
kickstarter.
These are 900 mhz fairly long range low bandwidth (i think up to 1 mbps?)
boards that can be programmed with a modified Arduino IDE.
These would be pretty good for a low-bandwidth disaster recovery mesh, or
for sensor reporting. I'm sending this mail to start people thinking about
possible uses.
Here's their kickstarter:
https://www.kickstarter.com/projects/flutterwireless/flutter-20-wireless-ar…
Here's my old write-up for the DisasterRadio project for inspiration
(currently in suspended animation):
https://sudoroom.org/wiki/DisasterRadio
--
marc/juul
Not a great deal of progress tonight.
Flashed the newly received nanostation m2 and picostation m2 and
investigated if any special configuration would be needed to support them
as extender nodes. Surprisingly it looks like the answer is no, even though
the nanostation m2 has a built-in switch.
Information about supporting these devices is logged here:
https://github.com/sudomesh/sudowrt-firmware/issues/46
Started a build of latest sudowrt on room.sudoroom.org:
tail -f
/home/juul/sudowrt-firmware/built_firmware/builder.ar71xx/build.log
Since we won't have to do any hook-script re-writing for nanostation I am
hopeful that we can complete the tasks I listed for 0.2 this week:
https://github.com/sudomesh/sudowrt-firmware/milestones/0.2%20-%20initial%2…
--
marc/juul
