The question is, are they charging you for total bandwidth used, or some real time rate limit? When you use bandwidth shaping, you can reduce your rate, but that will just spread things out. So if they are charging you for total bytes moved, then you would have to do some math to figure out what that breaks down to in Mbps, and put a throttle in to that rate. I'm not sure what Mike means by packets already traversing the network. If you shape your bandwidth, it's not like all those packets just pile up at your server's front door, waiting to get in. The IP protocol will pause within itself to not exceed your defined bandwidth.
-Daniel -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Hari Bhaskaran Sent: Friday, January 03, 2003 6:24 PM To: [EMAIL PROTECTED] Subject: Re: incoming bandwidth limiting using ipfilter > Hari: > > I think you are going to find that rate-limiting at the box won't > provide any fiscal relief. The packets have already traversed your > ISP's interface where the accounting is taking place. > > Mike That's bad. But if the machine doesn't accept more than N packets/sec, why would the ISP router forward any more packets to it? I wouldn't know the internals, but isn't there any kind of flow control in the protocol? -- Hari Bhaskaran (Mike, although I have cc-ed the list I haven't included your email anywhere in the reply) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
