On Mon, 20 Dec 1999, Jeff Cadow wrote:
> Have you tried the "nodefaultip" option with ppp v2.3.10?
>
Here are the fragment of my script file:
------------------------------------------------------
LOCAL_IP="195.58.18.5"
REMOTE_IP="195.58.18.6"
NETMASK=255.255.255.254
SPEED=38400
DEVICE=ttyS1
exec /usr/sbin/pppd debug 9 lock modem crtscts /dev/$DEVICE $SPEED \
escape FF kdebug 0 $LOCAL_IP:$REMOTE_IP \
bsdcomp 10,10 asyncmap 20A0000 nodefaultip \
noipdefault netmask $NETMASK defaultroute ipparam "root"
-------------------------------------------------------
and the result of "nodefaultip" option:
/usr/sbin/pppd: unrecognized option 'nodefaultip'
pppd version 2.3.10
Usage: /usr/sbin/pppd [ options ], where options are:
...
> >From the 2.3.10 README:
>
> * The `nodefaultip' option can be used in demand mode to say that pppd
> should not suggest its local IP address to the peer.
>
> The README.linux that comes with 2.3.10 says the following about local IP
> addresses:
>
> Here's a command for connecting to a PPP server by modem.
>
> pppd connect 'chat -v "" ATDT5551212 CONNECT "" ogin: ppp word:
> whitewater' \
> /dev/cua1 38400 debug crtscts modem defaultroute 192.1.1.17
>
> [...]
>
> 192.1.1.17 this is a degenerate case of a general option
> of the form x.x.x.x:y.y.y.y . Here x.x.x.x is the local IP
> address and y.y.y.y is the IP address of the remote end of the
> PPP connection. If this option is not specified, or if just
> one side is specified, then x.x.x.x defaults to the IP address
> associated with the local machine's hostname (in /etc/hosts),
> and y.y.y.y is determined by the remote machine. So if this
> example had been taken from the fictional machine 'billpc',
> this option would actually be redundant.
>
> Try checking your /etc/hosts file.
>
> Hope that's helpful.
>
> --Jeff Cadow
> Trilogy, Inc.
> Concord, MA
> www.tril-inc.com
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Dr.Nick P.Kostrov
> Sent: Monday, December 20, 1999 7:34 AM
> To: Linux-ppp list
> Subject: pppd-2.3.10: "Could not determine local IP address"
>
>
> Hello all,
>
> Recently I try to change the kernel on my network server to the new
> v2.3.33. But I can't. I've run into strange behavior of ppp-2.3.10(9) with
> this kernel.
> pppd says "Could not determine local IP address" and terminates the
> work:
>
> sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <compress VJ 0f 01>]
> rcvd [IPCP ConfRej id=0x1 <addr 0.0.0.0> <compress VJ 0f 01>]
> sent [IPCP ConfReq id=0x2 <addrs 0.0.0.0 195.58.18.6>]
> rcvd [IPCP ConfRej id=0x2 <addrs 0.0.0.0 195.58.18.6>]
> sent [IPCP ConfReq id=0x3]
> rcvd [IPCP ConfAck id=0x3]
> rcvd [IPCP ConfReq id=0x7f <addr 195.58.18.6>]
> sent [IPCP ConfAck id=0x7f <addr 195.58.18.6>]
> sent [IPCP TermReq id=0x4 "Could not determine local IP address"]
> rcvd [IPCP TermAck id=0x4]
> sent [LCP TermReq id=0x2 "No network protocols running"]
> rcvd [LCP TermAck id=0x2]
>
>
> The same was with v2.2.13.
>
> When I used pppd-2.3.5 with kernel 2.2.13 there are no problems. The system
> works fine. But pppd-2.3.5 doesn't work with kernel 2.3.33:
>
> /usr/sbin > pppd
> pppd: This system lacks kernel support for PPP. This could be because
> the PPP kernel module is not loaded, or because the kernel is
> not configured for PPP. See the README.linux file in the
> ppp-2.3.5 distribution.
>
>
> Can anybody tell me *how to* run pppd with the kernel v2.3.33?
>
> Thanks in advance,
> Nick
>
> P.S.
> I have leased line connection to ISP and Sclackware 4.0 inststalled on my
> PC.
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
> the body of a message to [EMAIL PROTECTED]
>
--
Dr. Nick P. Kostrov, Tel.: +7(3432) 678 880
Institute of Geophysics Fax : +7(3432) 678 872
100 Amundsen St. , E-mail: [EMAIL PROTECTED]
Ekaterinburg, 620016,
Russia.
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
