Child Item

Site Totals

61162 Questions Answered 267 Categories

Bionic Wifi issue

My wifi has been working perfect at work and at home. Used it last Friday at the office and all weekend at work. Today I turned it on, was out of the house before I turned it on so not sure if wifi worked at home.

I come to the office and it connects to wifi I see the wifi icon at the top but it's gray. I can get my work email since I'm inside the LAN network. I can browse out to devices on the network but I can't get WAN connectivity. I've pulled the battery, SIM, cleared all the saved networks and no change. It will not grab outside data at all. If I turn off wifi I get data off 4G no problem.

Nothing has changed for the work wifi. I administrator the network and I have other Android, iOS and laptops all working fine.

I just don't see what would cause the Bionic to do this. My last resort is a reset but would like to see if others have seen this before.

I have 2 AP's at the office I even rebooted one of them just to safe and still no change on the Bionic.

Comments

Arius1

Ok looking further into it seems to be that some Android devices, mostly Motorola can't handle scope routing properly. I redid some things and all is working now. We made a change on Friday for static routes that shouldn't have affected anything but it appears some droids it does.

It's a little annoying since it's not all Android devices and iOS devices handled it fine.

bvanaartsen

Can you elaborate on what you did to fix your issue? I am running into the same issues with my wife's Bionic at home. I have m0n0wall setup for my router and firewall with a Netgear WNDR3700v3 Wireless router acting as an AP. All other devices work just fine on wireless but the Bionic will not route traffic to the outside world.

Arius1

You'd have to layout what your network topology is. We have an MPLS connection for our two offices so that was are default gateway but we switched the gateway to our ASA firewall do to some issues with the MPLS router. Once we did that the scope of the DHCP had issues with some Droids, not all. Apparently this is an issue with the droids so once we took the MPLS route of the DHCP scope so the Droids would connect to the ASA directly it was fine.

Basically from the DHCP scope we had setup the Droids can't route from the MPLS to the ASA, not smart enough to figure it out. Again not all Droids has this, Motorola's did at least Droid Bionic and X's. One Samsung had the issue the other didn't. All the HTC devices we had worked. The iPhone's didn't have any issues either.

bvanaartsen

Its a pretty basic layout. Cable modem - > m0n0wall. m0n0wall -> access point(wireless router in AP mode). Nothing special configured for routing as there shouldn't need to be. The odd thing is if I remove m0n0wall from the picture and use the wireless router as a router, it works fine. I just hate to do that because I have a lot of firewall rules in m0n0wall blocking certain IP blocks from accessing my network.

Crazysane

I know this is a little old, but just to be clear, the IP address of 192.168.20.0/24 that's assigned to usb0 or usb1 on your phone/tablet isn't assigned to your USB port - it seems the LTE linecard is on its own tiny internal network inside the device. Your device's IP on that network is 192.168.20.1 and the linecard appears to always be 192.168.20.2.

I have this same issue with my tablet at my office. If I were Verizon/Moto I would have at least used a high range inside that Class C (say 192.168.20.250/251) in order to avoid conflicts with Wifi gateways, which is the issue I'm running in to. I have control over the corporate network, however; so I'll be moving the offending subnet off of .20.* sometime soon. It would be nice if they would allow us *power users* to adjust this internal network for cases like these (or at least auto-detect the conflict and adjust as needed.)

Hope this helps.

Matt

Child Item