DietPi-CloudShell IP/MAC missing

[noobs4u]

After the fix for the syntax error the following has happened and does not resolve until the unit is accessed via SSH:

After accessing SSH these 2 screens populate their information. Notice how the name of the Adapter name changes from eth0 to eth1. The IP and MAC also populate.

Once this window is open the info populates

These are the only 2 screens affected. All other screens show info/activity right away. Once I have accessed it (I simply open the SSH command window, that's it) the data continues to update. However if I reboot (or lose power) those 2 screens do not populate correctly upon reboot. I do have PlexMedia Server that auto-starts on this server also. It would be well to note that even watching a movie, those 2 screens will not populate network data. Nor do they populate when accessing an SFTP session and transferring files, which should show something.

Thanks.

[Fourdee]

Hi Erik,

I was unable to replicate this on my XU4+Cloudshell. IP and MAC for STATIC always shows up after a reboot, and being the only enabled scene.

Lets get some more information.

Could you please upload your network config?

Code: Select all

/etc/network/interfaces

Also, reboot system, when data is missing, please paste contents of:

Code: Select all

cat /DietPi/dietpi/.network
ifconfig -a
cat /sys/class/net/eth0/address

[noobs4u]

Hi Erik,

I was unable to replicate this on my XU4+Cloudshell. IP and MAC for STATIC always shows up after a reboot, and being the only enabled scene.

Lets get some more information.

Could you please upload your network config?

Code: Select all

/etc/network/interfaces

Also, reboot system, when data is missing, please paste contents of:

Code: Select all

cat /DietPi/dietpi/.network
ifconfig -a
cat /sys/class/net/eth0/address

Here is the first part of your request:

Code: Select all

#/etc/network/interfaces
#Please use DietPi-Config to modify network settings.

# Local
auto lo
iface lo inet loopback

# Ethernet
allow-hotplug eth1
iface eth1 inet dhcp
metric 0
address 192.168.0.100
netmask 255.255.255.0
gateway 192.168.0.1
#dns-nameservers 8.8.8.8 8.8.4.4

# Wifi
#allow-hotplug wlan0
iface wlan0 inet dhcp
metric 1
address 192.168.0.100
netmask 255.255.255.0
gateway 192.168.0.1
wireless-essid FuzonWifi
wireless-key abcde12345
wireless-mode Managed
wireless-power off
wpa-ssid FuzonWifi
wpa-psk abcde12345
#dns-nameservers 8.8.8.8 8.8.4.4

Unable to do the second part because as soon as I open the command prompt, all the missing data populates. I did it anyway, not sure if it will help.

Code: Select all

root@PlexMedia:~# cat /DietPi/dietpi/.network
1
0
eth1
192.168.1.163
root@PlexMedia:~# ifconfig -a
eth1      Link encap:Ethernet  HWaddr 00:1e:06:30:35:62
          inet addr:192.168.1.163  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::21e:6ff:fe30:3562/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:506 errors:0 dropped:0 overruns:0 frame:0
          TX packets:531 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:183534 (179.2 KiB)  TX bytes:91801 (89.6 KiB)

ip6tnl0   Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          NOARP  MTU:1452  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:441 errors:0 dropped:0 overruns:0 frame:0
          TX packets:441 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:153302 (149.7 KiB)  TX bytes:153302 (149.7 KiB)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@PlexMedia:~# cat /sys/class/net/eth0/address
cat: /sys/class/net/eth0/address: No such file or directory
root@PlexMedia:~#

Thanks.

[Fourdee]

Thanks Erik, very strange

It looks like your running DHCP:

Code: Select all

iface eth1 inet dhcp

I'll run a test tomorrow with DHCP (instead of static) and see if I can replicate the issue.

In the mean time, if your comfortable, could you try setting your eth1 adapter to STATIC. You can do this by running dietpi-config 8 1 . Reboot the system and see if the issue still occurs.

[Fourdee]

Unfortunately, time ran out today and tomorrow has turned into "the day after". Apologies.

I've created a Git ticket for this and will take a look tomorrow: https://github.com/Fourdee/DietPi/issues/359

[Fourdee]

Ok, so even with DHCP, i'am still unable to replicate the missing data. Works everytime, for me at least.

Notice how the name of the Adapter name changes from eth0 to eth1. The IP and MAC also populate.
Unable to do the second part because as soon as I open the command prompt, all the missing data populates.

Very strange.

I'd imagine DietPi is detecting the eth0 device as your default adapter during boot. This data is provided by the kernel, so at this point, eth0 is correct.

I'am not sure why its changing to eth1. Its also strange that the eth0 device is then disappearing from the system. I've seen eth1 on some Odroid boards from our users, but its mostly eth0. Maybe a slight change in network hardware/chip on some boards? not sure.

Either way, lets get dmesg log, might tell us more. Please paste the results:

Code: Select all

dmesg

[Fourdee]

Hi Erik,

I've updated the init code for DietPi-Cloudshell. It will update the DietPi active network adapter file during 1st run. Please can you test it and let me know if the issue reoccurs:

Code: Select all

wget https://github.com/Fourdee/DietPi/raw/78e6960cc98e849bfa04eb6306f295990f5335c9/dietpi/dietpi-cloudshell -O /DietPi/dietpi/dietpi-cloudshell

[noobs4u]

Sorry for the delay in response, been a very crazy week.

It still will not populate any data on these 2 screens unless I SSH. Now it is set to "Static" by default.

v119_dietpi2.JPG (19.9 KiB) Viewed 8054 times

v119_dietpi.JPG (21.83 KiB) Viewed 8054 times

After SSH the the eth0 switches to eth1, the data populates and switches back to DHCP.

v119_dietpi4.JPG (20.44 KiB) Viewed 8054 times

v119_dietpi3.JPG (21.52 KiB) Viewed 8054 times

Note: this is all still happening after a fresh install of dietpi.

[noobs4u]

Ran dietpi-config. Changed the adapter to "static" from "dhcp". Copied the current IP so I wouldn't have to configure one. Rebooted and all the data populated right away. No issues. I did another reboot and even did a cold boot to see if the info would clear and be empty, info still populated like it should. The issue appears to be on the DHCP side.


***Update***
As of today, those 2 screens are still working great. I did another "cold boot" and a separate reboot and the data still populated right away. For DHCP, it's still blank until I initiate an SSH session. I'm leaving it on static as it is not causing any issues.

-Tim

[Fourdee]

***Update***
As of today, those 2 screens are still working great. I did another "cold boot" and a separate reboot and the data still populated right away. For DHCP, it's still blank until I initiate an SSH session. I'm leaving it on static as it is not causing any issues.

-Tim

Thanks for the update Tim.

We've made some core changes to the networking in DietPi v120 which should prevent these missing details. v120 should be released within a week.
If you experience any missing details in v120, please let me know and reopen the ticket if possible: https://github.com/Fourdee/DietPi/issues/359.

Thanks Tim.