<HTML>
<HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="OPENWEBMAIL" name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
I'm not sure who to address this to - as it seems to be a long-term routing issue I've fought in BlueQuartz and now in BlueOnyx.
<br />
<br />One of my customer owns and uses many networks for their customers and hosting. In the hosting, they use one network's IPs for the server's main IP, and other networks for the user sites. The problem is - when a site is added, the BlueOnyx scripts create the new virtual site's IP with the network mask on the main server's IP. So instead of every site having a default 255.255.255.255 netmask, it picks up the 255.255.255.240 off the main IP and assigns that to every site's IP.
<br />
<br />This may not sound like much, but it causes routing problems and prevents us from using certain IPs in the second network (the server thinks some IPs are broadcast IPs and won't route to them when assigned to a site). I've had to go through a entire server's ifcfg-eth0:xx configurations, changing all virtual site's IPs to 255.255.255.255 netmask.
<br />
<br />And now, I'm fighting another bug. One server has a LOT of IPs in one network on it - and so it appears to assume it owns the whole /24 network. Each time a site is added/deleted/suspended/unsuspended or the server is rebooted - it adds this route to the server's routing table:
<br />
<br />216.xx.xxx.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
<br />
<br />And since the server now thinks it owns the entire 216.xx.xxx.0 network - it won't send back packets to other devices or servers with IPs in that same network.
<br />
<br />I can manually delete that route from the table with the command "route del -net 216.xx.xxx.0/24", which fixes all routing problems. But I'm having to do it every time a change is made to that server, or its rebooted.
<br />
<br />Does anyone know why virtual sites are not automatically created with a netmask of 255.255.255.255? And can we modify the site creation/modification scripts so sites are automatically created with the default netmask 255.255.255.255? I can't imagine why any virtual site would need a netmask other than 255.255.255.255 - but I guess we could add a netmask field to the "Add New Virtual Site" page, so a specific netmask can be defined.
<br />
<br />
<br />
<br />Chuck
<br />
<br />
</BODY>
</HTML>