| Anonymous | Login | 2024-04-19 23:04 MDT |
| 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 | ||||
| 0018531 | ClearOS | app-network - Network Settings | public | 2018-01-09 13:45 | 2018-10-24 18:02 | ||||
| Reporter | NickH | ||||||||
| Assigned To | user2 | ||||||||
| Priority | normal | Severity | minor | Reproducibility | have not tried | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 7.4.0 | ||||||||
| Target Version | Fixed in Version | 7.5.0 Updates | |||||||
| Summary | 0018531: Webconfig objects to PPPoE with 255.255.255.255 netmask in standalone mode | ||||||||
| Description | When ClearOS is in standalone mode with an external PPPoE interface, if its netmask is 255.255.255.255, the Webconfig Web Server app or Flexshare app gives an "Ooooops!Net mask is invalid.". If put into gateway mode the error disappears. It appears this bug was introduced in 7.4. I do not have PPPoE so I can't check it out, but please see the following forum thread: https://www.clearos.com/clearfoundation/social/community/system-update-to-7-4-show-ooooops-net-mask-is-invailid. [^] | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
||||||
|
||||||
 Relationships |
|
Notes |
|
|
(0006891) user2 2018-01-09 14:15 |
I'm not convinced this is a bug. I was hoping to get the ifconfig output to verify that the interface was indeed a PPPoE/PPP interface and not a regular (e.g. eth0) interface. I have a feeling it's the latter. |
|
(0006901) NickH (developer) 2018-01-10 01:04 |
Feedback posted to the forum: https://www.clearos.com/clearfoundation/social/community/system-update-to-7-4-show-ooooops-net-mask-is-invailid#reply-203141 [^] |
|
(0006911) user2 2018-01-10 02:14 |
Confirmed - thanks! Added to the bug queue. |
|
(0008001) user2 2018-09-24 20:11 |
Since the API is allowing 255.255.255.255 netmasks, it's now up to external apps to handle this scenario. For example, when Flexshare enumerates all the LANs on the network for "LAN Access", the underlying engine (Apache) won't like seeing 255.255.255.255 for non point-to-point interfaces. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2018-01-09 13:45 | NickH | New Issue | |
| 2018-01-09 14:15 | user2 | Note Added: 0006891 | |
| 2018-01-09 14:15 | user2 | Status | new => feedback |
| 2018-01-10 01:04 | NickH | Note Added: 0006901 | |
| 2018-01-10 01:04 | NickH | Status | feedback => new |
| 2018-01-10 02:14 | user2 | Note Added: 0006911 | |
| 2018-01-10 02:14 | user2 | Status | new => confirmed |
| 2018-01-10 02:14 | user2 | Target Version | => 7.4.0 Updates |
| 2018-02-12 10:19 | user2 | Target Version | 7.4.0 Updates => |
| 2018-09-24 19:44 | user2 | Issue cloned: 0021571 | |
| 2018-09-24 19:44 | user2 | Relationship added | related to 0021571 |
| 2018-09-24 20:11 | user2 | Note Added: 0008001 | |
| 2018-09-24 20:11 | user2 | Status | confirmed => resolved |
| 2018-09-24 20:11 | user2 | Fixed in Version | => 7.5.0 Updates |
| 2018-09-24 20:11 | user2 | Resolution | open => fixed |
| 2018-09-24 20:11 | user2 | Assigned To | => user2 |
| 2018-10-24 18:02 | user2 | Status | resolved => closed |
|
Issue History |