Reviving an old thread, I know, but I just ran into this need myself...
The original post asked how to use diald to set up and tear down an
interface to a second ethernet card instead of a modem. The second card was
connected to an ISDN router box such as a 3Com Office Connect LANModem.
The reply was that it was the router's job to bring the link up and down.
Well, that may be, but one could also argue that it is the *modem*'s job to
disconnect on idle, and if that worked as it should we wouldn't be
exchanging these little messages here, would we? In fact, all-in-one
router/modem boxes such as the OCLM suffer from the same problem as modems -
ISPs and the local network throw junk up and down the pipe which keeps the
link up when it needn't be.
Even if that weren't the case, using diald (or something like it) to control
the link state also allows one to generate statistics and link up-time and
traffic, which are really helpful in determining how to tune things.
Which leads back to the question - is there some configuration which will
allow diald to exert control over when traffic is allowed to go to/from the
router over that second NIC? For instance, the ip-up and ip-down scripts
could run ipchains to allow or disallow traffic to/from the card. Diald
would essentially do nothing except run the scripts at the appropriate
times, and record the activity in a log file. It would still, of course, be
monitoring/filtering traffic through the second interface so as to know when
to run the scripts.
As I said at the beginning, I have just run into a this situation myself and
haven't had time to play at making a solution...
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
