Hi, in the meantime I found a solution in a mail from Darren Greaves:
with two commands
# echo 1 > /proc/sys/net/ipv4/ip_forward
# echo 5 > /proc/sys/net/ipv4/ip_dynaddr
i got the hole thing going. Darren writes the two lines to a rc.d
file, I haven't done this but it shouldn't be a problem.
In case you understand why these commands work, I'd love an
explanation...
yours, Simon
>>>>>>>>>>>>>>>>>> Urspr�ngliche Nachricht <<<<<<<<<<<<<<<<<<
Am 1/24/00, 3:18:47 AM, schrieb Mathew <[EMAIL PROTECTED]> zum
Thema RE: two tries too get going:
> Hey, I'm getting the same thing. Wish someone out here can
> give some directions.
> Thanks
> Mat
> -----Original Message-----
> From: Simon Wenger [SMTP:[EMAIL PROTECTED]]
> Sent: Sunday, January 23, 2000 7:59 AM
> To: [EMAIL PROTECTED]
> Subject: two tries too get going
> Hello everybody,
> I know my diald 0.16 is really old, but after all I have most of it
> working and I don't think my problem has to do with the version ;-)...
> Every first try to connect fails in a timeout error of the connect
> script. (It dials ok, et voil�, that's it...), BUT funny enough every
> second try works fine. That must have something to do with the
> routing. I'm trying to find information about this, can you give me
> the man or any hints?
> Thanks, Simon
> -
> 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]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
