David Talkington wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
>
> An aside here; I've heard that dial-on-demand is alleged to have had
> problems in Linux, but I've never had any trouble with it.
diald has been very flakey for me. It just won't redial when the ISP
kills the connection even though I have it configured to force the
connection up between certain times.
> If it's an idle timeout, sometimes a cron-induced ping might be enough
> to keep you alive.
>
It isn't an idle timeout for which I get dropped. It happens
infrequently enought to *almost* ignore but frequently enough to be
annoying.
> >rules are being flushed properly, apparently by /etc/ppp/ip-down.local
> >-- but when PPP, because of the "persist" option in options, redials
> >the ISP and the link is up the /etc/ppp/ip-up.local script appears to
> >be ignored. None of the machines can get out to the Internet and a
> >quick check of the ipchains rules in force shows that none are. e.g.
> >ipchains -L -n shows ACCEPTS for the three chains without anything.
>
> It would help to see your ipchains scripts, and perhaps the
> ip-up.local.
>
I'm not currently at the office so I can't post it right now but will
shortly.
> Be aware, though, that it may not be necessary to go to all that
> trouble. I leave my firewall and masquarading rules in place
> permanently, and let pppd handle route changes dynamically with the
> defaultroute option. Is your setup too complex for that to work for
> you (e.g., you don't want all clients to have access to ppp0)?
>
Hmmm. I'll have to investigate that. I thought I'd need the IP
address of PPP0 for the firewall and masq to work correctly. Am I
wrong on this? Would you be willing to post or e-mail me your
firewall/masq script so that I may compare it with mine?
Thanks very much for replying David.
Barry
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
