qjkxbmwvz

joined 2 years ago
[–] qjkxbmwvz@startrek.website 1 points 10 hours ago

March in San Francisco is feeling like August in LA.

[–] qjkxbmwvz@startrek.website 8 points 22 hours ago* (last edited 22 hours ago)

Coup de.tar.gz

[–] qjkxbmwvz@startrek.website 37 points 1 day ago (5 children)

But what if the foe is really the Epstein files?

Having trouble finding it but I swear my PNY Nvidia GeForce FX 5200 (I think?) circa 2003 came with a Linux 3D desktop/launcher software that sounds like this. (X11 based I guess.)

Not sure if it was bundled with the card, came with the Nvidia drivers, or what...but it worked just fine with Linux at the time (probably Slackware, not positive what I was running then).

[–] qjkxbmwvz@startrek.website 4 points 1 day ago (1 children)

I've heard stories of grad students flat out refusing to work with HF. (Never relevant for me, other than being something very scary.)

California's breakdown has a lot more renewables than US as a whole (shocking!): https://en.wikipedia.org/wiki/Energy_in_California

[–] qjkxbmwvz@startrek.website 3 points 1 day ago (1 children)

Having kids has made random conversations somewhat frequent for me.

Something that I found super interesting learning about amateur (ham) radio was that antennas don't always work "backwards" as you'd expect. From Maxwell's equations they obey reciprocity, so it stands to reason (or so I thought) that an antenna that's good at receiving is also good at transmitting.

But it's not true! It turns out that the noise floor of the environment


in part due to atmospheric stuff like lightning


is so much higher than the sensitivity of radios (well above thermal/Johnson noise) that an inefficient antenna can be a really good antenna for receiving, in certain circumstances. Namely, if a receive antenna is inefficient but has good directionality, it can be useful...but probably no good for transmission!

It's not super profound or anything, but I found it pretty interesting.

Remember that RAID and redundancy is not backup.

Try to 3-2-1, or something similar/better, if you can.

I am fairly sloppy here, and I am also very cheap. I have multiple copies in my home for important stuff (mainly Immich), the in use copy being on SSD and a few backups on spinning rust. I have a raspberry pi with an external HDD at family's place, with a daily rsync+snapshot, for off site backups.

Of course, I've never had a catastrophic failure, so who knows how smooth that would be...

[–] qjkxbmwvz@startrek.website 2 points 4 days ago

I switched to Technitium and I've been pretty happy. Seems very robust, and as a bonus was easy to use it to stop DNS leaks (each upstream has a static route through a different Mullvad VPN, and since they're queried in parallel, a VPN connection can go down without losing any DNS...maybe this is how pihole would have handled it too though).

And of course, wildcards supported no problem.

[–] qjkxbmwvz@startrek.website 3 points 4 days ago* (last edited 4 days ago) (1 children)

Maybe take a look at Outline. (Not affiliated, but I host it for myself.)

I also host KitchenOwl, but mostly just as a grocery list.

[–] qjkxbmwvz@startrek.website 3 points 4 days ago (1 children)

Nice Dali-esque chair!

 

Hi,

I am considering upgrading my router (RB750Gr3). I am eyeing the CRS309-1G-8S+IN in the hopes that the fast ISP in town eventually expand to my street (10G fiber).

My question is about L3HW offloading, and how it plays with PBR. Currently, I have a number of rules (/routing/rule), some based on source IP and some on VLAN. The purpose is to route certain traffic through VPNs (WireGuard, but I run on a separate computer, not on the router itself). Example: VLAN10 routes all traffic through main routing table, VLAN20 routes local traffic through router but sends external traffic through VPN-1, and VLAN30 sends everything through VPN-2. I use a number of different VPNs, so it's not just a binary "main route or VPN."

I am unclear how this plays with L3HW offloading. This page ( https://help.mikrotik.com/docs/spaces/ROS/pages/62390319/L3+Hardware+Offloading#L3HardwareOffloading-Inter-VLANRoutingwithUpstreamPortBehindFirewall/NAT ) mentions pbr-cap/usage/lpm-bank but I am unclear if that's referring to what I'd be using. That page also says that only the main routing table is HW offloaded in the context of VRF, so I wasn't sure if that also applied to PBR.

The question then, is, does L3HW offloading 1) Just Work for PBR /routing/rule, 2) only work via Fasttrack (perhaps requiring some redirect-to-cpu switch rules), or 3) ain't gonna work?

To preempt a few questions: I know Fasttrack is a last resort. I am a single household, I don't have concerns about TCAM exhaustion. I am considering a CRS instead of a "true" router due to cost and reduced energy footprint. I also know that I don't "need" 10G; if it is ever offered on my street it'll be via an ISP with a "best effort" policy, i.e., they don't have throttled tiers, so 10G is their only offering (cheaper than we're paying now for asymmetric cable).

Thanks!

 

What I want: I want to be able to route specific clients through different interfaces (WireGuard tunnels), and I want this behavior to persist upon disconnect/reconnect. Clients can change which tunnel, with several VLANs being able to use the tunnels (so a client A on VLAN 124 and client B on VLAN 789 can both use VPN tunnel X or Y at their discretion).

What I have: IPv4 works fine (routing rule src address -> routing table). IPv6 works, but is not persistent, as clients change their IPv6 address. (I have a dinky script where I enter IPv4 address and country, and it will grab a VPN peer from a json file, set it up, and add the IPv4+current IPv6 address to the routing rules. This works well currently; I use Mullvad.)

Any recommendations? Ideas: use IPv6 mangle based on MAC address, but I have been having trouble getting this to work (extremely slow). Another idea is to have a script run and grab the IPv6 address of client (either by hostname or by DHCP lease+MAC info), but I'm not sure if it's possible to trigger a script upon IPv6 neighbor discovery.

Any help appreciated!

view more: next ›