How to set network interface manually?

Help
1

The install program was unable to detect my network interface. Curious if there is an available step by step tutorial on how to set it manually.

Thank you!

2

Can you post the output from ip a please?

3 
# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 98:4f:ee:05:50:d2 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.51/24 brd 192.168.1.255 scope global eth0
    inet6 fe80::9a4f:eeff:fe05:50d2/64 scope link
       valid_lft forever preferred_lft forever
4

The UNKONWN state of the eth0 interface is causing an issue. We don't know if the interface is up or down or working. Are you able to execute and ifup eth0 and set the state of the interface?

5

It says its already configured.

ifup eth0
ifup: interface eth0 already configured
6

Okay, try sudo ip link set dev eth0 up and if that doesn't work we'll check to see if we can manually edit the setup varables fle. Which OS and hardware are you running on?

7

ip link set dev eth0 up returns nothing. Another ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 98:4f:ee:05:50:d2 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.51/24 brd 192.168.1.255 scope global eth0
    inet6 fe80::9a4f:eeff:fe05:50d2/64 scope link
       valid_lft forever preferred_lft forever

Linux version 3.8.7 (gcc version 4.7.2 (Debian 4.7.2-5) ) / Intel Galileo Gen 2

8

I'm checking to see if we can support that platform. It appears that the Galileo is using connmanctl for network interface control, which would explain the UNKNOWN status.

What does ifconfig eth0 respond with?

9

Thank you! I appreciate your help.

root@galileo:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 98:4f:ee:05:50:d2
inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::9a4f:eeff:fe05:50d2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17071 errors:0 dropped:0 overruns:0 frame:0
TX packets:6202 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14988719 (14.2 MiB) TX bytes:972407 (949.6 KiB)
Interrupt:40 Base address:0x8000

10

Sure, one thing we do need to check is if connmand has assumed control of the DNS server and DHCP server on the board. Can you check netstat -tulpn and we can see if port 53 is already taken?

11 
root@galileo:~# netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      8645/lighttpd
tcp        0      0 0.0.0.0:53              0.0.0.0:*               LISTEN      8596/dnsmasq
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1821/sshd
tcp6       0      0 :::80                   :::*                    LISTEN      8645/lighttpd
tcp6       0      0 :::53                   :::*                    LISTEN      8596/dnsmasq
tcp6       0      0 :::22                   :::*                    LISTEN      1821/sshd
udp        0      0 0.0.0.0:27178           0.0.0.0:*                           1492/dhclient
udp        0      0 0.0.0.0:53              0.0.0.0:*                           8596/dnsmasq
udp        0      0 0.0.0.0:68              0.0.0.0:*                           1492/dhclient
udp6       0      0 :::11972                :::*                                1492/dhclient
udp6       0      0 :::53                   :::*                                8596/dnsmasq
12

Even if we could get the installer to run, we'd need to disable connman. It has taken over port 53, which is the DNS port, and port 80 for the Admin web interface. It also looks to be running the dhcp processes on its own. These all are needed for the Pi-hole to function. I don't know if there is a way to disable connman, hopefully there is a user that can help pitch in here while I do some research. (The BeagleBone lines use connman but to solve that one, we needed to create a custom OS image.)

13

Thank you Dan Schaper! I appreciate your help. Do you think this can work? Or not worth the trouble? I understand I'm an isolated case and you are busy guys.

14

If we can figure out a way to get rid of connman without breaking everything else, then it's something we can add to the installer code to make it more intelligent. So it may take a bit, but we'll work what we can.

15

---Thank you kindly!

16

After installing the pi-hole connman uses the DNS services and therefore FTLdns fails to start.
I have configured the IP to static and removed the name server and worked charm.

To add static IP address
connmanctl> config ethernet_d0xxxxxx_cable ipv4 manual 192.168.0.10 255.255.255.0 192.168.0.254

To remove nameservers
connmanctl> config ethernet_d0xxxxx_cable nameservers remove