Page 1 of 1

Can't access via ssh after add ifcfg-eno1:0

Posted: 2020/03/25 11:48:50
by giees7
1) DMZ in router (ZTE MF286) set to enable - 192.168.0.111
2) ifcfg-eno1 set to 192.168.0.111, and gate 192.168.0.1

This works fine, but directadmin don't work "The ip of this machine (192.168.0.111) does not match the ip in the license file". I created ifcfg-eno1:0 with my static IP (this IP is in the license file of directadmin), but then I can't access to server via ssh, and to directadmin via 2222 port. And now the strangest thing - after remove ifcfg-eno1:0 file, suddenly everything works great - ssh and directadmin, but only until reboot. After that everything stops working.

Re: Can't access via ssh after add ifcfg-eno1:0

Posted: 2020/03/25 12:09:36
by TrevorH
And what was the ip you added to the :0 file? Was it in the same subnet as the main ip?

Re: Can't access via ssh after add ifcfg-eno1:0

Posted: 2020/03/25 12:24:26
by giees7
In ifcfg-eno1:0 I added my external IP - 77.91.XX.XXX

Re: Can't access via ssh after add ifcfg-eno1:0

Posted: 2020/03/25 12:54:21
by TrevorH
Yeah, you can't do that if it's in use as your external address. It's a duplicate.

Re: Can't access via ssh after add ifcfg-eno1:0

Posted: 2020/03/27 13:08:47
by jlehtone
giees7 wrote:
2020/03/25 11:48:50
the strangest thing - after remove ifcfg-eno1:0 file, suddenly everything works great - ssh and directadmin, but only until reboot
Did you:
1. add bogus address
2. start directadmin service
3. remove bogus address
4. use directadmin

Sounds like the service checks license on start only.

Can't you update the license of directadmin?


Note on :0
IP-aliases are an obsolete way to manage multiple IP-addresses/masks per interface. Newer tools such as iproute2 support multiple address/prefixes per interface, but aliases are still supported for backwards compatibility.
The "newer tools" ... are almost two decades old by now.

I would not add second address to eth0 either. Not for this.
Perhaps a bridge interface with no legs. Real small subnet on it: 77.91.XX.XXX/32 and definitely no DNS&GW.