Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
20.1 Legacy Series
»
Alias Issue
« previous
next »
Print
Pages: [
1
]
Author
Topic: Alias Issue (Read 1612 times)
j2f
Newbie
Posts: 1
Karma: 0
Alias Issue
«
on:
April 23, 2020, 11:16:03 pm »
Hi,
Am currently testing OPNsense 20.1.4 in a VM on Proxmox 6.1-7 and am running into an alias issue...
I have an Amazon FireTV and am blocking updates via dd-wrt on my router. I can define the 4 websites to be blocked, for which one is "amzdigitaldownloads.edgesuite.net"
In OPNsense, I define an alias named "amazon_updates", type "Host(s)", and content "amzdigitaldownloads.edgesuite.net". When I click "Save", "Loading..." then appears in the alias list with no entries visible at all. After 90 seconds it displays "No results found!", still with no visible entries including the one I just created. Whether I click "Apply" at any point in this process makes no difference. If I navigate away and back to the aliases page, the 90 second loading cycle starts again. I can see the alias show up on the pfTables page, so I know the alias is actually being created
Issue is consistent across browsers such as Firefox, Opera, and Internet Explorer
Problem is I can no longer edit this alias (or any others) via the web page. Instead I must manually remove the "content" entry for the alias from /conf/config.xml via SSH. Once I do that and navigate back to the aliases page, my list reappears, including the new entry. But it is worthless as I cannot define the websites to be blocked. I would like to define all 4 and then set an outgoing LAN rule to the alias, since I cannot define the 4 addresses directly in the rule
I can create the alias with an empty "content" field just fine. It's when I try to save it with the web address that it craps out
Eventually I will be replacing my router with OPNsense, but for now I am in the testing phase and will continue to keep the websites blocked via my router. I removed the one Amazon address from my router and OPNsense allowed the alias to create successfully. Once I added the address back to my router the issue reoccurred. Also note that if I use a non-blocked address such as "amazon.com" in the alias I do not run into the issue. So it does appear the blocking on the router is the culprit
If OPNsense is trying to resolve the address on alias creation/modification, is it normal behaviour or a possible bug? Keep in mind this is not an issue and works just fine in pfSense 2.4.5, also in a VM on Proxmox
Any help would be appreciated
Thanks!
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
20.1 Legacy Series
»
Alias Issue