From owner-freebsd-isdn Mon Apr 6 05:38:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA18691 for freebsd-isdn-outgoing; Mon, 6 Apr 1998 05:38:05 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA18671 for ; Mon, 6 Apr 1998 05:38:00 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id OAA10100; Mon, 6 Apr 1998 14:35:53 +0200 (CEST) To: Arve Ronning cc: freebsd-isdn@FreeBSD.ORG Subject: Re: I4B: IPCP address negotiation In-reply-to: Your message of "Mon, 06 Apr 1998 14:20:03 +0200." <3528C873.88DEB913@alcatel.no> Date: Mon, 06 Apr 1998 14:35:53 +0200 Message-ID: <10098.891866153@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <3528C873.88DEB913@alcatel.no>, Arve Ronning writes: >The following is a slightly edited log from a _successful_ >call to my ISP > > Apr 5 12:27:03 Gate /kernel: isppp0: > > ipcp input(req-sent): > ipcp nak opts: address [wantaddr 192.193.194.179] [agree] > ipcp output > ipcp input(req-sent): > ipcp parse opts: address > ipcp parse opt values: address 0.0.0.1 [ack] send conf-ack > ipcp output > ipcp input(ack-sent): > ipcp tlu > >If I understand this correctly, my end accepts his proposal to use >hisaddr = 192.193.194.244. However, netstat shows that my end >continues to use hisaddr = 0.0.0.1. I'm worried about sending an >illegal IP address onto the Internet. This is all correct, you will not send illegal IPs. >If yes, what makes 0.0.0.1 special ? (reserved use in PPP ?) Read the manpage. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message