ClearFoundation Tracker - ClearOS |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0020331 | ClearOS | app-dmz - Routed DMZ Firewall | public | 2018-06-11 03:09 | 2019-02-23 17:05 |
|
| Reporter | NickH | |
| Assigned To | dloper | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | suspended | |
| Platform | | OS | | OS Version | |
| Product Version | 7.4.0 | |
| Target Version | 7.6.0 Updates | Fixed in Version | | |
|
| Summary | 0020331: Cannot specify subnet in DMZ Incoming Connection |
| Description | It is impossible to specify a subnet in the DMZ Incoming Connection > IP Address field. The documentation indicates this should be possible and it makes logical sense to be able to, so I don't think it is a documentation error. I have tried both CIDR notation and 1.2.3.0/255.255.255.0 notation and the Webconfig gives an "IP address is invalid." message.
Note that if a subnet is permissible, the "IP Address" text should also be changes to read something like "IP Address/Subnet"
This bug also exists in 7.5 Beta |
| Steps To Reproduce | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2018-06-11 03:09 | NickH | New Issue | |
| 2018-06-11 07:09 | user2 | Status | new => confirmed |
| 2018-06-11 07:09 | user2 | Target Version | => 7.5.0 Updates |
| 2018-10-30 18:11 | user2 | Target Version | 7.5.0 Updates => 7.6.0 Updates |
| 2019-02-23 17:05 | dloper | Note Added: 0009681 | |
| 2019-02-23 17:05 | dloper | Status | confirmed => closed |
| 2019-02-23 17:05 | dloper | Assigned To | => dloper |
| 2019-02-23 17:05 | dloper | Resolution | open => suspended |