On Tue, 17 Feb 2009 12:38:43 -0600, Andy Herkey wrote:

> Shannon McMackin wrote:
>> On Wed, 11 Feb 2009 22:06:35 -0600, Andy Herkey wrote:
>>
>>
>>> Shannon McMackin wrote:
>>>     
>>>> 1st, Andy, I apologize for not getting back to you on FC10.  I've had
>>>> to switch back to Ubuntu.
>>>>
>>>> We had it working on Intrepid.  I don't know for the life of me what
>>>> changed.  I'm using the libs from try3 that you sent me and here's
>>>> the output in the attached file.
>>>>
>>>>
>>> Shannon,
>>> I don't see anything obvious in the output except your provider did
>>> not respond to the request for an IP/DNS addresses properly.  Line 12
>>> should have looked like this from your provider:
>>>     rcvd [IPCP ConfNak id=0x1 <addr 10.67.241.190> <ms-dns1
>>> 172.16.145.103> <ms-dns2 172.16.145.103>] instead it looks like this:
>>>     rcvd [IPCP ConfNak id=0x1 <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
>>> So pppd kept sending requests for a local IP address and DNS servers
>>> until it gave up.
>>>
>>> 1 Connect: ppp0 <--> /dev/pts/1
>>> 2 sent [LCP ConfReq id=0x1 <asyncmap 0x0>] 3 rcvd [LCP ConfReq id=0x0
>>> <asyncmap 0x0> <auth pap>] 4 sent [LCP ConfAck id=0x0 <asyncmap 0x0>
>>> <auth pap>] 5 rcvd [LCP ConfAck id=0x1 <asyncmap 0x0>] 6 sent [PAP
>>> AuthReq id=0x1 user="Mariner-T61" password=<hidden>] 7 rcvd [PAP
>>> AuthAck id=0x1]
>>> 8 PAP authentication succeeded
>>> 9 sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2
>>> 0.0.0.0>] 10 rcvd [IPCP ConfReq id=0x1 <addr 169.254.1.1>] 11 sent
>>> [IPCP ConfAck id=0x1 <addr 169.254.1.1>] 12 rcvd [IPCP ConfNak id=0x1
>>> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>] 13 sent [IPCP ConfReq id=0x2
>>> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>] 14 rcvd [IPCP
>>> ConfNak id=0x2 <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>] 15 sent [IPCP
>>> ConfReq id=0x3 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>] 16
>>> rcvd [IPCP ConfNak id=0x3 <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>] 17 sent
>>> [IPCP ConfReq id=0x4 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2
>>> 0.0.0.0>] 18 rcvd [IPCP ConfNak id=0x4 <ms-dns1 0.0.0.0> <ms-dns2
>>> 0.0.0.0>] 19 sent [IPCP ConfReq id=0x5 <addr 0.0.0.0> <ms-dns1
>>> 0.0.0.0> <ms-dns2 0.0.0.0>] 20 rcvd [IPCP ConfNak id=0x5 <ms-dns1
>>> 0.0.0.0> <ms-dns2 0.0.0.0>] 21 sent [IPCP ConfReq id=0x6 <addr
>>> 0.0.0.0>] 22 rcvd [IPCP ConfNak id=0x6] 23 sent [IPCP ConfReq id=0x7
>>> <addr 0.0.0.0>] 24 rcvd [IPCP ConfNak id=0x7]
>>>
>>>
>>>  From what I see it looks good on your side. Are you still using the
>>> default barry-att_cingular scripts?
>>> Try running "sudo pppd dump debug call barry-att_cingular" so we can
>>> see what options pppd thinks are set.
>>>
>>> - Andy
>>>
>>>
>>>
>>>
>> 
------------------------------------------------------------------------------
>>   
>>> Create and Deploy Rich Internet Apps outside the browser with
>>> Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use
>>> existing skills and code to build responsive, highly engaging
>>> applications that combine the power of local resources and data with
>>> the reach of the web. Download the Adobe AIR SDK and Ajax docs to
>>> start building applications today-http://p.sf.net/sfu/adobe-com
>>>     
>>>     
>> Andy,
>>
>> Here's the output of the debug:
>>
>> pppd options in effect:
>> debug debug          # (from /etc/ppp/peers/barry-att_cingular) 
nodetach                #
>> (from /etc/ppp/peers/barry-att_cingular) dump                # (from 
command line)
>> noauth               # (from /etc/ppp/peers/barry-att_cingular) user 
                # (from
>> /etc/ppp/peers/barry-att_cingular) password ??????           # (from
>> /etc/ppp/peers/barry-att_cingular)
>>              # (from /etc/ppp/options)
>> connect /usr/sbin/chat -f /etc/chatscripts/barry- 
att_cingular.chat               #
>> (from /etc/ppp/peers/barry-att_cingular) pty /usr/sbin/pppob -P
>> 3ewfdsxz             # (from /etc/ppp/peers/barry- att_cingular)
>> nocrtscts            # (from /etc/ppp/peers/barry-att_cingular)
>>              # (from /etc/ppp/options)
>> noaccomp             # (from /etc/ppp/peers/barry-att_cingular) 
asyncmap 0              #
>> (from /etc/ppp/options) nomagic              # (from
>> /etc/ppp/peers/barry-att_cingular) mtu 1492          # (from
>> /etc/ppp/peers/barry-att_cingular) nopcomp           # (from
>> /etc/ppp/peers/barry-att_cingular) passive           # (from
>> /etc/ppp/peers/barry-att_cingular) lcp-echo-failure 999              # 
(from
>> /etc/ppp/peers/barry-att_cingular) lcp-echo-interval 0               # 
(from
>> /etc/ppp/peers/barry-att_cingular) hide-password             # (from
>> /etc/ppp/options) novj               # (from /etc/ppp/peers/barry-
att_cingular)
>> ipcp-accept-local            # (from /etc/ppp/peers/barry-att_cingular)
>> ipcp-accept-remote           # (from /etc/ppp/peers/barry-att_cingular)
>> noipdefault          # (from /etc/ppp/peers/barry-att_cingular) ipcp-
restart 7       
>> # (from /etc/ppp/peers/barry-att_cingular) defaultroute              # 
(from
>> /etc/ppp/peers/barry-att_cingular) proxyarp          # (from /etc/ppp/
options)
>> usepeerdns           # (from /etc/ppp/peers/barry-att_cingular) 
nobsdcomp               #
>> (from /etc/ppp/peers/barry-att_cingular) nodeflate           # (from
>> /etc/ppp/peers/barry-att_cingular) noipx             # (from /etc/ppp/
options)
>>
>> The remainder of the process is the same.  No IP address provided by
>> AT&T.
>>
>>
> Shannon,
> Pleasea send me these two files from you system: /etc/ppp/options
> /etc/ppp/pap-secrets
> 
> Thanks,
> - Andy
> 
> 
> 
------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San
> Francisco, CA -OSBC tackles the biggest issue in open source: Open
> Sourcing the Enterprise -Strategies to boost innovation and cut costs
> with open source participation -Receive a $600 discount off the
> registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H

Here's the file content.  I'm using Pan now for news and I don't see any 
good option to attach a file:

# /etc/ppp/options
# 
# Originally created by Jim Knoble <jmkno...@mercury.interpath.net>
# Modified for Debian by alvar Bray <al...@meiko.co.uk>
# Modified for PPP Server setup by Christoph Lameter <clame...@debian.org>
#
# To quickly see what options are active in this file, use this command:
#   egrep -v '#|^ *$' /etc/ppp/options

# Specify which DNS Servers the incoming Win95 or WinNT Connection should 
use
# Two Servers can be remotely configured
# ms-dns 192.168.1.1
# ms-dns 192.168.1.2

# Specify which WINS Servers the incoming connection Win95 or WinNT 
should use
# ms-wins 192.168.1.50
# ms-wins 192.168.1.51

# Run the executable or shell command specified after pppd has
# terminated the link.  This script could, for example, issue commands
# to the modem to cause it to hang up if hardware modem control signals
# were not available.
#disconnect "chat -- \d+++\d\c OK ath0 OK"

# async character map -- 32-bit hex; each bit is a character
# that needs to be escaped for pppd to receive it.  0x00000001
# represents '\x01', and 0x80000000 represents '\x1f'.
asyncmap 0

# Require the peer to authenticate itself before allowing network
# packets to be sent or received.
# Please do not disable this setting. It is expected to be standard in
# future releases of pppd. Use the call option (see manpage) to disable
# authentication for specific peers.
#auth
noauth
# ... Unfortunately, fixing this properly in the peers file
# (/etc/ppp/peers/ppp0, typically) is apparently incompatible with the
# paradigm used by gnome-system-tools and system-tools-backend for
# managing the peers files.  So in Ubuntu Feisty we change the default.

# Use hardware flow control (i.e. RTS/CTS) to control the flow of data
# on the serial port.
crtscts

# Use software flow control (i.e. XON/XOFF) to control the flow of data
# on the serial port.
#xonxoff

# Specifies that certain characters should be escaped on transmission
# (regardless of whether the peer requests them to be escaped with its
# async control character map).  The characters to be escaped are
# specified as a list of hex numbers separated by commas.  Note that
# almost any character can be specified for the escape option, unlike
# the asyncmap option which only allows control characters to be
# specified.  The characters which may not be escaped are those with hex
# values 0x20 - 0x3f or 0x5e.
#escape 11,13,ff

# Don't use the modem control lines.
#local

# Specifies that pppd should use a UUCP-style lock on the serial device
# to ensure exclusive access to the device.
lock

# Don't show the passwords when logging the contents of PAP packets.
# This is the default.
hide-password

# When logging the contents of PAP packets, this option causes pppd to
# show the password string in the log message.
#show-password

# Use the modem control lines.  On Ultrix, this option implies hardware
# flow control, as for the crtscts option.  (This option is not fully
# implemented.)
modem

# Set the MRU [Maximum Receive Unit] value to <n> for negotiation.  pppd
# will ask the peer to send packets of no more than <n> bytes. The
# minimum MRU value is 128.  The default MRU value is 1500.  A value of
# 296 is recommended for slow links (40 bytes for TCP/IP header + 256
# bytes of data).
#mru 542

# Set the interface netmask to <n>, a 32 bit netmask in "decimal dot"
# notation (e.g. 255.255.255.0).
#netmask 255.255.255.0

# Disables the default behaviour when no local IP address is specified,
# which is to determine (if possible) the local IP address from the
# hostname. With this option, the peer will have to supply the local IP
# address during IPCP negotiation (unless it specified explicitly on the
# command line or in an options file).
#noipdefault

# Enables the "passive" option in the LCP.  With this option, pppd will
# attempt to initiate a connection; if no reply is received from the
# peer, pppd will then just wait passively for a valid LCP packet from
# the peer (instead of exiting, as it does without this option).
#passive

# With this option, pppd will not transmit LCP packets to initiate a
# connection until a valid LCP packet is received from the peer (as for
# the "passive" option with old versions of pppd).
#silent

# Don't request or allow negotiation of any options for LCP and IPCP
# (use default values).
#-all

# Disable Address/Control compression negotiation (use default, i.e.
# address/control field disabled).
#-ac

# Disable asyncmap negotiation (use the default asyncmap, i.e. escape
# all control characters).
#-am

# Don't fork to become a background process (otherwise pppd will do so
# if a serial device is specified).
#-detach

# Disable IP address negotiation (with this option, the remote IP
# address must be specified with an option on the command line or in
# an options file).
#-ip

# Disable IPCP negotiation and IP communication. This option should
# only be required if the peer is buggy and gets confused by requests
# from pppd for IPCP negotiation.
#noip

# Disable magic number negotiation.  With this option, pppd cannot
# detect a looped-back line.
#-mn

# Disable MRU [Maximum Receive Unit] negotiation (use default, i.e.
# 1500).
#-mru

# Disable protocol field compression negotiation (use default, i.e.
# protocol field compression disabled).
#-pc

# Require the peer to authenticate itself using PAP.
#+pap

# Don't agree to authenticate using PAP.
#-pap

# Require the peer to authenticate itself using CHAP [Cryptographic
# Handshake Authentication Protocol] authentication.
#+chap

# Don't agree to authenticate using CHAP.
#-chap

# Disable negotiation of Van Jacobson style IP header compression (use
# default, i.e. no compression).
#-vj

# Increase debugging level (same as -d).  If this option is given, pppd
# will log the contents of all control packets sent or received in a
# readable form.  The packets are logged through syslog with facility
# daemon and level debug. This information can be directed to a file by
# setting up /etc/syslog.conf appropriately (see syslog.conf(5)).  (If
# pppd is compiled with extra debugging enabled, it will log messages
# using facility local2 instead of daemon).
#debug

# Append the domain name <d> to the local host name for authentication
# purposes.  For example, if gethostname() returns the name porsche,
# but the fully qualified domain name is porsche.Quotron.COM, you would
# use the domain option to set the domain name to Quotron.COM.
#domain <d>

# Enable debugging code in the kernel-level PPP driver.  The argument n
# is a number which is the sum of the following values: 1 to enable
# general debug messages, 2 to request that the contents of received
# packets be printed, and 4 to request that the contents of transmitted
# packets be printed.
#kdebug n

# Set the MTU [Maximum Transmit Unit] value to <n>. Unless the peer
# requests a smaller value via MRU negotiation, pppd will request that
# the kernel networking code send data packets of no more than n bytes
# through the PPP network interface.
#mtu <n>

# Set the name of the local system for authentication purposes to <n>.
# This is a privileged option. With this option, pppd will use lines in 
the
# secrets files which have <n> as the second field when looking for a
# secret to use in authenticating the peer. In addition, unless overridden
# with the user option, <n> will be used as the name to send to the peer
# when authenticating the local system to the peer. (Note that pppd does
# not append the domain name to <n>.)
#name <n>

# Enforce the use of the hostname as the name of the local system for
# authentication purposes (overrides the name option).
#usehostname

# Set the assumed name of the remote system for authentication purposes
# to <n>.
#remotename <n>

# Add an entry to this system's ARP [Address Resolution Protocol]
# table with the IP address of the peer and the Ethernet address of this
# system.
proxyarp

# Use the system password database for authenticating the peer using
# PAP. Note: mgetty already provides this option. If this is specified
# then dialin from users using a script under Linux to fire up ppp wont 
work.
# login

# If this option is given, pppd will send an LCP echo-request frame to the
# peer every n seconds. Normally the peer should respond to the echo-
request
# by sending an echo-reply. This option can be used with the
# lcp-echo-failure option to detect that the peer is no longer connected.
lcp-echo-interval 30

# If this option is given, pppd will presume the peer to be dead if n
# LCP echo-requests are sent without receiving a valid LCP echo-reply.
# If this happens, pppd will terminate the connection.  Use of this
# option requires a non-zero value for the lcp-echo-interval parameter.
# This option can be used to enable pppd to terminate after the physical
# connection has been broken (e.g., the modem has hung up) in
# situations where no hardware modem control lines are available.
lcp-echo-failure 4

# Set the LCP restart interval (retransmission timeout) to <n> seconds
# (default 3).
#lcp-restart <n>

# Set the maximum number of LCP terminate-request transmissions to <n>
# (default 3).
#lcp-max-terminate <n>

# Set the maximum number of LCP configure-request transmissions to <n>
# (default 10).
#lcp-max-configure <n>

# Set the maximum number of LCP configure-NAKs returned before starting
# to send configure-Rejects instead to <n> (default 10).
#lcp-max-failure <n>

# Set the IPCP restart interval (retransmission timeout) to <n>
# seconds (default 3).
#ipcp-restart <n>

# Set the maximum number of IPCP terminate-request transmissions to <n>
# (default 3).
#ipcp-max-terminate <n>

# Set the maximum number of IPCP configure-request transmissions to <n>
# (default 10).
#ipcp-max-configure <n>

# Set the maximum number of IPCP configure-NAKs returned before starting
# to send configure-Rejects instead to <n> (default 10).
#ipcp-max-failure <n>

# Set the PAP restart interval (retransmission timeout) to <n> seconds
# (default 3).
#pap-restart <n>

# Set the maximum number of PAP authenticate-request transmissions to
# <n> (default 10).
#pap-max-authreq <n>

# Set the maximum time that pppd will wait for the peer to authenticate
# itself with PAP to <n> seconds (0 means no limit).
#pap-timeout <n>

# Set the CHAP restart interval (retransmission timeout for
# challenges) to <n> seconds (default 3).
#chap-restart <n>

# Set the maximum number of CHAP challenge transmissions to <n>
# (default 10).
#chap-max-challenge

# If this option is given, pppd will rechallenge the peer every <n>
# seconds.
#chap-interval <n>

# With this option, pppd will accept the peer's idea of our local IP
# address, even if the local IP address was specified in an option.
#ipcp-accept-local

# With this option, pppd will accept the peer's idea of its (remote) IP
# address, even if the remote IP address was specified in an option.
#ipcp-accept-remote

# Disable the IPXCP and IPX protocols.
# To let pppd pass IPX packets comment this out --- you'll probably also
# want to install ipxripd, and have the Internal IPX Network option 
enabled
# in your kernel.  /usr/doc/HOWTO/IPX-HOWTO.gz contains more info.
noipx

# Exit once a connection has been made and terminated. This is the 
default,
# unless the `persist' or `demand' option has been specified.
#nopersist

# Do not exit after a connection is terminated; instead try to reopen
# the connection.
#persist

# Terminate after n consecutive failed connection attempts.
# A value of 0 means no limit. The default value is 10.
#maxfail <n>

# Initiate the link only on demand, i.e. when data traffic is present. 
# With this option, the remote IP address must be specified by the user on
# the command line or in an options file.  Pppd will initially configure
# the interface and enable it for IP traffic without connecting to the 
peer. 
# When traffic is available, pppd will connect to the peer and perform
# negotiation, authentication, etc.  When this is completed, pppd will
# commence passing data packets (i.e., IP packets) across the link.
#demand

# Specifies that pppd should disconnect if the link is idle for <n> 
seconds.
# The link is idle when no data packets (i.e. IP packets) are being sent 
or
# received.  Note: it is not advisable to use this option with the persist
# option without the demand option.  If the active-filter option is given,
# data packets which are rejected by the specified activity filter also
# count as the link being idle.
#idle <n>

# Specifies how many seconds to wait before re-initiating the link after
# it terminates.  This option only has any effect if the persist or demand
# option is used.  The holdoff period is not applied if the link was
# terminated because it was idle.
#holdoff <n>

# Wait for up n milliseconds after the connect script finishes for a valid
# PPP packet from the peer.  At the end of this time, or when a valid PPP
# packet is received from the peer, pppd will commence negotiation by
# sending its first LCP packet.  The default value is 1000 (1 second).
# This wait period only applies if the connect or pty option is used.
#connect-delay <n>

# Packet filtering: for more information, see pppd(8)
# Any packets matching the filter expression will be interpreted as link
# activity, and will cause a "demand" connection to be activated, and 
reset
# the idle connection timer. (idle option)
# The filter expression is akin to that of tcpdump(1)
#active-filter <filter-expression>

# ---<End of File>---

# /etc/ppp/pap-secrets
#
# This is a pap-secrets file to be used with the AUTO_PPP function of
# mgetty. mgetty-0.99 is preconfigured to startup pppd with the login 
option
# which will cause pppd to consult /etc/passwd (and /etc/shadow in turn)
# after a user has passed this file. Don't be disturbed therefore by the 
fact
# that this file defines logins with any password for users. /etc/passwd
# (again, /etc/shadow, too) will catch passwd mismatches.
#
# This file should block ALL users that should not be able to do AUTO_PPP.
# AUTO_PPP bypasses the usual login program so it's necessary to list all
# system userids with regular passwords here.
#
# ATTENTION: The definitions here can allow users to login without a
# password if you don't use the login option of pppd! The mgetty Debian
# package already provides this option; make sure you don't change that.

# INBOUND connections

# Every regular user can use PPP and has to use passwords from /etc/passwd
*       hostname        ""      *

# UserIDs that cannot use PPP at all. Check your /etc/passwd and add any
# other accounts that should not be able to use pppd!
guest   hostname        "*"     -
master  hostname        "*"     -
root    hostname        "*"     -
support hostname        "*"     -
stats   hostname        "*"     -

# OUTBOUND connections

# Here you should add your userid password to connect to your providers 
via
# PAP. The * means that the password is to be used for ANY host you 
connect
# to. Thus you do not have to worry about the foreign machine name. Just
# replace password with your password.
# If you have different providers with different passwords then you better
# remove the following line.

#       *       password


------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Reply via email to