On Mon, 18 May 1998, David A. Ranch wrote:
>
> >I could not get dhcpcd to work on 2.1.90, but I could manually
> >configure the ethernet with the proper IP and communicate with the
> >local network and the world.
>
> Hmmm.. that's odd. What version of dhcpcd are you running?
I tried so many versions I'm not even sure... I tried 0.65, 0.70, 1.3.3,
and a beta of 2.0 (I think the 2.0 one is a totally different client)
None of them worked under 2.1.102, all of them worked under 2.0.34pre14.
> echo "Extending MASQ timeouts.."
> /sbin/ipfwadm -M -s 7200 10 120
great, thanks! 7200 is only two hours. Is there a lot of problem
increasing that to something much larger, such as two days? Obviously it
takes more load to keep track of connections for that long, but my system
is pretty lightly used (only two machines behind the lan, my brother plays
a lot of net games and other short connects, and the TCPFIN timeout should
clear those out. I just like to leave an xbiff open from my server at
school, and I like keeping xterms around too.)
>
>
> BTW, if you haven't checked it out, check out my TrinityOS document.
> Its a HOWTO for setting up MASQ, DHCP, dual nics (cablemodems), DNS,
> PPP+DIALD (modem users), MASQ Sendmail, Security patching, etc.
Thanks for the pointer - it looks like good info.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]
