Radical.

Yes. Can be anyway.

I think it’s incompetence.

It’s going on a sidequest.

Yeah I remember that from history classes. Makes it even more on the nose with the whole star wars prequels inspiration.

Je suis le Senate!

I was just thinking there’s somebody rewriting coreutils in rustnand there it is. I’m omnipotent!

Credit and release any changes you made to it. No freeloading.

Easily done with licences. Corpo is scared of licensing.

Also unless you can hyperfocus and literally exhaust yourself in those 8h, you can’t do any type of white collar job for 8h a day. It’s impossible to be mentally productive for that amount of time day in day out. Forget doing anything creative.

Then again my 2016 stock yaris had the best sound I ever heard anywhere.

Most of physical media is just a box with a code inside these days. You’ll be lucky to get a DVD with some of the game data you still need to patch.

I work in IT and security, where everyone is an expert. Couple that with my inability to tell half-thruths about complex subjects I have incomplete info about, and I come out as incompetent. Yay.

I was trying to do something with AR back with 4.0, I think it’s great for plain phone apps too, but there wasn’t enough documentation back then.

I think this lead me on the right path: https://community.ui.com/questions/Having-trouble-allowing-WOL-fowarding/5fa05081-125f-402b-a20c-ef1080e288d8#answer/5653fc4f-4d3a-4061-866c-f4c20f10d9b9

This is for edgerouter, which is what I use, but I suppose opensense can do this just as well.

Keep in mind, don’t use 1.1.1.1 for your forwarding address, use one in your LAN range, just outside of DHCP because this type of static routing will mess up a connection to anything actually on this IP.

This is how it looks in my edge os config:

protocols {
  static {
    arp 10.0.40.114 {
      hwaddr ff:ff:ff:ff:ff:ff
    }
  }
}

10.0.40.114 is the address I use to forward WoL broadcast to.

Then I use an app called Wake On Lan on Android and set it up like this: Hostname/IP/Broadcast address: 10.0.40.114 Device IP: [actual IP I want to wake up on the same VLAN/physical network] WOL Port: 9

This works fine if you’re using the router as the gateway for both VPN and LAN, but it will get messy with masquarade and NAT - then you have to use port forwarding I guess, and it should work from WAN.

I just wanted it to be over VPN to limit my exposure (even if WoL packets aren’t especially scary).

There is a trick you could do to send a WoL packet to a separate IP on the sender network and modify it so it is repreated on the network of the machine you want to wake up.

I can’t find docs on thisb on mobile, but can look for it later.

It can’t work like a typical IP packet routing tho. I’ve only made it work with a VPN connection.

Another thing you can do is ssh to your router and send a WoL packet from there on the machine’s LAN.

It’s generic advice, but check kompose - it can translate docker compose yml into a bunch of k8s objects, as far as it sensibly can.

The mose issues can come from setting up volumes, since docker has different expectations towards the underlying filesystem.

It does save a bunch of work of rewriting everything by hand.

Rules are made up.

How it compares ro TreeStyleTabs?

If you don’t need external calls sip trunk is not needed.