Quote from: boxalex on February 20, 2018, 10:33:41 AM

Ok, here i'am again.

I described my problem on the first page of this topic allready.

What happened meanwhile with my Giant X10.

Bought a new orange pi, mounted it with a new fleash including

auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static

and the Baikal worked perfectly for some days now and a sudden back to the old problem.

Means. I can not login into the web interface anymore.
After one restart the baikal worked at least on my pools. Now after another shutdown the Baikal
made i even have no more access to it.

Strange thing is that after mounting the new orange pi he got the ip .117 assigned, while he former
was on .112. I thought now big deal, important he works, but after the shut down he is back to .112
now and as said allready, i again can not login anymore.

What could cause that behaviour? Only this Baikal is making problems, others work all perfectly.

The Routher has a static IP, after that there is a 24 port Cisco 2950 switch where the Ants and Baikals are connected.
I really have no more idea what to try. Strange thing is that with the new orange pi it worked perfectly for some days
and now back to old problem?!?! Huh

Any advice or help what to try??

Login to Baikal Terminal from Web Interface and then try to assign your static address. But first make sure there are no other devices already using .117. For example:

Baikal Login: baikal
Password: baikal
ifconfig
sudo ifconfig eth0 192.168.1.117 netmask 255.255.255.0
ifconfig
reboot

Then reserve .117 for your Baikal via your Router Admin interface.