I'm trying to troubleshoot a problem where some of my android devices fail to connect to a CHAP encrypted APN but others do. I want to check if the failing devices are in fact attempting to authenticate with CHAP and get some idea of why the authentication is failing. I should be able to see this with debug messages from pppd in the syslog, but pppd doesn't seem to be logging debug messages in any of my devices by default.
How can I enable debug output on pppd? I've tried adding a file named "options" to /etc/ppp containing the text "debug", but this didn't seem to do anything. Any ideas?
Thanks
Related
I have been playing with my new Kaiser(Tilt) since I got it earlier in the week. Rom is updated and everything is the way I like it. I would like to have my mac to connect to my Kaiser with bluetooth for internet access I just don't know what the AT&T setting are:
-telephone number
-account Name
-and password
I have looked all over and nothing I can find works. The Mac tells me
-A modem error occurred. Please verify your settings and try again.
What can I do to get this working? What setting are you using to make theis work for you?
You have to enable the Internet Sharing app. You can either find it in the Windows folder (IntShrUI), or you can do as I did and perform a hard reset but kill all the carrier customizations. By default, AT&T removes the program shortcut from your Programs folder. Here are some instructions, courtesy of the AT&T forums:
(1) From the Mac, initiate the pairing process with the phone. It will say the phone doesn't have any supported services, but then the last page of the Bluetooth wizard will say it supports a Personal Area Network.
(2) Open the "Internet Sharing" application on the phone.
(3) Change the method used to connect the computer from "USB" to "Bluetooth PAN".
(4) Click "Connect".
(5) On the Mac, click the Bluetooth menu on the Menu Bar and select "Join Network on [device]". (The Internet Sharing app on the phone should now say "Connected".)
Need more info
I got that part down, thanks. It's when it is trying to connect it imideatly disconects and tells me - A modem error occurred. Please verify your settings and try again. What are the settings on the mac side for
-telephone number
-account Name
-and password
Bluetooth PAN doesn't require those settings. It looks like what you're after is Bluetooth DUN. I believe you'll need to use the WModem app that's in the Connections tab. These should be the settings you're seeking:
Type [email protected] in the User name field.
Type CINGULAR1 in the Password field.
In the Dial field, type *99#.
thespiessman said:
I got that part down, thanks. It's when it is trying to connect it imideatly disconects and tells me - A modem error occurred. Please verify your settings and try again. What are the settings on the mac side for
-telephone number
-account Name
-and password
Click to expand...
Click to collapse
I am having problems setting up my WiFi connection with my SDA (HTC Tornado ...Tmobile unlocked) with Windows mobile 5 and i cant find a solution..please help me...
When using my laptop wifi connect I set up the following
Network Authentication OPEN
Data Encryption WEP
key is automatically provided (i tick this option)
Enable IEEE 802.1x authentication for this network
EAP Type as PEAP.
Then under configuration of PEAP I uncheck Validate Server Certificate and authentication method selected as "Secured password (EAP-MSCHAP v2) and "enable fast reconnect" is also ticked.
With these settings it works perfectly well in laptop. But with these settings made in the SDA phone it gives the following error msgs ; "The server certificate is issued by an unknown authority" and "Cannot log on to the wireless network. This network requires a personal certificate to positively identify you."
I have done the registry edit (adding DWORD ValidateServCert=0). It stopped showing the message ""The server certificate is issued by an unknown authority". But the other msg still comes. Actually for PEAP we wont want personal certificate. I think this is a bug. Then i installed a dummy personal cert to cover this bug. Now no more error msgs, but internet is not connected.
Then i installed the root certificate (specific for my univ) i got from my laptop (windows xp). But no effect. I checked under root cert to see if it is there and i saw it there.
Sorry for this long story sometimes we need long explanations to fully understand the problem.
SOMEBODY PLEASE HELP ....
try using a key that is not provided automatically. May not be the fix you want, but it works for me (never tried doing it your way).
For HRPD systems (1xEV-DO 0, a, b, etc.), I am having difficulty understanding when an access terminal receives the SID of an access network. In 1xRTT, the SID is being constantly broadcast on the Sync channel with a Sync message. In HRPD, the Sync message is constantly broadcast on the Control Channel but the data fields are only 1) MessageID, 2) MaximumRevision, 3) MinimumRevision, 4) PilotPN and 5) SystemTime.
I see that the HRPD Location Updata procedure in the Application layer provides a way for the access terminal to request the SID of the access network but I assume that I must be missing something. Why would HRPD systems be designed to allow for obtaining the SID ONLY after a session has been established? If the access terminal's perferred roaming list has PREF_ONLY=1 and the access network of which the access terminal is attempting to connect has its SID set as PREF_NEG=0 then it has to go all the way through session establishment just to figure out that the base station it is attempting to access is not one that it is permitted to connect to. It seems so ineffecient, hence the reason why I believe I am confused.
Also, the QuickConfig message and the SectorParameters message of the Overhead Messages Protocol (broadcast on the Control Channel before a session is established) also contain no SID so this does not eliminate the need to establish a session in order for the access terminal to obtain the SID.
So, do the access networks broadcast their SIDs (prior to a session) in some way that I am missing or in some way that is not in the standards? Do HRPD access terminal manufactures configure the devices to have the capability to obtain the SID before establishing a session and before having to receive it with a unicast message after session establishment?
I appreciate any help and references to applicable standards. If I am not confused, then what is the point of waiting until a session is established before the access network reveals its SID? I don't see any reason why anyone would want to change from how it was done in 1xRTT.
When hotspot is enabled, internet is available on connected clients, but not on the phone itself.
I did a quick check of the signal and dialed *#*#4636#*#*
Network Type shows LTE, however when clicking "Run ping test", I receive an error messages: IP addr not reachable
The Hostname(www dot google dot com): Fail: Host unreachable.
Meanwhile, the device connected to the phone's hotspot is perfectly fine.
Where can I start to debug this problem?
XDA Visitor said:
When hotspot is enabled, internet is available on connected clients, but not on the phone itself.
I did a quick check of the signal and dialed *#*#4636#*#*
Network Type shows LTE, however when clicking "Run ping test", I receive an error messages: IP addr not reachable
The Hostname(www dot google dot com): Fail: Host unreachable.
Meanwhile, the device connected to the phone's hotspot is perfectly fine.
Where can I start to debug this problem?
Click to expand...
Click to collapse
Greetings!
Thank you for using XDA Assist.
In order for us to help, you must provide your device's make and model.
Thanks.
Android 9 will not connect to our WiFi. I can connect with a windows device. We're using PEAP with MSCHAPV2. Certificate issued by internal CA. CA cert. has been installed on the Android device and it shows it as a CA. Initially I was getting an unknown CA error on the device. Turns out we were issuing SHA1 certs so I corrected that and that error is no longer showing now. Looking at the logcat log I can't find any other information that stands out to me other than "04-27 10:28:50.686 20424 20424 D wpa_supplicant: wlan0: Event DEAUTH (11) received". Packet capture shows the engotiation start between the android device and RADIUS and then RADIUS sends a reject which the code appears to mean an EAP method couldn't be negotiated. I've gone through the RADIUS server over and over and can't find anything wrong on that end and like I said earlier, windows laptops connect fine.
Update: I've got this working now. It was an issue on the Radius/NPS server side. Be sure to have TLS 1.1 and 1.2 enabled properly. There is some innacurate info. out there on the correct Hex values to use.