hopefully simple ppp dns or routing problem on Slack 9.1

Bill Unruh wrote:
> Clifford Kite <kite@see.signature.id> writes:
>
> ]John Gabriele <john3gz@bestwebz.net> wrote:
> ] > Clifford Kite wrote:
> ]
> ] > After I run netconfig to configure my NIC (as if I was using it with a
> ] > static IP on a LAN even though nothing is plugged into it), the only
> ] > changes I see are in:
> ] >
> ] > 1. /etc/hosts -- 127.0.0.1 me.example.net me ==>
> ] > 192.168.0.0 me.example.net me
> ]
> ] I'll take that to mean that these lines appear in /etc/hosts:
> ]
> ] 127.0.0.1 me.example.net me
> ] 192.168.0.0 me.example.net me
> ]
> ] I don't think the first one is a good idea, but there will be some that
> ] agree with me and some that won't. I'd replace the first line with
> ] these two:
> ]
> ] 127.0.0.1 localhost
> ] 127.0.0.2 me.example.net me
>
> I agree with Kite. The first address obtained will be the address used to get name to ip
> mapping. Thus me.example.net will always resolve to 127.0.0.1.

Check. Made the change.

>
> ] > 4. /etc/resolv.conf -- search my_isp.net ==> search example.net (which
> ] > I see can't work (since I'm not running my own DNS server or even a
> ] > LAN).
>
> The search option is more or less useless. you do not need it. What you
> need is the nameserver lines to point to proper DNS IP resolvers, and
> MUST be IP addresses not names.

Yup. I've got numbers in there. Sorry for the confusion.

>
>
> [snip]
>
> You could also try reading
> www.theory.physics.ubc.ca/ppp-linux.html
> which may give you hints as to how to hook up your ppp, and to debug the
> connection.

Thank you. I'll have a read.

> It sounds to me like your pppd never dialing out and making the
> connection, or your ISP expects something you are not sending.
>
> YOur log with time stamps are crucial to figure this out.

Ok, I'll uncomment the "debug" line in /etc/ppp/options and try
to get something more. Are there other log files I need to be looking
at besides /var/log/messages and /var/log/debug?

Can I tell syslog (?) to log more stuff to those files?

Thanks.

John Gabriele <john3gz@bestwebz.net> writes:

]Bill Unruh wrote:
]> Clifford Kite <kite@see.signature.id> writes:
]>
]> ]John Gabriele <john3gz@bestwebz.net> wrote:
]> ] > Clifford Kite wrote:
]> ]
]> ] > After I run netconfig to configure my NIC (as if I was using it with a
]> ] > static IP on a LAN even though nothing is plugged into it), the only
]> ] > changes I see are in:
]> ] >
]> ] > 1. /etc/hosts -- 127.0.0.1 me.example.net me ==>
]> ] > 192.168.0.0 me.example.net me
]> ]
]> ] I'll take that to mean that these lines appear in /etc/hosts:
]> ]
]> ] 127.0.0.1 me.example.net me
]> ] 192.168.0.0 me.example.net me
]> ]
]> ] I don't think the first one is a good idea, but there will be some that
]> ] agree with me and some that won't. I'd replace the first line with
]> ] these two:
]> ]
]> ] 127.0.0.1 localhost
]> ] 127.0.0.2 me.example.net me
]>
]> I agree with Kite. The first address obtained will be the address used to get name to ip
]> mapping. Thus me.example.net will always resolve to 127.0.0.1.

]Check. Made the change.

]>
]> ] > 4. /etc/resolv.conf -- search my_isp.net ==> search example.net (which
]> ] > I see can't work (since I'm not running my own DNS server or even a
]> ] > LAN).
]>
]> The search option is more or less useless. you do not need it. What you
]> need is the nameserver lines to point to proper DNS IP resolvers, and
]> MUST be IP addresses not names.

]Yup. I've got numbers in there. Sorry for the confusion.

]>
]>
]> [snip]
]>
]> You could also try reading
]> www.theory.physics.ubc.ca/ppp-linux.html
]> which may give you hints as to how to hook up your ppp, and to debug the
]> connection.

]Thank you. I'll have a read.

]> It sounds to me like your pppd never dialing out and making the
]> connection, or your ISP expects something you are not sending.
]>
]> YOur log with time stamps are crucial to figure this out.

]Ok, I'll uncomment the "debug" line in /etc/ppp/options and try
]to get something more. Are there other log files I need to be looking
]at besides /var/log/messages and /var/log/debug?

]Can I tell syslog (?) to log more stuff to those files?

Well, make sure you have
daemon.*;local2.* /var/log/ppplog
^^^^^^ or whatever you want to
call it-- maybe debug?

and then do killall -1 syslogd.

debug logs everything in the negotiations.

John Gabriele <john3gz@bestwebz.net> writes:

]Clifford Kite wrote:
]> John Gabriele <john3gz@bestwebz.net> wrote:

]Thanks for the continued replies Cliff. To make this less confusing,
]I'll refer to my actual computer, domain, and isp names (instead of
]the made-up "me" and the default (which is now changed) "example.net").
]I just edited /etc/HOSTNAME and /etc/hosts: My computer is now
]avocado.pinecountry.net. I ran Slack's netconfig again (using this
]new name when prompted) and then ran pppd's "pppsetup" utility again.

]While running netconfig, it asked what my gateway was, and said it
]was ok to leave it blank -- so I did.

]To briefly recap, before running ppp-go, "ifconfig -a" shows eth0 and
]lo only (both show up as being "UP").

]"route -n" tells me

] Destination Gateway Genmask Flags Metric Ref Use Iface
] 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
] 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo

]*After* running ppp-go (during which I can hear and see (modem lights)
]the modem dialing up and negotiating), route -n tells me the same thing
]as it just did. "ifconfig -a" though shows ppp0 now listed after eth0 and
]lo but with no "UP" line (the eth0 and lo entries are the same as before).

Is there an address listed for ppp0?




] 127.0.0.1 localhost
] 127.0.0.2 avocado.pinecountry.net avocado
] 192.168.0.1 avocado.pinecountry.net avocado

I would not have the second. Whenever you ask for the IP for avocado,
127.0.0.2 will be returned (a loopback address).

] search bestweb.net

The search line is usually pretty useless. It is what to use if you hand
your computer just a single undotted name.

] nameserver 209.94.100.100

Well, without a route to it, it is pretty useless.


]>>sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xd18d00f6> <pcomp> <accomp>]

If yuo have those with no response then your ISP at the other end is not
responding. We need to see the rest of the negotiations to see if it is
your fault or the ISP's fault.


] OK
] -- got it
] send (atdt6632120^M)
] timeout set to 75 seconds
] expect (CONNECT)
] ^M
] atdt6632120^M^M
] CONNECT
] -- got it

Are you sure there is nothing after the CONNECT

]------------- then pppd goes on to tell me:

] Serial connection established.
] Using interface ppp0
] Connect: ppp0 <--> /dev/modem

]with nothing about IP addresses (like mine and the ISP's gateway)
]getting set.

Should not be yet. There is a bunch of negotiation yet to do (or debug
output to be logged)



]How can I ask the system to tell me how authentication is going?
]I'd love to see something like "authentication failed/succeeded".

You need the debug option and the above option in /etc/syslog.conf.



]Also, I've got a hub and some cables, but I haven't yet looked into what's
]necessary to make these 2 computers talk to each other.

Ah. If you have ethernet cards on both, you should be able to make them
see each other via the net.

Set up your Linux to be say 192.168.1.1 and the Mac to be 192.168.1.2,
run a null ethernet cable between them (or a regular one from each to
the hub) and connect. Get ssh installed on the mac, make sure it is
installed on your Linux machine, start sshd on the Linux, and then do
scp from teh mac to the linux to copy over the files.



]> If there's no way then please include the timestamps, which sometimes
]> can provide a clue.

]Ok, I'll attempt to copy/past some log file data to this thread.
]Which log files, specifically? /var/log/messages and /var/log/debug?

Wherever you put the debug output from pppd
See the above line I suggest you put into /etc/syslog.conf
If you use my line, then it is the output in /var/log/ppplog.

John Gabriele <john3gz@bestwebz.net> wrote:
> Clifford Kite wrote:
>> John Gabriele <john3gz@bestwebz.net> wrote:

>> I'd recommend you buy the "Running Linux"
>> book published by Dover - it should be worthwhile since you run Slackware.

> I'll have to have a look through the couch cushions and
> see if I can come up with the dough. :) I didn't realize
> that the book had substantial Slackware-related info.

It helped me a lot and I still refer to it occasionally.

> I figure you mean this one (4th edition)
> http://www.powells.com/cgi-bin/bibli...7-0596002726-0
> by Welsh, Kaufman, and Dalheimer -- though it's published by
> O'Reilly rather than Dover.

My bad. It _is_ O'Reilly, the Dover slipped in because, long ago,
it was a source of inexpensive but good books on subjects I was
pursuing then.

Mine is the first edition, but the versions since then should be good
too and provide updated information.

>> My /etc/resolv.conf contains:
>>
>> search ev1
>> options attempts:5 rotate
>> nameserver 216.88.76.6
>> nameserver 216.88.77.7

> Hmm... Ok, I added a 2nd nameserver line (since my isp provides 2,
> and the resolver man page you point out says I can have 3).

>> I'd suggest you read "man 5 resolver" for explanations of the options.

> Thanks for the pointer. I don't see any mention of the "attempts"
> variable for the "options" config option. Only "debug" or "ndots:n".

Maybe you need to update the man pages. Here they contain:

attempts:n
sets the number of times the resolver will send a
query to its name servers before giving up and return-
ing an error to the calling application. The default
is RES_DFLRETRY (see <resolv.h> ).

Actually the options are there to help keep DNS server lookups going
until PPP comes up for IP when using demand dial-out. Otherwise the
application that brought pppd to life will likely exit.

> "chat" just gives me the usual in /var/log/messages:

> ... [snip]

> OK
> -- got it
> send (atdt6632120^M)
> timeout set to 75 seconds
> expect (CONNECT)
> ^M
> atdt6632120^M^M
> CONNECT
> -- got it

I agree with Bill Unruh, there should be one more line at least:

<date, ect>[<chat pid>]: send(<something>)

The very last part of the chat configuration should read

CONNECT \d\c

or similar. Double escapes if on the chat command line.

Not doing this could be causing the problem since otherwise, with some
ISPs, you might get a login prompt or menu that ignores pppd's attempt
at starting LCP negotiations.

> How can I ask the system to tell me how authentication is going?
> I'd love to see something like "authentication failed/succeeded".

You will get that after the PPP negotiations finish authentication.
You don't see anything now because negotiations don't get past the
first stage, LCP (Link Control Protocol).

> The PowerBook has no floppy drive, and I have no external floppy drive.
> I've got a USB flash drive, but when I use OS X to format it (UFS or some
> Windows/DOS format), I can't read the thing in Linux -- and when I format it
> in Linux (ext2), I can't read the thing in OS X.

> I've got a CD burner in the x86 box, but since I've only recently installed
> Slack, I haven't yet even attempted to burn anything with it yet.

That's likely to have a fairly steep learning curve.

> Also, I've got a hub and some cables, but I haven't yet looked into what's
> necessary to make these 2 computers talk to each other.

Bill Unruh's suggestion about a cross-over cable is good. Those should
be bought (it's a pain to make one), are relatively inexpensive, and
are easy to use.

>> If there's no way then please include the timestamps, which sometimes
>> can provide a clue.

> Ok, I'll attempt to copy/past some log file data to this thread.
> Which log files, specifically? /var/log/messages and /var/log/debug?

Follow Bill Unruh's recipe to create a log file that should contain all
the messages. But they may be in /var/log/{debug,messages}, as they
are here.

--
Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* Better is the enemy of good enough. */

Bill Unruh wrote:
> [snip]
>
> Well, make sure you have
> daemon.*;local2.* /var/log/ppplog
> ^^^^^^ or whatever you want to

....in /etc/syslog.conf I figure you mean. Ok, check.

> call it-- maybe debug?
>
> and then do killall -1 syslogd.

Whoops, I restarted the machine instead -- see notes below.

> debug logs everything in the negotiations.
>
>

Ok, hooked up the hub so now I can ssh into the Slack box from OS X. Neither scp nor
rcp work for me, but I can cat files to the terminal window and copy/paste so that's
good enough for now. :)

Uncommented the "debug" line in both /etc/ppp/options and options.demand.
Added the line:
daemon.*;local2.* -/var/log/ppplog
to my /etc/syslog.conf, then restarted stuff with
root# cd /etc/rc.d
root# ./rc.inet2 stop
root# ./rc.inet1 stop
root# ./rc.inet1 start
root# ./rc.inet2 start
touched /var/log/ppplog.
Opened up three xterms to "tail -f" /var/log{messages,debug,ppplog}

Hmm... nothing going to ppplog. Restarting the machine (forgot about Bill's
"killall" advice)...

Once restarted, the following log files show what happens when I run ppp-go.
Note, once "connected", I try a couple of pings, wait about 20 seconds, then
disconnect (with ppp-off at time: 14:00:03).

john@avocado:~$ cat messages.txt
Apr 23 13:47:46 avocado kernel: mice: PS/2 mouse device common for all mice
Apr 23 13:47:46 avocado sshd[931]: Server listening on 0.0.0.0 port 22.
Apr 23 13:47:56 avocado kernel: lp0: using parport0 (polling).
Apr 23 13:52:14 avocado kernel: [drm] AGP 0.99 aperture @ 0xd0000000 64MB
Apr 23 13:52:14 avocado kernel: [drm] Initialized mga 3.1.0 20021029 on minor 0
Apr 23 13:52:18 avocado gconfd (john-1010): starting (version 2.4.0.1), pid 1010 user 'john'
Apr 23 13:52:19 avocado gconfd (john-1010): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Apr 23 13:52:19 avocado gconfd (john-1010): Resolved address
"xml:readwrite:/home/john/.gconf" to a writable config source at position 1
Apr 23 13:52:19 avocado gconfd (john-1010): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Apr 23 13:52:30 avocado kernel: cdrom: This disc doesn't have any tracks I recognize!
Apr 23 13:58:48 avocado kernel: CSLIP: code copyright 1989 Regents of the University of
California
Apr 23 13:58:48 avocado kernel: PPP generic driver version 2.4.2
Apr 23 13:58:48 avocado pppd[1085]: pppd 2.4.1 started by root, uid 0
Apr 23 13:58:49 avocado chat[1088]: timeout set to 60 seconds
Apr 23 13:58:49 avocado chat[1088]: abort on (ERROR)
Apr 23 13:58:49 avocado chat[1088]: abort on (BUSY)
Apr 23 13:58:49 avocado chat[1088]: abort on (NO CARRIER)
Apr 23 13:58:49 avocado chat[1088]: abort on (NO DIALTONE)
Apr 23 13:58:49 avocado chat[1088]: send (AT&FH0^M)
Apr 23 13:58:49 avocado chat[1088]: expect (OK)
Apr 23 13:58:49 avocado chat[1088]: AT&FH0^M^M
Apr 23 13:58:49 avocado chat[1088]: OK
Apr 23 13:58:49 avocado chat[1088]: -- got it
Apr 23 13:58:49 avocado chat[1088]: send (atdt6632166^M)
Apr 23 13:58:50 avocado chat[1088]: timeout set to 75 seconds
Apr 23 13:58:50 avocado chat[1088]: expect (CONNECT)
Apr 23 13:58:50 avocado chat[1088]: ^M
Apr 23 13:59:17 avocado chat[1088]: atdt6632166^M^M
Apr 23 13:59:17 avocado chat[1088]: CONNECT
Apr 23 13:59:17 avocado chat[1088]: -- got it
Apr 23 13:59:17 avocado pppd[1085]: Serial connection established.
Apr 23 13:59:17 avocado pppd[1085]: Using interface ppp0
Apr 23 13:59:17 avocado pppd[1085]: Connect: ppp0 <--> /dev/modem
Apr 23 14:00:03 avocado pppd[1085]: Terminating on signal 2.
Apr 23 14:00:03 avocado pppd[1085]: Connection terminated.
Apr 23 14:00:04 avocado pppd[1085]: Exit.
john@avocado:~$


john@avocado:~$ cat debug.txt
Apr 22 22:15:33 avocado kernel: CPU: After generic, caps: 0183f9ff c1c7f9ff 00000000
00000000
Apr 22 22:15:33 avocado kernel: CPU: Common caps: 0183f9ff c1c7f9ff 00000000
00000000
Apr 23 13:01:01 avocado kernel: CPU: After generic, caps: 0183f9ff c1c7f9ff 00000000
00000000
Apr 23 13:01:01 avocado kernel: CPU: Common caps: 0183f9ff c1c7f9ff 00000000
00000000
Apr 23 13:14:39 avocado in.identd[1062]: started
Apr 23 13:43:27 avocado pppd[1251]: using channel 1
Apr 23 13:43:28 avocado pppd[1251]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic
0xd83b4aaa> <pcomp> <accomp>]
Apr 23 13:43:55 avocado last message repeated 9 times
Apr 23 13:47:46 avocado kernel: CPU: After generic, caps: 0183f9ff c1c7f9ff 00000000
00000000
Apr 23 13:47:46 avocado kernel: CPU: Common caps: 0183f9ff c1c7f9ff 00000000
00000000
Apr 23 13:59:17 avocado pppd[1085]: using channel 1
Apr 23 13:59:18 avocado pppd[1085]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic
0xdd58b32e> <pcomp> <accomp>]
Apr 23 13:59:46 avocado last message repeated 9 times
john@avocado:~$



john@avocado:~$ cat ppplog.txt
Apr 23 13:52:10 avocado modprobe: modprobe: Can't locate module char-major-10-134
Apr 23 13:52:14 avocado modprobe: modprobe: Can't locate module char-major-226
Apr 23 13:52:14 avocado last message repeated 3 times
Apr 23 13:58:48 avocado pppd[1085]: pppd 2.4.1 started by root, uid 0
Apr 23 13:58:49 avocado chat[1088]: timeout set to 60 seconds
Apr 23 13:58:49 avocado chat[1088]: abort on (ERROR)
Apr 23 13:58:49 avocado chat[1088]: abort on (BUSY)
Apr 23 13:58:49 avocado chat[1088]: abort on (NO CARRIER)
Apr 23 13:58:49 avocado chat[1088]: abort on (NO DIALTONE)
Apr 23 13:58:49 avocado chat[1088]: send (AT&FH0^M)
Apr 23 13:58:49 avocado chat[1088]: expect (OK)
Apr 23 13:58:49 avocado chat[1088]: AT&FH0^M^M
Apr 23 13:58:49 avocado chat[1088]: OK
Apr 23 13:58:49 avocado chat[1088]: -- got it
Apr 23 13:58:49 avocado chat[1088]: send (atdt6632166^M)
Apr 23 13:58:50 avocado chat[1088]: timeout set to 75 seconds
Apr 23 13:58:50 avocado chat[1088]: expect (CONNECT)
Apr 23 13:58:50 avocado chat[1088]: ^M
Apr 23 13:59:17 avocado chat[1088]: atdt6632166^M^M
Apr 23 13:59:17 avocado chat[1088]: CONNECT
Apr 23 13:59:17 avocado chat[1088]: -- got it
Apr 23 13:59:17 avocado pppd[1085]: Serial connection established.
Apr 23 13:59:17 avocado pppd[1085]: using channel 1
Apr 23 13:59:17 avocado pppd[1085]: Using interface ppp0
Apr 23 13:59:17 avocado pppd[1085]: Connect: ppp0 <--> /dev/modem
Apr 23 13:59:18 avocado pppd[1085]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic
0xdd58b32e> <pcomp> <accomp>]
Apr 23 13:59:46 avocado last message repeated 9 times
Apr 23 13:59:49 avocado pppd[1085]: LCP: timeout sending Config-Requests
Apr 23 14:00:03 avocado pppd[1085]: Terminating on signal 2.
Apr 23 14:00:03 avocado pppd[1085]: Connection terminated.
Apr 23 14:00:04 avocado pppd[1085]: Exit.
john@avocado:~$

Bill Unruh wrote:
> [snip]
>
> ]"route -n" tells me
>
> ] Destination Gateway Genmask Flags Metric Ref Use Iface
> ] 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
> ] 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
>
> ]*After* running ppp-go (during which I can hear and see (modem lights)
> ]the modem dialing up and negotiating), route -n tells me the same thing
> ]as it just did. "ifconfig -a" though shows ppp0 now listed after eth0 and
> ]lo but with no "UP" line (the eth0 and lo entries are the same as before).
>
> Is there an address listed for ppp0?
>

root@avocado /home/john # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo


root@avocado /home/john # ifconfig -a
eth0 Link encap:Ethernet HWaddr [*edited out by me*]
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0x2000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:100 (100.0 b) TX bytes:100 (100.0 b)

ppp0 Link encap:Point-to-Point Protocol
POINTOPOINT NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:1 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


root@avocado /home/john #


>
>
>
> ] 127.0.0.1 localhost
> ] 127.0.0.2 avocado.pinecountry.net avocado
> ] 192.168.0.1 avocado.pinecountry.net avocado
>
> I would not have the second. Whenever you ask for the IP for avocado,
> 127.0.0.2 will be returned (a loopback address).

Check. Commented it out.

>
> ] search bestweb.net
>
> The search line is usually pretty useless. It is what to use if you hand
> your computer just a single undotted name.
>

Check. Commented that line out.

> ] nameserver 209.94.100.100
>
> Well, without a route to it, it is pretty useless.
>

?

>
>[snip]
>
> ]Also, I've got a hub and some cables, but I haven't yet looked into what's
> ]necessary to make these 2 computers talk to each other.
>
> Ah. If you have ethernet cards on both, you should be able to make them
> see each other via the net.
>
> Set up your Linux to be say 192.168.1.1 and the Mac to be 192.168.1.2,
> run a null ethernet cable between them (or a regular one from each to
> the hub) and connect. Get ssh installed on the mac, make sure it is
> installed on your Linux machine, start sshd on the Linux, and then do
> scp from teh mac to the linux to copy over the files.

Thanks for the tips! As mentioned in my other post, I can now ssh from
my laptop to the Slackware box. :)

Clifford Kite wrote:

> [snip]
>
>>>My /etc/resolv.conf contains:
>>>
>>>search ev1
>>>options attempts:5 rotate
>>>nameserver 216.88.76.6
>>>nameserver 216.88.77.7
>
> [snip]
>
>>>I'd suggest you read "man 5 resolver" for explanations of the options.
>
>
>>Thanks for the pointer. I don't see any mention of the "attempts"
>>variable for the "options" config option. Only "debug" or "ndots:n".
>
>
> Maybe you need to update the man pages. Here they contain:
>
> attempts:n
> sets the number of times the resolver will send a
> query to its name servers before giving up and return-
> ing an error to the calling application. The default
> is RES_DFLRETRY (see <resolv.h> ).
>
> Actually the options are there to help keep DNS server lookups going
> until PPP comes up for IP when using demand dial-out. Otherwise the
> application that brought pppd to life will likely exit.

Ok, I added the options line to my /etc/resolve.conf, and with Bill's
recent advice too, it now says:

#search bestweb.net
options attempts:5 rotate
nameserver 209.94.100.100
nameserver 209.94.100.200

I restarted the machine and tried to connect again but still have
the same problem.

> [snip]
>
> The very last part of the chat configuration should read
>
> CONNECT \d\c
>
> or similar. Double escapes if on the chat command line.
>
> Not doing this could be causing the problem since otherwise, with some
> ISPs, you might get a login prompt or menu that ignores pppd's attempt
> at starting LCP negotiations.
>

???

Hmm... this could be something. My /etc/ppp/pppscript just ends with that
one CONNECT line. There's nothing funny after it. I've tried with and without
a newline after it, but it (thankfully :) doesn't seem to make a difference.
(Note -- I've been on a software project where a module was bombing because
of an extra newline at the end of a config file. Yikes.)

Wait... I think there's a space character after the word CONNECT. Ack, now
how do I get vim to show me this file in hex...

John Gabriele <john3gz@bestwebz.net> wrote:

> Ok, hooked up the hub so now I can ssh into the Slack box from
> OS X. Neither scp nor rcp work for me, but I can cat files to the
> terminal window and copy/paste so that's good enough for now. :)

Alright!

> Uncommented the "debug" line in both /etc/ppp/options and options.demand.
> Added the line:
> daemon.*;local2.* -/var/log/ppplog
> to my /etc/syslog.conf, then restarted stuff with
> root# cd /etc/rc.d
> root# ./rc.inet2 stop
> root# ./rc.inet1 stop
> root# ./rc.inet1 start
> root# ./rc.inet2 start

Unless these files have been modified and start/stop arguments added,
they are equivalent to doing ./rc.inet? twice. This is Slackware..

As you found out, logging didn't work without the "killall -1 syslogd"
or rebooting (restarting?).

> touched /var/log/ppplog.
> Opened up three xterms to "tail -f" /var/log{messages,debug,ppplog}

> Hmm... nothing going to ppplog. Restarting the machine (forgot about Bill's
> "killall" advice)...

> Once restarted, the following log files show what happens when I run ppp-go.
> Note, once "connected", I try a couple of pings, wait about 20 seconds, then
> disconnect (with ppp-off at time: 14:00:03).

....

> john@avocado:~$ cat ppplog.txt
> Apr 23 13:52:10 avocado modprobe: modprobe: Can't locate module
> char-major-10-134
> Apr 23 13:52:14 avocado modprobe: modprobe: Can't locate module
> char-major-226
> Apr 23 13:52:14 avocado last message repeated 3 times
> Apr 23 13:58:48 avocado pppd[1085]: pppd 2.4.1 started by root, uid 0
> Apr 23 13:58:49 avocado chat[1088]: timeout set to 60 seconds
> Apr 23 13:58:49 avocado chat[1088]: abort on (ERROR)
> Apr 23 13:58:49 avocado chat[1088]: abort on (BUSY)
> Apr 23 13:58:49 avocado chat[1088]: abort on (NO CARRIER)
> Apr 23 13:58:49 avocado chat[1088]: abort on (NO DIALTONE)
> Apr 23 13:58:49 avocado chat[1088]: send (AT&FH0^M)
> Apr 23 13:58:49 avocado chat[1088]: expect (OK)
> Apr 23 13:58:49 avocado chat[1088]: AT&FH0^M^M

The old Hayes standard defined H0 as a signal to the modem to hang up.
But everything below looks okay for chat so either the definition has
changed or is not accepted when appended to AT&F .

> Apr 23 13:58:49 avocado chat[1088]: OK
> Apr 23 13:58:49 avocado chat[1088]: -- got it
> Apr 23 13:58:49 avocado chat[1088]: send (atdt6632166^M)
> Apr 23 13:58:50 avocado chat[1088]: timeout set to 75 seconds
> Apr 23 13:58:50 avocado chat[1088]: expect (CONNECT)
> Apr 23 13:58:50 avocado chat[1088]: ^M
> Apr 23 13:59:17 avocado chat[1088]: atdt6632166^M^M
> Apr 23 13:59:17 avocado chat[1088]: CONNECT
> Apr 23 13:59:17 avocado chat[1088]: -- got it
> Apr 23 13:59:17 avocado pppd[1085]: Serial connection established.
> Apr 23 13:59:17 avocado pppd[1085]: using channel 1
> Apr 23 13:59:17 avocado pppd[1085]: Using interface ppp0
> Apr 23 13:59:17 avocado pppd[1085]: Connect: ppp0 <--> /dev/modem
> Apr 23 13:59:18 avocado pppd[1085]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
> <magic 0xdd58b32e> <pcomp> <accomp>]
> Apr 23 13:59:46 avocado last message repeated 9 times
> Apr 23 13:59:49 avocado pppd[1085]: LCP: timeout sending Config-Requests
> Apr 23 14:00:03 avocado pppd[1085]: Terminating on signal 2.
> Apr 23 14:00:03 avocado pppd[1085]: Connection terminated.
> Apr 23 14:00:04 avocado pppd[1085]: Exit.
> john@avocado:~$

PPP negotiation still doesn't get past LCP negotiation. It looks like
the ISP simply didn't start PPP. If ending the chat script correctly
doesn't work then do "killall -TERM pppd" and add the pppd option dryrun
so we can see the options pppd actually uses. On restarting pppd the
desired output is sent to the console and pppd should exit.

--
Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/

Clifford Kite <kite@see.signature.id> wrote in message news:<6u9b6c.36i.ln@corncob.localhost.tld>...
> John Gabriele <john3gz@bestwebz.net> wrote:
> > Clifford Kite wrote:
> >> John Gabriele <john3gz@bestwebz.net> wrote:
>
> >> I'd recommend you buy the "Running Linux"
> >> book published by Dover - it should be worthwhile since you run Slackware.
>
> > I'll have to have a look through the couch cushions and
> > see if I can come up with the dough. :) I didn't realize
> > that the book had substantial Slackware-related info.
>
> It helped me a lot and I still refer to it occasionally.
>
> > I figure you mean this one (4th edition)
> > http://www.powells.com/cgi-bin/bibli...7-0596002726-0
> > by Welsh, Kaufman, and Dalheimer -- though it's published by
> > O'Reilly rather than Dover.
>
> My bad. It _is_ O'Reilly, the Dover slipped in because, long ago,
> it was a source of inexpensive but good books on subjects I was
> pursuing then.
>
> Mine is the first edition, but the versions since then should be good
> too and provide updated information.
>
> >> My /etc/resolv.conf contains:
> >>
> >> search ev1
> >> options attempts:5 rotate
> >> nameserver 216.88.76.6
> >> nameserver 216.88.77.7
>
> > Hmm... Ok, I added a 2nd nameserver line (since my isp provides 2,
> > and the resolver man page you point out says I can have 3).
>
> >> I'd suggest you read "man 5 resolver" for explanations of the options.
>
> > Thanks for the pointer. I don't see any mention of the "attempts"
> > variable for the "options" config option. Only "debug" or "ndots:n".
>
> Maybe you need to update the man pages. Here they contain:
>
> attempts:n
> sets the number of times the resolver will send a
> query to its name servers before giving up and return-
> ing an error to the calling application. The default
> is RES_DFLRETRY (see <resolv.h> ).
>
> Actually the options are there to help keep DNS server lookups going
> until PPP comes up for IP when using demand dial-out. Otherwise the
> application that brought pppd to life will likely exit.
>
> > "chat" just gives me the usual in /var/log/messages:
>
> > ... [snip]
>
> > OK
> > -- got it
> > send (atdt6632120^M)
> > timeout set to 75 seconds
> > expect (CONNECT)
> > ^M
> > atdt6632120^M^M
> > CONNECT
> > -- got it
>
> I agree with Bill Unruh, there should be one more line at least:
>
> <date, ect>[<chat pid>]: send(<something>)
>
> The very last part of the chat configuration should read
>
> CONNECT \d\c
>
> or similar. Double escapes if on the chat command line.
>
> Not doing this could be causing the problem since otherwise, with some
> ISPs, you might get a login prompt or menu that ignores pppd's attempt
> at starting LCP negotiations.
>
> > How can I ask the system to tell me how authentication is going?
> > I'd love to see something like "authentication failed/succeeded".
>
> You will get that after the PPP negotiations finish authentication.
> You don't see anything now because negotiations don't get past the
> first stage, LCP (Link Control Protocol).
>
> > The PowerBook has no floppy drive, and I have no external floppy drive.
> > I've got a USB flash drive, but when I use OS X to format it (UFS or some
> > Windows/DOS format), I can't read the thing in Linux -- and when I format it
> > in Linux (ext2), I can't read the thing in OS X.
>
> > I've got a CD burner in the x86 box, but since I've only recently installed
> > Slack, I haven't yet even attempted to burn anything with it yet.
>
> That's likely to have a fairly steep learning curve.
>
> > Also, I've got a hub and some cables, but I haven't yet looked into what's
> > necessary to make these 2 computers talk to each other.
>
> Bill Unruh's suggestion about a cross-over cable is good. Those should
> be bought (it's a pain to make one), are relatively inexpensive, and
> are easy to use.
>
> >> If there's no way then please include the timestamps, which sometimes
> >> can provide a clue.
>
> > Ok, I'll attempt to copy/past some log file data to this thread.
> > Which log files, specifically? /var/log/messages and /var/log/debug?
>
> Follow Bill Unruh's recipe to create a log file that should contain all
> the messages. But they may be in /var/log/{debug,messages}, as they
> are here.
**

Here is the output of my route -n and ifconfig -a

root@wmr_srv01:~ # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
69.19.219.148 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 69.19.219.148 0.0.0.0 UG 0 0 0 ppp0

It looks like you are connected to the modem, but not to the server.
you are missing the IP address on the ppp0 interface.


root@wmr_srv01:~ # ifconfig -a
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:30 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1500 (1.4 Kb) TX bytes:1500 (1.4 Kb)

ppp0 Link encap:Point-to-Point Protocol
inet addr:66.81.27.54 P-t-P:69.19.219.148 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1524 Metric:1
RX packets:1724 errors:0 dropped:0 overruns:0 frame:0
TX packets:1274 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:1757393 (1.6 Mb) TX bytes:284191 (277.5 Kb)

Have you uncommented the debug in the /etc/ppp/options script?
This will give you extensive error messages.
Walt R.

Clifford Kite wrote:
> John Gabriele <john3gz@bestwebz.net> wrote:
>
>
>>Ok, hooked up the hub so now I can ssh into the Slack box from
>>OS X. Neither scp nor rcp work for me, but I can cat files to the
>>terminal window and copy/paste so that's good enough for now. :)
>
>
> Alright!

Thanks! I was pretty pleased with myself! :)

>
>>Uncommented the "debug" line in both /etc/ppp/options and options.demand.
>>Added the line:
>> daemon.*;local2.* -/var/log/ppplog
>>to my /etc/syslog.conf, then restarted stuff with
>> root# cd /etc/rc.d
>> root# ./rc.inet2 stop
>> root# ./rc.inet1 stop
>> root# ./rc.inet1 start
>> root# ./rc.inet2 start
>
>
> Unless these files have been modified and start/stop arguments added,
> they are equivalent to doing ./rc.inet? twice. This is Slackware..

Whoops. Correct you are. Although /etc/rc.d/rc.inet1 accepts start/stop
args, rc.inet2 does not (it just ignores any you pass it).

> As you found out, logging didn't work without the "killall -1 syslogd"
> or rebooting (restarting?).

Sorry for the sloppy language: I rebooted (since I wasn't exactly sure
if /etc/rc.inet1 stop, then start restarted everything.

>
>>touched /var/log/ppplog.
>>Opened up three xterms to "tail -f" /var/log{messages,debug,ppplog}
>
>
>>Hmm... nothing going to ppplog. Restarting the machine (forgot about Bill's
>>"killall" advice)...

Right. Should've writted "Rebooting" instead of "Restarting".

>
>
>>Apr 23 13:58:49 avocado chat[1088]: AT&FH0^M^M
>
>
> The old Hayes standard defined H0 as a signal to the modem to hang up.
> But everything below looks okay for chat so either the definition has
> changed or is not accepted when appended to AT&F .

Ok, I removed the H0 from that line in /etc/ppp/pppscript so now
it just reads

"" "AT&F"

Restarted networking by running "/etc/rc.d/rc.inet1 stop" then again
with "start". Tried dialing up but still the same problem, so I'm putting
the H0 back in.

>
>>Apr 23 13:58:49 avocado chat[1088]: OK
>>Apr 23 13:58:49 avocado chat[1088]: -- got it
>>Apr 23 13:58:49 avocado chat[1088]: send (atdt6632166^M)
>>Apr 23 13:58:50 avocado chat[1088]: timeout set to 75 seconds
>>Apr 23 13:58:50 avocado chat[1088]: expect (CONNECT)
>>Apr 23 13:58:50 avocado chat[1088]: ^M
>>Apr 23 13:59:17 avocado chat[1088]: atdt6632166^M^M
>>Apr 23 13:59:17 avocado chat[1088]: CONNECT
>>Apr 23 13:59:17 avocado chat[1088]: -- got it
>>Apr 23 13:59:17 avocado pppd[1085]: Serial connection established.
>>Apr 23 13:59:17 avocado pppd[1085]: using channel 1
>>Apr 23 13:59:17 avocado pppd[1085]: Using interface ppp0
>>Apr 23 13:59:17 avocado pppd[1085]: Connect: ppp0 <--> /dev/modem
>>Apr 23 13:59:18 avocado pppd[1085]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
>><magic 0xdd58b32e> <pcomp> <accomp>]
>>Apr 23 13:59:46 avocado last message repeated 9 times
>>Apr 23 13:59:49 avocado pppd[1085]: LCP: timeout sending Config-Requests
>>Apr 23 14:00:03 avocado pppd[1085]: Terminating on signal 2.
>>Apr 23 14:00:03 avocado pppd[1085]: Connection terminated.
>>Apr 23 14:00:04 avocado pppd[1085]: Exit.
>>john@avocado:~$
>
>
> PPP negotiation still doesn't get past LCP negotiation. It looks like
> the ISP simply didn't start PPP. If ending the chat script correctly
> doesn't work

Hm? Everything seems to end just fine when I run /usr/sbin/ppp-off.
That line above that says "Terminating on signal 2." is what happens
when I run ppp-off.

> then do "killall -TERM pppd"

# killall -TERM pppd
pppd: no process killed

> and add the pppd option dryrun
> so we can see the options pppd actually uses.

Hmm... well, there's a line in the ppp-go script that includes:

/usr/sbin/pppd -detach connect "/usr/sbin/chat -v -f /etc/ppp/pppscript" &

so I figure what you mean is, that I should just run a line like that, but
with the dryrun option (and without backgrounding it). Doing that yields
(on the command line where I ran the command from):


root@avocado /etc/ppp # pppd -detach connect \
"/usr/sbin/chat -v -f /etc/ppp/pppscript" dryrun

pppd options in effect:
debug # (from /etc/ppp/options)
-detach # (from command line)
dryrun # (from command line)
name john3gz@bestwebz.net # (from /etc/ppp/options)
/dev/modem # (from /etc/ppp/options)
115200 # (from /etc/ppp/options)
lock # (from /etc/ppp/options)
connect /usr/sbin/chat -v -f /etc/ppp/pppscript # (from command line)
crtscts # (from /etc/ppp/options)
modem # (from /etc/ppp/options)
asyncmap 0 # (from /etc/ppp/options)
passive # (from /etc/ppp/options)
noipdefault # (from /etc/ppp/options)
defaultroute # (from /etc/ppp/options)
root@avocado /etc/ppp #



(note, I'm spam-proofing my email address for the newsgroup posting, even
though in real life my correct email address is being used) and this in
/var/log/ppplog:

Apr 23 18:32:58 avocado pppd[1219]: pppd options in effect:
Apr 23 18:32:58 avocado pppd[1219]: debug^I^I# (from /etc/ppp/options)
Apr 23 18:32:58 avocado pppd[1219]: -detach^I^I# (from command line)
Apr 23 18:32:58 avocado pppd[1219]: dryrun^I^I# (from command line)
Apr 23 18:32:58 avocado pppd[1219]: name john3gz@bestwebz.net^I^I# (from /etc/ppp/options)
Apr 23 18:32:58 avocado pppd[1219]: /dev/modem^I^I# (from /etc/ppp/options)
Apr 23 18:32:58 avocado pppd[1219]: 115200^I^I# (from /etc/ppp/options)
Apr 23 18:32:58 avocado pppd[1219]: lock^I^I# (from /etc/ppp/options)
Apr 23 18:32:58 avocado pppd[1219]: connect /usr/sbin/chat -v -f /etc/ppp/pppscript^I^I#
(from command line)
Apr 23 18:32:58 avocado pppd[1219]: crtscts^I^I# (from /etc/ppp/options)
Apr 23 18:32:58 avocado pppd[1219]: modem^I^I# (from /etc/ppp/options)
Apr 23 18:32:58 avocado pppd[1219]: asyncmap 0^I^I# (from /etc/ppp/options)
Apr 23 18:32:58 avocado pppd[1219]: passive^I^I# (from /etc/ppp/options)
Apr 23 18:32:58 avocado pppd[1219]: noipdefault^I^I# (from /etc/ppp/options)
Apr 23 18:32:58 avocado pppd[1219]: defaultroute^I^I# (from /etc/ppp/options)
Apr 23 18:32:59 avocado pppd[1219]: Exit.

> On restarting pppd the
> desired output is sent to the console and pppd should exit.
>

Yup.

One thing to note is how my ISP requires that I use my email address (username
plus their domain name) to login with. Though, not sure if that might be an
issue here.

Oh, and that character after CONNECT in my pppscript was just a space. I removed
it. No change.

I'm still reading Bill's "How to Hook up PPP in Linux" doc.