Could not determine local IP address - PPP

This is a discussion on Could not determine local IP address - PPP ; I am trying to configure 2 linux machines that have multiple modems to be able to dial each other. I need to have both machines determine their own IP addresses and that is where I am running into problems. I've ...

+ Reply to Thread
Page 1 of 2 1 2 LastLast
Results 1 to 20 of 27

Thread: Could not determine local IP address

  1. Could not determine local IP address

    I am trying to configure 2 linux machines that have multiple modems to
    be able to dial each other. I need to have both machines determine
    their own IP addresses and that is where I am running into problems.

    I've searched the newsgroups over and over, and keep running into the
    advice that I should make sure noipdefault is not used and I am
    positive I am not using (even greped for it). If I make the
    options.ttyS2 file use localLine3:remoteLine3(both in my /etc/hosts
    file) then the caller determines both of the ip addresses, but I need
    the receiver to determine his own and the caller their own, but at
    least it works.


    Here are my config files and syslog:

    CALLER machine's /etc/ppp/options.ttyS2
    localLine3:

    RECIEVER machine's /etc/ppp/options.ttyS2
    localLine3:remoteLine3

    Both sides have use this /etc/ppp/options
    lock
    login
    modem
    crtscts
    nodetach
    novj
    ipcp-accept-remote

    snippet of /etc/mgetty-sendfax/login.conf
    ....
    /AutoPPP/ - a_ppp /usr/sbin/pppd
    ....

    /var/log/syslog
    Aug 3 09:45:44 localhost ifup-ppp: pppd started for ppp2 on
    /dev/ttyS2 at 19200
    Aug 3 09:45:45 localhost pppd[4988]: pppd 2.4.1 started by root, uid
    0
    Aug 3 09:45:46 localhost wvdial[5001]: WvDial: Internet dialer
    version 1.53
    Aug 3 09:45:46 localhost wvdial[5001]: Initializing modem.
    Aug 3 09:45:46 localhost wvdial[5001]: Sending: ATZ
    Aug 3 09:45:46 localhost wvdial[5001]: ATZ
    Aug 3 09:45:46 localhost wvdial[5001]: OK
    Aug 3 09:45:46 localhost wvdial[5001]: Sending: ATQ0 V1 E1 S0=0 &C1
    &D2
    Aug 3 09:45:46 localhost wvdial[5001]: ATQ0 V1 E1 S0=0 &C1 &D2
    Aug 3 09:45:46 localhost wvdial[5001]: OK
    Aug 3 09:45:46 localhost wvdial[5001]: Modem initialized.
    Aug 3 09:45:46 localhost wvdial[5001]: Sending: ATDT00881631013780
    Aug 3 09:45:46 localhost wvdial[5001]: Waiting for carrier.
    Aug 3 09:45:46 localhost wvdial[5001]: ATDT00881631013780
    Aug 3 09:46:04 localhost wvdial[5001]: CONNECT 19200
    Aug 3 09:46:04 localhost wvdial[5001]: Carrier detected. Chatmode
    finished.
    Aug 3 09:46:04 localhost pppd[4988]: Serial connection established.
    Aug 3 09:46:04 localhost pppd[4988]: using channel 5
    Aug 3 09:46:04 localhost pppd[4988]: Using interface ppp0
    Aug 3 09:46:04 localhost pppd[4988]: Connect: ppp0 <--> /dev/ttyS2
    Aug 3 09:46:04 localhost /etc/hotplug/net.agent: assuming ppp0 is
    already up
    Aug 3 09:46:05 localhost pppd[4988]: sent [LCP ConfReq id=0x1 1200> ]
    Aug 3 09:46:14 localhost last message repeated 3 times
    Aug 3 09:46:14 localhost pppd[4988]: rcvd [LCP ConfReq id=0x1
    ]
    Aug 3 09:46:14 localhost pppd[4988]: sent [LCP ConfAck id=0x1
    ]
    Aug 3 09:46:14 localhost pppd[4988]: rcvd [LCP ConfAck id=0x1 1200> ]
    Aug 3 09:46:14 localhost pppd[4988]: sent [IPCP ConfReq id=0x1 169.254.2.1> ]
    Aug 3 09:46:14 localhost pppd[4988]: sent [CCP ConfReq id=0x1
    ]
    Aug 3 09:46:15 localhost pppd[4988]: rcvd [LCP ConfAck id=0x1 1200> ]
    Aug 3 09:46:16 localhost pppd[4988]: rcvd [LCP ConfAck id=0x1 1200> ]
    Aug 3 09:46:16 localhost pppd[4988]: rcvd [IPCP ConfReq id=0x1 0.0.0.0>]
    Aug 3 09:46:16 localhost pppd[4988]: sent [IPCP ConfRej id=0x1 0.0.0.0>]
    Aug 3 09:46:16 localhost pppd[4988]: rcvd [CCP ConfReq id=0x1
    ]
    Aug 3 09:46:16 localhost pppd[4988]: sent [CCP ConfAck id=0x1
    ]
    Aug 3 09:46:16 localhost pppd[4988]: rcvd [IPCP ConfRej id=0x1
    ]
    Aug 3 09:46:16 localhost pppd[4988]: sent [IPCP ConfReq id=0x2 169.254.2.1>]
    Aug 3 09:46:16 localhost pppd[4988]: rcvd [CCP ConfAck id=0x1
    ]
    Aug 3 09:46:16 localhost pppd[4988]: Deflate (15) compression enabled
    Aug 3 09:46:18 localhost pppd[4988]: rcvd [IPCP ConfReq id=0x2 0.0.0.0 0.0.0.0>]
    Aug 3 09:46:18 localhost pppd[4988]: sent [IPCP ConfRej id=0x2 0.0.0.0 0.0.0.0>]
    Aug 3 09:46:18 localhost pppd[4988]: rcvd [IPCP ConfAck id=0x2 169.254.2.1>]
    Aug 3 09:46:19 localhost pppd[4988]: sent [IPCP ConfReq id=0x2 169.254.2.1>]
    Aug 3 09:46:19 localhost pppd[4988]: rcvd [IPCP ConfReq id=0x3]
    Aug 3 09:46:19 localhost pppd[4988]: sent [IPCP ConfAck id=0x3]
    Aug 3 09:46:21 localhost pppd[4988]: rcvd [IPCP ConfAck id=0x2 169.254.2.1>]
    Aug 3 09:46:21 localhost pppd[4988]: Could not determine remote IP
    address: defaulting to 10.64.64.64
    Aug 3 09:46:21 localhost pppd[4988]: local IP address 169.254.2.1
    Aug 3 09:46:21 localhost pppd[4988]: remote IP address 10.64.64.64
    Aug 3 09:46:21 localhost pppd[4988]: Script /etc/ppp/ip-up started
    (pid 5315)
    Aug 3 09:46:21 localhost pppd[4988]: rcvd [IPCP TermReq id=0x4 "Could
    not determine local IP address"]
    Aug 3 09:46:21 localhost pppd[4988]: IPCP terminated by peer (Could
    not determine local IP address)
    Aug 3 09:46:21 localhost pppd[4988]: sent [IPCP TermAck id=0x4]
    Aug 3 09:46:22 localhost kernel: eql: timer found dead slave,
    burying...
    Aug 3 09:46:23 localhost pppd[4988]: Script /etc/ppp/ip-up finished
    (pid 5315), status = 0x0
    Aug 3 09:46:23 localhost pppd[4988]: Script /etc/ppp/ip-down started
    (pid 5408)
    Aug 3 09:46:23 localhost pppd[4988]: Script ?? finished (pid 4997),
    status = 0x0
    Aug 3 09:46:23 localhost kernel: eql: timer found dead slave,
    burying...
    Aug 3 09:46:23 localhost pppd[4988]: rcvd [LCP TermReq id=0x2 "No
    network protocols running"]
    Aug 3 09:46:23 localhost pppd[4988]: LCP terminated by peer (No
    network protocols running)
    Aug 3 09:46:23 localhost pppd[4988]: sent [LCP TermAck id=0x2]
    Aug 3 09:46:24 localhost pppd[4988]: Terminating on signal 15.
    Aug 3 09:46:24 localhost pppd[4988]: Script /etc/ppp/ip-down finished
    (pid 5408), status = 0x0
    Aug 3 09:46:26 localhost pppd[4988]: Hangup (SIGHUP)
    Aug 3 09:46:26 localhost pppd[4988]: Modem hangup
    Aug 3 09:46:26 localhost pppd[4988]: Connection terminated.
    Aug 3 09:46:26 localhost pppd[4988]: Connect time 0.3 minutes.
    Aug 3 09:46:26 localhost pppd[4988]: Sent 100 bytes, received 134
    bytes.
    Aug 3 09:46:26 localhost /etc/hotplug/net.agent: NET unregister event
    not supported
    Aug 3 09:46:27 localhost pppd[4988]: Exit.

  2. Re: Could not determine local IP address

    junk@foushee.cc (Carey) writes:
    > CALLER machine's /etc/ppp/options.ttyS2
    > localLine3:
    >
    > RECIEVER machine's /etc/ppp/options.ttyS2
    > localLine3:remoteLine3


    That looks broken. Both sides are attempting to use the same IP
    address for their local address (localLine3).

    You likely want one of these:

    Caller specifies nothing, receiver specifies "X:Y".

    Caller specifies "X:", receiver specifies "Y:".

    Caller specifies "X:Y", receiver specifies "Y:X".
    (Belt-and-suspenders approach, I suppose.)

    Also, the traces you supply don't match those settings, so something
    else is wrong.

    > Aug 3 09:46:05 localhost pppd[4988]: sent [LCP ConfReq id=0x1 > 1200> ]


    MRU set to 1200? Why?

    > Aug 3 09:46:14 localhost pppd[4988]: sent [IPCP ConfReq id=0x1 > 169.254.2.1> ]


    You tell your peer that your local address is 169.254.2.1.

    > Aug 3 09:46:16 localhost pppd[4988]: rcvd [IPCP ConfReq id=0x1 > 0.0.0.0>]


    Peer says that he doesn't know his address.

    > Aug 3 09:46:16 localhost pppd[4988]: sent [IPCP ConfRej id=0x1 > 0.0.0.0>]


    You tell the peer that if he doesn't know his address, then you're
    stuck, because you don't know his address either.

    > Aug 3 09:46:16 localhost pppd[4988]: rcvd [IPCP ConfRej id=0x1
    > ]


    Peer says that he doesn't care about MS-DNS.

    > Aug 3 09:46:16 localhost pppd[4988]: sent [IPCP ConfReq id=0x2 > 169.254.2.1>]


    You insist that your address is 169.254.2.1 again.

    > Aug 3 09:46:18 localhost pppd[4988]: rcvd [IPCP ConfReq id=0x2 > 0.0.0.0 0.0.0.0>]


    Peer falls back to old-style addresses.

    > Aug 3 09:46:18 localhost pppd[4988]: sent [IPCP ConfRej id=0x2 > 0.0.0.0 0.0.0.0>]


    You refuse.

    > Aug 3 09:46:21 localhost pppd[4988]: Could not determine remote IP
    > address: defaulting to 10.64.64.64


    Bailing out: nobody specified a remote address.

    It looks like this log is from the "caller's" side. It seems that
    it's the "receiver" that is unable to find its configuration files.
    Perhaps it's not actually using /dev/ttyS2.

    --
    James Carlson, IP Systems Group
    Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677

  3. Re: Could not determine local IP address

    i believe i know what you are doing

    easier way:
    in your ip-up file

    delete the host route
    add a route via device to an ip alias on the server

    in your eql set a default gateway via device to the main ip on the server.



  4. Re: Could not determine local IP address

    Carey wrote:
    > I am trying to configure 2 linux machines that have multiple modems to
    > be able to dial each other. I need to have both machines determine
    > their own IP addresses and that is where I am running into problems.


    > I've searched the newsgroups over and over, and keep running into the
    > advice that I should make sure noipdefault is not used and I am
    > positive I am not using (even greped for it). If I make the
    > options.ttyS2 file use localLine3:remoteLine3(both in my /etc/hosts
    > file) then the caller determines both of the ip addresses, but I need
    > the receiver to determine his own and the caller their own, but at
    > least it works.


    > Here are my config files and syslog:


    > CALLER machine's /etc/ppp/options.ttyS2
    > localLine3:


    > RECIEVER machine's /etc/ppp/options.ttyS2
    > localLine3:remoteLine3


    If localLine3 is the local IP address for PPP on each host, so that IP
    address associated with localLine3 on the CALLER host differs from the
    IP address associated with localLine3 on the other host, then you need

    localLine3:

    configured for both hosts to let each determine it's own IP address.

    As James Carlson pointed out, the RECEIVER host doesn't know it's IP
    address for PPP, and that should be fixed first.

    --
    Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
    PPP-Q&A links, downloads: http://ckite.no-ip.net/
    /* Microsoft is a great marketing organization.
    * It _has_ to be */

  5. Re: Could not determine local IP address

    junk@foushee.cc (Carey) writes:

    ]I am trying to configure 2 linux machines that have multiple modems to
    ]be able to dial each other. I need to have both machines determine
    ]their own IP addresses and that is where I am running into problems.

    They do not determine their own IP addresses, they are assigned. Either by
    one of the machines or by both.

    ]I've searched the newsgroups over and over, and keep running into the
    ]advice that I should make sure noipdefault is not used and I am
    ]positive I am not using (even greped for it). If I make the
    ]options.ttyS2 file use localLine3:remoteLine3(both in my /etc/hosts
    ]file) then the caller determines both of the ip addresses, but I need
    ]the receiver to determine his own and the caller their own, but at
    ]least it works.

    Determine? Again, they do not determine anything. They are assigned.

    Put 10.0.0.1: into one machine's /etc/ppp/options and 10.0.0.2: into the
    other's

    ]Here are my config files and syslog:

    ]CALLER machine's /etc/ppp/options.ttyS2
    ]localLine3:

    That is not a number. 10.0.0.1: is an IP address. localLine3 is not.
    Put in an IP address into each of these slots.



    ]RECIEVER machine's /etc/ppp/options.ttyS2
    ]localLine3:remoteLine3

    Again what are these?

    Both machines cannot have the same IP (localLine3). If you would only have
    put in the actuall numbers we might not be confused, Instead you seem to be
    asking for help but making it as hard for us to give you help as you can.



    ]Both sides have use this /etc/ppp/options
    ]lock
    ]login
    ]modem
    ]crtscts
    ]nodetach
    ]novj
    ]ipcp-accept-remote


    Tell us EXACTLY (No coyness, make an exact copy changing nothing) what is
    in options.ttyS2
    (are you really sure it is ttyS2 that the modems are on? That is Com3, the
    sister to COM1. Why are you using COM3?


    ]snippet of /etc/mgetty-sendfax/login.conf
    ]...
    ]/AutoPPP/ - a_ppp /usr/sbin/pppd
    ]...

    ]/var/log/syslog
    ]Aug 3 09:45:44 localhost ifup-ppp: pppd started for ppp2 on
    ]/dev/ttyS2 at 19200
    ]Aug 3 09:45:45 localhost pppd[4988]: pppd 2.4.1 started by root, uid
    ]0
    ]Aug 3 09:45:46 localhost wvdial[5001]: WvDial: Internet dialer
    ]version 1.53
    ]Aug 3 09:45:46 localhost wvdial[5001]: Initializing modem.
    ]Aug 3 09:45:46 localhost wvdial[5001]: Sending: ATZ

    Horrible. ATZ usually leaves the modem in a completely undefined state. Use
    AT&F (or AT&F1 for sportster modems)

    ]Aug 3 09:45:46 localhost wvdial[5001]: ATZ
    ]Aug 3 09:45:46 localhost wvdial[5001]: OK
    ]Aug 3 09:45:46 localhost wvdial[5001]: Sending: ATQ0 V1 E1 S0=0 &C1
    ]&D2

    After sending the undefined ATZ you change some of the options.

    ]Aug 3 09:45:46 localhost wvdial[5001]: ATQ0 V1 E1 S0=0 &C1 &D2
    ]Aug 3 09:45:46 localhost wvdial[5001]: OK
    ]Aug 3 09:45:46 localhost wvdial[5001]: Modem initialized.
    ]Aug 3 09:45:46 localhost wvdial[5001]: Sending: ATDT00881631013780
    ]Aug 3 09:45:46 localhost wvdial[5001]: Waiting for carrier.
    ]Aug 3 09:45:46 localhost wvdial[5001]: ATDT00881631013780
    ]Aug 3 09:46:04 localhost wvdial[5001]: CONNECT 19200

    19200? rather slow.

    ]Aug 3 09:46:04 localhost wvdial[5001]: Carrier detected. Chatmode
    ]finished.
    ]Aug 3 09:46:04 localhost pppd[4988]: Serial connection established.
    ]Aug 3 09:46:04 localhost pppd[4988]: using channel 5
    ]Aug 3 09:46:04 localhost pppd[4988]: Using interface ppp0
    ]Aug 3 09:46:04 localhost pppd[4988]: Connect: ppp0 <--> /dev/ttyS2
    ]Aug 3 09:46:04 localhost /etc/hotplug/net.agent: assuming ppp0 is
    ]already up
    ]Aug 3 09:46:05 localhost pppd[4988]: sent [LCP ConfReq id=0x1 ]1200> ]
    ]Aug 3 09:46:14 localhost last message repeated 3 times
    ]Aug 3 09:46:14 localhost pppd[4988]: rcvd [LCP ConfReq id=0x1
    ] ]
    ]Aug 3 09:46:14 localhost pppd[4988]: sent [LCP ConfAck id=0x1
    ] ]
    ]Aug 3 09:46:14 localhost pppd[4988]: rcvd [LCP ConfAck id=0x1 ]1200> ]
    ]Aug 3 09:46:14 localhost pppd[4988]: sent [IPCP ConfReq id=0x1 ]169.254.2.1> ]

    And after trying to hide your IP address, here it is. Are you sure that you
    have teh right to use that address?


    ]Aug 3 09:46:14 localhost pppd[4988]: sent [CCP ConfReq id=0x1
    ] ]
    ]Aug 3 09:46:15 localhost pppd[4988]: rcvd [LCP ConfAck id=0x1 ]1200> ]
    ]Aug 3 09:46:16 localhost pppd[4988]: rcvd [LCP ConfAck id=0x1 ]1200> ]
    ]Aug 3 09:46:16 localhost pppd[4988]: rcvd [IPCP ConfReq id=0x1 ]0.0.0.0>]

    The remote machine asks you for its IP address.

    ]Aug 3 09:46:16 localhost pppd[4988]: sent [IPCP ConfRej id=0x1 ]0.0.0.0>]

    Your system has no idea what address teh remote system should have.


    ]Aug 3 09:46:16 localhost pppd[4988]: rcvd [CCP ConfReq id=0x1
    ] ]
    ]Aug 3 09:46:16 localhost pppd[4988]: sent [CCP ConfAck id=0x1
    ] ]
    ]Aug 3 09:46:16 localhost pppd[4988]: rcvd [IPCP ConfRej id=0x1
    ] ]
    ]Aug 3 09:46:16 localhost pppd[4988]: sent [IPCP ConfReq id=0x2 ]169.254.2.1>]
    ]Aug 3 09:46:16 localhost pppd[4988]: rcvd [CCP ConfAck id=0x1
    ] ]
    ]Aug 3 09:46:16 localhost pppd[4988]: Deflate (15) compression enabled
    ]Aug 3 09:46:18 localhost pppd[4988]: rcvd [IPCP ConfReq id=0x2 ]0.0.0.0 0.0.0.0>]
    ]Aug 3 09:46:18 localhost pppd[4988]: sent [IPCP ConfRej id=0x2 ]0.0.0.0 0.0.0.0>]
    ]Aug 3 09:46:18 localhost pppd[4988]: rcvd [IPCP ConfAck id=0x2 ]169.254.2.1>]
    ]Aug 3 09:46:19 localhost pppd[4988]: sent [IPCP ConfReq id=0x2 ]169.254.2.1>]
    ]Aug 3 09:46:19 localhost pppd[4988]: rcvd [IPCP ConfReq id=0x3]
    ]Aug 3 09:46:19 localhost pppd[4988]: sent [IPCP ConfAck id=0x3]
    ]Aug 3 09:46:21 localhost pppd[4988]: rcvd [IPCP ConfAck id=0x2 ]169.254.2.1>]
    ]Aug 3 09:46:21 localhost pppd[4988]: Could not determine remote IP
    ]address: defaulting to 10.64.64.64

    You never told your local system what address the remote should have. Teh
    remote system had no idea what address it should have. Your side gives up
    in disgust and assignes a "random " address but never told the remote
    system this.


    ]Aug 3 09:46:21 localhost pppd[4988]: local IP address 169.254.2.1
    ]Aug 3 09:46:21 localhost pppd[4988]: remote IP address 10.64.64.64
    ]Aug 3 09:46:21 localhost pppd[4988]: Script /etc/ppp/ip-up started
    ](pid 5315)
    ]Aug 3 09:46:21 localhost pppd[4988]: rcvd [IPCP TermReq id=0x4 "Could
    ]not determine local IP address"]
    The remote system has no idea what its address is.


    ]Aug 3 09:46:21 localhost pppd[4988]: IPCP terminated by peer (Could
    ]not determine local IP address)
    ]Aug 3 09:46:27 localhost pppd[4988]: Exit.

  6. Re: Could not determine local IP address

    Bill Unruh wrote:
    > junk@foushee.cc (Carey) writes:


    > ]RECIEVER machine's /etc/ppp/options.ttyS2
    > ]localLine3:remoteLine3


    > Again what are these?


    > Both machines cannot have the same IP (localLine3). If you would only have
    > put in the actuall numbers we might not be confused, Instead you seem to be
    > asking for help but making it as hard for us to give you help as you can.


    He said he put those in /etc/hosts. If IP addresses are assigned to
    them there - as certainly would be the case - then the resolver will
    pick up the IP addresses and pass them to pppd. Pppd allows using
    hostnames in place of IP addresses, but any alpha-numeric string
    assigned an IP address in /etc/hosts should work.

    However, as you noted, it does contribute to uncertainty as to whether
    the IP addresses used are correctly assigned.

    --
    Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
    PPP-Q&A links, downloads: http://ckite.no-ip.net/
    /* Slogan appropriate for a certain well-known software company:
    FAILURE IS NOT AN OPTION - it is built into the operating system
    and comes bundled with the software. And it attracts maggots. */

  7. Re: Could not determine local IP address

    Thanks for the suggestions so far and sorry I should have included the
    ip addresses localLine and remoteLine. I did have both defined in the
    /etc/hosts and they weren't different depending on which machine they
    were one, but for the sake of debugging I'm using real ip addresses
    but it gave me the same result. Also, this time have both the caller
    and receiver's syslog.

    Oh, and I used ttyS0 this time to avoid confusion there. (FYI: I
    actually have a computer with 4 modems in both the caller and
    reciever. They are iridium satelitte modems actually which is why I
    used a lower MTU.)

    Oh, by the way the modem speed is 2400 baud for the modems, the 19200
    is just the speed in which we communicate with the modems. I was
    under the understanding the CONNECT 19200 is really used anyhow, that
    the modems will negotiate the actual speed.

    You know after reading over some of the comments again and looking at
    the receivers log (see below) there is a strang line "Connect: ppp0
    <--> /dev/tts/0" shouldn't that be "Connect: ppp0 <--> /dev/ttyS0".
    If so, where could that have got set wrong? I checked my
    /etc/rc.serial and its using setserial ttyS0 and /dev/ttyS0 was there
    as well.

    CALLER'S SETUP:

    /etc/options.ttyS0
    169.254.2.1:

    /etc/options
    lock
    login
    modem
    crtscts
    nodetach
    novj
    ipcp-accept-remote

    RECEIVER'S SETUP:
    /etc/options.ttyS0
    169.254.10.1:

    /etc/options
    lock
    login
    modem
    crtscts
    nodetach
    novj
    ipcp-accept-remote

    CALLER'S LOGFILE:
    Aug 4 11:25:29 localhost ifup-ppp: pppd started for ppp0 on
    /dev/ttyS0 at 19200
    Aug 4 11:25:30 localhost pppd[16727]: pppd 2.4.1 started by root, uid
    0
    Aug 4 11:25:31 localhost wvdial[16740]: WvDial: Internet dialer
    version 1.53
    Aug 4 11:25:31 localhost wvdial[16740]: Initializing modem.
    Aug 4 11:25:31 localhost wvdial[16740]: Sending: ATZ
    Aug 4 11:25:31 localhost wvdial[16740]: ATZ
    Aug 4 11:25:31 localhost wvdial[16740]: OK
    Aug 4 11:25:31 localhost wvdial[16740]: Sending: ATQ0 V1 E1 S0=0 &C1
    &D2
    Aug 4 11:25:31 localhost wvdial[16740]: ATQ0 V1 E1 S0=0 &C1 &D2
    Aug 4 11:25:31 localhost wvdial[16740]: OK
    Aug 4 11:25:31 localhost wvdial[16740]: Modem initialized.
    Aug 4 11:25:31 localhost wvdial[16740]: Sending: ATDT00881631013780
    Aug 4 11:25:31 localhost wvdial[16740]: Waiting for carrier.
    Aug 4 11:25:32 localhost wvdial[16740]: ATDT00881631013780
    Aug 4 11:25:47 localhost wvdial[16740]: CONNECT 19200
    Aug 4 11:25:47 localhost wvdial[16740]: Carrier detected. Chatmode
    finished.
    Aug 4 11:25:47 localhost pppd[16727]: Serial connection established.
    Aug 4 11:25:47 localhost pppd[16727]: using channel 11
    Aug 4 11:25:47 localhost pppd[16727]: Using interface ppp0
    Aug 4 11:25:47 localhost pppd[16727]: Connect: ppp0 <--> /dev/ttyS0
    Aug 4 11:25:47 localhost /etc/hotplug/net.agent: assuming ppp0 is
    already up
    Aug 4 11:25:48 localhost pppd[16727]: sent [LCP ConfReq id=0x1 1200> ]
    Aug 4 11:25:57 localhost last message repeated 3 times
    Aug 4 11:25:58 localhost pppd[16727]: rcvd [LCP ConfReq id=0x1
    ]
    Aug 4 11:25:58 localhost pppd[16727]: sent [LCP ConfAck id=0x1
    ]
    Aug 4 11:25:58 localhost pppd[16727]: rcvd [LCP ConfAck id=0x1 1200> ]
    Aug 4 11:25:58 localhost pppd[16727]: sent [IPCP ConfReq id=0x1 169.254.2.1> ]
    Aug 4 11:25:58 localhost pppd[16727]: sent [CCP ConfReq id=0x1
    ]
    Aug 4 11:25:59 localhost pppd[16727]: rcvd [LCP ConfAck id=0x1 1200> ]
    Aug 4 11:25:59 localhost pppd[16727]: rcvd [LCP ConfAck id=0x1 1200> ]
    Aug 4 11:26:00 localhost pppd[16727]: rcvd [IPCP ConfReq id=0x1 0.0.0.0>]
    Aug 4 11:26:00 localhost pppd[16727]: sent [IPCP ConfRej id=0x1 0.0.0.0>]
    Aug 4 11:26:00 localhost pppd[16727]: rcvd [CCP ConfReq id=0x1
    ]
    Aug 4 11:26:00 localhost pppd[16727]: sent [CCP ConfAck id=0x1
    ]
    Aug 4 11:26:00 localhost pppd[16727]: rcvd [IPCP ConfRej id=0x1
    ]
    Aug 4 11:26:00 localhost pppd[16727]: sent [IPCP ConfReq id=0x2 169.254.2.1>]
    Aug 4 11:26:00 localhost pppd[16727]: rcvd [CCP ConfAck id=0x1
    ]
    Aug 4 11:26:00 localhost pppd[16727]: Deflate (15) compression
    enabled
    Aug 4 11:26:02 localhost pppd[16727]: rcvd [IPCP ConfReq id=0x2
    ]
    Aug 4 11:26:02 localhost pppd[16727]: sent [IPCP ConfRej id=0x2
    ]
    Aug 4 11:26:02 localhost pppd[16727]: rcvd [IPCP ConfAck id=0x2 169.254.2.1>]
    Aug 4 11:26:03 localhost pppd[16727]: sent [IPCP ConfReq id=0x2 169.254.2.1>]
    Aug 4 11:26:04 localhost pppd[16727]: rcvd [IPCP ConfReq id=0x3]
    Aug 4 11:26:04 localhost pppd[16727]: sent [IPCP ConfAck id=0x3]
    Aug 4 11:26:05 localhost kernel: eql: timer found dead slave,
    burying...
    Aug 4 11:26:05 localhost pppd[16727]: rcvd [IPCP ConfAck id=0x2 169.254.2.1>]
    Aug 4 11:26:05 localhost pppd[16727]: Could not determine remote IP
    address: defaulting to 10.64.64.64
    Aug 4 11:26:05 localhost pppd[16727]: local IP address 169.254.2.1
    Aug 4 11:26:05 localhost pppd[16727]: remote IP address 10.64.64.64
    Aug 4 11:26:05 localhost pppd[16727]: Script /etc/ppp/ip-up started
    (pid 17060)
    Aug 4 11:26:06 localhost pppd[16727]: rcvd [IPCP TermReq id=0x4
    "Could not determine local IP address"]
    Aug 4 11:26:06 localhost pppd[16727]: IPCP terminated by peer (Could
    not determine local IP address)
    Aug 4 11:26:06 localhost pppd[16727]: sent [IPCP TermAck id=0x4]
    Aug 4 11:26:07 localhost pppd[16727]: Script /etc/ppp/ip-up finished
    (pid 17060), status = 0x0
    Aug 4 11:26:07 localhost pppd[16727]: Script /etc/ppp/ip-down started
    (pid 17107)
    Aug 4 11:26:07 localhost pppd[16727]: Script ?? finished (pid 16736),
    status = 0x0
    Aug 4 11:26:07 localhost kernel: eql: timer found dead slave,
    burying...
    Aug 4 11:26:08 localhost pppd[16727]: rcvd [LCP TermReq id=0x2 "No
    network protocols running"]
    Aug 4 11:26:08 localhost pppd[16727]: LCP terminated by peer (No
    network protocols running)
    Aug 4 11:26:08 localhost pppd[16727]: sent [LCP TermAck id=0x2]
    Aug 4 11:26:08 localhost pppd[16727]: Script /etc/ppp/ip-down
    finished (pid 17107), status = 0x0
    Aug 4 11:26:11 localhost pppd[16727]: Connection terminated.
    Aug 4 11:26:11 localhost pppd[16727]: Connect time 0.4 minutes.
    Aug 4 11:26:11 localhost pppd[16727]: Sent 100 bytes, received 134
    bytes.
    Aug 4 11:26:11 localhost pppd[16727]: Hangup (SIGHUP)
    Aug 4 11:26:11 localhost pppd[16727]: Exit.

    RECEIVER'S LOGFILE:
    Aug 4 13:12:13 localhost pppd[2201]: pppd 2.4.1 started by root, uid
    0
    Aug 4 13:12:13 localhost pppd[2201]: Using interface ppp0
    Aug 4 13:12:13 localhost pppd[2201]: Connect: ppp0 <--> /dev/tts/0
    Aug 4 13:12:13 localhost /etc/hotplug/net.agent: assuming ppp0 is
    already up
    Aug 4 13:12:17 localhost pppd[2201]: Deflate (15) compression enabled
    Aug 4 13:12:21 localhost pppd[2201]: Could not determine local IP
    address
    Aug 4 13:12:23 localhost kernel: eql: timer found dead slave,
    burying...
    Aug 4 13:12:24 localhost pppd[2201]: Connection terminated.
    Aug 4 13:12:24 localhost pppd[2201]: Connect time 0.2 minutes.
    Aug 4 13:12:24 localhost pppd[2201]: Sent 94 bytes, received 100
    bytes.
    Aug 4 13:12:24 localhost pppd[2201]: Exit.

    RECEIVER'S /var/log/mgetty.ttyS0
    08/04 13:09:22 yS0 mgetty: experimental test release 1.1.30-Dec16
    08/04 13:09:22 yS0 check for lockfiles
    08/04 13:09:22 yS0 locking the line
    08/04 13:09:22 yS0 WARNING: DCD line still active, check modem
    settings (AT&Dx)
    08/04 13:09:22 yS0 lowering DTR to reset Modem
    08/04 13:09:23 yS0 TIOCMBIS failed: Input/output error
    08/04 13:09:23 yS0 cannot turn off soft carrier: Input/output error
    08/04 13:09:23 yS0 tcgetattr failed: Input/output error
    08/04 13:09:23 yS0 cannot get TIO: Input/output error
    08/04 13:09:23 yS0 mg_init_device failed, trying again
    08/04 13:09:23 yS0 lowering DTR to reset Modem
    08/04 13:09:23 yS0 send: \dATQ0V1H0[0d]
    08/04 13:09:24 yS0 waiting for ``OK'' ** found **
    08/04 13:09:24 yS0 send: ATS0=0Q0&D3&C1[0d]
    08/04 13:09:24 yS0 waiting for ``OK'' ** found **
    08/04 13:09:24 yS0 waiting...
    08/04 13:09:43 yS0 wfr: waiting for ``RING''
    08/04 13:09:43 yS0 send: ATA[0d]
    08/04 13:09:43 yS0 waiting for ``CONNECT'' ** found **
    08/04 13:09:44 yS0 send:
    08/04 13:09:44 yS0 waiting for ``_'' ** found **
    08/04 13:09:55 ##### failed dev=ttyS0, pid=1909, got signal 1, exiting

    --
    08/04 13:09:55 yS0 mgetty: experimental test release 1.1.30-Dec16
    08/04 13:09:55 yS0 check for lockfiles
    08/04 13:09:55 yS0 locking the line
    08/04 13:09:55 yS0 lowering DTR to reset Modem
    08/04 13:09:56 yS0 send: \dATQ0V1H0[0d]
    08/04 13:09:56 yS0 waiting for ``OK'' ** found **
    08/04 13:09:56 yS0 send: ATS0=0Q0&D3&C1[0d]
    08/04 13:09:56 yS0 waiting for ``OK'' ** found **
    08/04 13:09:57 yS0 waiting...
    08/04 13:12:02 yS0 wfr: waiting for ``RING''
    08/04 13:12:02 yS0 send: ATA[0d]
    08/04 13:12:02 yS0 waiting for ``CONNECT'' ** found **
    08/04 13:12:03 yS0 send:
    08/04 13:12:03 yS0 waiting for ``_'' ** found **
    08/04 13:12:13 ##### data dev=ttyS0, pid=2201, caller='none',
    conn='19200', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'

  8. Re: Could not determine local IP address

    I should add that I just tried putting 169.254.10.1: into my
    receiver's /etc/options file and it worked. So, I guess the question
    is why is it not reading my /etc/options.ttyS0 when its not in the
    options?

  9. Re: Could not determine local IP address

    junk@foushee.cc (Carey) writes:
    > Oh, by the way the modem speed is 2400 baud for the modems, the 19200
    > is just the speed in which we communicate with the modems. I was
    > under the understanding the CONNECT 19200 is really used anyhow, that
    > the modems will negotiate the actual speed.


    The truth is a little more complicated but, yes, that's accurate
    enough.

    (The truth is that modems have both a DTE side -- which is your 19200
    bps serial port -- and a DCE side -- which is the 2400 bps [bits per
    second, not baud] link over the telephone line. The CONNECT XXXX
    message is configurable on most modem firmware, and can be set to
    report DTE speed, DCE speed, or [sometimes] both.)

    (And it's worse than that. Some really old or strange modems cannot
    actually do the buffering and flow control necessary for rate
    adaptation, and require that the serial port [DTE] be set to the same
    rate as the DCE side.)

    (Baud isn't bits per second. It's a number of information-units per
    second. A 2400 bps modem [v.22bis] actually sends 600 baud, with 4
    bits per baud.)

    > You know after reading over some of the comments again and looking at
    > the receivers log (see below) there is a strang line "Connect: ppp0
    > <--> /dev/tts/0" shouldn't that be "Connect: ppp0 <--> /dev/ttyS0".


    Yes. That's why the configuration isn't coming out right. It doesn't
    matter what's in your /etc/ppp/options.ttyS0 file, as pppd won't be
    reading that.

    I don't know what /dev/tts/0 is. It must be something significant on
    your system.

    > If so, where could that have got set wrong?


    At a guess, that's on the dial-in (server) side, and the dial in
    software (mgetty?) is configured to run on /dev/tts/0. I don't think
    it's a PPP or pppd issue.

    > CALLER'S LOGFILE:

    [...]
    > Aug 4 11:26:00 localhost pppd[16727]: rcvd [IPCP ConfReq id=0x1 > 0.0.0.0>]


    Same problem.

    > RECEIVER'S LOGFILE:

    [...]
    > Aug 4 13:12:13 localhost pppd[2201]: Connect: ppp0 <--> /dev/tts/0


    pppd will read '/etc/ppp/options.tts.0' for options. If there isn't
    one, then it will read just /etc/ppp/options.

    > Aug 4 13:12:21 localhost pppd[2201]: Could not determine local IP
    > address


    There's the bug.

    > 08/04 13:12:13 ##### data dev=ttyS0, pid=2201, caller='none',
    > conn='19200', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'


    Strange. I don't know why mgetty is handing over /dev/tts/0 to pppd.

    --
    James Carlson, IP Systems Group
    Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677

  10. Re: Could not determine local IP address

    Yet another update to hopefully help give you more data to
    troubleshoot with. I switched the roles of the machines and had the
    caller receive the phone and got the same results.

    So, either I have both machines set up wrong when they are receiving a
    phone call, or the the "/dev/tts/0" line in the receiving units syslog
    shows up that way for some reason on a receving call. Its like its
    just not reading /etc/options.ttyS0 ??

  11. Re: Could not determine local IP address

    junk@foushee.cc (Carey) writes:
    > I should add that I just tried putting 169.254.10.1: into my
    > receiver's /etc/options file and it worked. So, I guess the question
    > is why is it not reading my /etc/options.ttyS0 when its not in the
    > options?


    Because it's not using /dev/ttyS0. It's using /dev/tts/0 -- whatever
    that might be.

    pppd forms the name of that file by stripping the leading "/dev/",
    converting any remaining slashes to ".", and then prepending
    "/etc/ppp/options." to the resulting string.

    It gets the name of the file by looking at the command line -- if it's
    there -- or by calling ttyname() function on stdin (fd 0) if it's not
    present.

    At a guess, mgetty starts up pppd without a device name on the command
    line, and the result of calling ttyname on fd 0 gives "/dev/tts/0" on
    this particular device. Perhaps /dev/ttyS0 is just a symlink on this
    system.

    For what it's worth, it's the same result that you'd get if you
    executed the /usr/bin/tty program after having logged into a regular
    shell on that same tty. If you configure mgetty to allow regular
    (text-mode) login, you should be able to prove that.

    --
    James Carlson, IP Systems Group
    Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677

  12. Re: Could not determine local IP address

    Carey wrote:

    > You know after reading over some of the comments again and looking at
    > the receivers log (see below) there is a strang line "Connect: ppp0
    > <--> /dev/tts/0" shouldn't that be "Connect: ppp0 <--> /dev/ttyS0".


    I believe you get /dev/tts/0 if devfs is enabled. The /dev filesystem
    (devfs) is on it's way out of the kernel anyway. You need a kernel with
    legacy (BSD) PTY or Unix98 support to get ttySx instead.

    (If you are using a 2.6 kernel then Unix98 support isn't explicitly
    mentioned in "make menuconfig," but I *think* enabling "8250/16550
    and compatible serial support" and/or "Maximum number of non-legacy
    8250/16550 serial ports" implicitly enables UNIX98. The structure
    for "make menuconfig" has changed and for me it was annoying to deal
    with the first time around.)

    > If so, where could that have got set wrong? I checked my
    > /etc/rc.serial and its using setserial ttyS0 and /dev/ttyS0 was there
    > as well.


    And very likely so was the directories /dev/{shm,tts}. Check /etc/fstab,
    and disable any mount that involves shm. That alone might do the trick.
    But according to my syslog for 2001 it seems there was some trouble with
    devfs and the 2.4.12 kernel that might have involved pppd, and I've not
    used it since then.

    > RECEIVER'S LOGFILE:
    > Aug 4 13:12:13 localhost pppd[2201]: pppd 2.4.1 started by root, uid
    > 0
    > Aug 4 13:12:13 localhost pppd[2201]: Using interface ppp0
    > Aug 4 13:12:13 localhost pppd[2201]: Connect: ppp0 <--> /dev/tts/0
    > Aug 4 13:12:13 localhost /etc/hotplug/net.agent: assuming ppp0 is
    > already up
    > Aug 4 13:12:17 localhost pppd[2201]: Deflate (15) compression enabled
    > Aug 4 13:12:21 localhost pppd[2201]: Could not determine local IP
    > address
    > Aug 4 13:12:23 localhost kernel: eql: timer found dead slave,
    > burying...


    Curious message. Anyone?

    > Aug 4 13:12:24 localhost pppd[2201]: Connection terminated.
    > Aug 4 13:12:24 localhost pppd[2201]: Connect time 0.2 minutes.
    > Aug 4 13:12:24 localhost pppd[2201]: Sent 94 bytes, received 100
    > bytes.
    > Aug 4 13:12:24 localhost pppd[2201]: Exit.


    --
    Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
    PPP-Q&A links, downloads: http://ckite.no-ip.net/
    /* The generation of random numbers is too important to be left
    to chance. */

  13. Re: Could not determine local IP address

    James Carlson wrote:

    > At a guess, mgetty starts up pppd without a device name on the command
    > line, and the result of calling ttyname on fd 0 gives "/dev/tts/0" on
    > this particular device. Perhaps /dev/ttyS0 is just a symlink on this
    > system.


    > For what it's worth, it's the same result that you'd get if you
    > executed the /usr/bin/tty program after having logged into a regular
    > shell on that same tty. If you configure mgetty to allow regular
    > (text-mode) login, you should be able to prove that.


    That's not the case for Linux. In an xterm window you get, e.g.,

    ~$ tty
    /dev/pts/0

    and in a virtual console you get, e.g.,

    ~$ tty
    /dev/tty1

    In the latter case the first agetty is configured for /dev/tty1 in
    inittab, although I see no reason they couldn't just as well start at
    /dev/tty0 (it may simply be started at tty1 so the virtual console
    ttyX corresponds to the FX key).

    --
    Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
    PPP-Q&A links, downloads: http://ckite.no-ip.net/
    /* For every credibility gap, there is a gullibility fill.
    -- R. Clopton */

  14. Re: Could not determine local IP address

    Clifford Kite writes:
    > > For what it's worth, it's the same result that you'd get if you
    > > executed the /usr/bin/tty program after having logged into a regular
    > > shell on that same tty. If you configure mgetty to allow regular
    > > (text-mode) login, you should be able to prove that.

    >
    > That's not the case for Linux. In an xterm window you get, e.g.,


    An xterm window isn't a serial port.

    Note that I said "a regular shell on that same tty." If you'd
    configured mgetty to provide a regular "login:" prompt instead on the
    same port currently used for PPP, logged in, and then typed "tty", you
    should see the same result that pppd does, as that program uses the
    same kernel interface to get the tty name. That should come out as
    /dev/tts/0.

    > ~$ tty
    > /dev/pts/0
    >
    > and in a virtual console you get, e.g.,
    >
    > ~$ tty
    > /dev/tty1


    The former is a pty, but I'm not sure what the latter is (or what the
    original poster would see if he tried that).

    --
    James Carlson, IP Systems Group
    Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677

  15. Re: Could not determine local IP address

    James Carlson wrote:
    > Clifford Kite writes:
    >> > For what it's worth, it's the same result that you'd get if you
    >> > executed the /usr/bin/tty program after having logged into a regular
    >> > shell on that same tty. If you configure mgetty to allow regular
    >> > (text-mode) login, you should be able to prove that.

    >>
    >> That's not the case for Linux. In an xterm window you get, e.g.,


    > An xterm window isn't a serial port.


    > Note that I said "a regular shell on that same tty." If you'd
    > configured mgetty to provide a regular "login:" prompt instead on the
    > same port currently used for PPP, logged in, and then typed "tty", you
    > should see the same result that pppd does, as that program uses the
    > same kernel interface to get the tty name. That should come out as
    > /dev/tts/0.


    Okay, it's now apparent I misread the paragraph preceding the first one
    quoted above and that, together with my lack of C experience, resulted
    in a wrong conclusion as to what you meant.

    My apologies for that. For the OP: This doesn't alter by belief that
    the devfs filesystem is responsible for the /dev/tts/0 and that BSD PTY
    or UNIX98 support should be used instead.

    -- Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
    PPP-Q&A links, downloads: http://ckite.no-ip.net/
    /* "PPPoE has many advantages for DSL service providers, and
    practically none for DSL consumers."
    - David F. Skoll */

  16. Re: Could not determine local IP address

    Clifford Kite writes:
    > My apologies for that.


    No problem.

    > For the OP: This doesn't alter by belief that
    > the devfs filesystem is responsible for the /dev/tts/0 and that BSD PTY
    > or UNIX98 support should be used instead.


    Why would he want to use ptys at all? I thought that the original
    poster was using real serial ports. How did ptys come into the
    picture?

    I think all he really needs to do is:

    # mv /etc/ppp/options.ttyS0 /etc/ppp/options.tts.0

    (Of course, that's assuming that /dev/tts/0 really is correct. It
    seems to be. But perhaps there's another problem here that I don't
    see ...)

    --
    James Carlson, IP Systems Group
    Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677

  17. Re: Could not determine local IP address

    junk@foushee.cc (Carey) writes:

    ]Yet another update to hopefully help give you more data to
    ]troubleshoot with. I switched the roles of the machines and had the
    ]caller receive the phone and got the same results.

    ]So, either I have both machines set up wrong when they are receiving a
    ]phone call, or the the "/dev/tts/0" line in the receiving units syslog
    ]shows up that way for some reason on a receving call. Its like its
    ]just not reading /etc/options.ttyS0 ??

    Could well be. If the system thinks it is using /dev/tts/0 then it will not
    think it is using ttyS0.
    Try putting the options into /etc/options and see if they work there.
    Or use the
    file
    option to pppd on both sides (ie put it into the AutoPPP line on the
    receiving side and on the command line on the originating)



  18. Re: Could not determine local IP address

    junk@foushee.cc (Carey) writes:

    ]Thanks for the suggestions so far and sorry I should have included the
    ]ip addresses localLine and remoteLine. I did have both defined in the
    ]/etc/hosts and they weren't different depending on which machine they
    ]were one, but for the sake of debugging I'm using real ip addresses
    ]but it gave me the same result. Also, this time have both the caller
    ]and receiver's syslog.

    Put it on the command line in login.config

    AutoPPP - a_ppp /usr/sbin/pppd 169.254.10.1:169.254.2.1 ttyS0

    (use whatever IP you want for the local and remote)
    Fix one problem at a time. Get connected and then figure out why
    options.ttyS0 is not being read.



    ]Oh, by the way the modem speed is 2400 baud for the modems, the 19200
    ]is just the speed in which we communicate with the modems. I was
    ]under the understanding the CONNECT 19200 is really used anyhow, that
    ]the modems will negotiate the actual speed.

    Yee gads. That is slow.


    ]You know after reading over some of the comments again and looking at
    ]the receivers log (see below) there is a strang line "Connect: ppp0
    ]<--> /dev/tts/0" shouldn't that be "Connect: ppp0 <--> /dev/ttyS0".
    ]If so, where could that have got set wrong? I checked my
    ]/etc/rc.serial and its using setserial ttyS0 and /dev/ttyS0 was there
    ]as well.

    On many modern system, ttyS0 is simply a link to tts/0


    ]CALLER'S SETUP:

    ]/etc/options.ttyS0
    ]169.254.2.1:

    ]/etc/options
    ]lock
    ]login
    ]modem
    ]crtscts
    ]nodetach
    ]novj
    ]ipcp-accept-remote

    ]RECEIVER'S SETUP:
    ]/etc/options.ttyS0
    ]169.254.10.1:

    ]/etc/options
    ]lock
    ]login
    ]modem
    ]crtscts
    ]nodetach
    ]novj
    ]ipcp-accept-remote

    ]CALLER'S LOGFILE:
    ]Aug 4 11:25:29 localhost ifup-ppp: pppd started for ppp0 on
    ]/dev/ttyS0 at 19200
    ]Aug 4 11:25:30 localhost pppd[16727]: pppd 2.4.1 started by root, uid
    ]0
    ]Aug 4 11:25:31 localhost wvdial[16740]: WvDial: Internet dialer

    I do not like wvdial for debugging.

    ]version 1.53
    ]Aug 4 11:25:31 localhost wvdial[16740]: Initializing modem.
    ]Aug 4 11:25:31 localhost wvdial[16740]: Sending: ATZ
    ]Aug 4 11:25:31 localhost wvdial[16740]: ATZ
    ]Aug 4 11:25:31 localhost wvdial[16740]: OK
    ]Aug 4 11:25:31 localhost wvdial[16740]: Sending: ATQ0 V1 E1 S0=0 &C1
    ]&D2
    ]Aug 4 11:25:31 localhost wvdial[16740]: ATQ0 V1 E1 S0=0 &C1 &D2
    ]Aug 4 11:25:31 localhost wvdial[16740]: OK
    ]Aug 4 11:25:31 localhost wvdial[16740]: Modem initialized.
    ]Aug 4 11:25:31 localhost wvdial[16740]: Sending: ATDT00881631013780
    ]Aug 4 11:25:31 localhost wvdial[16740]: Waiting for carrier.
    ]Aug 4 11:25:32 localhost wvdial[16740]: ATDT00881631013780
    ]Aug 4 11:25:47 localhost wvdial[16740]: CONNECT 19200
    ]Aug 4 11:25:47 localhost wvdial[16740]: Carrier detected. Chatmode
    ]finished.
    ]Aug 4 11:25:47 localhost pppd[16727]: Serial connection established.
    ]Aug 4 11:25:47 localhost pppd[16727]: using channel 11
    ]Aug 4 11:25:47 localhost pppd[16727]: Using interface ppp0
    ]Aug 4 11:25:47 localhost pppd[16727]: Connect: ppp0 <--> /dev/ttyS0
    ]Aug 4 11:25:47 localhost /etc/hotplug/net.agent: assuming ppp0 is
    ]already up
    ]Aug 4 11:25:48 localhost pppd[16727]: sent [LCP ConfReq id=0x1 ]1200> ]
    ]Aug 4 11:25:57 localhost last message repeated 3 times
    ]Aug 4 11:25:58 localhost pppd[16727]: rcvd [LCP ConfReq id=0x1
    ] ]
    ]Aug 4 11:25:58 localhost pppd[16727]: sent [LCP ConfAck id=0x1
    ] ]
    ]Aug 4 11:25:58 localhost pppd[16727]: rcvd [LCP ConfAck id=0x1 ]1200> ]
    ]Aug 4 11:25:58 localhost pppd[16727]: sent [IPCP ConfReq id=0x1 ]169.254.2.1> ]
    ]Aug 4 11:25:58 localhost pppd[16727]: sent [CCP ConfReq id=0x1
    ] ]
    ]Aug 4 11:25:59 localhost pppd[16727]: rcvd [LCP ConfAck id=0x1 ]1200> ]
    ]Aug 4 11:25:59 localhost pppd[16727]: rcvd [LCP ConfAck id=0x1 ]1200> ]
    ]Aug 4 11:26:00 localhost pppd[16727]: rcvd [IPCP ConfReq id=0x1 ]0.0.0.0>]
    ]Aug 4 11:26:00 localhost pppd[16727]: sent [IPCP ConfRej id=0x1 ]0.0.0.0>]
    ]Aug 4 11:26:00 localhost pppd[16727]: rcvd [CCP ConfReq id=0x1
    ] ]
    ]Aug 4 11:26:00 localhost pppd[16727]: sent [CCP ConfAck id=0x1
    ] ]
    ]Aug 4 11:26:00 localhost pppd[16727]: rcvd [IPCP ConfRej id=0x1
    ] ]
    ]Aug 4 11:26:00 localhost pppd[16727]: sent [IPCP ConfReq id=0x2 ]169.254.2.1>]
    ]Aug 4 11:26:00 localhost pppd[16727]: rcvd [CCP ConfAck id=0x1
    ] ]
    ]Aug 4 11:26:00 localhost pppd[16727]: Deflate (15) compression
    ]enabled
    ]Aug 4 11:26:02 localhost pppd[16727]: rcvd [IPCP ConfReq id=0x2
    ]]
    ]Aug 4 11:26:02 localhost pppd[16727]: sent [IPCP ConfRej id=0x2
    ]]
    ]Aug 4 11:26:02 localhost pppd[16727]: rcvd [IPCP ConfAck id=0x2 ]169.254.2.1>]
    ]Aug 4 11:26:03 localhost pppd[16727]: sent [IPCP ConfReq id=0x2 ]169.254.2.1>]
    ]Aug 4 11:26:04 localhost pppd[16727]: rcvd [IPCP ConfReq id=0x3]
    ]Aug 4 11:26:04 localhost pppd[16727]: sent [IPCP ConfAck id=0x3]
    ]Aug 4 11:26:05 localhost kernel: eql: timer found dead slave,
    ]burying...
    ]Aug 4 11:26:05 localhost pppd[16727]: rcvd [IPCP ConfAck id=0x2 ]169.254.2.1>]
    ]Aug 4 11:26:05 localhost pppd[16727]: Could not determine remote IP
    ]address: defaulting to 10.64.64.64
    ]Aug 4 11:26:05 localhost pppd[16727]: local IP address 169.254.2.1
    ]Aug 4 11:26:05 localhost pppd[16727]: remote IP address 10.64.64.64
    ]Aug 4 11:26:05 localhost pppd[16727]: Script /etc/ppp/ip-up started
    ](pid 17060)
    ]Aug 4 11:26:06 localhost pppd[16727]: rcvd [IPCP TermReq id=0x4
    ]"Could not determine local IP address"]
    ]Aug 4 11:26:06 localhost pppd[16727]: IPCP terminated by peer (Could
    ]not determine local IP address)
    ]Aug 4 11:26:06 localhost pppd[16727]: sent [IPCP TermAck id=0x4]
    ]Aug 4 11:26:07 localhost pppd[16727]: Script /etc/ppp/ip-up finished
    ](pid 17060), status = 0x0
    ]Aug 4 11:26:07 localhost pppd[16727]: Script /etc/ppp/ip-down started
    ](pid 17107)
    ]Aug 4 11:26:07 localhost pppd[16727]: Script ?? finished (pid 16736),
    ]status = 0x0
    ]Aug 4 11:26:07 localhost kernel: eql: timer found dead slave,
    ]burying...
    ]Aug 4 11:26:08 localhost pppd[16727]: rcvd [LCP TermReq id=0x2 "No
    ]network protocols running"]
    ]Aug 4 11:26:08 localhost pppd[16727]: LCP terminated by peer (No
    ]network protocols running)
    ]Aug 4 11:26:08 localhost pppd[16727]: sent [LCP TermAck id=0x2]
    ]Aug 4 11:26:08 localhost pppd[16727]: Script /etc/ppp/ip-down
    ]finished (pid 17107), status = 0x0
    ]Aug 4 11:26:11 localhost pppd[16727]: Connection terminated.
    ]Aug 4 11:26:11 localhost pppd[16727]: Connect time 0.4 minutes.
    ]Aug 4 11:26:11 localhost pppd[16727]: Sent 100 bytes, received 134
    ]bytes.
    ]Aug 4 11:26:11 localhost pppd[16727]: Hangup (SIGHUP)
    ]Aug 4 11:26:11 localhost pppd[16727]: Exit.

    ]RECEIVER'S LOGFILE:
    ]Aug 4 13:12:13 localhost pppd[2201]: pppd 2.4.1 started by root, uid
    ]0
    ]Aug 4 13:12:13 localhost pppd[2201]: Using interface ppp0
    ]Aug 4 13:12:13 localhost pppd[2201]: Connect: ppp0 <--> /dev/tts/0
    ]Aug 4 13:12:13 localhost /etc/hotplug/net.agent: assuming ppp0 is
    ]already up
    ]Aug 4 13:12:17 localhost pppd[2201]: Deflate (15) compression enabled
    ]Aug 4 13:12:21 localhost pppd[2201]: Could not determine local IP
    ]address
    ]Aug 4 13:12:23 localhost kernel: eql: timer found dead slave,
    ]burying...
    ]Aug 4 13:12:24 localhost pppd[2201]: Connection terminated.
    ]Aug 4 13:12:24 localhost pppd[2201]: Connect time 0.2 minutes.
    ]Aug 4 13:12:24 localhost pppd[2201]: Sent 94 bytes, received 100
    ]bytes.
    ]Aug 4 13:12:24 localhost pppd[2201]: Exit.

    ]RECEIVER'S /var/log/mgetty.ttyS0
    ]08/04 13:09:22 yS0 mgetty: experimental test release 1.1.30-Dec16
    ]08/04 13:09:22 yS0 check for lockfiles
    ]08/04 13:09:22 yS0 locking the line
    ]08/04 13:09:22 yS0 WARNING: DCD line still active, check modem
    ]settings (AT&Dx)
    ]08/04 13:09:22 yS0 lowering DTR to reset Modem
    ]08/04 13:09:23 yS0 TIOCMBIS failed: Input/output error
    ]08/04 13:09:23 yS0 cannot turn off soft carrier: Input/output error
    ]08/04 13:09:23 yS0 tcgetattr failed: Input/output error
    ]08/04 13:09:23 yS0 cannot get TIO: Input/output error
    ]08/04 13:09:23 yS0 mg_init_device failed, trying again
    ]08/04 13:09:23 yS0 lowering DTR to reset Modem
    ]08/04 13:09:23 yS0 send: \dATQ0V1H0[0d]
    ]08/04 13:09:24 yS0 waiting for ``OK'' ** found **
    ]08/04 13:09:24 yS0 send: ATS0=0Q0&D3&C1[0d]
    ]08/04 13:09:24 yS0 waiting for ``OK'' ** found **
    ]08/04 13:09:24 yS0 waiting...
    ]08/04 13:09:43 yS0 wfr: waiting for ``RING''
    ]08/04 13:09:43 yS0 send: ATA[0d]
    ]08/04 13:09:43 yS0 waiting for ``CONNECT'' ** found **
    ]08/04 13:09:44 yS0 send:
    ]08/04 13:09:44 yS0 waiting for ``_'' ** found **
    ]08/04 13:09:55 ##### failed dev=ttyS0, pid=1909, got signal 1, exiting

    ]--
    ]08/04 13:09:55 yS0 mgetty: experimental test release 1.1.30-Dec16
    ]08/04 13:09:55 yS0 check for lockfiles
    ]08/04 13:09:55 yS0 locking the line
    ]08/04 13:09:55 yS0 lowering DTR to reset Modem
    ]08/04 13:09:56 yS0 send: \dATQ0V1H0[0d]
    ]08/04 13:09:56 yS0 waiting for ``OK'' ** found **
    ]08/04 13:09:56 yS0 send: ATS0=0Q0&D3&C1[0d]
    ]08/04 13:09:56 yS0 waiting for ``OK'' ** found **
    ]08/04 13:09:57 yS0 waiting...
    ]08/04 13:12:02 yS0 wfr: waiting for ``RING''
    ]08/04 13:12:02 yS0 send: ATA[0d]
    ]08/04 13:12:02 yS0 waiting for ``CONNECT'' ** found **
    ]08/04 13:12:03 yS0 send:
    ]08/04 13:12:03 yS0 waiting for ``_'' ** found **
    ]08/04 13:12:13 ##### data dev=ttyS0, pid=2201, caller='none',
    ]conn='19200', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'


  19. Re: Could not determine local IP address

    Sure enough /dev/ttyS0 is symbolic link to /dev/tts/0. Is that
    "normal"? Oh, I have mandrake 9.1 which uses kernel 2.4.21.

    I made a /etc/ppp/options.tts.0 and everything worked fine.

    Here's the lines I put at the end of /etc/inittab file (which are the
    only changes I made):
    # Run mgetty to listen for incoming connections
    S0:2345:respawn:/sbin/mgetty -D ttyS0 -s 19200
    S1:2345:respawn:/sbin/mgetty -D ttyS1 -s 19200
    S2:2345:respawn:/sbin/mgetty -D ttyS2 -s 19200
    S3:2345:respawn:/sbin/mgetty -D ttyS3 -s 19200

    Also, I can tail and watch mgetty's log at /var/log/mgetty.ttyS0. So,
    I'm confused as to whats going here.

    Part of me is saying its working don't worry about it, but I would
    like to understand it and make any improvements (if possible) as well.

    Thanks.
    Carey

  20. Re: Could not determine local IP address

    junk@foushee.cc (Carey) writes:
    > Also, I can tail and watch mgetty's log at /var/log/mgetty.ttyS0. So,
    > I'm confused as to whats going here.
    >
    > Part of me is saying its working don't worry about it, but I would
    > like to understand it and make any improvements (if possible) as well.


    As I described in an earlier posting:

    Pppd uses one of two methods to determine the name of the serial port
    in use. If the name is specified on the pppd command line, then that
    name is used. If the name is not specified, then pppd calls the
    ttyname() function giving 0 (standard input) as the argument. The
    string that function returns is used as the name of the serial port.

    The name of the serial port -- no matter how determined -- is then
    used to figure the name of the appropriate /etc/options. file
    to load.

    Why ttyname() is returning /dev/tts/0 when you expect /dev/ttyS0 is
    something to ask the Linux maintainers, not pppd.

    --
    James Carlson, IP Systems Group
    Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677

+ Reply to Thread
Page 1 of 2 1 2 LastLast