[BlueOnyx:14030] Re: Problem setting interface alias net mask to 255.255.255.255

[wcstaff at webcoast.com]

> -----Original Message-----
> From: blueonyx-bounces at mail.blueonyx.it [mailto:blueonyx-bounces at mail.blueonyx.it] On
> Behalf Of Menno Jansz
> Sent: Wednesday, November 13, 2013 1:49 PM
> To: BlueOnyx General Mailing List
> Subject: [BlueOnyx:14029] Re: Problem setting interface alias netmask to 255.255.255.255
> 
> 
> On Wed, 13 Nov 2013 12:37:17 -0600, "Chuck Tetlow" <chuck at tetlow.net>
> wrote:
> > Chris,
> >
> > I suspect his server is set up the same way as a number of servers I
> > manage.
> >
> > There is a route-able IP on the main server interface, and all the
> > virtuals are on IPs in a different network.  So the 255.255.255.255
> netmask
> > is valid for the virtuals.  The server knows to send all traffic to its
> > default gateway router.  And the router has to be told to send traffic
> > destined for the virtual IPs to the main server IP.
> >
> > This is what happens when you have the main IP for the server in a
> > different network as the virtual site IPs.
> 
> Yes, when I queried why it is like this they said the netmask setup is
> just because of the number of servers they have and the fact the IPs are
> from different network ranges.
> 
> Menno
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at mail.blueonyx.it
> http://mail.blueonyx.it/mailman/listinfo/blueonyx

Sounds to me like your WSP doesn't have enough valid IP addresses. So they are creating their own in house subnets and creating their own network, similar to a 192.168.0.0 internal network.
This may be out of line, but I suggest moving to a service provider that can offer REAL static IP addresses.
I can imagine the traffic lag at times.