Bug 12568

Summary: BLUE zone not shown in WUI after configured via setup
Product: IPFire Reporter: Pete 5 <Pete_5>
Component: ---Assignee: Leo H <hofmann>
Status: CLOSED FIXED QA Contact:
Severity: Major Usability    
Priority: Will affect almost no one CC: daniel.weismueller, hofmann, michael.tremer, peter.mueller
Version: 2   
Hardware: unspecified   
OS: Unspecified   

Description Pete 5 2021-01-25 07:11:04 UTC
I wanted to configure the BLUE zone as VLAN on my IPFire running on an APU board with 3 NICs.
The network was configured as "Green + Red + Orange". Therefore I changed the network via the setup routine to "Green + Red + Orange + BLUE", set an IP address for blue, but left the NIC unassigned (just by selecting "IGNORE"). I expected the BLUE zone to show up in "Web Interface/Network/Zone Configuration" to configure its VLAN there, but the BLUE zone didn't show up.
I got the BLUE zone configured by editing the config files "/var/ipfire/ethernet/settings" & "/var/ipfire/ethernet/vlans" as mentioned in the video with Timo Eissler https://wiki.ipfire.org/en/optimization/vlan/start

I observed this behavior on IPFire running as a virtual machine (VirtualBox) as well on my IPFire running on an APU board. Both are running IPFire 2.25 - Core Update 153.
Comment 1 Michael Tremer 2021-01-25 18:14:53 UTC
Hello Pete,

yes, this might actually happen because of some side-effects. It is however not very easy to solve this quickly.

What you can do as a workaround is open /var/ipfire/ethernet/settings and find the "BLUE_DEV=" line. If you change it to something like "BLUE_DEV=blue0" and reload the web UI you should see the blue column.

Could you please test this for me and let me know if it worked?
Comment 2 Michael Tremer 2021-01-25 21:27:57 UTC
Hello Leo,

I take this as you are looking into it? I wasn't aware of it earlier, but it looks like this fits into the last couple of patches that you submitted. Yay :)
Comment 3 Leo H 2021-01-25 22:09:34 UTC
(In reply to Michael Tremer from comment #2)
> Hello Leo,
> 
> I take this as you are looking into it? I wasn't aware of it earlier, but it
> looks like this fits into the last couple of patches that you submitted. Yay
> :)

Hi Michael,

you are right, i will have a look at it :)
I think the new zone functions you merged earlier today already fix this. I just need to submit another patch to make zoneconf.cgi use them.
Comment 4 Michael Tremer 2021-03-16 12:25:13 UTC
Has this already been in c154?
Comment 5 Leo H 2021-03-16 14:24:29 UTC
This is that patch: https://patchwork.ipfire.org/patch/3899/

As far as I know it is planned for core 155
Comment 6 Michael Tremer 2021-03-16 14:47:11 UTC
Yes you are correct. Thank you very much :)