You are not logged in.

Pages: 1

#1 2017-12-26 19:51:10

Burner
Member
Registered: 2017-03-26
Posts: 36

Android wifi hotspot issues

Hi,

I got a lenovo B570. When creating a hotspot with my android phone I'm able to connect the the wifi but I can not access any sites or ping any IPs.
The hotspot itself works, I checked with other devices (Dell laptop also running arch, android phones). Also my local wifi works with the B570.

I don't really know where to start, google got me only unanswered forum posts.

uname -r
4.14.6-1-ARCH
ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether f0:... brd ff:ff:ff:ff:ff:ff
3: wlp2s0b1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether 60:... brd ff:ff:ff:ff:ff:ff
ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.43.169 icmp_seq=1 Destination Host Unreachable
From 192.168.43.169 icmp_seq=2 Destination Host Unreachable
From 192.168.43.169 icmp_seq=3 Destination Host Unreachable
From 192.168.43.169 icmp_seq=4 Destination Host Unreachable
From 192.168.43.169 icmp_seq=5 Destination Host Unreachable
From 192.168.43.169 icmp_seq=6 Destination Host Unreachable
^C
--- 8.8.8.8 ping statistics ---
8 packets transmitted, 0 received, +6 errors, 100% packet loss, time 7098ms
pipe 4
ping google.com
ping: google.com: Der Name oder der Dienst ist nicht bekannt

Offline

#2 2017-12-26 20:50:02

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,722

Re: Android wifi hotspot issues

How are you managing your wifi connections? 
Are you configured for static or dynamic addresses?

A 192.168.43.xx/24 address seems wrong.  What are the output of:
ip addr
ip route
and
iw dev wlp2s0b1 station dump
???

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#3 2017-12-26 21:19:43

Burner
Member
Registered: 2017-03-26
Posts: 36

Re: Android wifi hotspot issues

ewaller wrote:

How are you managing your wifi connections? 
Are you configured for static or dynamic addresses?

A 192.168.43.xx/24 address seems wrong.  What are the output of:
ip addr
ip route
and
iw dev wlp2s0b1 station dump
???

NetworkManager

dynamic addresses

ip addr
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: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether f0:... brd ff:ff:ff:ff:ff:ff
3: wlp2s0b1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 60:... brd ff:ff:ff:ff:ff:ff
    inet 192.168.43.169/24 brd 192.168.43.255 scope global dynamic noprefixroute wlp2s0b1
       valid_lft 3592sec preferred_lft 3592sec
    inet6 fe80::8158:bc23:e855:c8c6/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
ip route
default via 192.168.43.1 dev wlp2s0b1 proto dhcp metric 600 
192.168.43.0/24 dev wlp2s0b1 proto kernel scope link src 192.168.43.169 metric 600
iw dev wlp2s0b1 station dump
Station 00:... (on wlp2s0b1)
	inactive time:	6746 ms
	rx bytes:	58764
	rx packets:	597
	tx bytes:	4007
	tx packets:	39
	tx retries:	0
	tx failed:	0
	beacon loss:	0
	beacon rx:	281
	rx drop misc:	14
	signal:  	-29 dBm
	signal avg:	-31 dBm
	beacon signal avg:	225 dBm
	tx bitrate:	65.0 MBit/s MCS 6 short GI
	rx bitrate:	12.0 MBit/s
	expected throughput:	31.218Mbps
	authorized:	yes
	authenticated:	yes
	associated:	yes
	preamble:	long
	WMM/WME:	yes
	MFP:		no
	TDLS peer:	no
	DTIM period:	2
	beacon interval:100
	short preamble:	yes
	short slot time:yes
	connected time:	28 seconds

The gateway ip seems to be okay, same on the dell as I remember.

Last edited by Burner (2017-12-26 21:40:36)

Offline

#4 2017-12-27 12:49:24

Burner
Member
Registered: 2017-03-26
Posts: 36

Re: Android wifi hotspot issues

More information needed? Any ideas?

Offline

#5 2017-12-27 15:47:00

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,722

Re: Android wifi hotspot issues

No, it all looks rational to me.   How about the phone?  Can you ping its IP?

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#6 2017-12-27 19:07:17

Burner
Member
Registered: 2017-03-26
Posts: 36

Re: Android wifi hotspot issues

ewaller wrote:

No, it all looks rational to me.   How about the phone?  Can you ping its IP?

tried the following on the phone

 ping google.com
PING google.com (172.217.19.78) 56(84) bytes of data.
64 bytes from ham02s17-in-f14.1e100.net (172.217.19.78): icmp_seq=1 ttl=54 time=139 ms
64 bytes from ham02s17-in-f14.1e100.net (172.217.19.78): icmp_seq=2 ttl=54 time=129 ms
ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    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: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
    link/ether 76:... brd ff:ff:ff:ff:ff:ff
    inet6 fe80::74ab:d3ff:fe24:317b/64 scope link
       valid_lft forever preferred_lft forever
3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN group default
    link/sit 0.0.0.0 brd 0.0.0.0
4: rmnet0: <UP,LOWER_UP> mtu 2000 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/[530]
12: rmnet_data0: <UP,LOWER_UP> mtu 1500 qdisc htb state UNKNOWN group default qlen 1000
    link/[530]
    inet 10.49.132.214/30 scope global rmnet_data0
       valid_lft forever preferred_lft forever
    inet6 fe80::2d90:a0fa:2c48:bf82/64 scope link
       valid_lft forever preferred_lft forever
13: rmnet_data1: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/[530]
14: rmnet_data2: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/[530]
15: rmnet_data3: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/[530]
16: rmnet_data4: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/[530]
17: rmnet_data5: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/[530]
18: rmnet_data6: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/[530]
19: rmnet_data7: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/[530]
20: r_rmnet_data0: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/[530]
21: r_rmnet_data1: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/[530]
22: r_rmnet_data2: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/[530]
23: r_rmnet_data3: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/[530]
24: r_rmnet_data4: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/[530]
25: r_rmnet_data5: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/[530]
26: r_rmnet_data6: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/[530]
27: r_rmnet_data7: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/[530]
28: r_rmnet_data8: <> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/[530]
84: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:... brd ff:ff:ff:ff:ff:ff
    inet 192.168.43.1/24 brd 192.168.43.255 scope global wlan0
       valid_lft forever preferred_lft forever
    inet6 fe80::20a:f5ff:fefe:af38/64 scope link
       valid_lft forever preferred_lft forever
ip route
10.49.132.212/30 dev rmnet_data0  proto kernel  scope link  src 10.49.132.214
192.168.43.0/24 dev wlan0  proto kernel  scope link  src 192.168.43.1

pinging the phone results in this

ping 192.168.43.1
PING 192.168.43.1 (192.168.43.1) 56(84) bytes of data.
^C
--- 192.168.43.1 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9115ms

Last edited by Burner (2017-12-27 19:11:26)

Offline

#7 2017-12-28 12:19:36

Burner
Member
Registered: 2017-03-26
Posts: 36

Re: Android wifi hotspot issues

Just tried pinging the laptop from the phone

 ping 192.168.43.169
PING 192.168.43.169 (192.168.43.169) 56(84) bytes of data.
^C
--- 192.168.43.169 ping statistics ---
21 packets transmitted, 0 received, 100% packet loss, time 20007ms

Offline

#8 2017-12-31 08:33:04

Burner
Member
Registered: 2017-03-26
Posts: 36

Re: Android wifi hotspot issues

Anyone got an idea what else I could try?

bumping allowed?

Last edited by Burner (2018-01-09 17:48:06)

Offline

#9 2018-01-10 17:40:26

Burner
Member
Registered: 2017-03-26
Posts: 36

Re: Android wifi hotspot issues

bump

Offline

#10 2018-01-10 19:33:33

blufinney
Member
Registered: 2014-08-26
Posts: 59

Re: Android wifi hotspot issues

*edit - wanted to take my foot out of my mouth long enough to completely retract this statement, as this is indeed a private ip (time for me to dust off the ole ccna textbook, apparently, why was i thinking 192.168 was class c).

To add to the fun, my android native hotspot also provides a "192.168.43" address.  Looking into the android source code the range and gateway ip's seem to be hardcoded.  Unless rooted this part can't be configured incorrectly.

Maybe there is indeed something amiss with the config on the laptop?  Firewall, conflicting network management daemons, a manually added route?



==========================================
RETRACTED STATEMENT:
I agree with ewaller's initial comment - an ip address of "192.168.43.xx/24" is odd for the scenario you're describing in the OP - it's a subnet for public ip addresses.

Any additional info on the hotspot? Things like phone model, android version, hotspot software (built in adroid hotspot or is it a 3rd party hotspot app?).

In general (or as a 100% rule?) hotspots do not give out public ip's to their clients, this will cause issues when communicating to the internet at large.  It would be like trying to purchase alcohol using a fake id that looks nothing like you - denied all day long =P

May want to turn your focus to the hotspot software being used, seems it's not setup properly (didn't know this was even possible with consumer hotspots).

Last edited by blufinney (2018-01-10 20:59:51)

Offline

#11 2018-01-10 20:17:09

lo1
Member
Registered: 2017-09-25
Posts: 584

Re: Android wifi hotspot issues

`ip addr` from my laptop, connected with an android hotspot:

3: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 70:77:81:32:34:bf brd ff:ff:ff:ff:ff:ff
    inet 192.168.43.142/24 brd 192.168.43.255 scope global wlo1
       valid_lft forever preferred_lft forever
    inet6 fe80::7277:81ff:fe32:34bf/64 scope link 
       valid_lft forever preferred_lft forever

For the sake of information, this is normal.

Burner wrote:

bump

Don't.

If you can't ping your gateway after it has provided you an ip address there's something wrong happening with the route: use traceroute and eventually get acquainted with wireshark to understand what's happening.

I think wpa_supplicant may give some hints with the debug option set.

How To Ask Questions The Smart Way && Tacts Filters && K.I.S.S. &&
Rootless Root

Offline

Pages: 1

Board footer

Powered by FluxBB