OK, I think the problem here might not be with linux. I've got a windows 98
and a 2000 machine being masqueraded, yet the 98 doesn't time out while the
2000 does. So, does anyone know of somewhere to increase the timeout?
Adding dns servers has no effect.
What really puzzles me is why my impact iq takes 25 seconds before it begins
transferring. Shouldn't ISDN come up faster? Any ideas what I might have
configured incorrectly?
Just a thought,
Jacob Joseph
----- Original Message -----
From: "Erik Corry" <[EMAIL PROTECTED]>
To: "Michel Bouissou" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; "Steve Christall" <[EMAIL PROTECTED]>
Sent: Tuesday, January 11, 2000 3:08 AM
Subject: Re: First packets lost [Was: windows bringing up the link]
> On Tue, Jan 11, 2000 at 11:19:28AM +0100, Michel Bouissou wrote:
> > Hello,
> >
> > Erik Corry wrote:
> >
> > > > >echo "1" > /proc/sys/net/ipv4/ip_dynaddr
> > > >
> > > > Yes, I had it setup this way for long, but it doesn't help...
> > >
> > > You definitely need that, so if you got rid of it, put
> > > it back. It just can't work without that, especially if
> > > you have a cacheing name server on the Linux host.
> >
> > I have left it on,
>
> Good.
>
> I think you need to switch off the reroute option on diald, by the
> way.
>
> This stuff does work for a lot of people. I'm not sure why it doesn't
> work for a few.
>
> If you have a Linux machine in the masqueraded net, you might want to
> see whether it works from there. Something like
>
> telnet 17.254.0.91 80
>
> which should connect you to the http server of www.apple.com. Press
> return twice to get out again. For that matter, you might like to
> try that from the masquerading diald host, where it really should
> work too.
>
> > > Now you need to make sure that your Windows machines
> > > are not giving up too soon. Someone already posted the
> > > registry setting, you probably need that too.
> >
> > I don't think that this is the issue for the following reason: I made
the
> > following test:
> > - From one of my Windows machines, I request a Web page, that causes
dials
> > to dial. Using an analog modem, I know the dialing takes some time. So I
> > watch the dialing process and when the modem link establishes, I kill
the
> > web page request on the Windows machine, and request a web page from
another
> > machine. At this step, it will only take less than 5 seconds before the
PPP
> > link actually comes up.
> > - Anyway, the machine that requested the web page some seconds before
the
> > link is up will get no answer, and timeout, but much later.
>
> Well, you are probably right, that is not the answer.
>
> > > If that doesn't work, then a tcpdump of the PPP link
> > > while the problem is happening would be cool, though
> > > it's difficult to get that to work in my experience,
> > > since tcpdump doesn't like interfaces that go up and down.
> >
> > Yep, I'm not familar enough with tcpdump and the like to perform
thorough
> > testings on this.
>
> Unfortunately, noone who has the problem has yet managed to do a
> tcpdump of it.
>
> Did you already post the options you are giving diald? It might be
> good to see the output of 'route -n' and 'ifconfig' just after the
> link comes up.
>
> --
> Erik Corry [EMAIL PROTECTED] Ceterum censeo, Microsoftem esse
delendam!
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
