Taming the beasts… aka suricata blueprint

A Former User

Another deleted rule 2012688 !!! That's 3 rules out of my list in a week. Someone is being naughty and reading my list ;). Keep it up guys, with this pace we'll go through the entire list by next year's end.

wetspark

Ars Technica has a good article about IPv6 adoption up. We were running IPv6 is labs in the early 2ks and it continues to run heavily in the labs. I can enable services rapidly and easily for IPv6 on ADCs and run dual stack with keeping the backend IPv4 but still, interest remains low.

Good to see some of the rules getting addressed. I need to review the ones I've disabled to determine what's wrong with them. So much stuff to do, so little stuff I get paid to do. :)

q54e3w

@jflsakfja:

EDIT!!!! MISSED THE QUICK CHECKBOX. TICK THAT!

Question re floating rules for those who understand the black magic…
I've got my floating rules setup as earlier in this thread, all works fine except I now have a client who hosts his site on GoDaddy which conflicts which an IP in one of the PRI2 lists.
I can fix it easily by disabling the QUICK match on PRI2 rules as I have a whitelist in my LAN interface page which allows this address - but this seems inefficient, to my limited knowledge at least.
I tried to create a PASS/Quick rule in floating page higher up than the PRI2 entries but this doesn't work...it kind of half does but I still get a failed to load page ultimately although not as quickly. I suspect like outbound might work but not the accompanying inbound PASS...although Im way out of my depth here trying to debug it. Do PASS entries work in the floating page and if so, any guidance for a novice?
thx in adv

BBcan177

@irj972:

Question re floating rules for those who understand the black magic…

For the Pass Floating Rule, did you select both the inbound and outbound interfaces?

q54e3w

I duplicated what I had with the PRI1 etc for in & out with same set of interfaces, i.e
Whitelist Source = WAN (& VPN_WAN)
Whitelist Dest = LAN (& VPN_LAN)
pic attached in case it helps

EDIT: I trimmed some info from my setup to reduce noise however I now suspect this omission might have something to do with my problem. I suspect a gateway related issue as I run a VPN and it possibly doesn't know how to route packets originating from the VPN interface….I'll try and verify.
If anyone knows any good resources on how to build good firewall rules Id appreciate the pointer, learning by trial and error is tough going. thx again.

fw.png_thumb

G.D. Wusser Esq.

About IPv6 blacklisting.

It seems that experts in general have an opinion that blacklisting has not been all that effective in IPv4 world, so may as well just abandon it for IPv6, and concentrate on other tactics instead.

Say we still want to blacklist, I think we are going to quit blacklisting individual addresses all together, and ban entire /64 or /42 outright.
Has anyone dabbled in IPv6 blacklisting yet? How is the quality of public IPv6 blacklists?

A Former User

@G.D.:

About IPv6 blacklisting.

It seems that experts in general have an opinion that blacklisting has not been all that effective in IPv4 world, so may as well just abandon it for IPv6, and concentrate on other tactics instead.

Say we still want to blacklist, I think we are going to quit blacklisting individual addresses all together, and ban entire /64 or /42 outright.
Has anyone dabbled in IPv6 blacklisting yet? How is the quality of public IPv6 blacklists?

Have yet to be hit by anything "massive" in IPv6, so I'll just speculate.

IPv6 /64s are the equivalent of IPv4 /24s. An attacker can "move" within that subnet (dynamic IP, or just fast changing static IPs), and as long as he moves, the blacklisting has already gone to hell. I understand that an attacker can also move to a different subnet, but the same thing applies.

The way I currently do it, is if I see a single IP from a subnet, I block it (already taken care by suricata). If I see multiple IPs blocked from that subnet, I block the entire subnet and alert their upstream. If I'm ignored (suricata still firing up alerts), I look into the subnet more. What country does it come from? Does the upstream already have a different subnet on my permanently banned lists? How long (going back a few years) is that subnet being "naughty"? Did the same ISP have any other interesting subnet (again, going back a few years)? Depending on the answer to those questions and the severity of the traffic, The entire subnet is added to my permanently banned lists.

That's why I strongly disagree with using every single list that's out there. Use the bare essentials, weed out 90% of the traffic, let suricata weed out another 5% and only deal with the 5% that remains. Where it becomes difficult to keep it all together is hosts on the permanently banned list still causing alerts in suricata. There is a way to ignore them using a passlist, but it's not ideal. What I really need to do is ignore the packets originating from a predefined alias and not send them to suricata, but that a different story.

I think that the way IPv6 will be handled will be similar to what I described above. The bad thing about blocking entire subnets are the "innocent" people that go down with them. I consider them as collateral damage. In practice (as described in this guide) the way to perfect (and yes there IS perfect) network security is approaching it in a layered way. And anyone already typing "but eventually you will make a mistake" stop typing and read on.

By layered I mean:

build a trench around your castle. You have already stopped the horsemen.
build high strong walls, with sentries and hot oil. You have already stopped the heavy infantry.
build a strong gate. You have already stopped the rams.

What about catapults? What about them setting your gate on fire? Setting the gate on fire is easily circumvented. Get an iron gate. Catapults? You should already know that catapults are coming, and you should have already sabotaged them. What good are spies if you don't use them?

No I didn't go off in a tangent. Dealing with portscanners shouldn't be your priority. That should already be handled by suricata/pfsense. If the person doesn't know what's running on your hosts, then he can't just guess "ah, they are running ubuntu, let's launch this exploit hoping it will work". How many of your webservers are advertising the server's version in the response? Why not just say "webserver"? The attacker is already trying to find vulnerabilities to your network by interacting with the server. Does your server respond in a way that will alert suricata that host X is poking around, resulting in automatic banning? Does the host handle the automatic banning itself, then push the blocked host to your router? Is the software running on the server properly updated, or is it a 13 year old software (sidenote: checked a long list of hosts the other day (not mine) and some of them were running 13 year old software!!!). If it's not updated, why is it not updated? If it is updated, are there any other mitigations enabled? Is the underlying OS hardened in any way? Or is it happily running a completely up to date X ftp server, but also happily refusing logins without enforcing maximum retries? Is every ssh client connected jailed? Is every single php script running in the same pool? Are basedir restrictions being applied, or can the attacker simply upload a script anywhere and execute it? Does the webserver have access to the same memory that the ssh server uses? Can it write to it?

If you did your absolute best to secure a network and somebody managed to get in, you didn't make a mistake. You simply didn't try hard enough.

Using lists+pfsense+suricata you have already cut down the bad traffic by a LARGE amount. Don't simply sit idling and watch the rest of the traffic go through. Did something new pop up in the logs? Investigate it and don't ignore it.

MLS systems aren't simply installing SELinux and setting it to MLS and boasting "Hey, look at me, I'm running an MLS system!". NO. MLS systems are systems that were designed to separate security into different layers, and each layer dealing with something as efficiently as possible.

As long as the systems are capable of protecting themselves, you shouldn't need to worry about mass blocking hosts. That will naturally come on its own. What this does is add yet another layer to the security: Security through obscurity. Note to industry leaders: FOR THE MILLIONTH TIME: SECURITY THROUGH OBSCURITY IS REAL SECURITY.

Now, if there was a way to keep track of the blocked hosts and identify subnets that could be automatically banned…I'm looking at you BBcan177 ;) (same thing the script does, but using pfsense's snort2c table)

Reaction after previewing the post: "When did I type all that?"

squatch04

Getting a lot of these errors from lists in my syslog:

php: rc.filter_configure_sync: The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/AbusePalevo.txt.tmp' 'https://127.0.0.1:43/badips/AbusePalevo.txt'' returned exit code '1', the output was 'fetch: https://127.0.0.1:43/badips/AbusePalevo.txt: Operation timed out'

wcrowder

Port is wrong on your aliases should be: https://127.0.0.1:443/badips/AbusePalevo.txt not 43

Something looks off on the directory to…

@squatch04:

Getting a lot of these errors from lists in my syslog:

php: rc.filter_configure_sync: The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/AbusePalevo.txt.tmp' 'https://127.0.0.1:43/badips/AbusePalevo.txt'' returned exit code '1', the output was 'fetch: https://127.0.0.1:43/badips/AbusePalevo.txt: Operation timed out'

squatch04

@wcrowder:

Port is wrong on your aliases should be: https://127.0.0.1:443/badips/AbusePalevo.txt not 43

Something looks off on the directory to…

Here is where my de-duplicated lists are:


$ ls /usr/local/www/badips
ALIENVAULT.txt
AbusePalevo.txt
AbuseSpyeye.txt
AbuseZeus.txt
Atlas_Attacks.txt
Atlas_Botnets.txt
Atlas_Fastflux.txt
Atlas_Phishing.txt
Atlas_SSH.txt
Atlas_Scans.txt
Blut_TOR.txt
CIArmy.txt
DRG_SSH.txt
DRG_VNC.txt
DRG_http.txt
DangerRulez.txt
ET_Comp.txt
ET_TOR.txt
Feodo_Bad.txt
Feodo_Block.txt
Geopsy.txt
IBlock_BT_FS.txt
IBlock_BT_Hijack.txt
IBlock_BT_Spy.txt
IBlock_BT_Web.txt
IBlock_Badpeer.txt
IBlock_Onion.txt
Infiltrated.txt
MDL.txt
MalwareGroup.txt
NOThink_BL.txt
NOThink_Malware.txt
NOThink_SSH.txt
OpenBL.txt
SRI_Attackers.txt
SRI_CC.txt
Shunlist.txt
Spamhaus_drop.txt
Spamhaus_edrop.txt
VMX.txt
WatchGuard.txt
dShield_Block.txt
dShield_Top.txt
malc0de.txt

Ok so it should really be "https://127.0.0.1:443/usr/local/www/badips/AbusePalevo.txt"?

When done correctly shouldn't the IPs show up in the lists' Values in Firewall>>>> Aliases?

Also, would pfBlocker.widget.php_PATCH and diag_dns.php_PATCH work with 2.1.5?

When i try to test the patches i get this error:


Output of full patch apply test:

/usr/bin/patch --directory=/usr/local/www/ -t -p1 -i /var/patches/5401274d202ba.patch --check --forward --ignore-whitespace

Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- /usr/local/www/widgets/widgets/pfBlocker.widget.php 2014-06-28 13:11:18.000000000 -0400
|+++ /usr/local/www/widgets/widgets/pfBlocker.widget.php 2014-06-28 13:06:55.000000000 -0400
--------------------------
No file to patch.  Skipping...
Hunk #1 ignored at 2.
Hunk #2 ignored at 29.
Hunk #3 ignored at 39.
Hunk #4 ignored at 53.
Hunk #5 ignored at 61.
Hunk #6 ignored at 84.
Hunk #7 ignored at 92.
7 out of 7 hunks ignored--saving rejects to usr/local/www/widgets/widgets/pfBlocker.widget.php.rej
done


Output of full patch apply test:

/usr/bin/patch --directory=/usr/local/www/ -t -p1 -i /var/patches/5401259cb1b0c.patch --check --forward --ignore-whitespace

Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- /usr/local/www/diag_dns.php        2014-06-23 14:22:26.000000000 -0400
|+++ /usr/local/www/diag_dns.php        2014-06-23 14:22:02.000000000 -0400
--------------------------
No file to patch.  Skipping...
Hunk #1 ignored at 114.
Hunk #2 ignored at 158.
Hunk #3 ignored at 179.
Hunk #4 ignored at 276.
4 out of 4 hunks ignored--saving rejects to usr/local/www/diag_dns.php.rej
done

BBcan177

@squatch04:

Getting a lot of these errors from lists in my syslog:

php: rc.filter_configure_sync: The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/AbusePalevo.txt.tmp' 'https://127.0.0.1:43/badips/AbusePalevo.txt'' returned exit code '1', the output was 'fetch: https://127.0.0.1:43/badips/AbusePalevo.txt: Operation timed out'

How did you configure the Alias Table? It Should be a "URL Table".

I would also recommend just using the existing IR_ Tables that the Script already created. This saves you the effort of making dozens of Alias Tables.

/usr/local/www/aliastables/IR_MAIL
/usr/local/www/aliastables/IR_PRI1
/usr/local/www/aliastables/IR_IB
/usr/local/www/aliastables/IR_SEC1
/usr/local/www/aliastables/IR_PRI2
/usr/local/www/aliastables/IR_SEC3
/usr/local/www/aliastables/IR_TOR
/usr/local/www/aliastables/IR_SEC2
/usr/local/www/aliastables/IR_PRI3

BBcan177

@G.D.:

About IPv6 blacklisting.

It seems that experts in general have an opinion that blacklisting has not been all that effective in IPv4 world, so may as well just abandon it for IPv6, and concentrate on other tactics instead.

Say we still want to blacklist, I think we are going to quit blacklisting individual addresses all together, and ban entire /64 or /42 outright.
Has anyone dabbled in IPv6 blacklisting yet? How is the quality of public IPv6 blacklists?

I haven't even started to look at IPv6. I found this old link on Spamhaus website

http://www.spamhaus.org/organization/statement/012/spamhaus-ipv6-blocklists-strategy-statement

I don't know of any IPv6 Blocklists? If anyone has time to research, please forward to the group and we can begin to work out a process to include those.

@jflsakfja:

Now, if there was a way to keep track of the blocked hosts and identify subnets that could be automatically banned…I'm looking at you BBcan177 ;) (same thing the script does, but using pfsense's snort2c table)

In regards to the snort2c file, I think keeping track of Repeated Offenders is a great Idea. This should also involve the pfSense Firewall Blocks also.

I have been working away at getting a Beta of pfBlocker that incorporates my script and some other new features. I believe that I am 90% there. Would be nice to get help from the pfBlocker developers but they seem to have no interest in supporting a new release of pfBlocker. I am not even sure if the Devs want or will support it when I get it finalized. It may end up being a new package…..

A few members have been helping to beta test the package and that is helping weed out issues. If anyone has real time to spare, drop me a PM if you have interest in helping BETA test. Thanks to Cino and wcrowder for their support!! ;) ;)

BBcan177

@squatch04:

Also, would pfBlocker.widget.php_PATCH and diag_dns.php_PATCH work with 2.1.5?

I would assume that there are changes to those files in 2.1.5, so I will need to look at it and write a patch.

From looking at 2.2 and from the 2.1.5 release notes, I think they removed the ability to Resolve External IP lookups. If thats the case, not sure if we should add the functionality manually or leave it alone? Other possibility is to add a new Log in pfBlocker just for the Blocklists and Resolve from there. This way there is no mucking around with pfSense System Files.

- from the 2.1.5 Release Notes:

Remove javascript alert DNS resolution action from the firewall log
view. It was already removed from 2.2, and it's better not to allow a
GET action to perform that action

squatch04

@BBcan177:

@squatch04:
Getting a lot of these errors from lists in my syslog:
php: rc.filter_configure_sync: The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/AbusePalevo.txt.tmp' 'https://127.0.0.1:43/badips/AbusePalevo.txt'' returned exit code '1', the output was 'fetch: https://127.0.0.1:43/badips/AbusePalevo.txt: Operation timed out'
How did you configure the Alias Table? It Should be a "URL Table".

I would also recommend just using the existing IR_ Tables that the Script already created. This saves you the effort of making dozens of Alias Tables.

/usr/local/www/aliastables/IR_MAIL
/usr/local/www/aliastables/IR_PRI1
/usr/local/www/aliastables/IR_IB
/usr/local/www/aliastables/IR_SEC1
/usr/local/www/aliastables/IR_PRI2
/usr/local/www/aliastables/IR_SEC3
/usr/local/www/aliastables/IR_TOR
/usr/local/www/aliastables/IR_SEC2
/usr/local/www/aliastables/IR_PRI3

Thanks BBcan177,

I'll try the IR_ Tables instead.

Currently with the script installed and only Suricata configured following the guidelines on this thread my RAM usage is on average in the 80s%.

I was thinking of setting up simple cache (squid proxy) along with it but with my RAM usage so high is there anyway i can still get the most out of using Suricata/pfiprep with the squid cache?
What lists/rules would be fine to disable? (i've followed jflsakfja's guidelines but i still think that there are some lists/rules that may not apply to my usage scenario.)

I have a 50mbps connection & my pfSense system is an Athlon 64 3000+ with 1.25GB of RAM and 2 nics (LAN/WAN). That's connected to a switch with a wireless AP, 5 wired clients and possibly over 25 wireless clients.

We are basically a media consuming household (HD streaming,downloads,torrents,skype,teamviewer,facebook etc) and if it was up to me I'd block most of these kinds of traffic but all hell would break loose if i did that, seriously.
Other than my OpenVPN server that i have on my pfSense machine, squid cache, suricata, pfiprep…that's about it.

Any rules/lists that you recommend disabling to reduce memory usage?

wetspark

@G.D.:

About IPv6 blacklisting.

It seems that experts in general have an opinion that blacklisting has not been all that effective in IPv4 world, so may as well just abandon it for IPv6, and concentrate on other tactics instead.

Say we still want to blacklist, I think we are going to quit blacklisting individual addresses all together, and ban entire /64 or /42 outright.
Has anyone dabbled in IPv6 blacklisting yet? How is the quality of public IPv6 blacklists?

I see that jflsakfja already reply and I'd agree with near all except that I'd recommend blocking on subnet boundaries with IPv6 and here's why. /64 is the smallest advertisable block size for IPv6. In fact that size will likely be assigned to every home/consumer connection. A /56 or /64 will likely be the smallest allocated size and you'll get your own /64 or so for your home etc. Some are even saying that could be a /48 but I doubt that. The trick is that not everyone is a home user and you could have issues with hosted systems and hitting an innocent with a /64 block blacklist entry. There are other interesting characteristics about IPv6 and I think we will see some innovation in security due to it once we have a broad uptake of the address system.

So, blacklisting in IPv6 should near certainly be done at those boundaries or we'd be in hairy hell chasing an effective blocking measure. I'll take that conundrum over IPv4 hell we are in now.

A Former User

@squatch04:

Thanks BBcan177,

I'll try the IR_ Tables instead.

Currently with the script installed and only Suricata configured following the guidelines on this thread my RAM usage is on average in the 80s%.

I was thinking of setting up simple cache (squid proxy) along with it but with my RAM usage so high is there anyway i can still get the most out of using Suricata/pfiprep with the squid cache?
What lists/rules would be fine to disable? (i've followed jflsakfja's guidelines but i still think that there are some lists/rules that may not apply to my usage scenario.)

I have a 50mbps connection & my pfSense system is an Athlon 64 3000+ with 1.25GB of RAM and 2 nics (LAN/WAN). That's connected to a switch with a wireless AP, 5 wired clients and possibly over 25 wireless clients.

We are basically a media consuming household (HD streaming,downloads,torrents,skype,teamviewer,facebook etc) and if it was up to me I'd block most of these kinds of traffic but all hell would break loose if i did that, seriously.
Other than my OpenVPN server that i have on my pfSense machine, squid cache, suricata, pfiprep…that's about it.

Any rules/lists that you recommend disabling to reduce memory usage?

I'm seeing 22-25% of 4GB RAM usage on systems configured to the T using this guide, so your 80% of 1.25GB seems about right. 1.25 seems wrong though. What's that, 1GB+256MB stick, or 2x512MB+256MB stick? In either case, getting more RAM is what I would do. 1GB shouldn't be more than $20. If you are using 1GB+256MB just get another GB and replace the 256MB module. Since it takes about 1GB for each system configured according to this guide, you should drop down to 50% RAM, which should give you plenty of room to use other things if you need to.

squatch04

@jflsakfja:

@squatch04:

Thanks BBcan177,

I'll try the IR_ Tables instead.

Currently with the script installed and only Suricata configured following the guidelines on this thread my RAM usage is on average in the 80s%.

I was thinking of setting up simple cache (squid proxy) along with it but with my RAM usage so high is there anyway i can still get the most out of using Suricata/pfiprep with the squid cache?
What lists/rules would be fine to disable? (i've followed jflsakfja's guidelines but i still think that there are some lists/rules that may not apply to my usage scenario.)

I have a 50mbps connection & my pfSense system is an Athlon 64 3000+ with 1.25GB of RAM and 2 nics (LAN/WAN). That's connected to a switch with a wireless AP, 5 wired clients and possibly over 25 wireless clients.

We are basically a media consuming household (HD streaming,downloads,torrents,skype,teamviewer,facebook etc) and if it was up to me I'd block most of these kinds of traffic but all hell would break loose if i did that, seriously.
Other than my OpenVPN server that i have on my pfSense machine, squid cache, suricata, pfiprep…that's about it.

Any rules/lists that you recommend disabling to reduce memory usage?

I'm seeing 22-25% of 4GB RAM usage on systems configured to the T using this guide, so your 80% of 1.25GB seems about right. 1.25 seems wrong though. What's that, 1GB+256MB stick, or 2x512MB+256MB stick? In either case, getting more RAM is what I would do. 1GB shouldn't be more than $20. If you are using 1GB+256MB just get another GB and replace the 256MB module. Since it takes about 1GB for each system configured according to this guide, you should drop down to 50% RAM, which should give you plenty of room to use other things if you need to.

Thanks for the reply.

You're correct it's 1GB+256MB stick and usage is around 83% of that most of the time and if that's average use for the guide then I'll invest in another 1G of RAM. Security is more important than bandwidth/speed ;D

squatch04

@BBcan177:

@squatch04:
Getting a lot of these errors from lists in my syslog:
php: rc.filter_configure_sync: The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/AbusePalevo.txt.tmp' 'https://127.0.0.1:43/badips/AbusePalevo.txt'' returned exit code '1', the output was 'fetch: https://127.0.0.1:43/badips/AbusePalevo.txt: Operation timed out'
How did you configure the Alias Table? It Should be a "URL Table".

I would also recommend just using the existing IR_ Tables that the Script already created. This saves you the effort of making dozens of Alias Tables.

/usr/local/www/aliastables/IR_MAIL
/usr/local/www/aliastables/IR_PRI1
/usr/local/www/aliastables/IR_IB
/usr/local/www/aliastables/IR_SEC1
/usr/local/www/aliastables/IR_PRI2
/usr/local/www/aliastables/IR_SEC3
/usr/local/www/aliastables/IR_TOR
/usr/local/www/aliastables/IR_SEC2
/usr/local/www/aliastables/IR_PRI3

Followed your suggestion and changed the URL Tables and it seems to be working (the IPs show up when i mouse over the Aliases) but i still get syslog errors.


Aug 30 09:40:26 	php: rc.filter_configure_sync: The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/IR_SEC2.txt.tmp' 'https://127.0.0.1:443/usr/local/www/aliastables/IR_SEC2'' returned exit code '1', the output was 'fetch: https://127.0.0.1:443/usr/local/www/aliastables/IR_SEC2: Operation timed out'

Is this something to be concerned about?

pfIP Rep widget shows last update was Aug 30 09:43 with status arrow green (up) though…

BBcan177

@squatch04:

Getting a lot of these errors from lists in my syslog:

php: rc.filter_configure_sync: The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/AbusePalevo.txt.tmp' 'https://127.0.0.1:43/badips/AbusePalevo.txt'' returned exit code '1', the output was 'fetch: https://127.0.0.1:43/badips/AbusePalevo.txt: Operation timed out'

I don't understand where the .tmp extensions comes from? It should end with .txt?

If you are using the IR_ Alias URL Tables, I would remove URL Tables that are referencing the individual files as shown above. I would also delete these individual aliases in /var/db/aliastables

Hope that Helps.

squatch04

@BBcan177:

@squatch04:
Getting a lot of these errors from lists in my syslog:
php: rc.filter_configure_sync: The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/AbusePalevo.txt.tmp' 'https://127.0.0.1:43/badips/AbusePalevo.txt'' returned exit code '1', the output was 'fetch: https://127.0.0.1:43/badips/AbusePalevo.txt: Operation timed out'
I don't understand where the .tmp extensions comes from? It should end with .txt?

If you are using the IR_ Alias URL Tables, I would remove URL Tables that are referencing the individual files as shown above. I would also delete these individual aliases in /var/db/aliastables

Hope that Helps.

Hey BBCan177!

i figured it out.

"Operation timed out" was caused by the port being blocked. i had previously created a custom port and disabled anti-lockout so entering my port number 66 allowed the fetch command to access the list directory.
Even though it passed using the custom port i still had the fetch error "not found".
i confirmed my directory was correct which was "/usr/local/www/aliastables"


$ ls /usr/local/www/aliastables
IR_CC
IR_IB
IR_Match
IR_PRI1
IR_PRI2
IR_SEC1
IR_SEC2
IR_TOR

It seems like the directory was already defaulted to "/usr/local/www/" when adding the URL tables so the shortened directory address of "https://127.0.0.1:66/aliastables/IR_SEC2" for example worked for all the IR Lists.