Database Users

Captivate & 802.1x

I've had the captivate about 24 hours now and dig it. I've rooted it and remove the att bloatware (per titanium backup), I've also performed a backup using Rom Manager.
I'm having trouble getting it up and running on an enterprise wireless what uses 802.1x PEAP authentication. I can get through all the auth. steps, and the device is assigned an IP, but I am unable to do anything that requires an internet connection; browser, market, etc.
Has anyone else ran into this issue?
*****EDIT*****
sigh i just realized that this is in the wrong area, it should have been over in development...i'm an idiot

I had a similar problem on a WEP-encrypted network, which I fixed by setting a static IP on the phone and then setting it back to DHCP (the correct setting). However, your problem could be entirely different than mine (not that I even am sure what my problem was, just that I fixed it!)
Best of luck!

Having the same problem on enterprise access points regardless of encryption. Home wifi netwroks work great (open and WPA2). Enterprise APs (open and WEP) connect and give me an IP, but will not transfer data. Think its a driver issue with the Wifi, it happens on every captivate ive tested, and seems to be more widespread than the GPS issue.

I have had the same issue with my work at work. I can get it to connect and get a ip but can not pass any data.
Sent from my SAMSUNG-SGH-I897 using XDA App

Had the same problem at work. Luckily I'm an admin and figured mine out. Our monowall portal was the issue. I can give a detailed answer for my problem tomorrow when I get to work.
I actually had the cap wiped to go back, then I literally figured out the problem. Thanks go out to my team mate for helping me talk through this.
Sent from my SAMSUNG-SGH-I897 using XDA App

can't wait to hear what your fix was!
Sent from my SAMSUNG-SGH-I897 using XDA App

This sounds more like your network not being allowing your device rather then the device having an issue.

it's been frustrating as I know two other guys with android devices that didn't have an issue. one is a droid eris running 2.1 and the other is a nexus one running 2.2.
Sent from my SAMSUNG-SGH-I897 using XDA App

designgears said:
This sounds more like your network not being allowing your device rather then the device having an issue.
Click to expand...
Click to collapse
Worked closely with my highly experienced network admin in my dept. for an afternoon (we had some time to kill). He checked the firewall and dhcp servers, ran packet traces, etc.
With what I'm experiencing, its the device. These wifi networks we use with Cisco APs are completely wide-open. All other phones and mobile devices have always worked great for years. We rely on this network for many custom applications and mobile tools.
Once the dhcp server leases an address, it seems like the radio stack hangs, and the device ceases communication. Here's an older thread on the exact issue over at androidfouroms: http://androidforums.com/samsung-captivate/130403-wifi-terrible.html
I have tested multiple new unmodified captivates and the issue is identical accross the board.

Now that I am at work, and have coffee in me and not beer, I will go through the problem I had with miCap and works wireless. Due to my skeptical ways, I will be semi vague for security purposes. On with it.
When I originally got miCap (pet name for it) I was able to access our public wifi. It allowed me into the public portal to agree to terms. I played a little bit on it, but wanted to see if I could access our private wifi. I got in the private no problem. But after that I never was able to get back on to our public. It did the same thing as I've read. It got an ip no problem (via dhcp) and acted like all was well. No browser, or ap could get a connection. The phone would not switch over to 3g to get info.
Armed with ip and mac address, my co-worker and I started to did through our monowall. ( He also has a cap that had no issues on public or private). We try tried reserving the ip for miCap, didn't work. We tried static ip, didn't work. I spent the morning completely wiping miCap to get it back to return worthy.
This was when I decided on last ditch effort.
Our ap's are cisco's that connect into monowall. I got into monowall and dug around. I found that with in the captive portal (how fitting) that the ip/mac associated with my phone hadn't checked in for 8 days. Even though I tried everyday. I deleted the entry to the phone there and suddenly my phone was getting access again.
Now I understand that this may not help everyone, because setups vary from place to place. But digging deeper into configurations at the access points may be what is needed. Do I think the phone had nothing to do with it? No, I think it helped aggravate the problem.
We have had problems with the Intel 3945abg chipsets with the same exact setup. That problem was fixed with driver updates on the laptops.
sorry for the long winded reply.

So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.

Pmac25 said:
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Click to expand...
Click to collapse
Essentially yes. But it is not listed like that in the portal. Hmmm. I wonder about the combo of dhcp/dns being the culprit.

I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network

I sent a help ticket into samsung; maybe if enough folks do we can get it on their radar.

jhannaman82 said:
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
Click to expand...
Click to collapse
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.

phlunkie said:
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
Click to expand...
Click to collapse
Thanks for that, i figured the menu was built in somewhere just never found it.
:thumbsup:

UPDATE
So I flashed the i9000 Eclair rom last night, and when I got into work today I can connect and use the wifi here. So looks like something AT&T buggered up, big surprise there, when they "customized" the captivate.

As much as I normally love blaming AT&T for problems, that can't be done here. My Captivate (running Stock Firmware) connects just fine to my work network. We use 802.1x with PEAP/MSCHAPv2 for authentication.

Anyone been able to connect at over 802.11b speeds while connected to an 802.1x network? I show connections at G and N speeds on my WPA2 network but nothing over 11Mbps on 802.1x.
Sent from my SAMSUNG-SGH-I897 using XDA App

Hi,
I am also having problems with my work wifi network.
It is 802.1x, on TTLS/PAP it also requires a thawte premium server ca certificate insalled.
Is there any way to connect this kind of networks?
With my previous iphone 3g it was taking only 4-5 seconds.

Internet issues with Android devices at school

Hi,
Just got a shiny new Galaxy Note 10.1 last weekend. Yesterday, after receiving my case and keyboard from Amazon, I brought it in to school to start taking advantage of the S-Pen for note taking in classes that keyboards don't quite cut it in. Unfortunately, it revived an issue that I had and ignored on my HTC Rezound from last year... an issue that a WiFi device can't ignore, and unfortunately my phone's battery is not up to using CM10's tether function all day (and it might start running down my monthly data being used 5 days a week, all day).
So, any ideas what might cause this issue? The school primarily has Macs, and my Windows 8 Laptop sometimes has issues, but at least half the time it works fine. It is just Android devices that will not work. They connect, and get great signal strength, but just won't get any actual data. To my knowledge, nobody has ever gotten an Android device to connect. My Rezound is running an unofficial CM10 (4.1 JB) version, and my Note is using whatever the newest official update is (4.1 as well, I believe. Non-rooted). I don't know a whole lot about this type of stuff, but I'm not afraid to tinker around to try and get it working. I've tried a few other suggestions from numerous Google searches, but to no avail so far. The network is unprotected, and run by the school's IT people, so needless to say I have no way to easily change settings for the campus' network. I'd prefer not root the Note just yet, but if I need to, so be it. Any ideas what this might be?
Thanks

Some more Info
Coffeeist said:
[Original Post]
Click to expand...
Click to collapse
Some more info:
I cannot ping the tablet from my laptop (I get no packet loss, but all return 'Destination Host Unreachable'.
Same result if I try pinging my laptop or the router from my tablet using Terminal Emulator.
Sometimes, if set to DHCP, the tablet will give an 'Authentication Error Occured' error (or similar, I don't recall the actual wording). Sometimes it indicates a connection, but just won't work. I've never had a problem connecting using the same info as my laptop (with the IP changed, of course), but again, no internet, no ping.
Thanks

May or may not be the problem, but from what I've noticed, school networks tend to have a lot of blocked ports. I know the main Google Sync Framework uses port 5228. Try shooting an email to a network admin in your school's IT dept, asking about that port or just in general if they're aware that Android devices are unable to connect on their network.

Coffeeist said:
Some more info:
I cannot ping the tablet from my laptop (I get no packet loss, but all return 'Destination Host Unreachable'.
Same result if I try pinging my laptop or the router from my tablet using Terminal Emulator.
Sometimes, if set to DHCP, the tablet will give an 'Authentication Error Occured' error (or similar, I don't recall the actual wording). Sometimes it indicates a connection, but just won't work. I've never had a problem connecting using the same info as my laptop (with the IP changed, of course), but again, no internet, no ping.
Thanks
Click to expand...
Click to collapse
What do you mean by "same info as my laptop" what types of credentials are you referring to? Something you have to change on the laptop in order to get in? The more information regarding this you can provide (safely, mind you, mask/alter any sensitive info), the better we can assist you. If you have to do something like set a VLAN, then you're never going to get an Android device to work as we do not have the capability to use VLAN'd wireless like most PCs and Macs can with the proper configuration changes. If there's some browser catch-all page, then that should work, but based on your statement "with the IP changed" leads me to believe that you're messing with the adapter settings directly. I would be especially keen to helping you with more detailed networking issues like this should you provide me with the information requested. I look forward to your reply. (Yes, I like technical challenges like this, it's why I work VoIP support.)

IP address or no IP address
Coffeeist said:
Some more info:
I cannot ping the tablet from my laptop (I get no packet loss, but all return 'Destination Host Unreachable'.
Same result if I try pinging my laptop or the router from my tablet using Terminal Emulator.
Sometimes, if set to DHCP, the tablet will give an 'Authentication Error Occured' error (or similar, I don't recall the actual wording). Sometimes it indicates a connection, but just won't work. I've never had a problem connecting using the same info as my laptop (with the IP changed, of course), but again, no internet, no ping.
Thanks
Click to expand...
Click to collapse
since you know ping, then did you check the IP address for each device?
Back to basic:
1: ping your device gateway IP
2) if ok, then ping ur device (tablet or laptop)
3) if ok then ping bbc.co.uk (this will check your dns), if failed ping your dns's IP address.
If no IP on android, then check if there is any protection on device. It sound like no IP been allocated for you.
Depends on how good a school's IT dept. I have not seen many school actually put filter to stop non-window device.
I am not sure it has anything to do with VLAN yet. As a simple logon, device does not care VLAN or no VLAN.
The basic for us is 1) get an IP on device. 2) know how to get out (gateway IP) 3) interrept hwere you go (DNS resolution) 4) know how to get to internet (internet router, internet firewall, internet boardband et...)
If you have authentication error, then it is sure you are not going to get an IP address. If this is WiFi then check on security (WEP, WAP...TKIP...)

tinbox134 said:
since you know ping, then did you check the IP address for each device?
Back to basic:
1: ping your device gateway IP
2) if ok, then ping ur device (tablet or laptop)
3) if ok then ping bbc.co.uk (this will check your dns), if failed ping your dns's IP address.
If no IP on android, then check if there is any protection on device. It sound like no IP been allocated for you.
Depends on how good a school's IT dept. I have not seen many school actually put filter to stop non-window device.
I am not sure it has anything to do with VLAN yet. As a simple logon, device does not care VLAN or no VLAN.
The basic for us is 1) get an IP on device. 2) know how to get out (gateway IP) 3) interrept hwere you go (DNS resolution) 4) know how to get to internet (internet router, internet firewall, internet boardband et...)
If you have authentication error, then it is sure you are not going to get an IP address. If this is WiFi then check on security (WEP, WAP...TKIP...)
Click to expand...
Click to collapse
Hello Coffeeist,
Please contact your schools IT department and find out what kind of encryption they use on their APs.
If they use TKIP, then that is whats causing the problem with android devices.
Once TKIP is disabled on the AP you are connecting to, you will be able to reach the internet.
I say this because I had the same problem in the past (setting up Cisco APs), and can confirm that this is the cause of the problem.
TKIP shouldn't be used anyway. They should be using AES. TKIP is too weak.
I guess that last part answered another question that you might of had. (Why TKIP doesn't work with Android?) Android=Secure TKIP=WEAK.... Unacceptable for Android
Also, you mention something about not being able to ping your tablet from your laptop. If I understand this correctly, you have both your laptop and tablet connected to the same AP and you are trying to ping between the two. This wont work in most cases. Reason: "Port-Protection", which if enabled doesn't allow clients on the AP to communicate with each other.
Regards,
Ed
Let us know how it goes.

nasvi said:
Hello Coffeeist,
Please contact your schools IT department and find out what kind of encryption they use on their APs.
If they use TKIP, then that is whats causing the problem with android devices.
Once TKIP is disabled on the AP you are connecting to, you will be able to reach the internet.
I say this because I had the same problem in the past (setting up Cisco APs), and can confirm that this is the cause of the problem.
TKIP shouldn't be used anyway. They should be using AES. TKIP is too weak.
I guess that last part answered another question that you might of had. (Why TKIP doesn't work with Android?) Android=Secure TKIP=WEAK.... Unacceptable for Android
Also, you mention something about not being able to ping your tablet from your laptop. If I understand this correctly, you have both your laptop and tablet connected to the same AP and you are trying to ping between the two. This wont work in most cases. Reason: "Port-Protection", which if enabled doesn't allow clients on the AP to communicate with each other.
Regards,
Ed
Let us know how it goes.
Click to expand...
Click to collapse
With useful posts above the rest is not much left for me to say but a simple advice
Make sure your friends aren't playing a prank on you coz I tend to do it I use arpspoof and aireplay-ng to cause such mayhem
Sent from my A116 using Tapatalk 2

Airplay and Arpspoof wouldn't be possible if MFP is enabled on the AP. Also the OP is stating that it is with all android devices and not 1.
Sent from my HTC One XL using xda app-developers app

responses
First off, thanks for all of the posts, and I apologize for taking so long to respond.
Also, I did check port 5228 with my laptop, and it seemed to indeed be closed. Haven't been able to contact IT yet, but I will need to soon to solve an issue with another, unrelated issue.
Cynagen said:
What do you mean by "same info as my laptop" what types of credentials are you referring to? Something you have to change on the laptop in order to get in? The more information regarding this you can provide (safely, mind you, mask/alter any sensitive info), the better we can assist you. If you have to do something like set a VLAN, then you're never going to get an Android device to work as we do not have the capability to use VLAN'd wireless like most PCs and Macs can with the proper configuration changes. If there's some browser catch-all page, then that should work, but based on your statement "with the IP changed" leads me to believe that you're messing with the adapter settings directly. I would be especially keen to helping you with more detailed networking issues like this should you provide me with the information requested. I look forward to your reply. (Yes, I like technical challenges like this, it's why I work VoIP support.)
Click to expand...
Click to collapse
Just IP/DHCP/DNS (and I've also tried public DNS such as Google). Nothing fancy set up on the laptop (everything should be on Windows default network settings, same with Android on both devices). There is also no catch-all page, assuming I'm interpreting that correctly (as a login page sort of thing, like I'd get at Starbucks or a Hotel).
Glad to provide the challenge... truth be told, underneath the annoyance of lacking connection, I love issues like this because of the fun tricks and such that solving them can teach.
tinbox134 said:
since you know ping, then did you check the IP address for each device?
Back to basic:
1: ping your device gateway IP
2) if ok, then ping ur device (tablet or laptop)
3) if ok then ping bbc.co.uk (this will check your dns), if failed ping your dns's IP address.
If no IP on android, then check if there is any protection on device. It sound like no IP been allocated for you.
Depends on how good a school's IT dept. I have not seen many school actually put filter to stop non-window device.
I am not sure it has anything to do with VLAN yet. As a simple logon, device does not care VLAN or no VLAN.
The basic for us is 1) get an IP on device. 2) know how to get out (gateway IP) 3) interrept hwere you go (DNS resolution) 4) know how to get to internet (internet router, internet firewall, internet boardband et...)
If you have authentication error, then it is sure you are not going to get an IP address. If this is WiFi then check on security (WEP, WAP...TKIP...)
Click to expand...
Click to collapse
1. If I recall, this either had full loss, or Destination Host Unreachable, when pinging the gateway IP from the tablet.
2. Have tried this nonetheless, and I think I made it through once or twice just after turning on the tablet, but after that would only get Dest. Host Unreachable.
3. Had tried with Google, fails across any DNS.
I seem to get an IP, although sometimes I get the authentication error in Android and it won't connect. Whenever I set a static IP, based off of my laptop's IP (not the same, of course), I get connected, just no internet.
nasvi said:
Hello Coffeeist,
Please contact your schools IT department and find out what kind of encryption they use on their APs.
If they use TKIP, then that is whats causing the problem with android devices.
Once TKIP is disabled on the AP you are connecting to, you will be able to reach the internet.
I say this because I had the same problem in the past (setting up Cisco APs), and can confirm that this is the cause of the problem.
TKIP shouldn't be used anyway. They should be using AES. TKIP is too weak.
I guess that last part answered another question that you might of had. (Why TKIP doesn't work with Android?) Android=Secure TKIP=WEAK.... Unacceptable for Android
Also, you mention something about not being able to ping your tablet from your laptop. If I understand this correctly, you have both your laptop and tablet connected to the same AP and you are trying to ping between the two. This wont work in most cases. Reason: "Port-Protection", which if enabled doesn't allow clients on the AP to communicate with each other.
Regards,
Ed
Let us know how it goes.
Click to expand...
Click to collapse
Unless I am totally clueless about this stuff (er, moreso than I though I already was), it uses neither TKIP or AES, being an open and unsecured network.
sak-venom1997 said:
With useful posts above the rest is not much left for me to say but a simple advice
Make sure your friends aren't playing a prank on you coz I tend to do it I use arpspoof and aireplay-ng to cause such mayhem
Sent from my A116 using Tapatalk 2
Click to expand...
Click to collapse
Haha, I doubt it. None of my friends, especially the ones who I think would even try and do something like this, are tech-savvy enough for me to have any suspicion of that. Thanks though
Another piece of info (a pretty weird seeming one at that): Sometimes, I'll turn on my tablet in the middle of the day, and out of the blue there is an email notification there, for recent emails. Of course, if I go into browser, I can't get any pages. Can't think of any other networks that the device could/would connect to on campus, either.
Thanks!

Coffeeist said:
First off, thanks for all of the posts, and I apologize for taking so long to respond.
Also, I did check port 5228 with my laptop, and it seemed to indeed be closed. Haven't been able to contact IT yet, but I will need to soon to solve an issue with another, unrelated issue.
Just IP/DHCP/DNS (and I've also tried public DNS such as Google). Nothing fancy set up on the laptop (everything should be on Windows default network settings, same with Android on both devices). There is also no catch-all page, assuming I'm interpreting that correctly (as a login page sort of thing, like I'd get at Starbucks or a Hotel).
Glad to provide the challenge... truth be told, underneath the annoyance of lacking connection, I love issues like this because of the fun tricks and such that solving them can teach.
1. If I recall, this either had full loss, or Destination Host Unreachable, when pinging the gateway IP from the tablet.
2. Have tried this nonetheless, and I think I made it through once or twice just after turning on the tablet, but after that would only get Dest. Host Unreachable.
3. Had tried with Google, fails across any DNS.
I seem to get an IP, although sometimes I get the authentication error in Android and it won't connect. Whenever I set a static IP, based off of my laptop's IP (not the same, of course), I get connected, just no internet.
Unless I am totally clueless about this stuff (er, moreso than I though I already was), it uses neither TKIP or AES, being an open and unsecured network.
Haha, I doubt it. None of my friends, especially the ones who I think would even try and do something like this, are tech-savvy enough for me to have any suspicion of that. Thanks though
Another piece of info (a pretty weird seeming one at that): Sometimes, I'll turn on my tablet in the middle of the day, and out of the blue there is an email notification there, for recent emails. Of course, if I go into browser, I can't get any pages. Can't think of any other networks that the device could/would connect to on campus, either.
Thanks!
Click to expand...
Click to collapse
Based on your responses, I have a follow up question and comment. The question is as follows: Did you have to register your computer with your IT when you started school in order to be permitted on the wireless network? If this was the case they're likely filtering based on MAC address (which you won't be able to spoof on your Android, but you may be able to spoof on your laptop), get them to re-register your laptop after you spoof the MAC address so you can get both devices on using the same MAC address (though not at the same time of course unless you're fine with stuff randomly not working). The comment is as follows: Yeah, finding the workarounds to get back limitations like this is definitely a fun challenge because when you win, you've definitely learned something new. Oh, and you were right about my question of the gateway authentication page like a hotel wifi login page.

MAC
Cynagen said:
Based on your responses, I have a follow up question and comment. The question is as follows: Did you have to register your computer with your IT when you started school in order to be permitted on the wireless network? If this was the case they're likely filtering based on MAC address (which you won't be able to spoof on your Android, but you may be able to spoof on your laptop), get them to re-register it after you spoof the MAC address so you can get both devices on using the same MAC address (though not at the same time of course). The comment is as follows: Yeah, finding the workarounds to get back limitations like this is definitely a fun challenge because when you win, you've definitely learned something new.
Click to expand...
Click to collapse
Nope, it was up and running just through connecting normally, and has been since (mostly) - no registration or anything like that. Now, the reason that I put 'mostly' in parentheses is that sometimes the computer will be connected, but also have no internet (I don't think this started until I, dare I admit, upgraded to Windows 8). However, this only happens sometimes, whereas the Android devices never get internet access.
However, on the topic of MAC addresses, one post (in fact, I think it was on XDA) I saw awhile back while Google searching this problem was that someone had a similar issue, found to be with their device's MAC address having the letters 'FA' instead of 'FB' or something like that. Being that my Note isn't rooted, I haven't tested it with that, but perhaps I should give that a try with my CM10 Rezound?
(This is the post: HERE)
Thanks!

Coffeeist said:
Nope, it was up and running just through connecting normally, and has been since (mostly) - no registration or anything like that. Now, the reason that I put 'mostly' in parentheses is that sometimes the computer will be connected, but also have no internet (I don't think this started until I, dare I admit, upgraded to Windows 8). However, this only happens sometimes, whereas the Android devices never get internet access.
However, on the topic of MAC addresses, one post (in fact, I think it was on XDA) I saw awhile back while Google searching this problem was that someone had a similar issue, found to be with their device's MAC address having the letters 'FA' instead of 'FB' or something like that. Being that my Note isn't rooted, I haven't tested it with that, but perhaps I should give that a try with my CM10 Rezound?
(This is the post: HERE)
Thanks!
Click to expand...
Click to collapse
That shouldn't be it unless they have corporate level routers that don't recognize the MAC address of any devices manufactured after 2009 (when most of these manufacturers got the MAC addresses assigned to them (this is VERY unlikely)). I would honestly work with IT on campus and advise that it appears not a single Android device is allowed on the network. If they're blocking Android for any reason, check the terms of service for using the WiFi and see if there's any provisions for banning an entire brand of device/OS for whatever reason. If there's only provisions for individual banning, then take it back to them and show them that your record has not been abusive in the least and go from there. Make a case, otherwise draw one up with legal council. *shrugs* I don't believe anyone should ever be punished for the type of device they chose to purchase, that's first amendment choice, but it really comes down to their terms of service which you agree to by using the wifi.

Cynagen said:
That shouldn't be it unless they have corporate level routers that don't recognize the MAC address of any devices manufactured after 2009 (when most of these manufacturers got the MAC addresses assigned to them (this is VERY unlikely)). I would honestly work with IT on campus and advise that it appears not a single Android device is allowed on the network. If they're blocking Android for any reason, check the terms of service for using the WiFi and see if there's any provisions for banning an entire brand of device/OS for whatever reason. If there's only provisions for individual banning, then take it back to them and show them that your record has not been abusive in the least and go from there. Make a case, otherwise draw one up with legal council. *shrugs* I don't believe anyone should ever be punished for the type of device they chose to purchase, that's first amendment choice, but it really comes down to their terms of service which you agree to by using the wifi.
Click to expand...
Click to collapse
I'll give it a shot, thanks.

Coffeeist said:
I'll give it a shot, thanks.
Click to expand...
Click to collapse
Sorry to bump the thread, but seeing as it's my own I figured it would be alright...
I got around to asking the the school IT about the issue, and they said that the deliberately block mobile traffic, which they went on to find out does include Android tablets (I understand phones, but I can't even begin to understand why they target Android tablets... unfortunately, that's not my call). I Google searched a bit, and found that networking devices from a company called Aruba can be set to block traffic from specific types of devices (supposedly Cisco and a few other companies can do similar things too), by checking something with the HTML version, or something like that (I'm by no means a networking expert hehe).
So, I guess I'll make my last effort with this thing, and ask if anyone knows of some legal, non-hacky way of getting by this?
I'm guessing not, but worth asking.
Thanks

Coffeeist said:
Sorry to bump the thread, but seeing as it's my own I figured it would be alright...
I got around to asking the the school IT about the issue, and they said that the deliberately block mobile traffic, which they went on to find out does include Android tablets (I understand phones, but I can't even begin to understand why they target Android tablets... unfortunately, that's not my call). I Google searched a bit, and found that networking devices from a company called Aruba can be set to block traffic from specific types of devices (supposedly Cisco and a few other companies can do similar things too), by checking something with the HTML version, or something like that (I'm by no means a networking expert hehe).
So, I guess I'll make my last effort with this thing, and ask if anyone knows of some legal, non-hacky way of getting by this?
I'm guessing not, but worth asking.
Thanks
Click to expand...
Click to collapse
Before discussing any workarounds, you may need to review the Terms of Service for your wifi on the school premises first, review the consequences for bypassing their security measures, and figure if it's worth the risk to you... At this time, it'll be kind of "hacky" to get around such a block. In order to provide you with a valid workaround though we'll need a little bit of information regarding what's going on when you connect.
First, when you connect to the WiFi with your Android device, do you even receive an IP address? If you don't then we'll stop here, the only way to get around the types of blocks they're employing at this level would require hardware hacking/firmware reprogramming to change the identity of the device itself, which is flat out illegal in just about anywhere I can think of. Here's your checklist, fill out where applicable: (Even if you set static information to accomplish this, that will be a valid Y.)
Get an IP? (If Y, proceed)
Is it a valid IP address on the same network as your PC? (Either way, don't care)
Can you ping the gateway you got from DHCP on Android? (If Y, proceed)
Can you ping the DNS server(s) you got from DHCP on Android? (If Y, proceed)
Can you ping an external server such as Google DNS (8.8.8.8) on Android? (If Y, then we're done here)
It's kind of a bit of a process unfortunately, however, if you pass every single one of these tests with the Android device, there's good news. They're only filtering traffic based on the User-Agent identification of all your applications (and based on the MAC address of your device, denying your DHCP requests), you should be able to bypass this with a VPN tunnel back to your home from your Android (after setting your static IP) in order to encrypt and keep this information from leaking to their systems. However, this will likely set off alarms if they monitor their network heavily. If the school IT asks, then you're "working on projects in-between classes on your computer at home and your family has a home office with VPN already, so you used that to connect back to the house". Either way, they can't say much about it besides cut you off... again. Anywhos, I wouldn't recommend trying to bypass without doing all this research first, and then also evaluating the possible consequences, however the rewards are within themselves. You'll be the only person at school with a working mobile device, (besides those iSuckers). Technically, encrypting your traffic is completely legal (and they can't say anything legally about it), however, setting a static IP address in the same range as your computer at school may be against their TOS which you abide by being on campus. Let us know how everything goes.

Cynagen said:
Get an IP? (If Y, proceed)
Is it a valid IP address on the same network as your PC? (Either way, don't care)
Can you ping the gateway you got from DHCP on Android? (If Y, proceed)
Can you ping the DNS server(s) you got from DHCP on Android? (If Y, proceed)
Can you ping an external server such as Google DNS (8.8.8.8) on Android? (If Y, then we're done here)
Click to expand...
Click to collapse
With Static I set an IP and all other info (Gateway, DNS, etc, except for Network Prefix Length... no clue what that is, left it at 24 default), and could not ping gateway
Dynamic/DHCP I will have to check tomorrow, after downloading stuff for the tablet to get that info (I think I need root to use IfConfig with Terminal Emulator, correct?).
Whatever they use to block me out, it seems to have a slight hole built in... every day, multiple times a day, I will look down at my tablet and see notifications (mainly email, occasionally Facebook, etc) that pushed through on the schools network (I know that for sure, being that often times the emails are messages received during the day, in a time period where the tablet has been nowhere near any other networks). Maybe this hole can be breached?
Thanks!

Coffeeist said:
With Static I set an IP and all other info (Gateway, DNS, etc, except for Network Prefix Length... no clue what that is, left it at 24 default), and could not ping gateway
Dynamic/DHCP I will have to check tomorrow, after downloading stuff for the tablet to get that info (I think I need root to use IfConfig with Terminal Emulator, correct?).
Whatever they use to block me out, it seems to have a slight hole built in... every day, multiple times a day, I will look down at my tablet and see notifications (mainly email, occasionally Facebook, etc) that pushed through on the schools network (I know that for sure, being that often times the emails are messages received during the day, in a time period where the tablet has been nowhere near any other networks). Maybe this hole can be breached?
Thanks!
Click to expand...
Click to collapse
It seems like small gaps where the system doesn't block you long enough to receive some traffic, but that is promising. BTW, you can get your "network prefix" (netmask as we call it) from your computer. If you go into the command prompt on windows and run "ipconfig /all" you'll get 4 useful bits of info we need, IP address (so you can mimic it), the gateway, the subnet mask (usually 255.255.something.something) and the DNS servers. The subnet mask determines what you use, and I HIGHLY doubt they use 24 (that's mainly for home networks, 24 = 254 devices permitted on the DHCP, 16 = 65534 devices (this is WAY more likely)).

Cynagen said:
It seems like small gaps where the system doesn't block you long enough to receive some traffic, but that is promising. BTW, you can get your "network prefix" (netmask as we call it) from your computer. If you go into the command prompt on windows and run "ipconfig /all" you'll get 4 useful bits of info we need, IP address (so you can mimic it), the gateway, the subnet mask (usually 255.255.something.something) and the DNS servers. The subnet mask determines what you use, and I HIGHLY doubt they use 24 (that's mainly for home networks, 24 = 254 devices permitted on the DHCP, 16 = 65534 devices (this is WAY more likely)).
Click to expand...
Click to collapse
Well, I just had a clean connection for about 5 minutes, and had a normal-looking IP based on my PC. Using Terminal Emulator I pinged the gateway after my connection failed, still with no response. I still appeared to have a proper IP on my tablet, but no actual internet connection.
So, perhaps these small windows are something to pursue? Or perhaps sticking with the VPN plan is best?
Thanks!

Coffeeist said:
Well, I just had a clean connection for about 5 minutes, and had a normal-looking IP based on my PC. Using Terminal Emulator I pinged the gateway after my connection failed, still with no response. I still appeared to have a proper IP on my tablet, but no actual internet connection.
So, perhaps these small windows are something to pursue? Or perhaps sticking with the VPN plan is best?
Thanks!
Click to expand...
Click to collapse
You need to make sure your networking information is entered correctly, you still haven't said anything about the netmask in this situation. However, if you're entering this information in correctly then you should have a solid connection until they realize you've forced a device into the network. The only thing you can do beyond that point is during that window, open a VPN connection without using a single browser request so they don't know what the device is unless they check the MAC address. Either way, this is a window that can be used, you just need to avoid identifying your device in any way prior to initiating the VPN connection. Turn off Sync when you connect.

[Q] dreaded gray Wi-Fi bar

Hey guys,
My nexus 10 had a gray Wi-Fi bar and is failing to connect any of the Google services such as play store, search app, or gmail. Basically GAPPS. I cannot find a solution to this besides factory resetting, can someone help? My tablet is on stock rooted.
Thanks!
add12364

My N10 either has a grey WiFi bar or it disconnects completely. This happens very often and occurs no matter what rom I have, even stock. I've always felt that the WiFi has always had issues but never got resolved. I've looked around for solutions but not found any. Much appreciated if someone explained or had a solution.
Sent from my Nexus 10 using Tapatalk HD

I completely cannot use Google play, someone please help.

Toggle the Wifi off and then back on a few seconds later.
If this doesnt fix anything then you need to modify your router settings to be compatible.

Don't use 5g on router.
Sent from my Nexus 10

5GHz networks work fine on this tablet.

trickster2369 said:
Don't use 5g on router.
Sent from my Nexus 10
Click to expand...
Click to collapse
No offense meant, but that's a pretty silly claim. The transmission technology involved (2.4GHz/5GHz) or protocol (802.11a/b/g/n/ac) has no bearing on the color of the Wi-Fi indicator, which indicates just one thing: does a request to Google's secure servers work, or not? It's virtually always a problem with the network setup, be it with the ISP or the router blocking a port. OP should try using a public access point (coffee shop or something) or mobile hotspot to see if they're able to connect that way.

EniGmA1987 said:
5GHz networks work fine on this tablet.
Click to expand...
Click to collapse
My apologies. There was a lot of discussion concerning the use of 5ghz when the tablet was released. My comment was more of a suggestion than an absolute, and probably wasn't written the best.
Rirere said:
No offense meant, but that's a pretty silly claim. The transmission technology involved (2.4GHz/5GHz) or protocol (802.11a/b/g/n/ac) has no bearing on the color of the Wi-Fi indicator, which indicates just one thing: does a request to Google's secure servers work, or not? It's virtually always a problem with the network setup, be it with the ISP or the router blocking a port. OP should try using a public access point (coffee shop or something) or mobile hotspot to see if they're able to connect that way.
Click to expand...
Click to collapse
None taken. I was under the impression that grey/no bars, meant that there was no signal or there was a connection issue. I had no idea that the wifi state on the tablet had anything to do with Googles secure servers. I would like to learn more about that, if you would be so kind.

trickster2369 said:
None taken. I was under the impression that gray/no bars, meant that there was no signal or there was a connection issue. I had no idea that the wifi state on the tablet had anything to do with Googles secure servers. I would like to learn more about that, if you would be so kind.
Click to expand...
Click to collapse
The Wi-Fi state doesn't depend on the connection to Google's servers-- that's why it's quite possible to get full graybars. You'll also notice that if your Wi-Fi goes to sleep, when you wake up a (stock) Android device, you should basically always see it gray first, then turn blue after a second or so (speed depends on how good your connection is).
It's also not as simple as just going to google.com, because you can (usually) do that regardless of the status reported. That's because going to google.com only relies on basic HTTP/HTTPS web traffic through ports 80 and 443, which on most functioning networks are never going to be blocked (mostly because it would make even basic web browsing more or less impossible without workarounds). All of your "real" transactions with Google (Gmail sync, location reporting, etc.) happen through secured connections that run on different ports.
Some networks will block those ports for security reasons (the more ports you have open, the greater the network's functionality-- and its vulnerability to outside attack). In those situations, you'll see a gray bar indicating that while you've got connectivity, you won't be able to establish the connection to Google needed for some services to run (most importantly, any GCM/C2DM-based push notifications).
And no problem. Unfortunately, many OEMs muck around with the iconography, making this distinction meaningless on a pretty wide range of devices. It's annoying because this is one of the more common reasons that Google services don't work.

Rirere said:
The Wi-Fi state doesn't depend on the connection to Google's servers-- that's why it's quite possible to get full graybars. You'll also notice that if your Wi-Fi goes to sleep, when you wake up a (stock) Android device, you should basically always see it gray first, then turn blue after a second or so (speed depends on how good your connection is).
It's also not as simple as just going to google.com, because you can (usually) do that regardless of the status reported. That's because going to google.com only relies on basic HTTP/HTTPS web traffic through ports 80 and 443, which on most functioning networks are never going to be blocked (mostly because it would make even basic web browsing more or less impossible without workarounds). All of your "real" transactions with Google (Gmail sync, location reporting, etc.) happen through secured connections that run on different ports.
Some networks will block those ports for security reasons (the more ports you have open, the greater the network's functionality-- and its vulnerability to outside attack). In those situations, you'll see a gray bar indicating that while you've got connectivity, you won't be able to establish the connection to Google needed for some services to run (most importantly, any GCM/C2DM-based push notifications).
And no problem. Unfortunately, many OEMs muck around with the iconography, making this distinction meaningless on a pretty wide range of devices. It's annoying because this is one of the more common reasons that Google services don't work.
Click to expand...
Click to collapse
Would you happen to know if roms can affect wifi reception?

ikenvape said:
Would you happen to know if roms can affect wifi reception?
Click to expand...
Click to collapse
ROMs and kernels shouldn't affect reception in a technical sense (unless the kernel developer really messes up or something), but they will affect what your device can do with the signal it has. There are also various modes your device can follow that offer compromises (i.e. for CDMA devices, EVRC-B vs. EVRC-C -- one is better for normal usage, the other holds clearer calls with low signal).

Rirere said:
ROMs and kernels shouldn't affect reception in a technical sense (unless the kernel developer really messes up or something), but they will affect what your device can do with the signal it has. There are also various modes your device can follow that offer compromises (i.e. for CDMA devices, EVRC-B vs. EVRC-C -- one is better for normal usage, the other holds clearer calls with low signal).
Click to expand...
Click to collapse
Really appreciate the reply Rirere
I tried several lately. Since day one I have been receiving such poor reception. We have heavy wireless users here ranging from multiple game stations,phones tablets ,PC's etc. All have been receiving full strength except for the N10. From what your saying it seems like I have adjust the router for this one.

ikenvape said:
Really appreciate the reply Rirere
I tried several lately. Since day one I have been receiving such poor reception. We have heavy wireless users here ranging from multiple game stations,phones tablets ,PC's etc. All have been receiving full strength except for the N10. From what your saying it seems like I have adjust the router for this one.
Click to expand...
Click to collapse
Could you be a little more specific? Android has some nasty Wi-Fi issues (never have as many on my iOS devices), but the situation you describe doesn't sound like it helps. I'm the student manager at a college helpdesk, so we sometimes have this kind of problem in the dorms. If you give some more info about your setup, I might be able to at least point you in the right direction.
Things like what's the make and model of the router, where it's located, how close are neighbors, and so on. You can also use this app (https://play.google.com/store/apps/...SwxLDEsImNvbS5mYXJwcm9jLndpZmkuYW5hbHl6ZXIiXQ) to see if there's channel interference. If your router is new enough, you could also potentially kick it up to use 5GHz only (although that causes lower speeds the further you get much faster than auto 2.4GHz/5GHz).

Rirere said:
Could you be a little more specific? Android has some nasty Wi-Fi issues (never have as many on my iOS devices), but the situation you describe doesn't sound like it helps. I'm the student manager at a college helpdesk, so we sometimes have this kind of problem in the dorms. If you give some more info about your setup, I might be able to at least point you in the right direction.
Things like what's the make and model of the router, where it's located, how close are neighbors, and so on. You can also use this app (https://play.google.com/store/apps/...SwxLDEsImNvbS5mYXJwcm9jLndpZmkuYW5hbHl6ZXIiXQ) to see if there's channel interference. If your router is new enough, you could also potentially kick it up to use 5GHz only (although that causes lower speeds the further you get much faster than auto 2.4GHz/5GHz).
Click to expand...
Click to collapse
Your too kind Reiere Thank you,
I'm using a Media Link MWN-WAPR150N. I see, it doesn't support 5ghz which seems to be a total bummer. I could have sworn that I purchased a dual band model. It's a wonderful device as I'm not having to constantly power cycle it like in the past. We do catch a neighboring facility's wifi here on our devices so I believe this can be causing interference and it would be best to switch up to a 5ghz router? Definitely will check out the app. Thanks allot. I apologize for the ignorance in this area.

ikenvape said:
Your too kind Reiere Thank you,
I'm using a Media Link MWN-WAPR150N. I see, it doesn't support 5ghz which seems to be a total bummer. I could have sworn that I purchased a dual band model. It's a wonderful device as I'm not having to constantly power cycle it like in the past. We do catch a neighboring facility's wifi here on our devices so I believe this can be causing interference and it would be best to switch up to a 5ghz router? Definitely will check out the app. Thanks allot. I apologize for the ignorance in this area.
Click to expand...
Click to collapse
You're almost always going to get some degree of interference from other devices. How bad it is depends on the power of your neighbors' rig and its proximity. Other items, such as microwaves can cause temporary disruptions in wireless power, but it's much more unusual these days than it was in the past.
Given the way other devices in your network seem to be functioning alright, it might be a device-side issue. However, before that I would look into a Wi-Fi analyzing app like I posted earlier and try setting your network to a particular channel. If you pick one clear of your neighbors' wireless network, then if it's set to auto (which it probably is), it should adjust around yours and grant you a clear channel. (two networks on auto can occasionally snarl with one another, and the one with more power is going to win. Since yours is a single-band N home router, there's a good chance you'd lose with the routers out these days).

Share Your OnHub Feedback

Please Share your feedback to help current and future owners of the router

The setup was super easy. Wifi range is much better than the Asus RT-AC66U it replaced. The standard Ethernet cable doesn't fit if you want to keep the outer cover on. The included cables are too short and the power cable is also too short. Otherwise it works well.

I don't like how some "unnamed devices" show up with no IP address in the list of connected devices... how is that even possible? I get if those devices are connected with a set static IP on the device, but if they are assigned via DHCP the IP address *should* show up (I have a LinksysPAP VoIP device set to DHCP that would not show the IP and just shows up as an unnamed device).
Other than that... great device so far, easy to set up. Love the app and the LED light on the top.

lexcyn said:
I don't like how some "unnamed devices" show up with no IP address in the list of connected devices... how is that even possible? I get if those devices are connected with a set static IP on the device, but if they are assigned via DHCP the IP address *should* show up (I have a LinksysPAP VoIP device set to DHCP that would not show the IP and just shows up as an unnamed device).
Other than that... great device so far, easy to set up. Love the app and the LED light on the top.
Click to expand...
Click to collapse
I'm still waiting for mine to arrive tomorrow. Do the "unnamed devices" at least show the mac address, so you can identify what they are? I've been curious about how much control I'd have over settings, ip, etc... I'm currently running a Buffalo router with DD-WRT.

adrman said:
I'm still waiting for mine to arrive tomorrow. Do the "unnamed devices" at least show the mac address, so you can identify what they are? I've been curious about how much control I'd have over settings, ip, etc... I'm currently running a Buffalo router with DD-WRT.
Click to expand...
Click to collapse
Yes they all at least show the MAC - but that's about it. You can set a static IP and forward ports... but not much else. It's a very simple interface, but I'm assuming it was built that way. I have a feeling as their app evolves they will add more control.

Can you guys post some screenshots ?

Here's a screenshot of the "unnamed device" I was talking about.

Not great here. I'm getting 1/3 of my speed on wifi and 1/10th hard wired compared to my linksys wrt-ac1900. Tech support was pretty responsive and are looking into it. I'm running gigabit fiber. The range seems decent and setup was easy.

Anyone to from a time capsule to this? Wondering if it would be worth the switch.

Unboxing and set up
http://youtu.be/MW8VeWdCo0I
Sent from my iPhone using Tapatalk

No way to add devices that use WPS (not a huge deal).
Security is not configurable (not a deal breaker, just interesting)
No web-based interface
No DDNS client (not a huge deal)
No way to view uPnP mappings
The single ethernet port in the back is kind of a drag, but it wasn't an issue for me. Also standard cables will not fit with the cover on.
The "unnamed device" thing is kind of annoying (makes setting up static DHCP entries a hassle) but it's not a huge deal. It would be cool to be able to name these explicitly from within the app.
Setup was easy and quick. Seems to work well, no drop-outs so far. :good:

With the mixed reviews out there, I wasn't expecting much in terms of coverage or perf, but I was pleasantly surprised. Since I live in a fairly large multi story house, I've always had to have range extenders to get upstairs (even with a high-end WAP downstairs). Now, for the first time ever in my house, I have only one WAP (OnHub) and I'm getting 25MB in the farthest reaches of the house. I get 80MB via wifi close to the router (in the same room), but that is similar to what I got before. I get 170MB via wired, so no problem keeping up with a high bandwidth connection, it seems to have plenty of processing power. I suppose putting the OnHub up on a shelf does help with range and perf compared to the old WAP being lower (beneath the TV), but I can't believe placement is making that big of a difference, it seems the range and perf of the OnHub is actually really good. So before where I had 4 wifi networks to deal with (wifi2G, wifi5G, wifi2GExt, wifi5GExt), it's all now just consolidated into one wifi network, which is great. I agree it is kind of a bummer that guest networking is not yet implemented, but I never used it, so not a big issue for me.
I really like being able to do the admin from the mobile app, the simplicity actually takes some getting used to. True, you can't configure security or frequencies (2G, 5G, channels, etc) that I know of, but I'm actually kind of starting to appreciate the simplicity, it is definitely a whole new take on a high-end router/WAP.
Only one LAN port on the OnHub is not really an issue for me because I had more than 4 wired devices (7 to be exact), so I already had an 8 port switch in use, which now (obviously) runs into the one LAN port on the OnHub.
So really my only (minor) issue with it is the standard cables are too short, and I wasn't sure if they were Cat 6, so I just swapped them for 10ft Cat 6 cables I already had; problem solved. I had no problem getting the cover to lock on with normal cables, which sounds different from what others are posting, not sure why, works fine for me.
So far no drops from interference, which was a problem on all my old routers/WAPs since I live in a neighborhood with lots of WAPs in range of my house.
Overall, I'm very happy with it, it has solved most (if not all) my home networking challenges, especially on the wifi side.

llarch said:
With the mixed reviews out there, I wasn't expecting much in terms of coverage or perf, but I was pleasantly surprised. Since I live in a fairly large multi story house, I've always had to have range extenders to get upstairs (even with a high-end WAP downstairs). Now, for the first time ever in my house, I have only one WAP (OnHub) and I'm getting 25MB in the farthest reaches of the house. I get 80MB via wifi close to the router (in the same room), but that is similar to what I got before. I get 170MB via wired, so no problem keeping up with a high bandwidth connection, it seems to have plenty of processing power. I suppose putting the OnHub up on a shelf does help with range and perf compared to the old WAP being lower (beneath the TV), but I can't believe placement is making that big of a difference, it seems the range and perf of the OnHub is actually really good. So before where I had 4 wifi networks to deal with (wifi2G, wifi5G, wifi2GExt, wifi5GExt), it's all now just consolidated into one wifi network, which is great. I agree it is kind of a bummer that guest networking is not yet implemented, but I never used it, so not a big issue for me.
I really like being able to do the admin from the mobile app, the simplicity actually takes some getting used to. True, you can't configure security or frequencies (2G, 5G, channels, etc) that I know of, but I'm actually kind of starting to appreciate the simplicity, it is definitely a whole new take on a high-end router/WAP.
Only one LAN port on the OnHub is not really an issue for me because I had more than 4 wired devices (7 to be exact), so I already had an 8 port switch in use, which now (obviously) runs into the one LAN port on the OnHub.
So really my only (minor) issue with it is the standard cables are too short, and I wasn't sure if they were Cat 6, so I just swapped them for 10ft Cat 6 cables I already had; problem solved. I had no problem getting the cover to lock on with normal cables, which sounds different from what others are posting, not sure why, works fine for me.
So far no drops from interference, which was a problem on all my old routers/WAPs since I live in a neighborhood with lots of WAPs in range of my house.
Overall, I'm very happy with it, it has solved most (if not all) my home networking challenges, especially on the wifi side.
Click to expand...
Click to collapse
Exact experience I'm having with the Onhub.
Sent from my SM-G925V using Tapatalk

The range is awesome. OnHub replaced a RT-66U and Amped AP300 with external powered antenna. My whole house is covered now.
I struggled through the unknown devices issues to get all my static IPs and port fwds setup.
The big issue for me is the OnHub does not support NAT Loopback. So you cannot access your cameras and static devices while at home without using their IP addresses. So my IP Camera app will not be able to find my cameras at home with "xxxx.duckdns.org:1025" but this works when connected to another network or Mobile data. This is a big pain in the a$$ for those of us that like to access things on our networks remotely and while at home.
I contacted support and they have added NAT Loopback to the requests...

A tip if replacing a FiOS router; power down the Verizon ONT for half an hour. Before powering back up, connect the ethernet from the ONT to the OnHub. The power cycle will force a renewed IP and allow the OnHub to register on the network without the need to go through the VZW router.

av8rdude said:
The range is awesome. OnHub replaced a RT-66U and Amped AP300 with external powered antenna. My whole house is covered now.
I struggled through the unknown devices issues to get all my static IPs and port fwds setup.
The big issue for me is the OnHub does not support NAT Loopback. So you cannot access your cameras and static devices while at home without using their IP addresses. So my IP Camera app will not be able to find my cameras at home with "xxxx.duckdns.org:1025" but this works when connected to another network or Mobile data. This is a big pain in the a$$ for those of us that like to access things on our networks remotely and while at home.
I contacted support and they have added NAT Loopback to the requests...
Click to expand...
Click to collapse
What camera app? If you're using TinyCam you can have internal (wifi) and external (LTE) settings for each camera.

I got mine today. I was using a borrowed modem and router so I needed to purchase something, and was either going to get a Ubiquiti access point (and keep using the borrowed router) or the onhub. So far it's been a great experience. Solid connections. I set a static address for my NAS.

It seems to be working well for me also. My biggest gripe is the "unnamed" devices. With 17 devices and only 3 or 4 that provide a recognizable name to OnHub, perhaps I could give them names?

The unnamed devices thing is very annoying.
Also, when assigning static ip, they need to list the mac address... Otherwise it makes it basically impossible to assign a static ip to one of those unnamed devices... Because which unnamed device are you assigning the ip to? Can't tell...
Sent from my SM-N920V using Tapatalk

JasonJoel said:
The unnamed devices thing is very annoying.
Also, when assigning static ip, they need to list the mac address... Otherwise it makes it basically impossible to assign a static ip to one of those unnamed devices... Because which unnamed device are you assigning the ip to? Can't tell...
Click to expand...
Click to collapse
I had a 30 minute conversation with support over just that issue. The general response was "well, that's a power user issue and this isn't a power user device" Even so, I'm surprised there hasn't been an update of some kind pushed yet because viewing the mac address to set a static ip isn't exactly "power user" functionality, it's basic.

Nexus 6P Acts as Rogue DHCP Server

At work i was playing around with some networking and noticed some weird things. I kept seeing a rogue DHCP server coming up from an IP that I traced to Taiwan. After some time on Wireshark and using this tool I found that every time my Nexus 6P connected to our WiFi it would for a split second send out a DHCP offer to the network on behalf of that Taiwan IP. I thought "Oh My, did I get some malware?". So I reformatted the phone and with a fresh install of the latest Pure Nexus, sure enough on the Setup screen (not even booted all the way into the ROM yet) when I put in the WiFi credentials for the first time, the same broadcast goes out over my LAN. WTF. Is this some sort of phone home backdoor from Huawei or what? I know some phone malware can get in below the ROM level and basically turn your phone into a hypervisor. Hopefully that is not the case or I'll have to toss it in the trash...
Any help is appreciated.

Any easy way for non-techie users like myself to check and verify this?

Bump
Sent from my Nexus 6P using XDA-Developers Legacy app

treesurf said:
Any easy way for non-techie users like myself to check and verify this?
Click to expand...
Click to collapse
Download the dhcp find program and run it from your workstation.
https://www.symantec.com/connect/downloads/detect-rogue-dhcp-servers-network
When it runs it broadcasts a request over your network as if it were a device needing an IP address. Your router or server that controls your DHCP will respond with an offer IP to hand out. A common malware attack is a DHCP man in the middle attack where the rogue DHCP server sends the response before your DHCP server does and it then gives the client machine a different DNS server that is usually some sort of proxy for showing you ads or changing your internet experience for the worse etc. If the wifi hotspot was enabled you'd expect this because the phone does indeed become a DHCP server in order to hand out an IP to your leeching device to tether with. But I have that turned off so that is not the case unless there's a bug in the software.
Once you run that program (your phone needs to be connected to your same network), then turn the wifi off on your phone and then back on again. For me when it joins my Wifi it pings out a DHCP broadcast as shown in my screenshot. It's from an outside IP, originating in Taiwan if you trace it. I have geographic location blocking on my router so its impossible for traffic to actually get to me from that IP but that is what the phone is broadcasting out. I'm a long time sysadmin so I pay pretty close attention to these things i guess.

@Budwise, can you fish flash factory images and check to see it if happens on stock? If not I would definitely report this in the Pure Nexus thread.

I found that I was seeing some odd behavior even when it wasnt connected via WiFi so I believe it happening when it connects is a side effect of something else going on. I think this can be closed.