Is it possible to change an alias dynamically?

Tobi

@johnpoz said in Is it possible to change an alias dynamically?:

are you doing anything with captive portal settings?

No newer

johnpoz

@tobi so for whatever reason lan3 net is not populated.. Hmmmm??? That would for sure explain why it doesn't work.

edit: Wonder if maybe the IPv6 isn't working and that causing a problem.. Could you try turning off the IPv6 on this interface and then looking at the rules when set to Lan3 net.

Tobi

@johnpoz said in Is it possible to change an alias dynamically?:

That would for sure explain why it doesn't work.

I think so but I have absolut no idea whats going wrong here :(

johnpoz

@tobi see my edit - maybe try it with ipv6 turned off on the interface.

Tobi

@johnpoz said in Is it possible to change an alias dynamically?:

Wonder if maybe the IPv6 isn't working and that causing a problem..

IPv6 is working very well.

I can chack what happens if I disable "track" WAN Interface for IPv6 for this interface

johnpoz

@tobi yeah just grasping at straws on why when you pick lan3 net that says no source defined.

Tobi

@johnpoz said in Is it possible to change an alias dynamically?:

maybe try it with ipv6 turned off on the interface.

This chances nothing

# source address is empty.  label "USER_RULE: Ping"
# source address is empty.  label "USER_RULE: Ping"

Tobi

@johnpoz said in Is it possible to change an alias dynamically?:

yeah just grasping at straws on why when you pick lan3 net that says no source defined.

Yes it's true but this happens with each interface/ LanX Net I'm trying. Not only lan3

And If I try to modiify the Rule

Ping from Yellow_Network to LAN4 Net then in in rules.debug I see "destination address is empty"

stephenw10

Hmm... well that's extremely odd!

This is in pfSense 2.6?

Are you using any of the System Aliases (LANx Net) in any firewall rules successfully?

Do you see the 'system aliases' section in the rules.debug file?
Is LAN3 referencing the correct interface?
I expect both those to be true because the traffic is being blocked correctly still.

Try adding the v4 and v6 rules as separate lines in the config.
The scripts create then as separate rules line anyway but it could be trying to validate the LANx net alias as both v4 and v6 at the same time and failing both somehow.

Steve

Tobi

@stephenw10 said in Is it possible to change an alias dynamically?:

This is in pfSense 2.6?

Yes

@stephenw10 said in Is it possible to change an alias dynamically?:

Are you using any of the System Aliases (LANx Net) in any firewall rules successfully?

No.

@stephenw10 said in Is it possible to change an alias dynamically?:

Do you see the 'system aliases' section in the rules.debug file?

#System aliases

loopback = "{ lo0 }"
WAN = "{ pppoe0 }"
LAN0 = "{ igb1 }"
LAN1 = "{ igb2 }"
LAN2 = "{ igb3 }"
LAN3 = "{ igb4 }"
LAN4 = "{ igb3.150 }"
LAN5 = "{ igb3.250 }"
LAN6 = "{ igb3.20 }"
LAN7 = "{ igb2.30 }"
LAN8 = "{ igb2.40 }"
LAN9 = "{ igb2.50 }"
OpenVPN = "{ openvpn }"

@stephenw10 said in Is it possible to change an alias dynamically?:

Try adding the v4 and v6 rules as separate lines in the config.

Yesterday I tryed to disable ipv6 from this interface and create also a new rule only for IPv4 - nothing changes

Tobi

The only thing with system alias works here is my WAN Interface. I can create rule with "WAN Net" oder "WAN Address" and this works, but no other interfaces.