Be the change you want to see. Start calling it that and see if it catches on.
Be the change you want to see. Start calling it that and see if it catches on.
If the opnsense interface on the WAN VLAN has a public routable IP address there shouldn’t be a problem with double NAT. Double NAT should only be a problem if they have a crappy ISP that’s using CGNAT.
Edit: never mind, I reread your comment. We’re saying the same thing essentially.
He’s trying to run it on an esp32, didn’t you read the title? /s
Proud to be from the great state of 3i6nesota. You should come visit and explore our majestic waterfalls.
Are you making a crossover cable or installing it for the government? Those are the only places that I know of that A is used regularly. Nearly everywhere else uses B in my experience.
Clean Elizabeth
I’m still on the fence on this. I feel like they should federate fully instead of only one way, but I’m trying to understand the threat from Threads. I know it’s probably been done to death, but do you have a link or thorough explanation of why bringing more users and content to the fediverse is harmful?
Also, updates. A long uptime says I haven’t updated the kernel/firmware since at least this long.
Image server mangled by autocorrect? Best I can come up with.
Armed work ate my home dog.
Now I’m just waiting for Netgate to announce an end to CE so I have a reason to move to OPNsense. I’m lazy and it works so I haven’t taken the time to move yet. Weird for a company to EEE their own product.
It works in email too, but still makes the dot sender an asshole.