DHCP client problems after upgrade to Chimaera

user9898 · 2021-08-23 09:09:56

Hello community,

I upgraded my Devuan release from Beowolf to Chimaera.
and the DHCP client is having trouble receiving the IP address.
Here is my outpout.

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1504 qdisc mq state UP group default qlen 1000
    link/ether 02:88:04:81:d2:0a brd ff:ff:ff:ff:ff:ff
    inet6 fe80::88:4ff:fe81:d20a/64 scope link 
       valid_lft forever preferred_lft forever
3: lan2@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 02:88:04:81:d2:0a brd ff:ff:ff:ff:ff:ff
4: lan3@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 02:88:04:81:d2:0a brd ff:ff:ff:ff:ff:ff
5: lan4@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 02:88:04:81:d2:0a brd ff:ff:ff:ff:ff:ff
6: wan@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 02:88:04:81:d2:0a brd ff:ff:ff:ff:ff:ff
7: lan1@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 02:88:04:81:d2:0a brd ff:ff:ff:ff:ff:ff
8: wlx3c330047d226: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 3c:33:00:47:d2:26 brd ff:ff:ff:ff:ff:ff
blub@r1-devuan~$ sudo service networking restart
[sudo] Passwort für blub: 
Running /etc/init.d/networking restart is deprecated because it may not re-enable some interfaces ... (warning).
Reconfiguring network interfaces...Killed old client process
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/02:88:04:81:d2:0a
Sending on   LPF/eth0/02:88:04:81:d2:0a
Sending on   Socket/fallback
DHCPRELEASE of 192.168.178.37 on eth0 to 192.168.178.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
dhclient.c:2879: Failed to send 300 byte long packet over fallback interface.
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/02:88:04:81:d2:0a
Sending on   LPF/eth0/02:88:04:81:d2:0a
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
eDHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.
blub@r1-devuan~$ e

Hopefully someone can please help.

Thx,user9898

ralph.ronnquist · 2021-08-23 10:28:10

Is there a cable on eth0?

please post your /etc/network/interfaces

user9898 · 2021-08-23 10:55:40

Yes, there is a cable pluged-in.

cat interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
# This is an autoconfigured IPv6 interface
iface eth0 inet6 auto
blub@r1-devuan/etc/network$

Head_on_a_Stick · 2021-08-23 11:05:27

Have you tried removing the IPv6 configuration? Do you need IPv6?

Do static addresses work? My old router used to "run out" of DHCP slots so perhaps check that as well.

ralph.ronnquist · 2021-08-23 11:53:52

I think you should comment out that second eth0 configuration; if you need both ipv4 and ipv6 you'll need to combine them into a single configuration block, e.g. with "up" statements dealing with ipv6.

Do you have files in /etc/network/interfaces.d/ ? Where do the vlan adapters come from .. or what they are? Eg wan@eth0

EDIT: it looks like some kind of "openwrt" setup; could you post /etc/config/network if you have one?

user9898 · 2021-08-24 15:10:19

Head_on_a_Stick wrote:

Have you tried removing the IPv6 configuration? Do you need IPv6?
I did not try to remove the IPv6, but I no problem removing it.
Since I can always add it back to the system.
Do static addresses work? My old router used to "run out" of DHCP slots so perhaps check that as well.

I usually tell my router to use DHCP and on top of that I tell it to, to always issue the same IPs to the devices, otherwise all of port-forward settings would end up in a major mess.

user9898 · 2021-08-24 15:18:20

ralph.ronnquist wrote:

I think you should comment out that second eth0 configuration; if you need both ipv4 and ipv6 you'll need to combine them into a single configuration block, e.g. with "up" statements dealing with ipv6.
Do you have files in /etc/network/interfaces.d/ ? Where do the vlan adapters come from .. or what they are? Eg wan@eth0
EDIT: it looks like some kind of "openwrt" setup; could you post /etc/config/network if you have one?

No, I do not have any files in /etc/network/interfaces.d/
I changed to the configurating to this.

cat interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
#iface eth0 inet dhcp
iface eth0 inet static
address 192.168.178.37
netmask 255.255.255.0
gateway 192.168.178.1

tuxd3v · 2021-08-27 13:49:03

helo user9898,
Does you managed to succeed getting dhcp leases?
for what I understand you have a r1, it has a switch embedded

Does you have more than eth0 interfaces like wan, etc?

user9898 · 2021-08-27 14:27:25

Hello tuxd3v and community,
I am dealing with two parts of one problem here.
First is the RTC which is set to 1970 once the board boots up.
I am currently looking for ways to set it up manually and to store the time information in such a way that the RTC will be set to the correct time after a reboot.
Once the RTC problem is resolved the board should be able to receive IP Addresses via DHCP.

The second problem is the missing realtek driver.
Since the board, in it current state, can not communicative to the web, it therefore can not download any firmware updates.
Nor with a dynamic IP address or with a manually set one

One solution could be to download the driver it manually as a .deb file.
The problem here is that I do not know on which server and path to look for it.

Another solution could be to built the package myself,with debuild.
Her another problem would be the architecture.
Since I am not very experienced with debuild.

Thx,user9898

tuxd3v · 2021-08-27 18:31:54

hello user9898,

How have you done the upgrade from beowulf to chimaera?
It should have been there the drivers for the hardware, if you were previously in beowulf..

What is your hardware board?
Maybe you can set WIFI, if you have the driver for it( its also realtek ), and you need non-free in sources.list.

For the RTC, you need to have a daemon running the 'ntp' package does that, and it starts on boot, but if you don´t have Ethernet or WIFI it will not update
'ntp' package depends on:

# apt-cache depends ntp
ntp
  Depends: adduser
  Depends: lsb-base
  Depends: netbase
  Depends: tzdata
  Depends: libc6
  Depends: libcap2
  Depends: libedit2
  Depends: libopts25
  Depends: libssl1.1

It could be that you have 'ntpdate' package installed?
if you have you can do a:

ntpdate 0.pool.ntp.org

For the firmware 'firmware-realtek', doesn´t depend on nothing else, not even on the Architecture you are running, its just firmware to be loaded by the network device.. so you can grab him

This is the Initial page for the packages: https://www.devuan.org/os/packages

I am assuming that you are using armhf, right?

For Chimaera, I believe you want this:
https://pkginfo.devuan.org/cgi-bin/pack … 20210315-3

Click to download in " Filename: pool/DEBIAN/non-free/f/firmware-nonfree/firmware-realtek_20210315-3_all.deb"

Then on the board as root:

dpkg -i /path/to/firmware-realtek_20210315-3_all.deb
sync
reboot

Last edited by tuxd3v (2021-08-27 18:50:08)

user9898 · 2021-08-28 16:24:57

Hello tuxd3v

How have you done the upgrade from beowulf to chimaera?

I upgraded to to chimaera by editing the sources.list.
to so

  GNU nano 5.4                           /etc/apt/sources.list                                     
# deb http://deb.devuan.org/merged beowulf main

deb http://deb.devuan.org/merged chimaera main
deb-src http://deb.devuan.org/merged chimaera main

deb http://deb.devuan.org/merged chimaera-security main
deb-src http://deb.devuan.org/merged chimaera-security main

# beowulf-updates, previously known as 'volatile'
deb http://deb.devuan.org/merged chimaera-updates main
deb-src http://deb.devuan.org/merged chimaera-updates main

What is your hardware board?

The name of the board is a Lamobo R1 by Leemaker

https://linux-sunxi.org/Lamobo_R1

Some source's also call it BPI-R1 http://www.banana-pi.org/r1.html

I finally managed to establish some connectivity by using one of my old USB Nic interfaces, luckly I found one with a none Realtek chip.
Next I created a udev rule to give this new interface a custom name for better control over it.

From there I kept missing add a extra entry into the interface file.
eg let's say I gave the new interface the name of 'eth-x' I than forgot to add a extra line for eth-x.

iface eth-x inet dhcp

Once I added that line, the service networking restart, finally picked the new interface up and included it in the DHCP process.

Also thank you for the hint about

 main non-free contrib

I was actually missing that enty.
I added it like so

deb http://deb.devuan.org/merged beowulf main non-free contrib

Hopefully that is correct for Chimaera? Or should it say instead of Beowolf or Chimaera ?

Last edited by user9898 (2021-08-29 06:55:54)

tuxd3v · 2021-08-28 18:48:31

hello user9898,

For what I understand you have done it right..
Editing the sources.list and substituting 'beowulf' by 'chimaera' and doing:

apt-get update
apt-get dist-upgrade

Maybe the problem was that you didn´t had 'non-free' in the sources.list..

For Chimaera, the sources.list, with 'contrib' and 'non-free' is

deb http://deb.devuan.org/merged chimaera main non-free contrib

ho, I found this online, which suggests that all RJ45 ports are connected to the Switch( BCM 53125 ):
4+1 ports 10/100/1000 Ethernet RJ45 (BCM 53125)

I believe the kernel driver for that switch is the b53, and I found some Documentation for it:
https://www.kernel.org/doc/html/latest/ … a/b53.html

I don´t have this board..

user9898 · 2021-09-02 08:31:38

Thx alot for the link, about the switching interface. I take look at it once I have the time for it.

Right now, there are two last items of iritation left, concerning the 'non-free contrib' entry in my sources lists.

if my source-list file looks like this

 1 deb http://deb.devuan.org/merged chimaera main
 2 #deb-src http://deb.devuan.org/merged chimaera main
 3
 4 deb http://deb.devuan.org/merged chimaera-security main
 5 #deb-src http://deb.devuan.org/merged chimaera-security main
 6
 7 # beowulf-updates, previously known as 'volatile'
 8 deb http://deb.devuan.org/merged chimaera-updates main
 9 #deb-src http://deb.devuan.org/merged chimaera-updates main
10
11 deb http://deb.devuan.org/merged chimaera main non-free contrib
12

apt complains to me like so:

13 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Target Packages (main/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Translations (main/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Translations (main/i18n/Translation-de_DE) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Translations (main/i18n/Translation-de) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Packages (main/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Translations (main/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Translations (main/i18n/Translation-de_DE) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11
W: Target Translations (main/i18n/Translation-de) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list:11

I therefore disabled the first entry in line 1.

Hope that is correct.

The second one is, if it should say beowolf or chimaera in the last line.

tuxd3v · 2021-09-02 18:58:01

hello user9898,

yeah you have 2 lines for the same thing, so you will receive warnings about that
If you upgraded to Chimaera, its 'chimaera' that you should have there..

For now, since Chimaera was not yet released as stable,
You should pick only one entry, comment the others:

#deb http://deb.devuan.org/merged chimaera-security main
#deb-src http://deb.devuan.org/merged chimaera-security main
 
#deb http://deb.devuan.org/merged chimaera-updates main
#deb-src http://deb.devuan.org/merged chimaera-updates main

deb http://deb.devuan.org/merged chimaera main non-free contrib

so 'deb http://deb.devuan.org/merged chimaera main non-free contrib' is the line you want

After Chimaera release as stable,
'chimaera-security' and 'chimaera-updates' will also be available, until then, its only one line that you will need

The officially official Devuan Forum!

#1 2021-08-23 09:09:56

DHCP client problems after upgrade to Chimaera

#2 2021-08-23 10:28:10

Re: DHCP client problems after upgrade to Chimaera

#3 2021-08-23 10:55:40

Re: DHCP client problems after upgrade to Chimaera

#4 2021-08-23 11:05:27

Re: DHCP client problems after upgrade to Chimaera

#5 2021-08-23 11:53:52

Re: DHCP client problems after upgrade to Chimaera

#6 2021-08-24 15:10:19

Re: DHCP client problems after upgrade to Chimaera

#7 2021-08-24 15:18:20

Re: DHCP client problems after upgrade to Chimaera

#8 2021-08-27 13:49:03

Re: DHCP client problems after upgrade to Chimaera

#9 2021-08-27 14:27:25

Re: DHCP client problems after upgrade to Chimaera

#10 2021-08-27 18:31:54

Re: DHCP client problems after upgrade to Chimaera

#11 2021-08-28 16:24:57

Re: DHCP client problems after upgrade to Chimaera

#12 2021-08-28 18:48:31

Re: DHCP client problems after upgrade to Chimaera

#13 2021-09-02 08:31:38

Re: DHCP client problems after upgrade to Chimaera

#14 2021-09-02 18:58:01

Re: DHCP client problems after upgrade to Chimaera

Board footer