Hi!
For me it seems that lack of HTTPS support in OpenWrt is really
problematic. So all packages installation from official repositories go
over HTTP, if I am not mistaken. Does anyone know why this is not
something which bothers more people? :-)
Mitar
--
http://mitar.tnode.com/https://twitter.com/mitar_m
Since I've been using the mesh as my primary internet for a while now I've
been running into a few problems where people from the same hosting service
(digitalocean) have caused the IP range that includes our VPuN server to
become blocked.
These include: Wikipedia, Craiglist and Google
We can expect any IP we use to eventually become permabanned from wikipedia
and craigslist, though for wikipedia this only affects editing. Google will
more dynamically ban and unban.
There is one viable solution: Get Internet routable IPv6 addresses for all
mesh clients and try to ensure that clients use IPv6 for problematic
services.
Here's some info on how various operating systems decide whether to use
IPv4 or IPv6:
http://superuser.com/questions/403716/how-do-client-applications-know-to-us…
If we can get everything working correctly on our end then we can spend our
time pestering people who block us to implement IPv6 instead of trying to
get them to unblock an open relay.
I wonder if they allow people to request specific IPv6 ranges when
applying?
CAFE:CODE:FOOD:42:: ?
--
marc/juul
Just wanted to announce that my new home in west oakland, a collective
house with six inhabitants, is now the first house to receive 100% of its
internet connectivity through the People's Open Network!
This was accomplished using the sudo mesh 0.2 firmware which is currently
in alpha testing!
Thanks to everyone who participated, especially Pete Forsyth for being node
0 in this 0.2 mesh and for being so patient during extended debugging
sessions!
--
marc/juul
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 :)
Does anyone know how to find the reason for last reboot on AR71xx and newer?
I'm assuming there is a register somewhere that will tell me if it was
triggered by the hardware watchdog but I'm not finding any info on this
anywhere.
--
marc/juul
We've now had problems with the internet at our first mesh-only-internet
house twice. Both times it seems like it was actually the ISP and the
problem went away on its own.
It would be really cool if we can have the web UI tell the node operator
when a problem is caused by their own ISP or by us and to help them
troubleshoot.
Maybe we can come up with some ideas for a helpful troubleshooting page for
the UI tonight?
I also had the through that it'd be a really great idea if people could go
to their node admin UI URL even when on peoplesopen.net but that it would
then only show information that can be safely made public and tell the user
to log on to their private SSID to make changes and get more information.
Most of the troubleshooting info could actually be available via
peoplesopen.net with no danger. The biggest potential problem is if someone
is accidentally getting connected to a neighbor's node and then get the
admin UI for the wrong router. We can help mitigate that by putting a big
"you are connected to the peoplesopen.net node with private wifi name:
<your name>" at the top of the page.
------ more unnecessary thoughts below.
I wrote an email about this earlier but it was about the more fanciful
scenario where I imagined having a router that talks.
Here are some scenarios that would be pretty cool to handle:
"Uh oh, I had internet within the past 48 hours but the ethernet cable to
your modem or Internet router has been physically disconnected. Is the
cable connected and is your modem or internet router powered on? [get help
troubleshooting]"
"I see that you plugged my WAN port into another device, but it isn't
giving me an IP address. Are you sure you plugged me into your modem /
Internet router?"
"I can connect to the Internet but it looks like none of the People's Open
Network tunnel endpoints are online right now. Somewhere nearby a bunch of
technicians are running around with their hair on fire. Hopefully the issue
will be fixed shortly! You should still be able to use your private wifi
network called <name>. Sorry for the outage :("
"It seems that I am connected to your modem / Internet router but I cannot
connect to the Internet. You should call your Internet Service Provider and
ask them to fix the issue. Please remember that People's Open Network is
not associated with your Internet Service Provider and that some Internet
Service Providers do not allow you to share your connection. To see a list
of Internet Service Providers in the Bay Area that explicitly allow sharing
[click here]. If you don't see your ISP in the list then there is a chance
that you may be breaking your terms of service by sharing Internet so it's
probably best not to mention the People's Open Network or Sudo Mesh when
you call your ISP :)"
"I'm connected to the Internet but I'm getting terrible latency. This means
that there is a very long delay whenever data is sent and received from the
Internet. It looks like the problem is coming from your Internet Service
Provider. ... <insert ISP disclaimer>"
