So I originally started writing a post here that was half-rant and half-discussion-of-my-findings-sofar. But I ended up fixing the issue, so I will explain what my issue was and how I fixed it.
So, I’m trying to use the webserver feature of FreeNAS. It’s a different instance of the webserver than the one used to manage the server itself. This one purely lists the files in a directory, allowing for easy browsing and downloading, and it runs on a different port. People outside the network could not get the page to load, even though the port had been forwarded correctly.
Here are the steps I went through to troubleshoot, and the results:
1. I could access it perfectly from inside the network, behind the firewall. This indicated that the service was running correctly.
2. After forwarding the port, I had people outside the firewall attempt to connect. Nothing.
3. I changed the port, in case my ISP was messing with my janx. Still nothing.
4. Forward a different port to a different machine with a different service. Nothing.
At this point, it looks like a network problem, even though I had looked at the router configuration for literally minutes.
5. The routing platform I am using, pfSense, includes a simple packet capturing utility. I fired this up, and with some tweaking, I was able to get a clean capture of the pertinent traffic. I was able to export it from pfSense and import it into Wireshark, which revealed the following:
What is not shown in that picture is that those are all SYN packets.
I’m going to stop here for the night, and will post the exciting conclusion tomorrow. If you have any thought as to what it might be, feel free to post them.
And yes, I included an animated .gif of Geordi La Forge diving like a badass under a slowly closing door.
1. So are you supposed to be Geordi La Forge or the wall?
2. Your entry doesn’t make much pfSense to me.
3. You’re so smart, lovebucket.
Was it Lupus?