Date: Tue, 07 Dec 1999 23:07:56 +0100 From: Gary Jennejohn <garyj@peedub.muc.de> To: Juergen Lock <nox@jelal.kn-bremen.de> Cc: Gary Jennejohn <garyj@muc.de>, freebsd-isdn@FreeBSD.ORG Subject: Re: i4b syncppp not talking with Ascend Max (HP,4000-6000) version 6.1.3 - 6.1.7 ? Message-ID: <199912072207.XAA05730@peedub.muc.de> In-Reply-To: Your message of "Tue, 07 Dec 1999 21:27:57 %2B0100." <19991207212756.A1824@saturn.kn-bremen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Juergen Lock writes: > >OK here you go... > >isp3: ipcp nak opts: address [wantaddr 212.162.0.121] <7>isp3: sppp_set_ip_ad >dr: rtinit DEL failed, error=65 <== EHOSTUNREACH >isp3: sppp_set_ip_addr: rtinit ADD failed, error=17[agree] <== EEXIST > ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Hmm is that the problem, does that mean it is unable to add the route? > Certainly looks like it. It appears that the kernel is convinced that a route already exists. The fact that you were still seeing 0.0.0.0 using ethereal (as reported in your previous mail) supports that. The failure to delete can be explained by the fact that was no route there to be deleted, I suppose. Unfortunately, I can't tell what happens in a normal connection because I have static IP addresses and sppp_set_ip_addr never gets called. Does it work to other ISPs ? >isp3: ipcp output <conf-req id=0x4 len=10 03-06-d4-a2-00-79> >isp3: ipcp input(req-sent): <conf-req id=0x2 len=10 03-06-c3-7a-80-21> >isp3: ipcp parse opts: address >isp3: ipcp parse opt values: address 0.0.0.1 [ack] send conf-ack >isp3: ipcp output <conf-ack id=0x2 len=10 03-06-c3-7a-80-21> >isp3: ipcp input(ack-sent): <conf-ack id=0x4 len=10 03-06-d4-a2-00-79> >isp3: ipcp tlu >isp3: lcp close(opened) >isp3: phase terminate did you bring the interface down here ? The failure in sppp_set_ip_addr should not cause this. >isp3: ipcp down(opened) >isp3: ipcp close(starting) >isp3: sppp_set_ip_addr: rtinit DEL failed, error=65 >isp3: sppp_set_ip_addr: rtinit ADD failed, error=17<7>isp3: lcp output <term-r >eq id=0x5 len=4> here it's trying to reinstate the old IP address in the routing table. >isp3: lcp input(closing): <term-ack id=0x5 len=4> >isp3: phase dead >isp3: lcp down(closed) >isp3: Down event (carrier loss) > > So, is the problem maybe just that the local and remote addresses are on >entirely different nets? Is that against the ppp spec? > I don't know for sure, but I don't think so. Seems to me that I was getting IP addressed which had almost no relation to the address of the router when I was still using an ISP who assigned dynamic addresses. Unfortunately, I can't explain why adding the route fails. The routing code is nearly impossible to understand based on cursory examination and I'm not willing to invest the time needed to figure it out. --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912072207.XAA05730>