Can not connect to wired DHCP network

Rademes · 2018-05-10 18:42

OK, I booted q4os-2.4-x64.r9.iso, and after 10 seconds I already discovered a bug, which really surprised and disappointed me.
In short, Live system completely refused to connect to simple wired DHCP network!

Linux Mint, System rescue CD, Puppy Linux connects without any problems, but Q4OS refuses.... I don`t know, maybe it`s because I have donated only 20$....
Anyway, this bug makes Q4OS unusable for me now...
My new computer:

q4osteam · 2018-05-10 18:56

We are not able to reproduce this, Q4OS can connect fine to a wired DHCP server. So we would guess a hardware dependent issue. We would need to get more info to investigate on this, please provide output of following commands:
$ ip a
$ sudo ifconfig
You could also try to connect using 'nmtui' utility, just run in terminal:
$ nmtui

Rademes · 2018-05-11 18:38

With nmtui no connection too...

q4osteam · 2018-05-11 19:14

The network device looks good, are you using ipv6 or ipv4 dhcp server ?

Please provide systemd debug info, run in terminal:
$ sudo journalctl | gzip > /tmp/journal.gz
and send generated '/tmp/journal.gz' file via e-mail "support@q4os.org" or attach it here to analyze. You can add attachment by 'post reply -> choose file'

Rademes · 2018-05-15 16:39

Sorry for delay, but network suddenly started to work! I don`t know why, I did nothing, just restarted my router. Checked several times, restarted router again, and now network works very well. I think problem solved, sorry for posting...
No, unfortunately it happened again...

Last edited by Rademes (2018-05-17 18:21)

Rademes · 2018-05-17 18:20

It happened again! Again Q4OS 2.4 Live can not connect to wired DHCP network. Router restart did not helped now...
I have IPv4 DHCP server.
Journal attached.

Last edited by Rademes (2018-05-18 09:11)

Attachments:

journal.gz, Size: 17.41 KiB, Downloads: 788

Rademes · 2018-05-20 21:16

Still no success. Rebooting router does not help any-more... Another journal attached.

Attachments:

journal.gz, Size: 17.36 KiB, Downloads: 807

q4osteam · 2018-05-20 23:21

The journal log looks like the dhcp server is not responding to the client's request for dynamic IP. There is no reason available, just like the DHCP server would be offline. We are not able to reproduce such behavior using a standard DHCP server configuration. It would be helpful to attach journal from another system, for ex Mint, that successfully connects, for comparison.

Anyone else noticed similar issue ?

Rademes · 2018-05-21 16:23

Here is Linux Mint 18.3 Xfce journal. Connects successfully every time...

Attachments:

journal.gz, Size: 25.68 KiB, Downloads: 778

q4osteam · 2018-05-22 18:35

We can see from the logs, that Mint uses "dhclient" external utility to get IP address, while Q4OS uses internal network manager dhcp client. That's the difference. We guess, the internal DHCP client could suffer from some kind of a specific bug, that breaks dhcp negotiation with your router. Unfortunately, we are not able to reproduce the issue at the moment. If anyone else noticed similar issue, reporting here would be appreciated. Anyway, we will continue to try reproduce this issue some way, and investigate it as best as possible.

q4osteam · 2018-06-02 16:11

@Rademes
The issue could be fixed within the new Q4OS 2.5 live media just released. A feedback would be appreciated, if you will be trying that.

diyako · 2018-06-02 20:55

I had the similar issue with network connection, however it was my wireless connection. In order to re-connect after a restart I had to reboot my router every time.
I could not find a way to rectify this issue so, unfortunately I left with no choice but to move away from Q4OS and install another linux system that I wouldn't have this issue with.

Dai_trying · 2018-06-02 23:36

I use wireless all the time and haven't had any problems so far (I hope I'm not tempting fate here) but was wondering if you have a 5Ghz router or just 2.4Ghz?

I am currently using a 2.4Ghz model that supports b/g/n but have got a newer one which has both 2.4Ghz and 5Ghz that support a/b/g/n/ac and will be setting it up sometime this week and was wondering if this might cause me some issues. Obviously if I encounter a problem I will post here, but wondered if this could be part of this problem.

Rademes · 2018-07-09 15:33

q4osteam wrote:

@Rademes
The issue could be fixed within the new Q4OS 2.5 live media just released. A feedback would be appreciated, if you will be trying that.

I have tested Q4OS 2.5 recently. Looks like this issue was fixed. I will continue to test.

clive · 2019-06-23 12:32

I believe that I have the same issue using the current stable release Q4OS 2.7 Scorpion. I am a noob so some requests made by mods are difficult to follow. I'm doing my best, please be patient if I appear to be clueless.
For example I tried to follow the instructions above

"Please provide systemd debug info, run in terminal:
$ sudo journalctl | gzip > /tmp/journal.gz
and send generated '/tmp/journal.gz' file via e-mail "support@q4os.org" or attach it here to analyze. You can add attachment by 'post reply -> choose file"

with the result below
clive@q4os-desktop:~$ $ sudo journalctl | gzip > /tmp/journal.gz
bash: $: command not found
clive@q4os-desktop:~$ sudo journalctl | gzip > /tmp/journal.gz
[sudo] password for clive:
clive@q4os-desktop:~$ sudo journalctl | gzip > /tmp/journal.gz
clive@q4os-desktop:~$ journalctl | gzip > /tmp/journal.gz
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.

And later:
clive@q4os-desktop:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
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: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether d0:50:99:71:90:19 brd ff:ff:ff:ff:ff:ff
3: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether d0:50:99:71:90:1b brd ff:ff:ff:ff:ff:ff
inet 192.168.1.10/24 brd 192.168.1.255 scope global dynamic enp0s25
valid_lft 86039sec preferred_lft 86039sec
inet6 fe80::2e3d:949e:e41e:26ec/64 scope link
valid_lft forever preferred_lft forever
clive@q4os-desktop:~$ sudo ifconfig
sudo: ifconfig: command not found
clive@q4os-desktop:~$

I hope info I have been able to supply is useful. Thanks in advance

Dai_trying · 2019-06-23 12:49

The commands should be run without the $ at the beginning which is why it is saying that the command $ is not found. This is used in many forums to denote that the command (sudo journalctl | gzip > /tmp/journal.gz) should be run as normal user, if the line begins with a # it denote the command should be run as root user.
so the actual command should be

sudo journalctl | gzip > /tmp/journal.gz

clive · 2019-06-23 22:59

Dai_trying wrote:

The commands should be run without the $ at the beginning which is why it is saying that the command $ is not found. This is used in many forums to denote that the command (sudo journalctl | gzip > /tmp/journal.gz) should be run as normal user, if the line begins with a # it denote the command should be run as root user.
so the actual command should be
sudo journalctl | gzip > /tmp/journal.gz

Thanks for that. Makes things clearer

clive · 2019-06-23 23:00

Solved. Clean install and use Trinity rather than KDE

Q4OS Forum

#1 2018-05-10 18:42

Can not connect to wired DHCP network

#2 2018-05-10 18:56

Re: Can not connect to wired DHCP network

#3 2018-05-11 18:38

Re: Can not connect to wired DHCP network

#4 2018-05-11 19:14

Re: Can not connect to wired DHCP network

#5 2018-05-15 16:39

Re: Can not connect to wired DHCP network

#6 2018-05-17 18:20

Re: Can not connect to wired DHCP network

#7 2018-05-20 21:16

Re: Can not connect to wired DHCP network

#8 2018-05-20 23:21

Re: Can not connect to wired DHCP network

#9 2018-05-21 16:23

Re: Can not connect to wired DHCP network

#10 2018-05-22 18:35

Re: Can not connect to wired DHCP network

#11 2018-06-02 16:11

Re: Can not connect to wired DHCP network

#12 2018-06-02 20:55

Re: Can not connect to wired DHCP network

#13 2018-06-02 23:36

Re: Can not connect to wired DHCP network

#14 2018-07-09 15:33

Re: Can not connect to wired DHCP network

#15 2019-06-23 12:32

Re: Can not connect to wired DHCP network

#16 2019-06-23 12:49

Re: Can not connect to wired DHCP network

#17 2019-06-23 22:59

Re: Can not connect to wired DHCP network

#18 2019-06-23 23:00

Re: Can not connect to wired DHCP network

Board footer