4 ms·

Those little devices are in high demand. I've been buying them in quantities of 10-at-a-time (Especially when they were cheaper) since they are useful for putt

Those little devices are in high demand. I've been buying them in quantities of 10-at-a-time (Especially when they were cheaper) since they are useful for putting VOIP phones securley behind VPN. I've seen a lot of folks recommend them on HN. They support OpenVPN + Wireguard out of the box and are easy enough for non-techs to reconfigure in the field w/ remote instructions.

nathancahill 6y ago
I deployed a remote/home office printer sharing setup with these little guys for my friend's company. The VPN integration is fantastic, at least for low bandwidth uses like that.
rektide 6y ago
Betcha it wouldn't be too hard to use an rpi to do these tasks. ;) Hence why I love seeing posts like the one's submitted: lessons learned, that we can all possibly use to upgrade ourselves. It would be nice for mainstream linux (not just openwrt) to grow more user-friendly tooling. I look at opnsense in envy, but I'm not really interest in splitting my expertise, taking on learning FreeBSD too. I know I wouldn't really have to touch the OS much, that opnsense is a pretty complete UI package, but I like to keep a fuller-stack view of things, have some up & down mastery.
TechBro8615 6y ago
Make sure you flash them / check their traffic. They make some telemetry requests IIRC.
- 1vuio0pswjnm7 6y ago
  By extracting the firmware^1 one can see that GL.inet provides a cloud storage service. This is opt-in. It is not enabled by default. The cloud storage has a telemetry address listed in /etc/config/glbigdata (and a ping address to Google at 8.8.8.8). Perhaps one could use the service and change "telemetry.goodcloud.xyz" to the loopback or delete it. I have no inclination to test this as I do not use cloud storage. 1. https://s3.us-east-2.amazonaws.com/download.gl-inet.com/firmware/mt300n-v2/v1/openwrt-mt300n-v2-3.201-0402.bin https://s3.us-east-2.amazonaws.com/download.gl-inet.com/firm... With default configs IME one will see some constant traffic to 8.8.8.8. This is from OpenWRT mwan3's default configs. These defaults are left unchanged by GL.inet and probably other routers running OpenWRT. I have never seen anyone complain about this traffic. I doubt this is what is being referred to as "telemetry" in the above comment. Nevertheless, it is constant pinging to Google, OpenDNS or some other third party. In typical Linux fashion, mwan3, a daemon not every user is going to need, is enabled by default anyway. https://github.com/gl-inet/gli-pub/raw/master/mwan3/files/etc/config/mwan3 https://github.com/gl-inet/gli-pub/raw/master/mwan3/files/et...

nathancahill 6y ago

I deployed a remote/home office printer sharing setup with these little guys for my friend's company. The VPN integration is fantastic, at least for low bandwidth uses like that.

rektide 6y ago

Betcha it wouldn't be too hard to use an rpi to do these tasks. ;) Hence why I love seeing posts like the one's submitted: lessons learned, that we can all possibly use to upgrade ourselves. It would be nice for mainstream linux (not just openwrt) to grow more user-friendly tooling. I look at opnsense in envy, but I'm not really interest in splitting my expertise, taking on learning FreeBSD too. I know I wouldn't really have to touch the OS much, that opnsense is a pretty complete UI package, but I like to keep a fuller-stack view of things, have some up & down mastery.

TechBro8615 6y ago

Make sure you flash them / check their traffic. They make some telemetry requests IIRC.

1vuio0pswjnm7 6y ago
By extracting the firmware^1 one can see that GL.inet provides a cloud storage service. This is opt-in. It is not enabled by default. The cloud storage has a telemetry address listed in /etc/config/glbigdata (and a ping address to Google at 8.8.8.8). Perhaps one could use the service and change "telemetry.goodcloud.xyz" to the loopback or delete it. I have no inclination to test this as I do not use cloud storage. 1. https://s3.us-east-2.amazonaws.com/download.gl-inet.com/firmware/mt300n-v2/v1/openwrt-mt300n-v2-3.201-0402.bin https://s3.us-east-2.amazonaws.com/download.gl-inet.com/firm... With default configs IME one will see some constant traffic to 8.8.8.8. This is from OpenWRT mwan3's default configs. These defaults are left unchanged by GL.inet and probably other routers running OpenWRT. I have never seen anyone complain about this traffic. I doubt this is what is being referred to as "telemetry" in the above comment. Nevertheless, it is constant pinging to Google, OpenDNS or some other third party. In typical Linux fashion, mwan3, a daemon not every user is going to need, is enabled by default anyway. https://github.com/gl-inet/gli-pub/raw/master/mwan3/files/etc/config/mwan3 https://github.com/gl-inet/gli-pub/raw/master/mwan3/files/et...