Assigning VLAN to WAN - changing ISP

[nightcom]

Hello everyone,

I'm in middle of changing my ISP and new provider requires to use VLAN's on certian services, like internet on VLAN300. I already did everything and it seems to work fine but I'm not sure does it's done correctly - I have doubts.

I would like to ask you for advice, correction or approval of present configuration.

What I did?
I created VLAN in Interfaces -> Other types -> VLAN




Then I went to Interfaces -> Assignments
and I assign VLAN300 to WAN, replacing present igc0 (WAN) with vlan2 (tag300) and it looks like this:


as you can see in + Assign a new interface now it's still igc0 interface that I can assign somwhere or create new interface, is it normal?

Now when I go to Interfaces -> Overview I see something like this:

My Wieguard stoped working but I think it's just a matter of reconfig but I doubt does rest of config, assigning VLAN to WAN, correct?

What I wanted to do is reverse everything and try to do it from CLI and just to reconfig WAN (igc0). Second idea was to edit my backup and hoping to find line with VLAN in port igc0 and add to it VLAN 300 and restore backup. Do I overthink and everything is fine with this config? I'm not a master of networking but WAN as loopback I don't think it should be like that.

Can community verify this and correct me if needed?

Thank you in advance


Edit: I have Zenarmor, Suricata, Unbound, ID and Wireguard services running on it also. Looks like everything is working, beside Wireguard like I wrote and I checked configs but I didn't found anything unusual or that something needs to be changed - maybe I miss something but my main question is still about assigning VLAN to WAN.

[dseven]

The VLAN configuration looks good to me. Not sure what you mean by "WAN as a loopback"?

[nightcom]

It was my mistake, I didn't notice that there was one more tab and I was thinking that WAN is now in loopback what was strange to me. I already corrected screenshot and my question.

I'm now more wondering can I remove this "unassigned port igc0" from list....my Wireguard is not working what I also don't understand since all rules are refering to interfaces and not physical ports in OPNsense....but I will look into it tomorrow.

Thanks for your confirmation!

[dseven]

You can just leave igc0 unassigned. You probably could assign it if you want, but don't try to configure IP on it. You can't delete it - it's a physical NIC device, so it won't go away.

[nightcom]

Yes that's what I was thinking also, just wanted confirmation. Thank you once again and I hope I will not need to create tomorrow new topic about Wireguard I already removed all settings related to it and will build from sratch tomorrow.

Do you know should I also assign somewhere VLAN in Wireguard? I will Google tomorrow anyway.

Thanks!

[dseven]

I don't think that Wireguard should care about your WAN connection being on a VLAN interface, but I imagine your public IP changed? Maybe you have that "hard-coded" somewhere? Not knowing how you're using Wireguard (server for remote access to your LAN? As a client to some VPN service? etc), it's harder to guess what might be wrong