[News]

News: Welcome to GLomation peer support forum

[mmenti]

mmenti

mmenti

Show mmenti's last posts.

Show general stats for mmenti.

• 
• Super Hero
• Posts: 20

Hi

After a power loss, the network if doesn't seem to come up again:

"Setting up networking....
Configuring network interfaces...ifup: interface lo already configured
ifup: interface eth0 already configured"

After that, eth0 won't be available. After a second reboot, eth0 comes up again.

I was guessing that removing the file /etc/network/run/iftstate at bootup will fix that - but no luck. Any ideas?

Best regards,

Marco

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

ifdown eth0 and then ifup eth0 should always get network restarted.

[mmenti]

mmenti

mmenti

Show mmenti's last posts.

Show general stats for mmenti.

• 
• Super Hero
• Posts: 20

ifdown eth0 and then ifup eth0 should always get network restarted.

This guess this works (calling udhcpc helps also) - but we're planning to have at least hundreds of boards running in unattended devices - so I need an "automatism" which cleans up at startup...

Best regards

Marco

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

The factory installed file system is Emdebian which uses a lot Debian start up scripts.  For embedded use some of the scripts may have to be changed.  The network can be startup by calling DHCP client directly without the ifup or ifdown and avoid any state variable that is used by the network script.

[mmenti]

mmenti

mmenti

Show mmenti's last posts.

Show general stats for mmenti.

• 
• Super Hero
• Posts: 20

I did it the simple (and maybe a bit dirty) way: I changed /etc/init.d/networking and added "ifdown -a || true". Now, the interfaces come even up after an unclean shutdown.