ClearOS Bug Tracker


View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001875ClearOSapp-network - Network Settingspublic2014-07-30 03:392018-09-24 19:56
Reportersipherdee 
Assigned Touser2 
PriorityimmediateSeverityfeatureReproducibilityN/A
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version6.5.0 
Target VersionFixed in Version7.5.0 Updates 
Summary0001875: Netmask is invalid when adding a /32 subnet
DescriptionAs it has been reported on the forums (please see the link in 'Additional Information'), the GUI at reboot is giving a "Ooooops: Netmask is invalid." error message when adding a '255.255.255.255' netmask.
Steps To ReproduceTry to configure a virtual server in bridge mode at OVH using their guide.
Additional Informationhttp://www.clearfoundation.com/component/option,com_kunena/Itemid,232/catid,28/func,view/id,57753/ [^]

This is required by some ISPs like OVH for bridge mode and the requested configuration seems impossible to do with ClearOS. Please see their guide for more details:

http://help.ovh.co.uk/BridgeClient#link4 [^]

OVH has started to migrate servers to a new infrastructure which requires this setup for virtual servers. To my knowledge, they started the maintenance yesterday. This makes ClearOS servers unavailable after they have been moved. More cases are sure to follow.
TagsNo tags attached.
Attached Filespng file icon ClearOS+Ooooops__Netmask_is_invalid.png [^] (5,798 bytes) 2014-07-30 11:31

- Relationships

-  Notes
(0001254)
user2
2014-07-30 08:37

Wah? That's so dirty. A 255.255.255.255 netmask is only valid on point-to-point interfaces. With all the bits set on the subnet mask, the box can only talk to itself! That's why point-to-point connections have the other side of the point defined inside it's network interface definition.

I know the smart guys over at OVH know this, but they did it anyway. I'll look for a workaround.
(0001255)
user2
2014-07-30 08:38

Changing the severity to "feature request" since it should not be categorized as a bug. It's still an "immediate" priority though!
(0001256)
sipherdee (reporter)
2014-07-30 11:51
edited on: 2014-07-30 11:53

The server is accessible again if the the "GATEWAYDEV" parameter in '/etc/sysconfig/network' is commented out. This is the only thing that needs to be done after having followed the BridgeClient OVH guide.

Thanks to Peter that came up with that solution.

The graphical console still display a "Ooooops: Netmask is invalid." with a grey background (see the attached file) but the server is working properly. In one of your next releases, maybe that something could be done to reenable the usual GUI display at the console. I will be able to do the testing when this will be needed. Thanks again!

(0007991)
user2
2018-09-24 19:56

ClearOS 7 only.

- Issue History
Date Modified Username Field Change
2014-07-30 03:39 sipherdee New Issue
2014-07-30 08:37 user2 Note Added: 0001254
2014-07-30 08:38 user2 Note Added: 0001255
2014-07-30 08:38 user2 Severity block => feature
2014-07-30 08:38 user2 Status new => acknowledged
2014-07-30 11:31 sipherdee File Added: ClearOS+Ooooops__Netmask_is_invalid.png
2014-07-30 11:51 sipherdee Note Added: 0001256
2014-07-30 11:53 sipherdee Note Edited: 0001256 View Revisions
2018-09-24 19:55 user2 Status acknowledged => resolved
2018-09-24 19:55 user2 Fixed in Version => 7.5.0 Updates
2018-09-24 19:55 user2 Resolution open => fixed
2018-09-24 19:55 user2 Assigned To => user2
2018-09-24 19:56 user2 Note Added: 0007991
2018-09-24 19:56 user2 Status resolved => closed