0 Members and 1 Guest are viewing this topic.
I am afraid i don't understand well what you have said....Do you want to mean that if Kloxo can reboot itself then i don't have to worry about the IOCLT error message?
it look like you use dhcp tru change to static ip # Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+DEVICE=eth0BOOTPROTO=staticIPV6INIT=yesIPV6_AUTOCONF=yesONBOOT=yesIPADDR=987.654.321.987NETMASK=255.255.255.0GATEWAY=987.654.321.1
Quote from: "goblog"it look like you use dhcp tru change to static ip # Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+DEVICE=eth0BOOTPROTO=staticIPV6INIT=yesIPV6_AUTOCONF=yesONBOOT=yesIPADDR=987.654.321.987NETMASK=255.255.255.0GATEWAY=987.654.321.1As @MRatWork have advise early i just change it for static, but it still maintain the error .Thanks for your input
I have tried it now with no success... still have the error.
[root@hostname ~]# service network restartShutting down interface eth0: [ OK ]Shutting down loopback interface: [ OK ]ioctl: Invalid argumentBringing up loopback interface: [ OK ]Bringing up interface eth0: Determining IP information for eth0... done. [ OK ]
Page created in 0.082 seconds with 21 queries.