So, someone on reddit thought it would be rather funny to post a link to this image on our server at work:
It was posted under the heading “NSFW” (Not Safe For Work). If you aren’t aware, that typically denotes a post to something inappropriate in nature. It’s work safety gear, so it’s pretty funny. One of the comments on the thread suggested that: “Their sysadmin is going to be very confused.” Indeed, we were:
The original image was rather large in nature, so we were moving a lot of outbound traffic (a lot for us anyway). So, to mitigate, I resized the image, and did an http 301redirect back to a custom (and very slim) html page:
We’ve never had that much traffic before, and we appreciate the opportunity to see what it’s like… even for a silly reason.
If you didn’t guess by the title, this is Part 3 in a whole series about abusing iptables. It’d be wise to read Part 1, then Part 2, then come back here.
If you are looking for a copy/paste answer, you won’t find it. The actual solution is spattered throughout all three parts to tell […]
If you haven’t read Part 1: The Problem, I’d suggest you go do that first.
After discovering the actual problem, I started pouring over UCM documentation and options. Different combinations of options cause the SIP trunk to behave in different ways, but there doesn’t seem to be anything related to this mystical port 4000. Finally […]
Technically speaking: stateless source address and port translation. Only on relevant packets, which are indistinguishable at the packet level from irrelevant packets. Why? Well, Music On Hold, of course.
The article that follows is dedicated to all of my friends and family who encompass my entire career as: “He fixes computers”. Here is a brief […]