Project

General

Profile

Still requires ifdown eth0 / ifup eth0 (DHCP)

Added by Daniel Paley over 6 years ago

I'm still having trouble with the dns services. I've narrowed it down to two items:
1). at boot I still need to log into the machine and run ifdown eth0; ifup eth0
2). or sometime a restart of the avahi-daemon.services (systemctl start avahi-daemon.service) will also work

what am I doing wrong? seems that I've configured things correctly - and I've check around to see 'what else' could be causing the trouble. The mityDSP board just
sometime come up with out any issue (getting a dhcp IP correctly and registering on the DNS without issue) and at other times it cannot get either a DNS entry or even an IP address.
I've played with host to set this correctly. I've played with /lib/systemd/system/avahi-daemon.service and networking.service to no real solution.

Is there a requirement to have something additional to the networking.service file (such as a Before)?


Replies (4)

RE: Still requires ifdown eth0 / ifup eth0 (DHCP) - Added by Bob Duke over 6 years ago

Hello Dan,

Are you using a custom filesystem or an example filesystem from our MDK? Are you running with the MityDSP-L138 module in our development board or from your own baseboard?

Could you post the contents of your networking.service file, as well as the contents of /etc/network/networking?

Thanks,

-Bob

RE: Still requires ifdown eth0 / ifup eth0 (DHCP) - Added by Daniel Paley over 6 years ago

I believe that I'm using the 'released' version of hte file system (MDK).

root@mityT1-dev:/lib/systemd/system# more networking.service

[Unit]
Description=Networking
Before= display-manager.service app.service
After=dev-tty1.device

[Service]
ExecStart=-/etc/init.d/networking start

Type=oneshot

[Install]
WantedBy=multi-user.target
root@mityT1-dev:/lib/systemd/system#

There is not directory /et/networking - enclosed is the interfaces from from /etc/network/interfaces.

  1. /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
  1. The loopback interface
    auto lo
    iface lo inet loopback
  1. Wireless interfaces
    iface wlan0 inet dhcp
    wireless_mode managed
    wireless_essid any
    wpa-driver wext
    wpa-conf /etc/wpa_supplicant.conf

iface atml0 inet dhcp

  1. Wired or wireless interfaces
    auto eth0
    iface eth0 inet dhcp
    hostname mityT1-dev # set to my host name

iface eth1 inet dhcp

  1. Ethernet/RNDIS gadget (g_ether)
  2. ... or on host side, usbnet and random hwaddr
    iface usb0 inet static
    address 192.168.7.2
    netmask 255.255.255.0
    network 192.168.7.0
    gateway 192.168.7.1
  1. Bluetooth networking
    iface bnep0 inet dhcp

RE: Still requires ifdown eth0 / ifup eth0 (DHCP) - Added by Daniel Paley over 6 years ago

Sorry - files formated above, enclosed below
--Daniel

sample1.txt View (1.07 KB)

RE: Still requires ifdown eth0 / ifup eth0 (DHCP) - Added by Daniel Paley over 6 years ago

adding a bit more information:

seems that I'm not getting dbus.service or avahi-daemon.service starting automatically.  systemctl reports:
avahi-daemon.service loaded inactive dead Avahi mDNS/DNS-SD Stack
dbus.service loaded inactive dead D-Bus System Message Bus

non-working log included.

what - systemctl list-units -a (51.6 KB)

    (1-4/4)
    Add picture from clipboard (Maximum size: 500 MB)