Is it possible to change an alias dynamically?
-
@bob-dig As I understand it, he's trying to create firewall rules for an IPv6 subnet that changes. I was thinking the "Net" interfaces would update with the new IPv6 subnet, though (sorry) I haven't tried that.
Ryan @rcoleman-netgate do you know at what point the "Net" interface definition updates if the assigned IPv6 changes? Is it not instant?
@Tobi Do you need to know the IPv6 subnet at the point of doing the rules? I mean, can you not just allow or block IPv6 on that interface? Or are you trying to allow one subnet but block another IPv6 subnet routed through it? Also your example was IPv4, though I'd have expected that to work based on your rule. The rule did allow something because it shows 350 bytes.
Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
Upvote 👍 helpful posts! -
@steveits said in Is it possible to change an alias dynamically?:
I was thinking the "Net" interfaces would update with the new IPv6 subnet, though (sorry) I haven't tried that.
They do or there is no IPv6 connectivity at all.
-
@bob-dig said in Is it possible to change an alias dynamically?:
They do or there is no IPv6 connectivity at all.
Here is a ICMP response with my "Yellow_Network" Alias
"ping www.google.com
Ping wird ausgeführt für www.google.com [2a00:1450:4001:82a::2004] mit 32 Bytes Daten:
Antwort von 2a00:1450:4001:82a::2004: Zeit=7ms
Antwort von 2a00:1450:4001:82a::2004: Zeit=8ms
Antwort von 2a00:1450:4001:82a::2004: Zeit=7ms
Antwort von 2a00:1450:4001:82a::2004: Zeit=7ms" -
@steveits said in Is it possible to change an alias dynamically?:
The rule did allow something because it shows 350 bytes.
Yes, because with the alias (Yellow_network ) ping works, both ipv4 and ipv6
-
@tobi Show us what is not working and what you are trying in great detail.
-
@bob-dig -
I'm trying simple ping (ICMP)with "lan3 net"
it will not work. All packages are block.
same rule but with my alias "Yellow_Network" all works great.
-
@bob-dig said in Is it possible to change an alias dynamically?:
@steveits said in Is it possible to change an alias dynamically?:
I was thinking the "Net" interfaces would update with the new IPv6 subnet, though (sorry) I haven't tried that.
They do or there is no IPv6 connectivity at all.
OK well when you write it out like that... :) That's why I suggested LAN3 Net but he's saying it doesn't work, which doesn't make a lot of sense to me.
@Tobi are you sure it's not another rule blocking it? If you click the red X on the log line you'll get a popup like:
"The rule that triggered this action is:
@58(0) block drop in log quick on igb1 from bogonsv6:132925 to any label "block bogon IPv6 networks from WAN" ridentifier 11002" -
@steveits - This rule is not blocking the trafic. But pfSense don't see the source as part of "Lan3 net" -what is not true
LAN3 192.168.4.10/24. My source is 192.168.4.15And blocking rule is at the end
Red X means:
"Die Regel, die diese Aktion ausgelöst hat, ist:
@480(0) block drop in log quick on igb4 inet from <Yellow_Network:2> to any label "USER_RULE: Deny LAN3" ridentifier 1631830970"
" -
@tobi So, it sounds like you have a separate "Deny LAN3" rule that is blocking the pings.
-
@steveits No. I have many rules they allows things and at the end on each interface I have "Deny Rule for ALL"
-
@tobi said in Is it possible to change an alias dynamically?:
I have "Deny Rule for ALL"
There really is no reason for a deny rule at the end - default is deny. So unless you want to say not log anything you don't allow (default is to log).. There isn't really a reason to add specific block at the end.. Unless you wanted to make it a reject maybe for your local devices so they get a icmp notice that rejected and can save your clients some time doing retrans, etc.
-
@johnpoz said in Is it possible to change an alias dynamically?:
There really is no reason for a deny rule at the end
Maybe you are right. But the point is :
with Yellow_Network Alias is my Pinng "going" through this rule:
And if I change "Yellow_Network" to lan3 then my ping is not goint through this rule and is blocked at the end. And this is my problem not my rule at end.
And this because pfSense don't see that my source ip 192.168.4.15 is part of LAN3 network -
@tobi said in Is it possible to change an alias dynamically?:
that my source ip 192.168.4.15 is part of LAN3 network
Well is it, what is listed on your Lan3 interface? You sure you didn't maybe make it a /32 - I believe it can default to /32 when you set the IP.
-
@johnpoz - thank you very much for your time!
my definition is correct
But from Docs I'm not sure if this can work because:
"Interface Net
An entry in this list is present for each interface on the firewall. These macros specify the subnet for that interface exactly, including any IP alias VIP subnets that differ from the defined interface subnet."
So this don't mean each IP address from this Network -
@tobi said in Is it possible to change an alias dynamically?:
So this don't mean each IP address from this Network
huh? Sure it does, along with any vip networks you might have setup on it.
The lan 3 net on that interface should be 192.168.4.0/24 so yeah your 192.168.4.15 - you sure you didn't use lan3 address vs net?
For your source?
You have that rule going to some queue? Maybe that is being problematic?
-
@johnpoz said in Is it possible to change an alias dynamically?:
you sure you didn't use lan3 address vs net?
Yes I am sure. See my screenshots above
@johnpoz said in Is it possible to change an alias dynamically?:
You have that rule going to some queue?
I have no queues for any rules
-
@tobi said in Is it possible to change an alias dynamically?:
I have no queues for any rules
My bad "nicht gesetzt" hehehe = none or not set, etc. Doh!
BTW always better to show the full rules list vs 1 rule, since depending you could have some odd rules that trigger before rule that allows, etc.
And your floating is empty?
-
@johnpoz said in Is it possible to change an alias dynamically?:
And your floating is empty?
Yes
@johnpoz said in Is it possible to change an alias dynamically?:
always better to show the full rules list
The only thing I change in the last rule you see here is from Yellow_Network to lan3 network
The same thing I have with all interfaces and all rules if I change from Alias to laX Network :(
-
@tobi well that first rule is pointless - when you enable dhcp on an interface, hidden rules are created that allow dhcp to work.
So if you if your lan3 interface is 192.168.4.10/24 and your saying if you change the source to lan3 net no rules work?
That makes no sense - all of my interfaces use X net as the source.. The only way for that to be a problem is if the X network built in aliases are not populating.
Off the top I am not sure how to actually look at that table - let me look into that.. @stephenw10 or @Derelict might be able to help us validate if X networks are actually populated or what might be not working so they are not populated.
So floating rules are empty - are you doing anything with captive portal settings?
So look at your rules when set as yellow_network alias with
cat /tmp/rules.debug
And then look at rules after you change to X network, does it not list the cidr range?
example here is my lan rule
pass in quick on $LAN inet from 192.168.9.0/24 to any ridentifier 0100000101 keep state label "USER_RULE: Default allow LAN to any rule" label "id:0100000101"Here are rules on a different interface
If I look in rules I see specific with the cidr range from dmz network as source.
pass in quick on $DMZ inet from 192.168.3.0/24 to any ridentifier 1512830140 keep state label "USER_RULE" label "id:1512830140"Here is the specific rule that allows icmp echoreq from my dmz net to dmz address
pass in quick on $DMZ inet proto icmp from 192.168.3.0/24 to 192.168.3.253 icmp-type echoreq ridentifier 1513193472 keep state label "USER_RULE" label "id:1513193472" -
@johnpoz said in Is it possible to change an alias dynamically?:
lan3 interface is 192.168.4.10/24 and your saying if you change the source to lan3 net no rules work?
That makes no senseYes he is and I agree it doesn't make sense. :) Also his OP asked about IPv6 but the examples are IPv4. Not that that's a problem (other than it not working) but the IPv4 subnet would not normally change over time...possibly ever.
@Tobi are you creating these rules ON the LAN3 interface? So the rule with the source of LAN3 Net is on LAN3 not another interface? Your example above was on LAN9 but that could be just what you screen captured. (a rule on LAN9 with a source of LAN3 Net isn't going to match because packets will never arrive on LAN9 from that).
