WAN interface address alias is not working in rules

[stephenw10]

Ah, yes! That was it.
Any chance you did something similar here @Mixka?

[Mixka]

@stephenw10 @johnpoz

Well... As said, I installed pfSense from scratch (did not restored any old config), BUT indeed, I manually changed interface names from config file.

First thing what I did to vanilla config was that I made two WAN ports. WAN1 was named as WAN and WAN2 was named as LAN, so I exported that config and replaced WAN and LAN as WAN1 and WAN2 under interface and restored that back to pfSense. That was only thing what I have done manually to config file. Everything else is made via web GUI.

I did search in config file that is there any other references to these ports, but there was none.

<interfaces>
  <wan1>
    <enable></enable>
    <if>igb0</if>
    <blockpriv></blockpriv>
    <blockbogons></blockbogons>
    <descr><![CDATA[WAN1]]></descr>
    <ipaddr>dhcp</ipaddr>
    ...
  </wan1>
  <wan2>
    <enable></enable>
    <if>igb1</if>
    <blockpriv></blockpriv>
    <blockbogons></blockbogons>
    <descr><![CDATA[WAN2]]></descr>
    <ipaddr>dhcp</ipaddr>
    ...
  </wan2>
</interfaces>

[stephenw10]

Ah, OK, that will do it.

I opened a report to track that issue in the other thread but as I predicted it was rejected because that's not expected to work: https://redmine.pfsense.org/issues/13376
It interesting that it doesn't whilst everything else seems to work fine but the backend interface names in the config should not be changed. The interface description can be changed which is what the GUI displays.

Steve

[Mixka]

@stephenw10

Oh damn... I already have made quite complex setup on top of that. And I think it is beyond fixable. Manually changing now everything back in config file is nightmare.

And yes, description is what most part of pfSense web GUI is showing to user, but for example in VLAN config there is only interface name and tag showing. No description at all.

I expect that is case in somewhere else too. That is why I did change that tag in first place. It would be really missleading to see WAN2 as LAN.

[johnpoz]

@mixka said in WAN interface address alias is not working in rules:

but for example in VLAN config there is only interface name and tag showing. No description at all.

Huh? Not following, once you assign a vlan to can for sure have it show up as different name.

So for example if I add a new vlan, give it a description and then once assigned I can then name that OptX interface whatever you want by editing its description.

[stephenw10]

Mmm, the point of the backend interface tags is that they are independent of the actual NICs and interface 'Names'. That allows you to re-assign or rename an interface and keeps all the same rules etc referencing it.

Now in retrospect it might have been better to use, for example, int0..int1 etc. I believe that was inherited from m0n0wall.
Whilst it's sometimes easier to edit the config directly it's not expected that the average user will ever do that.

Steve

[Mixka]

@johnpoz said in WAN interface address alias is not working in rules:

@mixka said in WAN interface address alias is not working in rules:

but for example in VLAN config there is only interface name and tag showing. No description at all.

Huh? Not following, once you assign a vlan to can for sure have it show up as different name.
...

I can see same "problem" in your screenshots too.

Yes, you can assign as good descriptions you want, but for example when selecting interface for VLAN you can just see name and tag.

I know that it is just visual and does not change how things work, but at least for my OCD brains it hurts a little to select "LAN" interface for WAN connection. Like strange feeling that under the hood something is not "right". At least it is confusing.

Or maybe I am alone with this and just need to book therapist :D

[johnpoz]

@mixka said in WAN interface address alias is not working in rules:

it hurts a little to select "LAN" interface for WAN connection.

I personally would of never used that interface.. Would of just used a different interface. And used lan for something on the lan side of your network.

But you can change the lan description as well.

[Mixka]

@johnpoz said in WAN interface address alias is not working in rules:

I personally would of never used that interface.. Would of just used a different interface. And used lan for something on the lan side of your network.

It is way more convinient that WAN interfaces are next to each others. Or is it possible to change physical interface to interface? I know it is possible in config file, but would it broke something? And is it possible to rearrange interface tags under config file?

@johnpoz said in WAN interface address alias is not working in rules:

But you can change the lan description as well.

As I have done (WAN2), but in VLAN parent interface selection still shows "lan" (and only that).

[stephenw10]

Mmm, that's true it does show the internal interface name there.

That could probably be switched. You could open a feature request if there isn't one already.
https://redmine.pfsense.org/

[johnpoz]

@mixka said in WAN interface address alias is not working in rules:

As I have done (WAN2), but in VLAN parent interface selection still shows "lan" (and only that).

Ah I get what your saying now. Even though I changed my Lan name description, if I go to add a vlan it still shows lan on there.

Yeah that could prob be changed, put in a feature request prob be best option there.

But it doesn't only show that it clearly shows the actual interface does it not, for example mine is igb0

[stephenw10]

https://redmine.pfsense.org/issues/8867

[Mixka]

@johnpoz said in WAN interface address alias is not working in rules:

it clearly shows the actual interface

Yes, but it is not friendly name or something that user can change without breaking something.

Do you guys know would it break something when physical interface name is changed in config file?

<interfaces>
  <wan>
    <if>igb0</if>
    <descr><![CDATA[WAN1]]></descr>
    ...
  </wan>
  <lan>
    <if>igb2</if>
    <descr><![CDATA[LAN]]></descr>
    ...
  </lan>
  <opt1>
    <if>igb1</if>
    <descr><![CDATA[WAN2]]></descr>
    ...
  </opt1>
</interfaces>

And what about re-arrange interface tags?

<interfaces>
  <wan>
    <if>igb0</if>
    <descr><![CDATA[WAN1]]></descr>
    ...
  </wan>
  <opt1>
    <if>igb1</if>
    <descr><![CDATA[WAN2]]></descr>
    ...
  </opt1>
  <lan>
    <if>igb2</if>
    <descr><![CDATA[LAN]]></descr>
    ...
  </lan>
</interfaces>

[stephenw10]

The xml there is identical. The order doesn't matter for assigning the interfaces.

[Mixka]

@stephenw10

Yep. It at least matter that much that order does change in web GUI if I change tags order. Hoping that nothing brokes under the hood :)

[johnpoz]

@mixka if you take a look at the redmine link Steve put up - he changed that to a feature request that would allow for you to edit the friendly name in the gui, and then that would show up in your list of where to put a vlan, etc.

Like what happens with other interfraces - as you saw in my first example.

[stephenw10]

Yes the order they are parsed/returned in determines the order they are displayed but nothing else as far as I know.