Re: [Discuss] Wireguard and Traveling and Network Overlaps oh my!

2024-11-02 Thread Rich Pieri
On Sat, 2 Nov 2024 15:44:07 -0700 Kent Borg wrote: > Except last I looked a lot of hardware doesn't run a current version > of OpenWRT. Did you look at the OpenWRT web site/table of hardware? -- \m/ (--) \m/ ___ Discuss mailing list Discuss@lists.blu

Re: [Discuss] Wireguard and Traveling and Network Overlaps oh my!

2024-11-02 Thread Kent Borg
On 11/2/24 1:14 PM, Rich Pieri wrote: GL ship a fork of OpenWRT, but the fork is their own UI on top of vanilla. Full LuCI is available underneath, and you can flash vanilla OpenWRT on almost everything. Except last I looked a lot of hardware doesn't run a current version of OpenWRT. My hope

Re: [Discuss] Wireguard and Traveling and Network Overlaps oh my!

2024-11-02 Thread Rich Pieri
On Sat, 2 Nov 2024 10:53:25 -0700 Kent Borg wrote: > But the GL people seem to ship OpenWRT on all their hardware. That > suggests that there will be longer support for this hardware. GL ship a fork of OpenWRT, but the fork is their own UI on top of vanilla. Full LuCI is available underneath, a

Re: [Discuss] Wireguard and Traveling and Network Overlaps oh my!

2024-11-02 Thread Kent Borg
On 11/2/24 9:31 AM, Rich Pieri wrote: I bought a GL.iNet travel router. Pocket-sized device, USB-C power (15W), runs OpenWRT, bridges to existing WiFi networks (repeater mode). The "runs OpenWRT" part caught my eye! I like OpenWrt but am annoyed that with the zillions of routers out there, I

Re: [Discuss] Wireguard and Traveling and Network Overlaps oh my!

2024-11-02 Thread Rich Pieri
Why hack a solution when I can throw some money at it? I've long held the belief that a portable/personal firewall device would solve many problems. I just never dug into it. Until now: I bought a GL.iNet travel router. Pocket-sized device, USB-C power (15W), runs OpenWRT, bridges to existing WiFi

Re: [Discuss] apache

2024-11-02 Thread Rich Pieri
On Tue, 29 Oct 2024 19:31:13 -0400 dan moylan wrote: > sorry, i forgot to mention at the outset i disabled selinux. Double-check that to be sure nothing has quietly re-enabled SELinux. Otherwise, the directory being written needs to be writable by the UID or GID doing the writing, and all paren