On 12 Dec 2014 22:34:50 -0400, in the Usenet newsgroups comp.protocols.ppp and
comp.os.linux.networking, in article <87r3w4s...@bogus.nodomain.nowhere>,
Mike Spencer wrote:
>Moe Trin <ibup...@painkiller.example.tld.invalid> wrote:
>>> Mike Spencer wrote:
>> Are you using the "same" dialin scripts?
>No. The other, still locally managed, ISP is still using text mode
Wow! How do they get windoze boxes to connect? If they're using the
ordinary windoze Dial-Up-Networking app, that's a non-text mode, and
you're very lucky that the ISP went the extra mile to configure the
>> 1. TEMPORARILY rename /etc/ppp/options to /etc/ppp/OPTIONS to get
>> it out of the way.
>Not relevant if the connection is never getting far enough into LCP to
>negotiate PAP (or CHAP or whatever).
Actually, it depends on what you've got in there. The file is read
when the pppd program starts, not when it needs a particular variable.
The idea was to avoid accidental confusion.
>> PROBABLY not needed
>My pap-secrets file has:
> <username> "istar" <password>
>I think if I replaced "istar" with "*", then "remotename istar"
>wouldn't be needed in the pppd invocation. Otherwise, it is needed.
Correct. I use the 'user' option to select the right secret to use
(like you, I have multiple ISPs, and my single dialing script takes
a number to specify which of <currently> 16 phone-numbers/ISPs to use
OR the word "next" to use the "next" number in rotation).
>> 2. Run the following (enormous) one-line script.
>Bingo! That connects. I owe you a beer (or Laphroig or other
>beverage of choice) should you be in Nova Scotia.
Haven't been there in maybe 35 years, but glad to be able to help.
>So: doing extensive, if not *quite* exhaustive, testing, it appears
>that the source of the problem was the "escape FF" option to pppd.
James? I _think_ that might work if you used "escape 0xff", but
the usual mantra is "if you don't KNOW you need it, don't use it". (My
"C" language skills are decidedly "emergency use only", and I don't
see the clues I need in the ppp-2.4.7/pppd/options.c source file.)
>I have no recollection where that (or the other "not needed")
>elements came from, lost in the distant past after several changes,
>alarums and excursions.
That's partly why I always recommend using that "one-liner" to see if
you can get things working.
>So now I've ported your one-liner into a stripped-down script to call
>pppd which in turn references another that runs your chat invocation.
That will work!
>An aside on the modem init: The Win-XP log *does* show the modem init
>strings XP uses. I see some that don't appear in any of the Hayes or
>USR docs I have:
Supposedly, microsoft did query the various modem manufacturers to try
to get "best" strings, to use, but that assumes windoze can ID the
modem (or the user manages to tell windoze the right stuff). I've
found using the factory defaults works every time. "A" problem about
using ATZ is that it may pull up a "saved" configuration (AT&Wn on USR
modems) that was b0rken accidentally. On the other hand, virtually
every modem knows ATZ, but not all have a AT&Fn or equal.
>I see some that don't appear in any of the Hayes or USR docs I have:
> +MR=2; +DR=1; +ER=1; +ES=3,0,2;
> +DS=3; +IFC=2,2;
Plus commands are often Rockwell chip-set, and refer to FAX modes.
Rockwell - report DCE speed on connect, rather than DTE (port) speed.
Got me there - not in any of my books
>> ...I have a dial-up account with an ISP that has nine "local"
>> access numbers that actually connect to three different
>> Point-Of-Presence providers
>Isn't that nice? :-\ With my two completely differentr ISPs, I have a
>script, called from each of the scripts that starts a connection to
>one or the other ISP, that swaps in the right version of
>/etc/mail/mailertable.db so sendmail will go to the right smarthost
>for outgoing mail.
[fermi ~]$ wc /usr/local/bin/dialin
189 539 5055 /usr/local/bin/dialin
[fermi ~]$ wc /etc/ppp/ip-*local
31 167 984 /etc/ppp/ip-down.local
127 640 4492 /etc/ppp/ip-up.local
158 807 5476 total
Lots of 'if elif else' and and a couple of case statements. ;-)
>> Sounds like it's time to find another ISP.
>Easier said than done where I am. With a lot of bother (with
>antennae, cables, poles, guys in the yard trying to get signal
>somewhere) I could have wireless broadband, just one notch faster
>than the very slowest of wired broadband services.
In 1996, we got transferred to Phoenix, Arizona, which is not all that
bad, though quite large. I'm about 21 miles North of city hall (but
still 6 miles South of the northern city boundary) which is a bit off
the beaten path. When we moved here, the only options were a not
very reliable (but expensive) wireless link, or the standard copper
telephones. We went with the latter (had three lines - one for phone,
one for "our" modem use, and one provided by my wife's employer for
business use). The local cable company (Cox) finally dragged in some
lines (everything here is underground - we see several thunderstorms
in the Metro area each year that blow down a half mile or so of pole
line). Not to be out-done, the local telco (US West, which was borged
into QWest, which has been bought by CenturyLink) pulled fiber far
enough to set up road-side Remote Access Multiplexers to permit DSL
in the area using existing copper. Currently, CenturyLink has pulled
fiber into the local streets, and is flogging that as the latest
greatest thing ever... (at exorbitant but wildly varying quoted
prices, plus taxes and fees).
>In any case, I've been with the offending ISP since they were a bunch
>of guys I knew doing a startup in Nova Scotia in the mid-90s. IPO'd,
>borged, spun off, mergered, sold, sold again but I'm a long-time
>customer. Better the devil you know than the devil you don't. Frying
>pan/fire etc. I'll have to bite the wax tadpole and do the Rural
>Wireless one of these days.
Yup - know the problem all too well.
>> Code speak for "we don't want your dial-up business - you must
>> upgrade to our new Fiber service".
and now you have an idea where I'm coming from with that. Verizon,
which now owns/operates the copper in the New York city region has
been pushing this one hard. See news://comp.risks/ such as Risks-
Forum Digest Volume 28 issues 01 ("When the Landline Is a Lifeline")
and 20 ("How Verizon lets its copper network decay to force phone
customers onto fiber") as examples.
>Thank you very much for your point-by-point attention.
Glad to be able to help!
>Now, if the torrential rain will just stop, I can get out into the
>yard or the blacksmith shop and do something more productive than
>try to fix something that somebody else broke. (You're in Phoenix?
>Torrential rain is probably not a problem there. :-)
Actually, we had a deluge a couple of weeks ago that flooded out the
Interstate 10 when several underpasses had their drains clogged. And
over this last night, I got 0.35 inches, which brings me to 11.33
inches for the year which is a bit over my 10-year average (10.90
inch). The official City of Phoenix average is 7.66 inch and the
current, 8.35 inches. Most of the rainfall here is thunderstorms
("Cloudburst" from "Grand Canyon Suite" by Ferde Grofe'), so rain
tends to be hit-or-miss. This shows up in the "standard deviation" of
the annual rates - in my case, it's 3.57", and I've seen years with
5.11 to 17.44 inches at the extremes. Phoenix has longer records than
I do, and their extremes are 2.82 (1956) to 19.73 (1905) inches for a
calender year. Hmmm... I hear thunder now... and it is spitting.