Bug 11187

Summary: Tor Reply limit
Product: IPFire Reporter: Jarred Casselton <help>
Component: ---Assignee: Jan Paul Tuecking <earl>
Status: CLOSED DUPLICATE QA Contact:
Severity: Balancing    
Priority: Will only affect a few users CC: itsuperhack, michael.tremer, peter.mueller
Version: 2Keywords: GoodFirstBug
Hardware: all   
OS: All   
See Also: https://bugzilla.ipfire.org/show_bug.cgi?id=11783

Description Jarred Casselton 2016-09-19 13:54:20 UTC
PFire version:	IPFire 2.19 (i586) - core104
Pakfire version:	2.19.1
Kernel version:	Linux cache 3.14.79-ipfire-pae #1 SMP Tue Sep 13 23:26:41 GMT 2016 i686 GNU/Linux

Tor Add-on package

-Enable Tor Relay
   -Tor Relay Configuration
      -Bandwidth Settings
if you set a burst &/or max below 1Mbit/s (any kbit/s) - Tor service fails to start.

Jarred
Comment 2 Timmothy Wilson 2016-09-21 14:20:15 UTC
(In reply to Jarred Casselton from comment #0)
> PFire version:	IPFire 2.19 (i586) - core104
> Pakfire version:	2.19.1
> Kernel version:	Linux cache 3.14.79-ipfire-pae #1 SMP Tue Sep 13 23:26:41
> GMT 2016 i686 GNU/Linux
> 
> Tor Add-on package
> 
> -Enable Tor Relay
>    -Tor Relay Configuration
>       -Bandwidth Settings
> if you set a burst &/or max below 1Mbit/s (any kbit/s) - Tor service fails
> to start.
> 
> Jarred
Yes, they have changed the minimum bandwith settings recently.
Sorry - my fault. Didn't test that (used ~ 5 MBit/s).

IMO, it's just a simple patch to remove all kbit/s* entries from the menue.
Comment 3 Jarred Casselton 2016-09-21 22:19:39 UTC
no worries, no apologies needed. Just trying to help you guys find these little bugs.
Great product, keep up the awesome work
Jarred
Comment 4 Peter Müller 2018-02-06 20:56:36 UTC
I think we just need to drop all bandwith options below that limit, right?
Comment 5 Peter Müller 2019-03-08 19:24:41 UTC

*** This bug has been marked as a duplicate of bug 12001 ***