Upset millennial.
Code quality matters.
Arguably the worst book in the series is 10. I got slagged for 4 years at that point until surrendering to the audiobook. It felt like a disjointed midpoint with nowhere to go. So, feel you on just abandoning joy because quitting wasn’t an option.
A surface dwelling dark elf society that’s established a sizeable banana empire in the tropics of Faerun.
Ah yes, Menzobananazan
Fhaf’s jusf how we wrife f’s here.
I have absolutely no idea. I just run this over wireguard and call it a day.
That sucks 🤷
Except no one in the house has an Amazon account
If only to be go back to that stage of the internet
Comes to internet for help
Handed a path to a solution
shoots footgun
Draw it!!!
Draw a network map!!! It’s what I’ve done on every security engagement, ever. Mark out all your IP addresses, draw lines to denote the communicating RHP (random high port) against the well-known, e.g. 443/tcp HTTPs, for networks of hosts to servers. Then draw boxes around those IP spaces that are colocated on the same box. Then draw red lines perpendicular to every connection from a client to server that isn’t bounded on a single host.
The red lines denote non-localhost traffic - places to be observed, and for the most part the only IP:port assignments you should be relying on for routing.
My rec, draw the map and if that doesn’t help get back to us w it - or feel free to dm me.
Edit: I’ll find and post an example as a response this thread later.
And they’ll shoot you if you try.
Inherently this. Keeping security/spam/admin@ open are generally benevolent behaviors for the internet. The more appropriate response is to start blocking domains and hosting providers from contacting those channels. If someone cares, they’ll reach out.
Microsoft properties on the other hand, can suck my whole asshole.
I gave the example of PPPoE, the other option is to read the linked kernel docs to understand traffic steering and infer where those situations could occur.
Opensense is often bound by single-core operations depending on where a network packet may plumb itself through the kernel. A great example is any PPPoE connections on the base OS BSD. Vyos doesn’t have these same limitations since it’s minted on Linux - which supports traffic steering.
Really though, IaC for vyos has always been rock solid. Even though the persistent config in Opnsense is cool, adding new features or configs can be a bit of a pain in the ass
Possessive nouns over people are annoying af, mad get it. It’s not supposed to come off that way but, words mean things.
Yeah this is the only answer for that price
You have no idea how hard it was to end up here and not there. No idea, Michael.