Installation of Exagear desktop seems to break dhcp

Installation of Exagear desktop seems to break dhcp

Postby rookieone » Wed Aug 16, 2017 12:30 pm

Hi,

I've experienced the following now more than once (meaning, after reinstalling Exagear), so I was wondering if anyone else is experincing this or if this is a known bug, and if there's a known workaround :)

As host I am using:

Description: Ubuntu 16.04.3 LTS

The version of Exagear I am using on my Pinebook:

http://downloads.eltechs.com/exagear-desktop-v-2-1/exagear-desktop-armv8.tar.gz


The issue:

DHCP for the host is no longer working after the installation of Exagear.
Connection to the WIFI AP seems eastablished but is dropped again after no IP is assigned.
Setting a static IP works, after which a normal connection to the WIFI AP is established (and Internet connectivity works norally).
The same problem happens connecting to a different WIFI AP (setting static IP there also makes it work).
On another sdcard booting another linux without Exagear, the problem is not there
The problems seem to start after installing Exagear

syslog shows i.e.:

Code: Select all
Aug 13 20:16:12 localhost NetworkManager[653]: <warn>  [1502648172.7823] dhcp4 (wlan0): request timed out
Aug 13 20:16:12 localhost NetworkManager[653]: <info>  [1502648172.7825] dhcp4 (wlan0): state changed unknown -> timeout
Aug 13 20:16:12 localhost NetworkManager[653]: <info>  [1502648172.9064] dhcp4 (wlan0): canceled DHCP transaction, DHCP client pid 1420
Aug 13 20:16:12 localhost NetworkManager[653]: <info>  [1502648172.9067] dhcp4 (wlan0): state changed timeout -> done
Aug 13 20:16:12 localhost NetworkManager[653]: <info>  [1502648172.9094] device (wlan0): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Aug 13 20:16:12 localhost NetworkManager[653]: <info>  [1502648172.9105] manager: NetworkManager state is now DISCONNECTED
Aug 13 20:16:12 localhost NetworkManager[653]: <warn>  [1502648172.9138] device (wlan0): Activation: failed for conneer ction 'my-ssid-removed'
Aug 13 20:16:12 localhost NetworkManager[653]: <info>  [1502648172.9199] device (wlan0): state change: failed -> disconnected (reason 'none') [120 30 0]

Aug 13 20:16:12 localhost NetworkManager[653]: <warn>  [1502648172.9875] sup-iface[0x7387a0,wlan0]: connection disconnected (reason -3)
Aug 13 20:16:12 localhost NetworkManager[653]: <info>  [1502648172.9882] device (wlan0): supplicant interface state: completed -> disconnected
Aug 13 20:16:12 localhost NetworkManager[653]: <info>  [1502648172.9905] policy: auto-activating connection 'my-ssid-removed'
Aug 13 20:16:13 localhost NetworkManager[653]: <info>  [1502648173.0157] device (wlan0): Activation: starting connection 'my-ssid-removed' (ebd749d7-3846-46e5-a19b-014735157c
ff)
Aug 13 20:16:13 localhost NetworkManager[653]: <info>  [1502648173.0206] device (wlan0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Aug 13 20:16:13 localhost NetworkManager[653]: <info>  [1502648173.0214] manager: NetworkManager state is now CONNECTING
Aug 13 20:16:13 localhost NetworkManager[653]: <info>  [1502648173.0267] device (wlan0): state change: prepare -> config (reason 'none') [40 50 0]
Aug 13 20:16:13 localhost NetworkManager[653]: <info>  [1502648173.0282] device (wlan0): Activation: (wifi) access point 'my-ssid-removed' has security, but secrets are requi
red.
Aug 13 20:16:13 localhost NetworkManager[653]: <info>  [1502648173.0296] device (wlan0): state change: config -> need-auth (reason 'none') [50 60 0]


Aug 13 20:16:18 localhost wpa_supplicant[927]: wlan0: WPA: Key negotiation completed with ma:ca:dd:re:ss:01 [PTK=CCMP GTK=CCMP]

Aug 13 20:16:18 localhost NetworkManager[653]: <info>  [1502648178.5220] device (wlan0): supplicant interface state: 4-way handshake -> completed

Aug 13 20:16:18 localhost wpa_supplicant[927]: wlan0: CTRL-EVENT-CONNECTED - Connection to ma:ca:dd:re:ss:01 completed [id=0 id_str=]

Aug 13 20:16:18 localhost NetworkManager[653]: <info>  [1502648178.5222] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'rijeranslo'.
Aug 13 20:16:18 localhost NetworkManager[653]: <info>  [1502648178.5225] device (wlan0): state change: config -> ip-config (reason 'none') [50 70 0]
Aug 13 20:16:18 localhost NetworkManager[653]: <info>  [1502648178.5247] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Aug 13 20:16:18 localhost NetworkManager[653]: <info>  [1502648178.5503] dhcp4 (wlan0): dhclient started with pid 1597
Aug 13 20:16:18 localhost NetworkManager[653]: <warn>  [1502648178.5518] device (wlan0): The kernel does not support extended IFA_FLAGS needed by NM for IPv6 private addresses. This feature is not available

Aug 13 20:16:18 localhost kernel: [   99.142670] type=1400 audit(1502648178.571:16): apparmor="DENIED" operation="sendmsg" profile="/sbin/dhclient" name="/run/systemd/journal/dev-log" pid=1597 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Aug 13 20:16:18 localhost kernel: [   99.180605] type=1400 audit(1502648178.611:17): apparmor="DENIED" operation="exec" profile="/sbin/dhclient" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=1598 comm="dhclient" requested_mask="x" denied_mask="x" fsuid=0 ouid=0
Aug 13 20:16:18 localhost kernel: [   99.181050] type=1400 audit(1502648178.611:18): apparmor="DENIED" operation="sendmsg" profile="/sbin/dhclient" name="/run/systemd/journal/dev-log" pid=1598 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Aug 13 20:16:18 localhost kernel: [   99.247278] type=1400 audit(1502648178.681:19): apparmor="DENIED" operation="sendmsg" profile="/sbin/dhclient" name="/run/systemd/journal/dev-log" pid=1597 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Aug 13 20:16:18 localhost kernel: [   99.270190] type=1400 audit(1502648178.701:20): apparmor="DENIED" operation="sendmsg" profile="/sbin/dhclient" name="/run/systemd/journal/dev-log" pid=1597 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Aug 13 20:16:18 localhost kernel: [   99.277532] type=1400 audit(1502648178.711:21): apparmor="DENIED" operation="exec" profile="/sbin/dhclient" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=1599 comm="dhclient" requested_mask="x" denied_mask="x" fsuid=0 ouid=0
Aug 13 20:16:18 localhost kernel: [   99.278610] type=1400 audit(1502648178.711:22): apparmor="DENIED" operation="sendmsg" profile="/sbin/dhclient" name="/run/systemd/journal/dev-log" pid=1599 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Aug 13 20:16:18 localhost kernel: [   99.546106] type=1400 audit(1502648178.981:23): apparmor="DENIED" operation="sendmsg" profile="/sbin/dhclient" name="/run/systemd/journal/dev-log" pid=1597 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

Aug 13 20:16:19 localhost kernel: [  100.493265] RTL871X: recv eapol packet
rookieone
 
Posts: 2
Joined: Sat Sep 10, 2016 2:37 pm

Re: Installation of Exagear desktop seems to break dhcp

Postby rookieone » Mon Sep 04, 2017 12:05 am

No one else experiencing this dhcp problem after installing Exagear?
rookieone
 
Posts: 2
Joined: Sat Sep 10, 2016 2:37 pm

Re: Installation of Exagear desktop seems to break dhcp

Postby BrianWalker » Wed Sep 06, 2017 5:27 am

ExaGear Desktop is restrictive programming. Along these lines, you need to buy a permit here to utilize ExaGear Desktop. For the most part, enactment of ExaGear happens naturally and you don't need to do any unique activity. In any case, sometimes, initiation may come up short and beneath the depiction how you can settle it. Writing Services By Assignment Empire
BrianWalker
 
Posts: 1
Joined: Wed Sep 06, 2017 5:19 am

Re: Installation of Exagear desktop seems to break dhcp

Postby penguinjeff » Thu Sep 14, 2017 10:47 am

I'm wondering if some networking tool in the guest os is trying to configure the network interface at the same time. Make sure that NetworkManager is disabled in the guest os.
penguinjeff
 
Posts: 8
Joined: Thu Sep 14, 2017 7:56 am

Re: Installation of Exagear desktop seems to break dhcp

Postby RehmaanMalik » Thu Jan 11, 2018 10:09 pm

The ExaGear Desktop Trial is currently available for Raspberry Pi and Odroid devices and is kept on Raspberry Pi and Odroid repositories respectively. To set up your ExaGear Desktop and get the trial license you need to do the following steps: Open the command line; Input two simple commands.
Hope this will help.
Web Developer @ Carmetc ( Mobile App Development Company )
Ui Developer @ RailsCarma & Carmatec
RehmaanMalik
 
Posts: 1
Joined: Thu Jan 11, 2018 10:02 pm


Return to ExaGear Desktop

Who is online

Users browsing this forum: No registered users and 2 guests

cron