Date: Wed, 08 Dec 1999 09:46:06 +0100 From: Gary Jennejohn <garyj@peedub.muc.de> To: Juergen Lock <nox@jelal.kn-bremen.de> Cc: 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: <199912080846.JAA06546@peedub.muc.de> In-Reply-To: Your message of "Wed, 08 Dec 1999 01:18:24 %2B0100." <19991208011823.A18553@saturn.kn-bremen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Juergen Lock writes:
>On Tue, Dec 07, 1999 at 11:07:56PM +0100, Gary Jennejohn wrote:
>> Does it work to other ISPs ?
>> =
> Yep, with mobilcom or talkline for example it works. (essentially same
>setup, just other interfaces with different numbers and login/passwords.=
)
>At my `regluar' ISP btw i have static IPs too (and still use raw IP not
>syncppp for lower overhead), but during the day these `Call-by-Call'
>ISPs are cheaper than a local call, and that not working new one
>now even would be between 1800 and 2100...
>
OK, I played around some. Here's what I discovered:
# netstat -nra
isp0: flags=3Da015<UP,DEBUG,POINTOPOINT,LINK1,MULTICAST> mtu 1500
inet 0.0.0.0 --> 0.0.0.1 netmask 0xff000000
isp1: flags=3Da011<UP,POINTOPOINT,LINK1,MULTICAST> mtu 1500
inet 193.149.49.109 --> 193.149.48.12 netmask 0xffffff00
isp2: flags=3Da015<UP,DEBUG,POINTOPOINT,LINK1,MULTICAST> mtu 1500
inet 0.0.0.0 --> 0.0.0.1 netmask 0xffffffff
isp0 points at one of my ISPs, isp2 points at L=FCbeckernachrichten. Try
to connect to LN:
Dec 8 09:20:55 peedub /kernel.nb: isp2: ipcp nak opts: address [wantadd=
r 212.162.14.157] <7>isp2: sppp_set_ip_addr: rtinit DEL =
failed, error=3D65
Dec 8 09:20:55 peedub /kernel.nb: isp2: sppp_set_ip_addr: rtinit ADD fai=
led, error=3D17[agree]
same thing you saw.
# ifconfig isp0 down delete
# netstat -nra
isp0: flags=3Da014<DEBUG,POINTOPOINT,LINK1,MULTICAST> mtu 1500
isp1: flags=3Da011<UP,POINTOPOINT,LINK1,MULTICAST> mtu 1500
inet 193.149.49.109 --> 193.149.48.12 netmask 0xffffff00
isp2: flags=3Da015<UP,DEBUG,POINTOPOINT,LINK1,MULTICAST> mtu 1500
inet 0.0.0.0 --> 0.0.0.1 netmask 0xffffffff
Connect to LN:
Dec 8 09:24:10 peedub /kernel.nb: isp2: ipcp input(req-sent): <conf-nak =
id=3D0x6 len=3D10 03-06-d4-a2-0f-b3>
Dec 8 09:24:10 peedub /kernel.nb: isp2: ipcp nak opts: address [wantadd=
r 212.162.15.179] [agree]
Dec 8 09:24:10 peedub /kernel.nb: isp2: ipcp output <conf-req id=3D0x7 l=
en=3D10 03-06-d4-a2-0f-b3>
it works !!! And they have a fast internet connection, too.
So, it's obvious that you cannot have more than 1 interface with 0.0.0.0 =
and
0.0.0.1 and expect it to succeed. Seems reasonable, since the routing
routines see 2 entries with the same addresses and just reject any attemp=
t
to modify the second one.
This would be a good application for connect/disconnect scripts. Just dow=
n
and delete any interfaces with 0.0.0.0/0.0.0.1 after use and up them just=
before use.
Seems like a good FAQ entry.
---
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?199912080846.JAA06546>