15 Feb
2013
15 Feb
'13
9:46 a.m.
Looks like space (192.168.0.3) is consuming 100% of our bandwidth. anyone
know what's up with that? if it's bit torrent can we cap it around 3 Mbit
to allow some wiggle room for user's connections?
-Wolfy
15 Feb
15 Feb
6:24 p.m.
On Fri, Feb 15, 2013 at 9:46 AM, Matthew Meier <wolfy(a)wlfy.it> wrote:
Looks like space (192.168.0.3) is consuming 100% of
our bandwidth. anyone
know what's up with that? if it's bit torrent can we cap it around 3 Mbit
to allow some wiggle room for user's connections?
Yeah that was me. I limited the bandwidth thinking the unit was
kilobits and it was actually kilobytes. Sorry for the trouble. I have
now limited the bandwidth to 2 mbit down, and a tiny bit up, so you
can uncap the connection at the router/firewall (it seems to be capped
at 400 kbit/sec right now).
--
Marc Juul
16 Feb
16 Feb
2:54 p.m.
I didn't cap it. Might have been the ISP.
On Friday, February 15, 2013, Marc Juul wrote:
On Fri, Feb 15, 2013 at 9:46 AM, Matthew Meier
<wolfy@wlfy.it<javascript:;>>
wrote:
Looks like space (192.168.0.3) is consuming 100%
of our bandwidth. anyone
know what's up with that? if it's bit torrent can we cap it around 3
Mbit
to allow some wiggle room for user's
connections?
Yeah that was me. I limited the bandwidth thinking the unit was
kilobits and it was actually kilobytes. Sorry for the trouble. I have
now limited the bandwidth to 2 mbit down, and a tiny bit up, so you
can uncap the connection at the router/firewall (it seems to be capped
at 400 kbit/sec right now).
--
Marc Juul
4109
days inactive
4110
days old
2 comments
2 participants
participants (2)
-
Marc Juul -
Matthew Meier