After changing the MAC address and rebooting ipfire the zone configuration page looks very odd. Is this a cosmetic issue?
Before MAC address change
I think there is a wrong entry (double) in /var/ipfire/ethernet/settings
go to setup and remove all nic assignments and reassing it. (or fix the file manually)
1 Like
Assign MAC Address
Has always done this to meā¦
It would be great to be fixedā¦
On updates sometimes my
Network cards would get reassignedā¦
When I was using Orange vlan.
I would have to run setup again to
Fix network card assignment.
My WUI looks like that also.
1 Like
These steps did not resolve the issue
Hi, I just experienced the same thing. I wanted to force a new dynamic IP from my ISP, so I changed the MAC address of RED. After reboots of modem and IPFire, IPFire came up with a new IP address from my ISP (yay) but when I went back to the Zone Configuration page, it is showing no NICs assigned to RED. Everything is obviously working normally. I appears that if a custom MAC is used on RED then the Zone page gets thrown off.
Details:
IFPire appliance has 4 NICs, ending in aa (eth0), ab(eth1), ac(eth2), ad (eth3). GREEN is assigned to ab. I changed the MAC of RED to end in ae.
Now, the NICs are ab(eth0), ac(eth1), ad(eth2), ae(eth3), and the UI is showing āNoneā for all four of them under RED. GREEN is still attached to ab, though now it is eth0. It should be showing āNativeā for ae under RED.
Hey there,
did you check the file ā/var/ipfire/ethernet/settingsā?
You must either update the MAC-entry for your RED ZONE there or via āsetupā in the cli.
Greetings
Alex
2 Likes
Thanks. Iām not sure you got the point that everything is functioning normally.
In the settings file at /var/ipfire/ethernet/settings, RED MAC is still set as aa even though on the Assign-MAC Address page I have it changed to ae and the Zone Configuration page shows it unset.
Isnāt the point of Assign-MAC Address to spoof the RED MAC address? It appears to be working, as it forced the ISP to change my dynamic IP while still showing as aa in the settings file. I am guessing there is another file somewhere in IPFire that maps the spoof. AKA:
00-e0-97-1d-6e-aa = 00-e0-97-1d-6e-ae
The incorrect information showing on Zone Configurations appears to be cosmetic.
Am I incorrect in my assumptions?
Hey there,
I got that and my hint was only to make it look ārightā again. 
Because of the function itself, someone of the devās has to answer this because Iām not that familiar with the configuration.
It seems a bit weird that itās still working because I guess, not only the MAC but also the name has changed (if you changed aa to ae, I guess it changed from eth0 to eth3 as well?).
Maybe somewhere else in the configuration it is hard-linked to the pcibus or somethingā¦ just a guess.
2 Likes
Mine has looked like that for a very long time.
when using Assign MAC-Address.
If there is a fix I donāt Know it.
1 Like
Have not looked at the internals.
But I think the problem is caused by two distinct configurations:
- āAssign MAC addressā does the reconfiguration of the NIC.
- the relation MAC <ā> zone is defined in the settings ( an IPFire file! ) and read from the WUI. The settings file is handled by setup.
To me it seems like a bug. If there is an option to spoof the MAC Address of RED in the WUI, then it should make the Zone Config page look correct if you proceed.
2 Likes