Date: Sun, 14 Feb 1999 18:32:05 From: Ross Finlayson <finlayson@live.com> To: dmaddox@conterra.com Cc: multimedia@FreeBSD.ORG Subject: "mrouted" over a modem connection Message-ID: <3.0.5.16.19990214183205.6bf7af06@shell7.ba.best.com> In-Reply-To: <19990214181851.A230@dmaddox.conterra.com> References: <3.0.5.16.19990214145504.210f3c9c@shell7.ba.best.com> <3.0.5.16.19990212230409.0a2f3962@shell7.ba.best.com> <19990207123933.A3236@dmaddox.conterra.com> <3.0.5.16.19990212230409.0a2f3962@shell7.ba.best.com> <19990213121112.A23304@dmaddox.conterra.com> <3.0.5.16.19990214145504.210f3c9c@shell7.ba.best.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 06:18 PM 2/14/99 -0500, Donald J . Maddox wrote: >Wow, 33.6 huh? Sometimes my 128K ISDN link gets utterly swamped >by big route updates... It's amazing that you find it useable at >such a low bitrate. Maybe you know some configuration tricks that >I don't? I'd really like to get a look at your mrouted.conf No tricks; it's just: tunnel <my-addr> <remote-addr> rate_limit 28 >and the one on your [remote?] host :-) It's similar, as far as I know. Yes, my link sometimes gets swamped by routing updates too (especially just after "mrouted" starts up), but this doesn't happen often enough to be a problem. It's important, though, to run "mrouted" v2.9, so that DVMRP prunes get retransmitted, for reliability. Ross. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.5.16.19990214183205.6bf7af06>