aMule Bug Tracker - aMule |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000954 | aMule | Servers | public | 2006-08-29 01:17 | 2006-09-09 17:06 |
|
| Reporter | gjc | |
| Assigned To | GonoszTopi | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | 2.1.3 | |
| Target Version | | Fixed in Version | | |
| Fixed in Revision | |
| Operating System | Any |
|
| Summary | 0000954: amule now filters servers, not only connections |
| Description | Previously aMule used the filtering table (ipfilter.dat) only to filter client connections. You could thus setup a filter to block only clients, but still connect to servers within the blocked range. Now aMule no longer allows that, and for me that is a regression.
|
| Steps To Reproduce | |
| Additional Information | Please note that in certain backwards countries (such as Portugal) we have severe traffic limits for "international traffic" (i.e. going to outside the country). In these cases, people use the filtering functionality not for security reasons but merely to restrict data transfer to clients within the same geographical region. But we don't have any emule server in Portugal, and usually connect to international ones, since the amount of traffic between client and server is very small. |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2006-08-29 01:17 | gjc | New Issue | |
| 2006-08-29 01:17 | gjc | Operating System | => Any |
| 2006-09-08 10:11 | GonoszTopi | Status | new => assigned |
| 2006-09-08 10:11 | GonoszTopi | Assigned To | => GonoszTopi |
| 2006-09-09 17:06 | GonoszTopi | Status | assigned => resolved |
| 2006-09-09 17:06 | GonoszTopi | Resolution | open => fixed |
| 2006-09-09 17:06 | GonoszTopi | Note Added: 0002101 | |