ptz

joined 2 years ago
[–] ptz@dubvee.org 1 points 13 hours ago* (last edited 13 hours ago)

I've always thought the firewall color codes were arbitrary, though I might just have not paid attention all these years lol.

Just to clarify: I meant connect your OpenWRT device to your hotspot instead of the AP you've been working with. Just to rule out multiple MACs being blocked on the AP.

Beyond that, I'm not really able to help troubleshoot further, but worst case and if all you need is internet, you can set your OpenWRT device up so that it just NATs your downstream connections. Double-NAT, in most cases, is fine.

 

“America has spoken. Pile my food in a fucking bowl like I’m a dog. I don't give a shit anymore”

[–] ptz@dubvee.org 2 points 1 day ago* (last edited 1 day ago) (2 children)

Hmm. Is the upstream AP some kind of fancy deal or a run of the mill consumer router?

I've seen some Cisco APs configured to not allow multiple MAC addresses from the same station. Caused problems when trying to do VMs on my laptop that had the network in bridge mode.

Are you able to put your phone into hotspot, connect to that instead of the upstream AP, and see if it works?

[–] ptz@dubvee.org 5 points 1 day ago* (last edited 1 day ago) (4 children)

I did that with a GL.iNet travel router after flashing stock OpenWRT, and used it as a wireless bridge for several years. It uses relayd to bridge the Wifi station interface and Ethernet. Once you have an ethernet bridge, you can connect another AP or do whatever from there.

If you create a second wifi interface in AP mode (in addition to the station/client one connected to the upstream), you should be able to add that to the LAN bridge alongside the ethernet interfaces. That bridge will then be part of the relayd bridge, and it all should just work (should, lol. I haven't tested that config since I only needed to turn wifi into wired ethernet with this setup).

Interfaces:

LAN Bridge: Ethernet interfaces to be bridged to the wifi

I have both of its interfaces in this bridge, and it also has a static management IP (outside of the WLAN subnet). This management IP is a static out-of-band IP since the devices connected over ethernet won't be able to access it's WLAN IP (in the main LAN) to manage it. To access this IP, I just statically set an additional IP on one of the downstream ethernet client devices.

The LAN bridge is in a firewall zone called LAN.

WWAN: Wireless station interface that's configured as a client to the AP providing upstream access. I have this configured statically, but DHCP is fine too. Firewall zone is WLAN.

WLANBRIDGE: The relayd bridge (Protocol: relay bridge). It's interfaces are the LAN bridge and the WWAN interface.

Disregard the WGMesh parts; that's separate and not related to the wireless bridging mode.

collapsed inline media

collapsed inline media

[–] ptz@dubvee.org 10 points 2 days ago* (last edited 2 days ago)

Right? It's refreshing to see a post here that's about technology that works for us rather than yet another article about AI being shoved into more places that no one asked for or development progress updates on the Torment Nexus.

More posts like this, please.

[–] ptz@dubvee.org 8 points 2 days ago* (last edited 2 days ago) (1 children)

Oh, nice! The Xiao seed, unlike the Heltec's I have, comes with 8 MB of PSRAM which makes it suitable for acting as a store-and-forward node.

May have to pick up at least one of these since that's one thing I'd like to add to the mesh I'm putting together.

[–] ptz@dubvee.org 6 points 3 days ago* (last edited 3 days ago) (2 children)

He's a bastard coated bastard with bastard filling, but got dayum I love Bob Kelso.

Edit: Also, that's the Ally McBeal-esque daydream sequence playing in my mind when I have to go into the office.

[–] ptz@dubvee.org 32 points 3 days ago (1 children)

Is there a c/NotMyJob in the fediverse yet? This could be the inaugural post if not.

[–] ptz@dubvee.org 3 points 5 days ago* (last edited 5 days ago)

Probably from US east coast to Oklahoma (not my choice of destination lol). Missouri seemed like it would never end and was the absolute worst leg of the whole trip. There's a huge sense of progress when you cross state lines, and Missouri is just so wide, so flat, so....nothing that it made the whole trip stagnate.

[–] ptz@dubvee.org 6 points 5 days ago* (last edited 5 days ago) (3 children)

I completely understand the appeal of it, and on paper, I'd be right there with you. But, in practice, I personally hate the whole experience; it's just not for me. I'm more of a road trip guy which kind of limits me to North and South American continents, lol, since I also hate cruises. If I can't open the window, I'm not going 😆

 

Developers: I will never ever do that, no one should ever do that, and you should be ashamed for guiding people to. I get that you want to make things easy for end users, but at least exercise some bare minimum common sense.

The worst part is that bun is just a single binary, so the install script is bloody pointless.

Bonus mildly infuriating is the mere existence of the .sh TLD.

Edit b/c I'm not going to answer the same goddamned questions 100 times from people who blindly copy/paste the question from StackOverflow into their code/terminal:

WhY iS ThaT woRSe thAn jUst DoWnlOADing a BinAary???

  1. Downloading the compiled binary from the release page (if you don't want to build yourself) has been a way to acquire software since shortly after the dawn of time. You already know what you're getting yourself into
  2. There are SHA256 checksums of each binary file available in each release on Github. You can confirm the binary was not tampered with by comparing a locally computed checksum to the value in the release's checksums file.
  3. Binaries can also be signed (not that signing keys have never leaked, but it's still one step in the chain of trust)
  4. The install script they're telling you to pipe is not hosted on Github. A misconfigured / compromised server can allow a bad actor to tamper with the install script that gets piped directly into your shell. The domain could also lapse and be re-registered by a bad actor to point to a malicious script. Really, there's lots of things that can go wrong with that.

The point is that it is bad practice to just pipe a script to be directly executed in your shell. Developers should not normalize that bad practice.

 

Power company recently outsourced their payment system and now have to pay a fuckin' fee to pay my goddamned bill. The only way to avoid that is autopay.

Further infuriating is I have to re-add my bank info to yet another third party system.

Fuck the modern world, man.

view more: next ›