I did successfully upgrade from an ALIX-board (i586) to an APU2-board (x64) with options backup/restore (works great!). However, on boot I observe these messages on serial console:
Setting hostname to *xxx*.localdomain... [ OK ]
Setting up firewall
iptables v1.8.5 (legacy): Invalid MAC address specified.
Try `iptables -h' or 'iptables --help' for more information.
iptables v1.8.5 (legacy): Invalid MAC address specified.
NIT: Entering runlevel: 3ables --help' for more information.
Are there somewhere references to the old mac adresses left over (where to search?) or can these iptables messages savely be ignored? Device runs fine so far and does its job.
PS: Every 15 minutes I also see this message from Addon wio in /var/log/messages:
Yes, I did and also read comments in collectd script why /etc/sysconfig/lm_sensors is rebuild as an empty file. But I will double check /var/log/rrd tomorrow, maybe I have overseen that.
As you have changed your hardware then the mac address for your red connection to your ISP will also have changed. Could the message about the invalid mac address be related to that. Some ISP’s record a mac address and that is then permanent. If that is the case with your ISP then you can change your red mac address in the Network - Assign MAC Address to the one you used to have.
This is a bit of a guess on my part, having never seen that error message in my system.
I just updated successfully to Core Update 169 and watched booting on serial console. Still these strange messages occur:
Setting hostname to xxx.localdomain... [ OK ]
Setting up firewall
iptables v1.8.8 (legacy): Invalid MAC address specified.
Try `iptables -h' or 'iptables --help' for more information.
iptables v1.8.8 (legacy): Invalid MAC address specified.
Try `iptables -h' or 'iptables --help' for more information.
iptables v1.8.8 (legacy): Invalid MAC address specified.
Try `iptables -h' or 'iptables --help' for more information.
iptables v1.8.8 (legacy): Invalid MAC address specified.
Try `iptables -h' or 'iptables --help' for more information.
As I do not think it is related somehow to our ISP, where do I find corresponding logfiles to get an idea what’s going on… I do more suspect some ancient and obsolete setting somewhere.
The start of this thread mentioned a change of hardware from an ALIX-board (i586) to an APU2-board (x64). Did you have some firewall rules set up with mac addresses that were changed with the change of hardware?
/var/log/messages - Nothing relevant found.
/etc/sysconfig/firewall.local - Nothing added in there. Firewall → Firewall Rules? Nothing special, only port 443 of one server in GREEN
Yes, that is my guess, too. But how to find and correct them? Anyway, the box works fine and the wrong iptable statements do not disturb as they are discarded.
firewall rules configured through the web interface are stored in CSV files in /var/ipfire/firewall/ on an IPFire installation. Given the screenshot you posted, these files should be rather brief, not containing any MAC address whatsoever.
Just to be sure: Could you check them for any dangling MAC address?
No, there is a list of activated coupons with single valid MAC addresses. In that list I found the ones with no related MAC address dating 1.1.1970. I do not know how these entries got there, maybe some conversion issue dating years back.
