Siduction Forum

Siduction Forum => Software - Support => Topic started by: jaegermeister on 2015/03/19, 16:52:03

Title: ifconfig and network daemon conflicts
Post by: jaegermeister on 2015/03/19, 16:52:03
Hello,

sometimes it happens that I want to configure eth1 in a special way to make experiments or create ad hoc networks to support other boxes. Usually I issue something like:

ifconfig eth1 10.0.0.1/23

This lasts for a short time (no more than minutes) then some daemon (something like wicd which is not running on this machine, anyway) clears the interface up leaving it without any address. Fiddling with the tray icon and creating a manual profile does not survive cable unplugs and so on.

I arrived to the conclusion that, if I want peace of mind, I have to manually pkill the daemon behind all this.
What is the daemon I got to kill? Maybe NetworkManager?

THX
Title: Re: ifconfig and network daemon conflicts
Post by: bullgard4 on 2015/06/08, 21:30:42
Quote from: jaegermeister on 2015/03/19, 16:52:03This lasts for a short time (no more than minutes) then some daemon (something like wicd which is not running on this machine, anyway) clears the interface up leaving it without any address.
This should reflect in the output of '# journalctl -xb'. Please provide the output of '# journalctl -xb' around that time interval.
Regards
bullgard
Title: Re: ifconfig and network daemon conflicts
Post by: bullgard4 on 2015/06/08, 21:39:55
Quote from: jaegermeister on 2015/03/19, 16:52:03I arrived to the conclusion that, if I want peace of mind, I have to manually pkill the daemon behind all this.
What is the daemon I got to kill? Maybe NetworkManager?
All what you wrote is no prove that you have to pkil a daemon.
What is the output of '~$ sudo journalctl -xb | grep network' ?
Regards,
bullgard
Title: Re: ifconfig and network daemon conflicts
Post by: bullgard4 on 2015/06/08, 21:41:36
Quote from: bullgard4 on 2015/06/08, 21:39:55
Quote from: jaegermeister on 2015/03/19, 16:52:03I arrived to the conclusion that, if I want peace of mind, I have to manually pkill the daemon behind all this.
What is the daemon I got to kill? Maybe NetworkManager?
All what you wrote is no prove that you have to pkil a daemon.
What is the output of '~$ sudo journalctl -xb | grep network' ?
Regards,
bullgard4
Title: Re: ifconfig and network daemon conflicts
Post by: jaegermeister on 2015/06/09, 14:13:03
Hi,

I checked the output of

# journalctl -xb | grep network

and found nothing relevant. For the records,

# pkill NetworkManager

does the job in a very good way.
Thanks
Title: Re: ifconfig and network daemon conflicts
Post by: bullgard4 on 2015/06/09, 15:38:31
The facts that you have delivered are not sufficient so that I could explain the described behavour. I am sorry.
Regards,
bullgard