>> 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.
Well, though I know the 2.0.x kernels very well, I've only started to
play around with th 2.1.x kernels. With the 2.1.x kernels, you
need to use Juanjo's "IPMASQADM" timeout program to change TCP timeouts
vs. using IPFWADM for the 2.0.x kernels.
Check out his site at:
http://juanjox.home.ml.org
About DHCP, does it work on the INSIDE LAN? When you load DHCPd on
the Linux box, what does it log in /var/log/messages? Also.. per
the instructions.. are you creating the 255.255.255.255 route?
>great, thanks! 7200 is only two hours. Is there a lot of problem
>increasing that to something much larger, such as two days?
Like Nigel said, it's kinda silly. You can do it if you want
but I usually find 2hrs is fine. Plus... xbiff should keep your
connections active as long as you get an email every 2 hrs.
--David
.----------------------------------------------------------------------------.
| David A. Ranch - Remote Access/Linux/PCs [EMAIL PROTECTED] |
!---- ----!
`----- For more detailed info, see http://www.ecst.csuchico.edu/~dranch -----'
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]
