Failing to add URL alias with mixed IPv4 and IPv6 addresses
-
I found the same issue with Enom. If I create an alias, it will always be used. I use an alias to convert a long host name from my ISP to one on my domain for IPv4. But I have the proper host names on IPv6 for my network.
-
Yeah this does "seem" a bit buggy to me as well. From my quick check.
I was able to duplicate what your seeing.. Where the the last url seems to be the only one listed.. If v4 is on bottom, then v4 are listed, if v6 is bottom. The v6 is listed in the table.
You would have to use 2 different lists to see if that is due to the ipv6 and ipv4 different lists. Or if the same sort of thing happens if you have 2 different v4 or v6 lists. And only the bottom url is stored in the table.
To be honest I would think url (tables) would be the alias you would want to use anyway. This would be reloaded per the number of days you choose from 1 to 128.. Since I would assume these lists could change..
But with those you can only use 1 url.
As a work around until can get to the bottom of it. I would suggest create 2 url (table) aliases - one for v4 and one for v6 and use those in different rules for v4 and v6..
-
@johnpoz Thank you! Excellent suggestion. Indeed, two different IPv4 lists exhibit the same behaviour.
Your suggested work-around makes sense. I guess I should also report this issue to the maintainers. Is Redmine the right place to do so?
Reference files: https://github.com/lindhe/netgate-topic-159803/
-
Yes the correct place would be redmine, with link to this thread for discussion of and showing that others have duplicated the problem.
As another work around, you could prob leverage pfblocker aliases, they allow for multiple lists in the same alias.. Then use the pfblocker native alias in you rules.
-
@johnpoz This seems similar, but I don't think it's the same issue. Do you think so too?
https://redmine.pfsense.org/issues/9296
-
I would say yeah its sim in nature.. But what your doing here is pulling a list of ips, nothing has to be resolved, other then where your list is hosted.. Guess that could be related to why only the 2nd url listed loads?
-
@johnpoz I tried now to use two different domains (github and cloudflare) for the URLs, and it still only resolves the last one.
-
Here is the issue I created for it: https://redmine.pfsense.org/issues/11256
-
@lindhe Please test it on the latest 2.5 snapshot
-
@viktor_g Hi! Thanks for getting back to me! I'll need to make sure I have a proper backup before I'll venture into unreleased territory. Do you know if I can always "upgrade back" again if I go from 2.4 to 2.5, if something breaks?
-
@lindhe said in Failing to add URL alias with mixed IPv4 and IPv6 addresses:
Do you know if I can always "upgrade back" again if I go from 2.4 to 2.5, if something breaks?
Not you can not auto "upgrade" to 2.4.. Just make sure you have a backup of your config.. And install media.. Be that CE or if your FE, open a ticket with netgate and they will send you link to FE copy you can download.
So if you decide you want to roll back, its really simple.
But to be honest 2.5 is close - I would be surprised if there was an issue that would force you to roll back.
-
Unfortunately, the issue still persists in the latest stable version (21.02_1). :/
-
Or, no not quite the same. Adding two lists of IPv4 urls works now. But nested aliases still fail.
I guess that I can now use a reasonable work-around by creating a mixed (unnested) alias instead. But it's overflowing the text box, so I don't know how to verify that all addresses are in the alias now. How can I verify that the alias is correct?
-
@lindhe said in Failing to add URL alias with mixed IPv4 and IPv6 addresses:
Or, no not quite the same. Adding two lists of IPv4 urls works now. But nested aliases still fail.
I guess that I can now use a reasonable work-around by creating a mixed (unnested) alias instead. But it's overflowing the text box, so I don't know how to verify that all addresses are in the alias now. How can I verify that the alias is correct?
Redmine issue created:
https://redmine.pfsense.org/issues/11863
