Quote:
Originally Posted by dodddummy
- - - - - -
The issue I have isn't with reliable network operation. It's any network operation because I have the dxg drivers on a dx.
|
Makes no difference, since there isn't any "driver" as such.
You must be thinking non-*nix world, maybe even "Winmodem" world (which does have drivers).
There might be some differences in a configuration file (a chance of different network providers) but I have all K2 and DX models and they all work with the local provider.
You are misleading yourself with technical terms that do not apply.
All series 2 devices are 3G-GSM only, no wifi, no 2G fall-back.
I have posted here both the technical manual and the user (command) manual for the QualComm modem used.
Do you recall the modem commands established by Hayes?
That is, the: "AT" command set used by "dial up" modems?
Well, guess what, the QualComm modem (in both the Kindles and in your cell 'phone) are just such "dial up" modems.
The original "AT" command set has been extended over the years to accommodate the requirements of digital cell 'phones but it is only an extension, not something new and different.
As far as Linux is concerned, they are just another "AT" command set modem.
Do not think "Internal WinModem", think "External Complete Modem" (even thought it is internal).
So they are controlled by the pppd deamon and its chat program.
Which use the common *nix control files.
The thing to do is compare those on a working/non-working setups -
Your looking for a borked network access number or some other part of the command sequence that got hosed up by indiscriminate file modifiers.
- - - - -
And of course, you have to prevent your servers from requiring TLS, since neither the series 2 nor series 3 firmwares have that ability, they are all SSL only. (Well, Amazon did issue firmware patches when they went to TLS only on their network - but that is another groddy tail/tale)