[SOLVED] dhcp name resolving fails when tethering with android phone

luciferHasa · 2018-10-04 15:11:21

Hello
I'm connecting my pc to internet by tethering my android phone via usb,
so this is what happens.
if i tether my phone while arch is booting up i am able to connect to the internet and browse normally
but if i login, and then tether the phone my browser wouldn't connect with any site
i can ping to 8.8.8.8 but cannot ping to www.google.com
so I suppose the problem is with name space resolving
what can I do about this?
Thanks in advance

Last edited by luciferHasa (2018-10-04 20:38:08)

x33a · 2018-10-04 18:05:55

How have you configured the network on your Arch machine?

luciferHasa · 2018-10-04 18:22:11

theres a dnscrypt, dnsmasq, and a dnssec running and the name space resolver is set to 127.0.0.1
if thats what you were asking, if you could be more specific i could paste some output of something

actually what happens is enp0s29f3f7 or whatever the interface i get according to the usb port i connect to doesnt get an ip address as well if tried tethering after i login,

Slithery · 2018-10-04 18:35:28

What's the ouput of...

systemctl list-unit-files --state=enabled

I'm going to guess you have something like dhcpcd running at boot in which case your issue is the expected behaviour, the service runs at boot to get IP addresses for any attached networks. If you connect a new interface you'll need to manually run dhcpcd to get an address for it.

luciferHasa · 2018-10-04 19:01:46

Slithery wrote:

What's the ouput of...
systemctl list-unit-files --state=enabled

[hasanka@lucifer ~]$ sudo systemctl list-unit-files --state=enabled
UNIT FILE                                   STATE  
autovt@.service                             enabled
bluetooth.service                           enabled
clamav-daemon.service                       enabled
clamav-freshclam.service                    enabled
dbus-org.bluez.service                      enabled
dbus-org.freedesktop.network1.service       enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service  enabled
dhcpcd.service                              enabled
display-manager.service                     enabled
dnscrypt-proxy.service                      enabled
dnsmasq.service                             enabled
fail2ban.service                            enabled
getty@.service                              enabled
httpd.service                               enabled
iptables.service                            enabled
lm_sensors.service                          enabled
netctl-wait-online.service                  enabled
netctl.service                              enabled
NetworkManager-dispatcher.service           enabled
NetworkManager-wait-online.service          enabled
NetworkManager.service                      enabled
nmb.service                                 enabled
sddm.service                                enabled
systemd-networkd-wait-online.service        enabled
systemd-networkd.service                    enabled
teamviewerd.service                         enabled
clamav-daemon.socket                        enabled
systemd-networkd.socket                     enabled
remote-fs.target                            enabled

30 unit files listed.

Slithery wrote:

I'm going to guess you have something like dhcpcd running at boot in which case your issue is the expected behaviour, the service runs at boot to get IP addresses for any attached networks. If you connect a new interface you'll need to manually run dhcpcd to get an address for it.

yes.. dhcpcd starts at boot, but,
I tried

dhcpcd -k

and executed dhcpcd again, but still no change,
and restarted network manager, reloaded system daemon,

systemctl restart NetworkManager
systemctl restart httpd.service
systemctl daemon-reload

and still no effect

Last edited by luciferHasa (2018-10-04 19:09:16)

Slithery · 2018-10-04 19:16:55

Read the note...
https://wiki.archlinux.org/index.php/Ne … k_managers

You currently have dhcpcd, netctl, NetworkManager and systemd-networkd all enabled and running - this is bound to cause all sorts of problems. Choose one service to manage your network and disable all the others.

luciferHasa · 2018-10-04 19:27:50

Thank you very much, I think I did enable some services manually while installing something, i was suspecting "tomcat" installation was where something went wrong since i couldn't connect to localhost by typing localhost in address bar but 127.0.0.1 worked instead and thats where i thought it should be name space resolver what's giving me the trouble. I'll disable all except NetworkManager since i happen to have the nm widget running on kde task bar and maybe those two are linked. I'll post the update after i disable them and reboot and try tethering after logging in.

quick question, do I have to disable

systemd-networkd-wait-online.service

along with

systemd-networkd.service

luciferHasa · 2018-10-04 19:29:03

(was that too much typing? lol sorry i just typed what i thought)

luciferHasa · 2018-10-04 19:38:09

Thank you again Slithery,
it worked!!!

systemd-networkd-wait-online.service

was disabled automatically when i disabled

systemd-networkd.service

Slithery · 2018-10-04 19:40:11

luciferHasa wrote:

quick question, do I have to disable
systemd-networkd-wait-online.service
along with
systemd-networkd.service

Nope, it's a dependency of systemd-networkd and will be automatically disabled with it. Read the output when you do this

luciferHasa · 2018-10-04 20:15:22

yes, figured that out 4 others were removed along with it,
thank you again for your help.
it connects normally again

Slithery · 2018-10-04 20:29:12

Great.

Please remember to mark this thread [SOLVED].
CoC - How to post

Arch Linux

#1 2018-10-04 15:11:21

[SOLVED] dhcp name resolving fails when tethering with android phone

#2 2018-10-04 18:05:55

Re: [SOLVED] dhcp name resolving fails when tethering with android phone

#3 2018-10-04 18:22:11

Re: [SOLVED] dhcp name resolving fails when tethering with android phone

#4 2018-10-04 18:35:28

Re: [SOLVED] dhcp name resolving fails when tethering with android phone

#5 2018-10-04 19:01:46

Re: [SOLVED] dhcp name resolving fails when tethering with android phone

#6 2018-10-04 19:16:55

Re: [SOLVED] dhcp name resolving fails when tethering with android phone

#7 2018-10-04 19:27:50

Re: [SOLVED] dhcp name resolving fails when tethering with android phone

#8 2018-10-04 19:29:03

Re: [SOLVED] dhcp name resolving fails when tethering with android phone

#9 2018-10-04 19:38:09

Re: [SOLVED] dhcp name resolving fails when tethering with android phone

#10 2018-10-04 19:40:11

Re: [SOLVED] dhcp name resolving fails when tethering with android phone

#11 2018-10-04 20:15:22

Re: [SOLVED] dhcp name resolving fails when tethering with android phone

#12 2018-10-04 20:29:12

Re: [SOLVED] dhcp name resolving fails when tethering with android phone

Board footer