| Anonymous | Login | 2024-12-22 00:32 MST |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0001175 | ClearOS | app-firewall - Firewall | public | 2013-06-07 12:43 | 2019-04-24 08:28 | ||||
| Reporter | user2 | ||||||||
| Assigned To | |||||||||
| Priority | normal | Severity | tweak | Reproducibility | N/A | ||||
| Status | closed | Resolution | won't fix | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0001175: Add support for hostnames in bandwidth engine | ||||||||
| Description | In some circumstances, using hostnames is useful with advanced bandwidth rules. However, the "tc filter" command only accepts IP addresses. If an advanced bandwidth rule uses a hostname, the underlying tc command ends up looking something like: /sbin/tc filter add dev imq0 protocol ip parent 1: pref 1 u32 match ip src EXAMPLE.COM flowid 1:10 ... which bombs out. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2013-06-07 12:43 | user2 | New Issue | |
| 2013-06-07 12:43 | user2 | Status | new => assigned |
| 2013-06-07 12:43 | user2 | Assigned To | => dsokoloski |
| 2013-06-12 11:31 | user2 | Target Version | 6.4.0 Updates => |
| 2019-04-24 08:28 | NickH | Note Added: 0011621 | |
| 2019-04-24 08:28 | NickH | Status | assigned => closed |
| 2019-04-24 08:28 | NickH | Assigned To | dsokoloski => |
| 2019-04-24 08:28 | NickH | Resolution | open => won't fix |
|
Issue History |