Red Hat Bugzilla – Bug 154102
piranha gui does not save netmask
Last modified: 2009-04-16 16:23:19 EDT
Description of problem:
The GUI does not save the value of the NAT nmask. There is no way to change the
mask other than manually editing the lvs.cf file and inserting a nat_nmask value.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. select a NAT configuration
2. modify netmask.
3. reload interface.
no value stored in config file
value gets stored.
I would argue that if the lvs ip is within the same subnet as that of any
existing ip/alias on the chosen interface then it should use the same netmask.
The effects of allowing multiple overlapping subnets on a single interface (or
at all) can be extreme. In the cases I have seen the result was an overlapping
set of netmasks for the same region (10/8 & 10.0.0/24) which meant VPN clients
didn't work, various other subnets couldn't see the lvs ip, the ARP table
filled, iptables masquerading interface enforcement failed, and general service
Obviously fixing the GUI is a first step, but some thought on the above (or
incorporation of a really big warning) would also be nice.
This works in my setup. Maybe I've got the wrong version?
Actually, nat_nmask seems to be preserved even if I change router types...
For what its worth, I'm having the same problem on piranha-0.7.10-2.
Martin, Mark - I reproduced it on 0.7.10 on RHCS3/RHEL3, but RHCS4 is 0.8.x,
which is what this bug is filed against.
Was it mistakenly filed against RHCS4 when it should have been against RHCS3?
/me is confused... I think it should be version 3, not 4; it works for me on 4.
I think you'll find BZ has wobbled. I filed this back in April against RHCS3.
I'm glad to hear you've reproduced the problem. I was dealing with a customer
issue where they had both /22 & /28 mask subnets in evidence.
Changing to RHCS 3, then.
*** Bug 198479 has been marked as a duplicate of this bug. ***
Reassigning to component owner