interfaces auto up at booting

[Luis_Miguel_Mig]

Hi,

A nic of one of my gateways failed. I replaced it, booted the gateway and I couldn't find the interfaces on it with ifconfig.
I could see them with ethtool, so I brought them up with ifup, I installed the policy etc.

But then I rebooted it again to see if the interfaces this time would go up and the same happened the interfaces of this specific card don't go up after a reboot.

In /var/log/messages I can see clearly:

Configuring interface eth1

Setting eth1 state to Down

I am wondering if there is a a file a command in the gaia to control the behaviour of the interfaces at boot time

I was wondering if there is something equivalent to:
/etc/network/interfaces

auto eth1

[G_W_Albrecht]

What is shown and configured in GAiA WebGUI ? Have all the IFs Enabled checked ?

[Luis_Miguel_Mig]

The ports of this nic are not set to enable actually. I wonder why. Is it not the same that state on in the clish config

I have noticed on this file that ONBOOT is set to YES but BOOTPROTO is DHCP when it is expected to be STATIC.

I don't know how it changed.

cat /etc/sysconfig/network-scripts/ifcfg-eth1
#  
DEVICE=eth1
ONBOOT=yes
BOOTPROTO=dhcp
HWADDR=xxxx

[G_W_Albrecht]

And what happens if you use GAiA WebGUI and enable the IFs there ? Same issue on reboot ?

[Luis_Miguel_Mig]

I haven't tried it yet. It is in production.
I am also wondering why the network-scripts are configured with BOOTPROTO=DHCP when they should be static.
I guess that if I correct it manually next time I boot it, it will be overwritten with DHCP.

it is weird that the interfaces is "state on" in the clish and not enable in the WebGUI

[G_W_Albrecht]

You have to accept that GAiA is different from standard linux - for this reason configuration by WebGUI is best practice, as some linux bash commands can corrupt the configuration ☹️

[Luis_Miguel_Mig]

Thanks Albrecht

Enabling the interface from the webGui resolved the problem.
I still don't understand though how that interface got to that state (disabled in the WebGui and state on in the the clish), a state that survived  reboots.

[G_W_Albrecht]

As i told you before - WebGUI is the preferred tool, as GAiA does some things differently compared to standard linux. Also i can see that you did not use the clish commands from Gaia R81 Administration Guide p.88 but standard linux IF commands.

Example of the correct syntax:

gaia> set interface eth2 ipv4-address 40.40.40.1 subnet-mask
255.255.255.0
gaia> set interface eth2 mtu 1400
gaia> set interface eth2 state on

gaia> set interface eth2 link-speed 100M/full

[Luis_Miguel_Mig]

ìt was configured with "state on" in the clish. 
We only used ifup because we couldn't understand the interface was inactive with "state on" configured in the clish.

Anyway sorted.

[G_W_Albrecht]

Strange - should work both ways.