Manual mapping of ETHnn names to hardware interfaces

Forums Network Management ZeroShell Manual mapping of ETHnn names to hardware interfaces

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #65478

    I recently added a 4 port ethernet card to my ZS box and wanted to remove the 2 port card that was there previously. ETH00 is the motherboard ethernet port. ETH01 and ETH02 were on the 2 port card. Now that I have added the 4 port card, I had hoped that ETH01 and ETH02 would simply migrate to the new card and add ETH03 and ETH04. What actually happened is that ETH01 and ETH02 were retained, but marked as removed. The new card is now ETH03 – ETH06.

    This is frustrating! I have complex rules throughout the system that by necessity include ETH01 and ETH02 (and their VLANs). For now, I have put the system back the way it was while I look for a solution. I don’t want to have to hand craft an entirely new configuration changing the ETH numbers throughout.

    Is there a mapping somewhere that associates ETH numbers with the underlying hardware interfaces that could be edited to reflect my new configuration? If not, perhaps this is a feature request that this mapping be added to the GUI somewhere in the Setup section so that the mapping can be applied manually.

    Does anyone have other thoughts on this?


    Easiest way I can think of:

    Zeroshell hardware data like this is part of the underlying Linux, NOT the database you create with all your settings.

    Backup or copy your Database off to external storage, I.e. not the same SD card or USB device as the Zeroshell install.

    Swap your hardware, then REINSTALL Zeroshell. This will reassign the ETHxx interfaces. Make sure when you are in the demo database, that the interfaces show up the way you want.

    Restore your database or plug in the external USB that has your database on it. Then go to Storage and “activate” the database. This will reboot Zeroshell to use your saved rules and settings.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.