From owner-freebsd-isdn Sat Dec 19 12:19:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13140 for freebsd-isdn-outgoing; Sat, 19 Dec 1998 12:19:16 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from castor2.freiepresse.de (castor2.freiepresse.de [194.25.232.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13019 for ; Sat, 19 Dec 1998 12:19:10 -0800 (PST) (envelope-from G.Sittig@abo.FreiePresse.DE) Received: from speedy.gsinet (ppp-pln173.freiepresse.de [194.25.234.173]) by castor2.freiepresse.de (8.8.4/8.8.4) with ESMTP id VAA05838 for ; Sat, 19 Dec 1998 21:17:08 +0100 (MET) Received: from speedy.gsinet (sittig@speedy.gsinet [192.168.10.129]) by speedy.gsinet (8.8.8/8.8.8) with SMTP id QAA32738 for ; Sat, 19 Dec 1998 16:07:17 +0100 Date: Sat, 19 Dec 1998 16:07:16 +0100 (CET) From: Gerhard Sittig X-Sender: sittig@speedy.gsinet cc: FreeBSD-ISDN Mailingliste Subject: Re: updates to i4b In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org There was a discussion here lately about the first packets being dropped (or strictly speaking not being answered to correctly) which seems to apply to this case. Packets being generated when the connection is established get all the params right and cause no trouble. On Wed, 16 Dec 1998, Nico Bouthoorn wrote: > DNS?, I've made a setup with my own named server and dns caching, > if the connection is timed out I've also to call up the URL twice. That's when the DNS query is handled locally and the HTTP requests causes the first packets to go out (and trigger dialing, which does a renegotiation of the addresses and invalidates the source address the packet already carries). > I've a dynamic IP number instead of a fixed one. That's the prerequisite to these kind of problems :) > If I use the dns server of the ISP everything works fine > I want to use this setup for a small office network. Then the DNS query triggers dialing and experiences the problem. The HTTP request sees an established connection. It always turns out to be the same scenario. The solution to this is the dynip patch (available for Linux, at least) which queues the triggering packets and resends them with the current IP address after IPCP negotiation took place. > > I'm connected to my ISP via i4b's ppp. > > i4b is configured to hang up after a certain idle time. > > > > Let's say I browse the web with netscape, often I have to > > call up URL two times (first time to initiate a new connection, > > second time to fetch the page) and after some time, I get > > strange error messages. Gerhard Sittig -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message