Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #185589 > unrolled thread

Static IP not working ("connmand" problem)?

Back to article view | Back to linux.debian.user

Contents

  Static IP not working ("connmand" problem)? Steffen Dettmer <steffen.dettmer@gmail.com> - 2017-08-20 20:00 +0200
    Re: Static IP not working ("connmand" problem)? Sven Hartge <sven@svenhartge.de> - 2017-08-20 20:20 +0200
      Re: Static IP not working ("connmand" problem)? Steffen Dettmer <steffen.dettmer@gmail.com> - 2017-08-20 21:00 +0200
      Re: Static IP not working ("connmand" problem)? Steffen Dettmer <steffen.dettmer@gmail.com> - 2017-08-22 15:10 +0200
        Re: Static IP not working ("connmand" problem)? Sven Hartge <sven@svenhartge.de> - 2017-08-22 17:10 +0200
    Re: Static IP not working ("connmand" problem)? Glenn English <ghe2001@gmail.com> - 2017-08-20 20:30 +0200

#185589 — Static IP not working ("connmand" problem)?

Hi,

in short:
How to configure static IP? network/interfaces as in [1] seem not to
work because of a "connmand".

in detail:
I had a failure of my DHCP server and was unable to connect to my
statically configured Debian 8 server. Or at least I intended to
configure static IP. The setup is very simple, just one Ethernet NIC,
static IP and static routing. However I failed to configure it
unfortunately.

According to [1] I configured a "iface eth0 inet static" stanza with
"address 192.168.9.24" etc in /etc/network/interfaces[2] and I though
I would be done, but this seems not work for me.

After fixing DHCP server I checked /var/log/syslog and found during
the fail time:

  Aug 20 18:42:03 lia connmand[1444]: eth0 {del} address
169.254.141.65/16 label eth0
  Aug 20 18:42:03 lia connmand[1444]: eth0 {del} route 169.254.0.0 gw
0.0.0.0 scope 253 <LINK>

and after fixing DHCP entries change to:

  Aug 20 19:21:24 lia connmand[1444]: eth0 {add} address
192.168.9.24/24 label eth0 family 2
  Aug 20 19:21:24 lia connmand[1444]: eth0 {add} route 192.168.9.0 gw
0.0.0.0 scope 253 <LINK>

but as said, I have to use static IPs for servers of course (namely to
be safe for DHCP failures).

Except a non helping man page, I found no documentation about
"connmand" (using google). I'm pretty sure that I did a standard
server installation and did not install network manager things
manually, so I have no clue why I have this package installed at all.
Also I found none of the documented configuration files on disk, but
there is e.g. /etc/init/connman.conf.

I hope someone can answer my questions:

How do I configure a static IP to my server?

Where do I find the log messages about DHCP? I'm used to see DHCP
server IP, max lease time etc.

What is "connmand", where can I learn more about it, and why is it
installed at all? Can I / should I simply "apt-get purge" it?

Is the documentation [1] the wrong place to look? If not, should I
update it according to the replies to my questions?

"dpkg -i connman" tells "Intel Connection Manager daemon" and points
to "https://connman.net", but there I get ERR_CONNECTION_REFUSED.  Is
this an official debian package at all? Google search seem to suggest
Ubuntu packages only. I hope I didn't somehow to manage to install
Ubuntu packages and messed up something...

Any background info (documentation links) that helps me to understand
what happens would be highly appreciated!

Steffen



[1] https://wiki.debian.org/NetworkConfiguration#Configuring_the_interface_manually
[2] /etc/network/interfaces:
allow-hotplug eth0
iface eth0 inet static
  address 192.168.9.24
  netmask 255.255.255.0
  gateway 192.168.9.30

[toc] | [next] | [standalone]

#185592

Steffen Dettmer <steffen.dettmer@gmail.com> wrote:

> How to configure static IP? network/interfaces as in [1] seem not to
> work because of a "connmand".

connmand? The package "connman" is not contained in the default
installation of Debian.

> What is "connmand", where can I learn more about it, and why is it
> installed at all? Can I / should I simply "apt-get purge" it?

You can remove it. You will then see which package depends on it. From
the dependencies I can see it may be pulled in via "lxqt" via the "cmst"
package.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

[toc] | [prev] | [next] | [standalone]

#185596

On Sun, Aug 20, 2017 at 8:09 PM, Sven Hartge <sven@svenhartge.de> wrote:
>> How to configure static IP? network/interfaces as in [1] seem not to
>> work because of a "connmand".
>
> connmand? The package "connman" is not contained in the default
> installation of Debian.
>
>> What is "connmand", where can I learn more about it, and why is it
>> installed at all? Can I / should I simply "apt-get purge" it?
>
> You can remove it. You will then see which package depends on it. From
> the dependencies I can see it may be pulled in via "lxqt" via the "cmst"
> package.

There were no dependencies shown. So I removed it.

Now the server is unreachable :-(

Steffen

[toc] | [prev] | [next] | [standalone]

#185704

Hi,

On Sun, Aug 20, 2017 at 8:09 PM, Sven Hartge <sven@svenhartge.de> wrote:
>> How to configure static IP? network/interfaces as in [1] seem not to
>> work because of a "connmand".
>
> connmand? The package "connman" is not contained in the default
> installation of Debian.

Thank you for your help. Just to report my final result, after
removing the package and rebooting the system, it seems to work fine!
I didn't made a test with unavailable DHCP yet but I think it will
pass, logs look better now.

So what I think what had been left open:
- how came the package onto this system?
- the Wiki documentation of network config is imprecise / incomplete
As I did not fully understand the issue, I think I better not update the Wiki.

Steffen

[toc] | [prev] | [next] | [standalone]

#185715

Steffen Dettmer <steffen.dettmer@gmail.com> wrote:
> On Sun, Aug 20, 2017 at 8:09 PM, Sven Hartge <sven@svenhartge.de> wrote:

>>> How to configure static IP? network/interfaces as in [1] seem not to
>>> work because of a "connmand".
>>
>> connmand? The package "connman" is not contained in the default
>> installation of Debian.

> So what I think what had been left open:
> - how came the package onto this system?

/var/log/dpkg.log* might tell you. Also /var/log/apt/{history,term}.log*
may be of interest.

S°

-- 
Sigmentation fault. Core dumped.

[toc] | [prev] | [next] | [standalone]

#185594

On Sun, Aug 20, 2017 at 5:55 PM, Steffen Dettmer  safe for DHCP failures).

> [1] https://wiki.debian.org/NetworkConfiguration#Configuring_the_interface_manually
> [2] /etc/network/interfaces:
> allow-hotplug eth0
> iface eth0 inet static
>   address 192.168.9.24
>   netmask 255.255.255.0
>   gateway 192.168.9.30

Mine for a 2 interface machine on 216.17.134.200/29 and a Comcast cable net:


auto lo eth0 eth1

# The loopback network interface
iface lo inet loopback
    allow-hotplug eth0

# The primary network interface
iface eth0 inet static
    address 216.17.134.205
    netmask 255.255.255.248
    broadcast 216.17.134.207
    network 216.17.134.200
    gateway 216.17.134.201

# Comcast
iface eth1 inet dhcp


(There may be some redundant info in there, but it works.)

Then reboot (or restart networking). Then look at 'ifconfig' or 'ip
addr' to verify that they're there.

--
Glenn English

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web